On Fri, Oct 19, 2001 at 12:34:05PM -0700, J C Lawrence wrote:
I've been reading RFC 2822 on the subject of Reply-To and noticed that the content of Reply-To is a list. ie you can have more than one address listed under a Reply-To:
reply-to = "Reply-To:" address-list CRLF address-list = (address *("," address)) / obs-addr-list address = mailbox / group mailbox = name-addr / addr-spec name-addr = [display-name] angle-addr angle-addr = [CFWS] "<" addr-spec ">" [CFWS] / obs-angle-addr group = display-name ":" [mailbox-list / CFWS] ";" [CFWS] display-name = phrase mailbox-list = (mailbox *("," mailbox)) / obs-mbox-list
eg:
Reply-To: list@foo.conm, list@bar.com, claw@kanga.nu
This would seem to potentially remove one of the complaints on Reply-To: lists -- that they nix/kill crossposting, and lose the actual semantic value of the original Reply-To header.
Ergo, if a given list is configured to do reply-To munging and it receives a message with Reply-To set, then it makes sense to _ADD_ the list's address to the Reply-To: header if present, rather than replacing it.
Assuming that mailers correctly handle such a Reply-to.
And note that this message arrived here with no To: header, FWIW.
Cheers, -- jra
Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 804 5015
"Usenet: it's enough to make you loose your mind." -- me