You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
imaplib should convert line endings to be rfc2822 complient #38332
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2003-04-30.00:02:30.000>created_at=<Date2003-04-19.00:16:16.000>labels= ['library']
title='imaplib should convert line endings to be rfc2822 complient'updated_at=<Date2003-04-30.00:02:30.000>user='https://bugs.python.org/anadelonbrin'
When imaplib.append is called, it should convert line
endings from whatever they are (\r, \n or \r\n) to the
format required by rfc2822 (in turn, required by rfc1730),
i.e. CRLF - \r\n.
The email package generates mail with Python "internal"
line endings (i.e. \n), and so if a message is flattened
and then appended via imap improper line endings are
sent.
While some imap servers are ok with this, at least one
(Communigate Pro) mangles the message (all the
headers become part of the body).
This is a bug. Can't think how it's managed to survive for
so long (there must be a lot of forgiving imap servers out
there). Anyway,
I've just checked in a fix (based on the smtplib code -
thanks for
the ref.)
And thanks for the bug report.
anadelonbrin commented on Apr 29, 2003
anadelonbrinmannequin
MannequinAuthor
More actions
Logged In: YES
user_id=552329
By the way, since posting this there was some discussion
about the re used in smtplib. Tim Peters, Tim Stone and
Skip Montareo eventually agreed (more or less) that
CRLF_RE = re.compile(r'\r\n|\r|\n')
was better than the one in smtplib. (I really ought to suggest
that to whoever maintains smtplib as well...)
But anyway, thanks for fixing it. I must say that the imap
servers I have access to are forgiving enough - but it only
takes one...
pierslauder commented on Apr 30, 2003
pierslaudermannequin
Mannequin
More actions
Logged In: YES
user_id=196212
Couldn't agree more :-) Now uses the much simpler regex.
I'm also going to mark this bug as 'fixed"
Activity
anadelonbrin commentedon Apr 19, 2003
When imaplib.append is called, it should convert line
endings from whatever they are (\r, \n or \r\n) to the
format required by rfc2822 (in turn, required by rfc1730),
i.e. CRLF - \r\n.
The email package generates mail with Python "internal"
line endings (i.e. \n), and so if a message is flattened
and then appended via imap improper line endings are
sent.
While some imap servers are ok with this, at least one
(Communigate Pro) mangles the message (all the
headers become part of the body).
smtplib has an example of how to do this.
anthonybaxter commentedon Apr 19, 2003
Logged In: YES
user_id=29957
You may want to contact imaplib's author, (Piers Lauder
<[email protected]>)
directly about this.
mwhudson commentedon Apr 19, 2003
Logged In: YES
user_id=6656
Or just assign it to him :-)
pierslauder commentedon Apr 29, 2003
Logged In: YES
user_id=196212
This is a bug. Can't think how it's managed to survive for
so long (there must be a lot of forgiving imap servers out
there). Anyway,
I've just checked in a fix (based on the smtplib code -
thanks for
the ref.)
And thanks for the bug report.
anadelonbrin commentedon Apr 29, 2003
Logged In: YES
user_id=552329
By the way, since posting this there was some discussion
about the re used in smtplib. Tim Peters, Tim Stone and
Skip Montareo eventually agreed (more or less) that
CRLF_RE = re.compile(r'\r\n|\r|\n')
was better than the one in smtplib. (I really ought to suggest
that to whoever maintains smtplib as well...)
But anyway, thanks for fixing it. I must say that the imap
servers I have access to are forgiving enough - but it only
takes one...
pierslauder commentedon Apr 30, 2003
Logged In: YES
user_id=196212
Couldn't agree more :-) Now uses the much simpler regex.
I'm also going to mark this bug as 'fixed"