From: Dave Page <dpage@pgadmin.org>
To: Dean Gibson (DB Administrator) <postgresql@ultimeth.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Bouncing replies
Date: Mon, 11 Feb 2008 08:54:04 +0000
Message-ID: <937d27e10802110054h6538294bwcb8100665048bd57@mail.gmail.com> (raw)
In-Reply-To: <47AFD7DD.2040000@ultimeth.com>
References: <47AFA703.5060907@ultimeth.com>
<15372.1202698673@sss.pgh.pa.us>
<15505.1202699499@sss.pgh.pa.us>
<47AFD7DD.2040000@ultimeth.com>
On Feb 11, 2008 5:06 AM, Dean Gibson (DB Administrator)
<postgresql@ultimeth.com> wrote:
> If mail to my list address doesn't come from one of your list
> servers (and those seems to change much more often than any other list I
> belong to), it gets rejected.
Those must be some *really* long-lived lists. Our mailserver has been
mail.postgresql.org for probably 7 or 8 years now. Many moons ago we
did use some additional relay servers, but I don't think we've done
that for 5+ years.
> I'm curious as to why the list server defaults to using a sender's
> address as the "Reply-to" address, rather than using the list address.
> That means that, unless the user is careful to "reply all" (or even
> better, just reply to the list address), any discussion immediately goes
> private.
Because thats the convention on these lists that people are used to
and prefer in general.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: dpage@pgadmin.org, postgresql@ultimeth.com
Subject: Re: Bouncing replies
In-Reply-To: <937d27e10802110054h6538294bwcb8100665048bd57@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox