Hi, * Derrick 'dman' Hudson [02-07-13 00:12:42 +0200] wrote: > On Thu, Jul 11, 2002 at 10:29:47PM +0200, Rocco Rutte wrote: > | * Thorsten Haude [02-07-11 22:10:53 +0200] wrote:
> | > Could you tell more about this? How did you identify the > | > broken MTA and what did you do to fix it? > | Someone else found out that GMX escapes 'from' at the > | beginning of a line to '>from' which was the reason why I > | could not verify a few mails. It's a short sed/python/perl > | solution to remove it again. As I said, a few still remain. > Actually, that MDA MUST do that mangling, or else your > mbox will be corrupted. No, the parser is just broken. No matter why a piece of software changes message bodies, changing bodies is always a bad idea since it breaks more things than it attempts to repair. > That's the problem with mbox. I don't think GMX uses mbox internally. But even if they did, there're other possibilities than to change bodies. The 'Content-Length' header is just one. Not to store mails in mbox another. The most simple solution is, IMHO, just to set a Content- Length header and further parse a From_ line in the message body. > As a workaround, the PGP/MIME RFCs recommend that the > sending MUA use quoted-printable, and escape all From_ > lines before transmitting the message. Well, such issues require software authors to have lots of knowledge of what exactly they're dealing with. There're MUA which even can't handle threading or header encoding. Not talking about escaping From_ lines in bodies. Mutt not only is great from an ordinary user's point of view because of its configurability. It also does correct header encoding, threading and MIME handling. Including such cool features like escaping From_ lines and leading dots. bye, Rocco
