From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-www(at)postgresql(dot)org |
Subject: | Re: List removals |
Date: | 2017-12-04 18:03:38 |
Message-ID: | e977b99a-aa84-894c-314b-1b010321b828@kaltenbrunner.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
On 12/04/2017 03:42 PM, Tom Lane wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
>> * Andres Freund (andres(at)anarazel(dot)de) wrote:
>>> How about just redirecting some of them to more appropriate lists
>>> instead?
>
>> They'd screw up people's filters, we're trying to deprecate the
>> @postgresql.org list aliases, we'd end up making those lists look
>> active through the archives when they really aren't (without more code
>> anyway), and, frankly, I just don't see there really being value to it.
>
> I think a bounce would be fine if the bounce message contained something
> like "this list is inactive, please send to <xxx(at)lists(dot)postgresql(dot)org>
> instead". How feasible is that?
doable - but the challenge there is that if we want to generate a proper
bounce we will have to accept the mail and send back a bounce - that
however makes us vulnerable to bounce blow-back (if say somebody fakes a
an email sender and we direct the bounce in that direction back).
The other option is to reject the RCPT TO at SMTP time with a message
like the above on our frontends - the problem there is that is it up the
sending MTA to wrap that text into a bounce that might or might not be
parsable by a human :/
Stefan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-12-04 19:03:50 | Re: List removals |
Previous Message | Tom Lane | 2017-12-04 14:42:34 | Re: List removals |