Re: List removals
От | Stephen Frost |
---|---|
Тема | Re: List removals |
Дата | |
Msg-id | 20171204193027.GJ4628@tamriel.snowman.net обсуждение исходный текст |
Ответ на | Re: List removals (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>) |
Список | pgsql-www |
Greetings, * Stefan Kaltenbrunner (stefan@kaltenbrunner.cc) wrote: > On 12/04/2017 03:42 PM, Tom Lane wrote: > > Stephen Frost <sfrost@snowman.net> writes: > >> * Andres Freund (andres@anarazel.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@lists.postgresql.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). Gah, no, absolutely not. This is definitely not worth that. > 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 :/ I'd be alright with this as long as it's only a minimal amount of effort required. We've already spent more time discussing this than I think it's worth. Thanks! Stephen
В списке pgsql-www по дате отправления: