Re: Recovering from bad disk ...

On Mar 10, 2011, at 8:51 AM, Bart Silverstrim wrote:

> On 03/10/2011 10:32 AM, objectwerks inc wrote:
>> 
>> You still do not get it Chris.  This has nothing to do with the
>> listserve and how it is configured.
> 
> Actually, it kinda' is. Something in the headers, when I hit reply, only goes to the sender, not the list. When I hit reply all, it goes to the list and anyone else in the headers.

> This is the only list I've been on that I recall this happening.

Well as it turns out other lists are using Reply-To and stomping on author's (those who use it) Reply-To's. So they are using Reply-To as a hack work around for email clients that don't honor List-Post. I understand the hack work around and actually prefer it, but the *right* thing to do is for Apple Mail to honor List-Post. 

While I'd prefer Omni change the listserve to behave like other listserves, what they are doing is technically not wrong, it's actually conforming to RFC.

> If the community is generally screwing it up or finds it irritating, the behavior of the list should probably be modified. Isn't that a fairly simple rule of software usability?

Yes except in this case our complaint is with email clients primarily. The email client should honor List-Post. If that is set to No, then it would work as "Reply" presently behaviors, which is the reply is populated with the Reply-To: (which should be the author of the email, not the list), and if Reply-To is not set, then populated with From:. If List-Post is an address, then Reply should default to the address in my opinion, however the email client could make the behavior configurable, they could even have a "Reply List" button for only those emails that contain List-Post. I'd prefer Reply mean Reply List anytime List-Post is used.

So while I'd rather the email apps work correctly with respect to List-Post. The munging of Reply-To is a long standing and effective way of dealing with (apparently) craptastic behavior on the part of email clients.

Chris Murphy