From: Rob M. <rob...@gm...> - 2006-02-14 14:08:57
|
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. -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche |