Thomas M?rbauer via Postfix-users:
> >That's rather different than what you appeared to say. Here there's
> >folding whitespace *before* (not in the middle of) the Message-ID.
> Sorry, could have been more clear about that. The folding can only
> occur after the header label according to the non obsolete RFCs.
>
> >There are no clear cut rules on what to do with folding in the
> >middle of the Message-ID payload, and it has long been obsolete,
> >so just tolerating whitespace after the header label should
> >be sufficient.
> I agree on that.
>
> Is there any fix for this special case in sight or would you accept
> patches if provided?
You're welcome to try. There is no promise it will be adopted.
Folding a Message-ID: header after the ":" will keep the line length
under 78, only if the message ID *value* is shorter than 78. Folding
will merely make the problem happen 12 bytes later.
If you're thinking about writing a patch to extract multiline header
info in bounce_notify_util.c, then that patch must not accumulate
more content than $header_size_limit (messages that are still in
the maildrop queue can have headers that exceed this limit).
A more "technically correct" fix is to update the cleanup server,
which already inspects multiline header values and stores findings
based on header/body content, as named attribute records in the
"extracted" queue file segment. Examples of such extracted information
are content type, content encoding, header/body FILTER action,
REDIRECT action, etc. An extracted message-id record could go there.
The code in bounce_notify_util.c already anticipates on the possibility
of records in the extracted segment.
More correct does not mean that it would make sense.
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
