Re: Can we filter out BCCs?

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Selena Deckelmann <selena(at)chesnok(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-www(at)postgresql(dot)org
Subject: Re: Can we filter out BCCs?
Date: 2011-05-26 00:11:58
Message-ID: BANLkTinMAJqbhDmu5HWjxm0iCpkwKHAoEw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Wed, May 25, 2011 at 9:30 PM, Selena Deckelmann <selena(at)chesnok(dot)com> wrote:
> On Wed, May 25, 2011 at 1:58 PM, Kevin Grittner
> <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
>> `Josh Berkus <josh(at)agliodbs(dot)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

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Josh Berkus 2011-05-26 01:25:04 Re: Can we filter out BCCs?
Previous Message Dave Page 2011-05-26 00:07:32 Re: Proposal to shutdown pgFoundry