Re: [Exim] -t and Resent- header lines

Top Page
Delete this message
Reply to this message
Author: Exim Users Mailing List
Date:  
To: Avleen Vig
CC: Exim Users Mailing List
Subject: Re: [Exim] -t and Resent- header lines
[ On Thursday, May 8, 2003 at 11:05:18 (-0700), Avleen Vig wrote: ]
> Subject: Re: [Exim] -t and Resent- header lines
>
> RFC2822 needs to be clearer, and should require a seperator between
> blocks as it does for Trace fields.


Ineed, but that's far from the correct solution. Anything that
introduces required (i.e. "MUST") order to headers is totally bogus and
broken by definition.

The best solution is for the MTA to simply add another "resent-" prefix
to all existing "resent-*" headers when it is resending a message so
that now most sane MTAs will simply ignore these new "resent-resent-*"
headers. Note too that this is existing practice, though I forget just
exactly where. (maybe even in the MUA I use, ViewMail! ;-)

--
                                Greg A. Woods


+1 416 218-0098;            <g.a.woods@???>;           <woods@???>
Planix, Inc. <woods@???>; VE3TCP; Secrets of the Weird <woods@???>