| From: | Selena Deckelmann <selena(at)chesnok(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-www(at)postgresql(dot)org |
| Subject: | Re: Can we filter out BCCs? |
| Date: | 2011-05-25 21:30:14 |
| Message-ID: | BANLkTin3XtwXn_FWZvM1iebdbc3xie342g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
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.
-selena
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2011-05-26 00:07:32 | Re: Proposal to shutdown pgFoundry |
| Previous Message | Kevin Grittner | 2011-05-25 20:58:19 | Re: Can we filter out BCCs? |