Re: [HACKERS] [pgsql-www] Schedule for migration to pglister - Mailing list pgsql-www

From Tom Lane
Subject Re: [HACKERS] [pgsql-www] Schedule for migration to pglister
Date
Msg-id 24353.1509983184@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] [pgsql-www] Schedule for migration to pglister  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [HACKERS] [pgsql-www] Schedule for migration to pglister  (Magnus Hagander <magnus@hagander.net>)
List pgsql-www
Magnus Hagander <magnus@hagander.net> writes:
> On Mon, Nov 6, 2017 at 4:40 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I suggest doing that the other way 'round.  Otherwise, the email
>> about the change will inevitably go into a lot of peoples' bit
>> buckets if they haven't adjusted their mail filters yet.

> The argument for doing it after the migration is that the complaints that
> we have received so far have all been from people where email ends up in
> the *inbox* after the migration, not the bitbucket. That's the default
> action in most peoples MUAs when their rules no longer match...

Hm, around here it's no match -> spam bucket.  But in any case, why
would you not want to send it before so that it would end up where
they're accustomed to seeing the list's traffic?
        regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-www by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [pgsql-www] Schedule for migration to pglister
Next
From: Magnus Hagander
Date:
Subject: Re: [HACKERS] [pgsql-www] Schedule for migration to pglister