[issue5525] Problem with email.MIME* library, using wrong new line

R. David Murray added the comment: Effectively this is a duplicate of issue 1349106, since you are right that it affects more than just boundary production. I believe we are going to address this in a new version of the email module. -- nosy: +r.david.murray priority: -> normal resol

[issue5525] Problem with email.MIME* library, using wrong new line

Luca clementi added the comment: I forgot to say that the \n should be substitute with \r\n CRLF Luca -- ___ Python tracker ___ ___

[issue5525] Problem with email.MIME* library, using wrong new line

New submission from Luca clementi : I'm running Python 2.5.2 under Ubuntu 8.10. In the file email/generator.py from the core library at line 228 in the function _handle_multipart() # delimiter transport-padding CRLF print >> self._fp, '\n--' + boundary but if this functio