Linda Walsh said the following on 05/08/2013 10:13 PM:
RFC 882 STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES...
Well 882 has long since been outdated and replaced, but that's beside
the point
Better to quote
http://woozle.org/~neale/papers/reply-to-still-harmful.html"
People still using these two documents to debate the issue are wasting everybody's time. The issue was definitively settled in 2001, and Chip won. .... In April of 2001, the IETF issued af new document, RFC 2822, which obsoletes RFC 822. In this new RFC, the author addresses the Reply-To header field in a few places, but the most relevant to this discussion is the following in section 3.6.2 "Originator fields": When the "Reply-To:" field is present, it indicates the mailbox(es) to which the author of the message suggests that replies be sent. Your list software is not "the author of the message", so it must not set or in any way meddle with the Reply-To header field. That field exists for the author and the author alone. If your list munges it, you are violating the standard. </quote> It then goes on to say <quote> RFC 2369 specifies, in section 3.4, the List-Post header field: The List-Post field describes the method for posting to the list. This is typically the address of the list, but MAY be a moderator, or potentially some other form of submission. For the special case of a list that does not allow posting (e.g., an announcements list), the List-Post field may contain the special value "NO". Modern mail list software sets this header field, or provides some mechanism for the administrator to set it. </quote> And LO! there in the message headers is the List-Post field: Mailing-List: contact opensuse+help@opensuse.org; run by mlmmj X-Mailinglist: opensuse List-Post: mailto:opensuse@opensuse.org List-Help: mailto:opensuse+help@opensuse.org List-Subscribe: mailto:opensuse+subscribe@opensuse.org List-Unsubscribe: mailto:opensuse+unsubscribe@opensuse.org List-Owner: mailto:opensuse+owner@opensuse.org List-Archive: http://lists.opensuse.org/opensuse/ I think the author of that article put it very nicely when he sys <quote> People want their mail client to be consistent. When they hit "reply" they want it to go to the person who wrote the message. When they hit "reply to all", they want it to also go to everyone who received it. Most people understand this by now, since it's how their mail reader has worked for every email they've ever gotten. Your list shouldn't be any different. </quote> At the very least, viewing the index at the IETF gives 0822 STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES. D. Crocker. August 1982. (Format: TXT=106299 bytes) (Obsoletes RFC0733) (Obsoleted by RFC2822) (Updated by RFC1123, RFC2156, RFC1327, RFC1138, RFC1148) (Also STD0011) (Status: INTERNET STANDARD) Always check for updates to standards! Oh, and check for errata as well <quote src="http://www.rfc-editor.org/errata.php"> Published RFCs never change. Although every published RFC has been submitted to careful proofreading by the RFC Editor and the author(s), errors do sometimes go undetected. Use the form on this page to query the errata database for entries related to an RFC. Errata are for the RFCs as available from rfc-editor.org. Search results from the RFC search engine will include hyperlinks to any corresponding errata entries. </quote> And yes, RFC822 has errata. So does RFC2822. -- A generation which ignores history has no past and no future. Robert Heinlein (1907 - 1988), The Notebooks of Lazurus Long -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org