PortableUnixMailbox versus UnixMailbox as superclass for Mailman's Mailbox class
![](https://secure.gravatar.com/avatar/632bc87a86b0db6153c56defac0ba682.jpg?s=120&d=mm&r=g)
Hello experts
In MM 2.1.3, the Mailbox class defined in Mailman.Mailbox uses the standard Python class mailbox.PortableUnixMailbox as its superclass.
This has caused me some grief with an unescaped 'From ...' line following a blank line in an mbox archive. The use of PortableUnixMailbox leads to a false splitting of this message when the mbox is being read by the next() function, with consequent failure in processing of the second, false, message.
Having the mailbox.UnixMailbox class as the superclass of the Mailman Mailbox class prevents this problem.
Can anyone tell me why MM's 2.1.3 code currently uses PortableUnixMailbox instead of UnixMailbox and what the downside is of my continuing to run my system with the modification to use UnixMailbox.
Thanks in advance
Richard
Richard Barrett http://www.openinfo.co.uk
participants (1)
-
Richard Barrett