Changes by xavierd xdelan...@cloudmark.com:
Added file: http://bugs.python.org/file22919/orig.eml
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12515
xavierd xdelan...@cloudmark.com added the comment:
This patch does:
- when a close boundary isn't found then the error
'email.errors.CloseBoundaryNotFoundDefect' is added to the defects list.
- it doesn't modify the current behaviour of the feedparser
(eg: the function
Changes by xavierd xdelan...@cloudmark.com:
Added file: http://bugs.python.org/file22888/orig.eml
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12515
xavierd xdelan...@cloudmark.com added the comment:
with the patch applied:
{{{
$ ./test.py
PARSER INVALID EMAIL
defects found !
[email.errors.CloseBoundaryNotFoundDefect instance at 0x7f41421c0488]
}}}
--
Added file: http://bugs.python.org/file22889/test.py
New submission from xavierd xdelan...@cloudmark.com:
the function 'email.message_from_file' modifies the message structure when the
parsed is invalid (for example, when a closed boudary is missing). The
attribute defects is also empty
In the attachment (sample.tgz) you will find
