[issue11728] mbox parser incorrect behaviour

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.8, Python 3.9 -Python 2.7, Python 3.2, Python 3.3, Python 3.4 ___ Python tracker ___

[issue11728] mbox parser incorrect behaviour

Petri Lehtinen pe...@digip.org added the comment: Some thoughts on doing clever tricks to enhance mbox parsing: http://www.jwz.org/doc/content-length.html -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11728

[issue11728] mbox parser incorrect behaviour

Petri Lehtinen pe...@digip.org added the comment: Actually, you're right. Sorry for overlooking the RFC. But that said, the RFC itself refers to the same manpage as a reference that's mostly authoritative for those variations that are otherwise only documented in anecdotal form. So I guess

[issue11728] mbox parser incorrect behaviour

Petri Lehtinen pe...@digip.org added the comment: It seems to me that ^From is the correct way to match the start of each message. This is also what the qmail manual page (linked in the previous message) says. So closing as invalid. -- nosy: +petri.lehtinen resolution: - invalid

[issue11728] mbox parser incorrect behaviour

valera vmasu...@apache.org added the comment: Hello Petri Qmail manpage does not sound as a valid reference for me, I've pointed relevant RFC (which dictates correct behaviour) as a reference, python mbox parser does not conform to it. Best regards, Valery Masiutsin On Sun, Jun 24, 2012 at

[issue11728] mbox parser incorrect behaviour

Steffen Daode Nurpmeso sdao...@googlemail.com added the comment: Hello Valery Masiutsin, i recently stumbled over this while searching for the link to the standart i've stored in another issue. (Without being logged in, say.) The de-facto standart (http://qmail.org/man/man5/mbox.html) says: HOW

[issue11728] mbox parser incorrect behaviour

Changes by Terry J. Reedy tjre...@udel.edu: -- stage: - test needed type: - behavior versions: -Python 2.5, Python 2.6, Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11728 ___

[issue11728] mbox parser incorrect behaviour

New submission from valera vmasu...@apache.org: mailbox.mbox parser is splitting mbox files by ^From pattern, which is wrong , in fairy it should split mbox by \nFrom . Illustration: -- From bla-blah@localhost Header1 Header2 body1 body2 From blah-blah2@localhost Header1 body1 From your

[issue11728] mbox parser incorrect behaviour

R. David Murray rdmur...@bitdance.com added the comment: All the references I could find talk about triggering the match without the proceeding newline. That is, it is not certain that a blank line will precede the 'From ' header, and the typical quoting rules for mbox format call for any

[issue11728] mbox parser incorrect behaviour

valera vmasu...@apache.org added the comment: On Thu, 31 Mar 2011 14:13:50 + R. David Murray rep...@bugs.python.org wrote: R. David Murray rdmur...@bitdance.com added the comment: All the references I could find talk about triggering the match without the proceeding newline. That