Re: Can we filter out BCCs?

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: Can we filter out BCCs?
Дата
Msg-id BANLkTinMAJqbhDmu5HWjxm0iCpkwKHAoEw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Can we filter out BCCs?  (Selena Deckelmann <selena@chesnok.com>)
Ответы Re: Can we filter out BCCs?  (Josh Berkus <josh@agliodbs.com>)
Re: Can we filter out BCCs?  (Susanne Ebrecht <susanne@2ndquadrant.de>)
Список pgsql-www
On Wed, May 25, 2011 at 9:30 PM, Selena Deckelmann <selena@chesnok.com> wrote:
> On Wed, May 25, 2011 at 1:58 PM, Kevin Grittner
> <Kevin.Grittner@wicourts.gov> wrote:
>> `Josh Berkus <josh@agliodbs.com> wrote:
>>
>>> Just got a piece of spam to a PostgreSQL list which was to
>>> "undisclosed-recipients".  Seems like Majordomo ought to be able
>>> to filter out BCCs for all public lists.
>>
>> The best way I've seen to "move" a thread from one list to a more
>> appropriate one is to include the new list in "to" or "cc" and put
>> the old list in 'bcc".  If we could leave that without causing other
>> problems, that would be nice.  It's always possible to just post two
>> messages, though.
>
> This is the exact use-case I was going to post about.
>
> Please do not filter out all BCCs.

Agreed. The sender should still need to be registered though, so we
can always remove them if they're abusing the list. Not much we can do
if a spammer has picked up their address of course, except perhaps ask
them to send from an alternate address.


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


В списке pgsql-www по дате отправления:

Предыдущее
От: Dave Page
Дата:
Сообщение: Re: Proposal to shutdown pgFoundry
Следующее
От: Josh Berkus
Дата:
Сообщение: Re: Can we filter out BCCs?