Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ripemime #8

Open
tszarans opened this issue May 11, 2018 · 0 comments
Open

ripemime #8

tszarans opened this issue May 11, 2018 · 0 comments

Comments

@tszarans
Copy link

tszarans commented May 11, 2018

First off -- great software!

Would it be possible to provide an option to name attachments by their content id in place of, --name-by-type?
We have a process where we are using ripmime to take an maildir email and replace the embedded CID images with URL, so the email when loaded from the database does not have any of the document, or inline images as part of the data. This has been working quite well, until we run into email messages which do not name the content, which makes it difficult to link the decoded image/attachment back to the Content-ID in the header.

Right now when I use --name-by-type option, I get a sample content header block:

--=_related 00633EA78625828A_=
Content-Type: image/gif
Content-ID: <_1_0C814D9C0C81499C00633EA78625828A>
Content-Transfer-Encoding: base64

With actual filename that is extracted as: image-gif3

If the Content-ID has a name such as:

Content-Type: image/gif; name="image001.gif"
Content-ID: <_1_0C814D9C0C81499C00633EA78625828A>
Content-Transfer-Encoding: base64

It will be named image001.gif and we can find it, however if option --name-by-contentid was used, it would write out _1_0C814D9C0C81499C00633EA78625828A in place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant