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

Relax MIME-Version header checking #112

Merged
merged 1 commit into from Apr 6, 2017

Conversation

acammack-r7
Copy link
Contributor

Some email senders, notably Yahoo and Amazon SES, send email with a
non-compliant MIME-Version header like:

MIME-Version: 1.0
    boundary="----=_Part_505990_122814590.1475767204022"

This extra data does not seem important, and discarding it does not
hamper parsing the email.

I have reached out to a few vendors to see what purpose the extra data holds and why it was stuck on the MIME-Version header, but I have yet to receive a response.

Some email senders, notably Yahoo and Amazon SES, send email with a
non-compliant MIME-Version header like:

MIME-Version: 1.0
	boundary="----=_Part_505990_122814590.1475767204022"

This extra data does not seem important, and discarding it does not
hamper parsing the email.
@Vagabond
Copy link
Collaborator

Vagabond commented Oct 7, 2016

Ugh. I guess we can do this, anyone else have any thoughts?

@acammack-r7
Copy link
Contributor Author

Any update on this @Vagabond? I have some coming additions that fall firmly under #10, so I can start by option-guarding this, if you prefer.

@mworrell
Copy link
Collaborator

mworrell commented Apr 6, 2017

It is ugly, but then that Email sender is ugly ... guess we need to leak their ugliness into our own code...

@acammack-r7 thanks!

@mworrell mworrell merged commit a97dfa3 into gen-smtp:master Apr 6, 2017
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

Successfully merging this pull request may close these issues.

None yet

3 participants