🚀 go-pugleaf

In article: <885046994snz@dsl.co.uk>  bhk@dsl.co.uk (Brian {Hamilton Kelly}) 
writes:
> 
> In article <705236596wnr@roborat.demon.co.uk>
>            dave@roborat.demon.co.uk "Dave Scott" writes:
> 
> > Upon receipt of the forwarded message, it has an extra 'From ' embedded
> > in it's headers, which cause it to be broken into 2 separate posts - the
> > 1st part consisting of a few "Resent-from:" type headers, the 2nd being
> > the original message without any forwarding information.
> 
> Hmm; that second "From " ought not to have been included in the forwarded
> message AT ALL; if the forwarding mechanism merely prefixes Resent-From
> type headers, then it has a DUTY to ensure that the remainder of the
> headers are RFC-822 conformant: a line starting "From " is not, and
> should either have been discarded, or rewritten as Return-Path in RFC-822
> syntax.

Thank you Brian! I was thinking about this from the wrong end, and the
real problem I need to fix is in the *incoming*, not outgoing messages.
What happens is this...

WinDIS downloads into the mbox file, each message prefixed with a 'From '
header. PM-Demon's mailin.exe program then copies each message with this
line intact, and it's this that get's preserved in forwarded messages.

OTOH, a quick test with the Pegasus built-in POP3 transport shows
messages received that way don't have this header. The solution
therefore seems to be to fix mailin to translate the 'From ' into a
Return-Path: as you suggest.

(I might still also perform the original modification of 'From ' to
'>From ' on *outgoing* messages I was asking about, *unless* anyone
knows of a reason not to?)

Dave.
-- 
    ()---()
     (0 0)    Dave Scott   e-mail: dave@roborat.demon.co.uk
----m-( )-m-------------------------------------------------------------
      =o=