On Mar 10, 2011, at 12:42 PM, Chris Murphy wrote: > > No. It is precisely for non-human consumption, the header is not shown by > default, there's no good reason why a human would go looking for it except as > a troubleshooting measure - certainly not as part of actual functional daily > workflow. Of course it's for the client application. It's just not REQUIRED > to be honored in any specific way.
It is there for human consumption for those people who want to look. Some email clients may make it more accessible. Most clients have a way of showing headers for those who want to see them. I can stick in ANY HEADER I WANT in the headers. That header is not part of the email specification of how clients need to behave. It is there for INFORMATIONAL PURPOSES. The headers are formatted such that they can be read and used programmatically by the client. > > >>>> There is a reason for it, whether you agree with that reason or not. You >>>> are not the list owner. >>> >>> Nor are you. And what you are saying is speculative at best, and not >>> supportable logically. >> >> It is supported logically -- the list works exactly the way I described and >> it is supported by historical posts from the Omni list maintainers. > > 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. List-Post, per the RFC, is merely informational on how to post to the list. Per the RFC. It is not there to say how to respond to a post or anything (beyond the address you need to send your reply to). It does not dictate list behavior per se. > 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. What you describe has nothing to do with standards. The List-* headers are informational about the list so that if you want to participate in the list you have the information you need to do so. For example the list in question sets the following headers List-Id List-Unsubscribe List-Archive List-Post List-Help List-Subscribe Each of those headers is INFORMATIONAL to tell you how to do each action or where to find the info needed. They have nothing to do with how your reply to a list posting (other than telling you which address you should address your reply to). > > > Chris Murphy _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
