Re: [fetchmail-devel] Re: [fetchmail-users] Incorrect header line and lost mails

[Matthias A. <mat...@gm...>]

Frederic Marchal <fre...@wo...> writes:

> I expect this mail will be wrapped so here is the explanation. The
> References header is one long line and is wrapped at some point after
> the <43ea8d070602140508w6af9d34aq5c which leaves the
> 222...@ma...> all by itself on a line. You have
> received that e-mail and can compare it to your copy
>
> On my side, the References line is truncated at column 263. rfc821
> specifies a maximum line length of 1000 characters but an implementation
> should be prepared for longer lines or reject the mail. It is not what
> is happening here.
>
> The culprit may be Mercury/32 or the Wingate proxy which is not listed
> in the header.

Is there any chance we might isolate the bug before we fix it? 

Even if that isn't of immediate help for you, documenting this properly
might help other people solve their problem, and we may be able to write
a workaround in the least intrusive way.

> Anyway, I can't change any of them and nothing prevent the mail from
> being delivered. Moreover I can read it in thunderbird without any
> warning or inconvenience.

I think given the vast number of varieties how messages can be broken,
and one workaround might break another, the best bet is probably to wrap
the message up as a MIME message/rfc822 attachment that contains a short
introductory text that tells the end user the message contained broken
headers.

-- 
Matthias Andree