From: Frederic M. <fre...@wo...> - 2006-02-14 14:47:21
|
Rob MacGregor wrote: > On 2/14/06, Matthias Andree <mat...@gm...> wrote: > >> The bigger concern is that fetchmail shouldn't be emitting headers it >> knows are broken, so that the next hop (the MTA or MDA) does not get >> confused. I wonder if fetchmail should prefix the broken lines with >> X-Fetchmail-Escaped-Broken-Header: or something similar. >> > > My 0.02$CURRENCY - when fetchmail finds a mail such as this it should > create a new mail, addressed to the postmaster address, with the > illegal email as a text/plain attachment. > > If you're feeling kind, insert a blank line before the offending > illegal header and include that altered version as a message/rfc822 > attachment (but still have the text/plain attachment) > > There's no point in passing on the known broken email as is, and > simply "fixing" it may result in more problems. At least if the > postmaster gets it as an attachment then they can decide how to handle > it. > > Personally, I'm curious to know what mail client is producing such > borken emails, and what MTAs are passing them on. > > This thread started in fetchmail-user. My problem is that at least one good e-mail (I mean one I would have want to receive) had an invalid header line and was deleted by fetchmail. The mail was sent by hotmail with a very long TO header (it is not rfc822 compliant) and further wrapped at some point. As a result, the header contained one line without colon and not starting with a blank character. The whole mail was simply deleted by fetchmail although it could have been delivered. I believe it is not fetchmail's job to enforce rfc822 that way. It should be left to a program dedicated to that task or, at least, it should not be the default option. It would be a good idea to tag the mail with a specific header though. It would make it easier to filter out with a program such as procmail. I wouldn't divert the mail to the postmaster either. It is likely that a busy postmaster will throw it away without looking at it if he is not the obvious recipient. The drawback is that if the mail is really junk, it will be downloaded and processed until it encounters the spam filter. It is a problem for a dialup link or even a DSL line with a low download limit. That's a reason to keep it an option the user can set. Frederic |