Message88593
I was using email.message_from_string which eventually feeds block of
8192 bytes into the actual e-mail parsing code. However, in my case one
the blocks split the \r\n at the end of a submessage. This caused the
code to identify it as two newlines and thus the submessage headers were
interpreted as being content.
For my purposes I've changed:
NLCRE_crack = re.compile('(\r\n|\r|\n)')
to
NLCRE_crack = re.compile('(\r\n)')
Which prevents the problem.
I suspect that is not a good fix but I do not know the standard well
enough to know what would be a good fix. |
|
Date |
User |
Action |
Args |
2009-05-31 05:14:47 | WinstonEwert | set | recipients:
+ WinstonEwert |
2009-05-31 05:14:45 | WinstonEwert | set | messageid: <1243746885.91.0.189696323445.issue6153@psf.upfronthosting.co.za> |
2009-05-31 05:14:41 | WinstonEwert | link | issue6153 messages |
2009-05-31 05:14:31 | WinstonEwert | create | |
|