Glenn,
The bcc information is usually stripped out before it leaves the sender's
domain, so it is not available to procmail to filter on. I use rules very
similar to yours which work most of the time. The only exceptions of course
is when the list itself is bcc'd. I also have problems when more than one
list I'm on is copied in a single message with the procmail continuation
stuff, but this of course could be solved by a more complete (and
complicated) .procmailrc file.
Best Regards,
Tim Kehres
International Messaging Associates
http://www.ima.com
----- Original Message -----
From: Glenn Shiffer <[EMAIL PROTECTED]>
To: J. T. B. <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, October 22, 1999 10:14 AM
Subject: Re: Req, For List Admin
>
> I filter using
>
> :0
> * ^TO: [EMAIL PROTECTED]
> $MAILDIR/Firewalls
>
> in procmail. That catches all the to, cc, bcc, etc headers and works
> fine for me.
>
> You could also pipe the messages thru formail and add an X header for
> spool reading clients.
>
> Glenn
>
>
> >>>>> "J" == J T B <[EMAIL PROTECTED]> writes:
>
> J> I was just wondering, would it be possible to have the list
> J> server add something to the subject line for the list?
>
> J> I'm thinking along the lines of:
>
> J> Subject: {Firewall} message subject
>
> J> Or some such thing, reason being is there's currently nothing
> J> to grab from the messages to use for a rule filter, and this
> J> would help conciderably.
>
> J> Just my thoughts.
>
>
>
> --
> Glenn Shiffer [EMAIL PROTECTED]
> __ __
> / // /___ (_)__ __
> / // // _ \ / /\ \/ / . . . Takes a licking
> \_,_//_//_//_/ /_/\_\ and keeps on ticking.
>
> -
> [To unsubscribe, send mail to [EMAIL PROTECTED] with
> "unsubscribe firewalls" in the body of the message.]
>
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
