The bad news is that we might have to deviate from the stdlib if it is indeed a bug with their implementation (or if it isn't a bug and we just want to go in a more flexible direction). It looks like there just isn't a blank line between the headers and the body. Not sure if we could smash the utf-8 back one line or simply ignore it.
Or, the girl you’ve been enjoying romantic dates with turns out to be married.
Vikas Salar has invited you to Desktopdating Hi, I have just joined the Desktopdating network. See you at Desktopdating Vikas Salar To accept the invitation copy the link given below and paste it in the address bar of your browser
I'm not opposed to do go on a different route where instead of trying to parse malformed emails, we could try to write a different library that reads an malformed email, fixes it (pre-defined rules I guess) and then writes it out renewed. I could see this being a bit more flexible in the long term.
For now, let me go read through all the RFC's to see authoritatively what they say about this kind of stuff.
At the very least, I'll mention it to the Golang devs if they are, in fact, somehow not enforcing the same flexibility requested by the RFC.