On Mar 10, 2011, at 12:06 PM, objectwerks inc wrote: > > On Mar 10, 2011, at 10:46 AM, Chris Murphy wrote: > >> >> On Mar 10, 2011, at 8:35 AM, objectwerks inc wrote: >>> >>> Read what I just posted on why the list is set up the way it is. It is >>> purposefully set up to reply to each poster individually, and not the list. >> >> Conjecture on your part. >> > > It is not conjecture on my part. It was specifically said in this list by > the omni rep several years ago when this question came up.
I find it hard to believe any thinking person would want to micromanage human behavior so much they'd actually think they way you proposed it: "to try and keep crap me-to posts and similar off the list". The rational response to the present behavior is Reply All, which most people say they are using. So it could not possibly, to a thinking person, be about keeping crap me-too posts off a list. I think management of such rare events is with derision is sufficient. F*ing up everyone elses's workflow for a few "me too" morons is itself puerile. > List-Post is merely a header to tell you which address to send posts to. It > is not a mail header that has specific meaning to email clients to tell them > how to respond. 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. >>> 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. 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. Chris Murphy_______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
