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

2009-03-21 Thread Luca clementi

Luca clementi luca.cleme...@gmail.com added the comment:

I forgot to say that the 
\n
should be substitute with 
\r\n
CRLF

Luca

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5525
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



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

2009-03-19 Thread Luca clementi

New submission from Luca clementi luca.cleme...@gmail.com:

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 function is run under Unix it print only the LF and not the
CRLF as by required by the standard. 

My guess is that this error is also in other part of the library.
SMTP (as HTTP) requires CRLF as new line, by standard, while I see that
at the beginning of the generator.py
NL = '\n'

Am I missing something?

Luca

--
components: Library (Lib)
messages: 83851
nosy: lclement
severity: normal
status: open
title: Problem with email.MIME* library, using wrong new line
type: behavior
versions: Python 2.5

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5525
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com