On Mar 10, 2011, at 12:42 PM, Chris Murphy wrote: > > This is not consistent with RFC 2369 3.4 at all. Combined with RFC 2822, it's > very clear the behavior is up to the client email application, the list owner > has no say what the default behavior is when List-Post is set to an email > address. If the list is non-posting, List-Post is to be set to No. That's the > limit of the list owner's ability to describe reply behavior. The default > reply-to list posted email addresses behavior is NOT in the domain of the > listserve maintainer. It's client side domain. > > So you can bitch and whine and provide all the evidence of list owner intent > you want. The described intent is inconsistent with the IETF standards.
Sure it is. The RFC shows INFORMATIONAL headers which are there to tell the human user how to post to the list. If an email client wants to make use of them that is up to the client but there is nothing in the RFC that says that an email client HAS to do anything with List-Post. Your email client does what YOU tell it to do, and nothing more. And you are telling it to do the wrong thing when you REPLY ALL and don't trim down the resultant shotgun blast of addresses. _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
