lists(_at_)professional(_dot_)org writes:
I've got a simple remailer script I'm using in Procmail to resend messages
posted by anyone from a group out to other members of the group. The
resending is working fine, but folks using the Pegasus mailer complain that
they don't see the original author's address in their message summary
window, and while quoted replies show the author's name, it apparently
shows the reply-to address (the list) for the address instead of the
authors address.
In attempting to determine what the possible cause of this is, I noted that
the sendmail config on my host is apparently automatically inserting
Resent-From and Resent-Date headers -- because *I* am not (certainly not
the Date). How can I control the addition or removal of these headers
(I've tried -IResent-From: in the main formail operation -- and originally,
I did have a Resent-From: listname(_at_)domain header present -- I just wanted
to remove it for testing, which is when I realized that I couldn't).
If a message contains any of:
Resent-From: *
Resent-To:
Resent-Cc:
Resent-Bcc:
Resent-Message-Id: *
Resent-Date: *
Resent-Sender:
(and maybe some others), then sendmail will consider the message to be
a resent message, and will guarantee that the message contains the
headers starred above. If you don't want ther message to have any of
those, then don't put any Resent- headers in at all, period.
Also, one thing that struck me was that Pegasus (which I don't use) might
be scanning the header and using the LAST "from-like" header to identify
the author, rather than following the precedence set in RFC822. Does
anyone have more intimate knowledge of how this app might be handling the
headers?
Last I heard, rfc822 does *not* set a precedence between the Resent-
and 'bare' forms of a header when replying. If you want to make sure a
given address will be choosen, then you should *not* use Resent-
headers but instead override the original headers, possibly saving
their original values elsewhere.
Philip Guenther