Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> The basic issue is that the current setup encourages
> reply-to-author-and-list, while adding Reply-To encourages
It also makes it impossible to reply to the author personally. Normally there
are two actions possible on a message, "followup/wide-reply" and "reply" and
MUAs provide separate buttons. Setting reply-to inappropriately essentially
forces both buttons to be "wide-reply".
The suggested behaviour is actually the worst of both worlds since it would
mean "reply" would sometimes send a personal reply to the poster and sometimes
send a wide-reply to the list, depending on whether the poster had already set
Required reading on the subject:
There are proper ways to encourage reply-to-list-only. Set the header:
> Personally: if Reply-To is added to the list headers, I can and will
> reprogram my mail software to ignore it. But I doubt that most
> contributors to the lists have that option.
In fact what they do is ask for MUA features to ignore reply-to headers.
Leading to an escalating weapons race of lists more and more forcefully
breaking MUAs so that MUAs can more and more forcefully break standards in
order to work correctly in the face of broken lists. Compatibility and
standards are collateral damage.
In response to
pgsql-hackers by date
|Next:||From: Zeugswetter Andreas DAZ SD||Date: 2004-11-29 16:30:18|
|Subject: Re: Stopgap solution for table-size-estimate updatingproblem|
|Previous:||From: Andreas Pflug||Date: 2004-11-29 16:03:38|
|Subject: Re: Error: column "nsptablespace" does not exist|
pgsql-general by date
|Next:||From: Scott Cain||Date: 2004-11-29 17:00:03|
|Subject: ERROR: could not access status of transaction 210|
|Previous:||From: 金更达||Date: 2004-11-29 14:46:14|