From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: No reply-to in list messages. |
Date: | 2013-10-30 15:00:43 |
Message-ID: | 3936.1383145243@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Francisco Olarte <folarte(at)peoplecall(dot)com> writes:
> I use gmail. The mailing list messages from psql-bugs come without
> reply-to, so when I hit reply directly I do it to the original sender
> ( I've checked the archives to conform this is the case and gmail is
> not CCing the list behind my back ) without copying to the list. I do
> not know if this is intentional ( I'm used to the classical messages
> form the mailing list, Messages come in with from=the sender, to=the
> list, list send them out with from=the sender, reply to = the list,
> to = everyone subscribed ) and, if intentional, if someone knows if I
> have misconfigured something, or I should just use reply-all in every
> post ( to have the original sender CCed ).
It's intentional that there's no Reply-To: header in the PG lists,
particularly on pgsql-bugs where many messages come from unsubscribed
people. With a Reply-To: header, the default behavior would fail to
respond to the original bug reporter if he/she wasn't subscribed ---
and many MUAs don't make it easy to override that. Without Reply-To,
it's easier to get either of the typical response patterns (to sender
only, or to sender + list): you just have to hit reply all rather than
reply.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Johnston | 2013-10-30 16:41:58 | Re: BUG #8569: with recursive work incorrectly with function |
Previous Message | Francisco Olarte | 2013-10-30 14:32:58 | No reply-to in list messages. |