On Tue, May 30, 2000 at 11:58:37PM +1000, Jeff Waugh wrote:
| I remembered that Anand mentioned a 'panacea' for mailing-list overload a
| while back, so I peeked though the archives and found it:
|
| :0:
| * ^((List-Id|X-(Mailing-)?List):(.*[<]\/[^>]*))
| {
| LISTID=$MATCH
|
| :0:
| * LISTID ?? .*\/[^@.]*
| Lists/$MATCH
| }
|
| Only, for most of my lists, including SLUG, it doesn't work! Everything
| falls through into my normal box. Is this just a problem for old lists, or have I
|buggered it up?
[Aside] Your reply-to or from is busted - my reply just tried to mail
"jdub" instead of "[EMAIL PROTECTED]" - FIX THIS!
Your recipe is incomplete. Many (most) lists don't put in a List-Id or
X-(Mailing-)?List header. I filter this on To: line first and when that
misses I usually fall back onto the Sender: line. For slug I have:
Linux-SLUG [EMAIL PROTECTED]
Linux-SLUG [EMAIL PROTECTED]
Linux-SLUG [EMAIL PROTECTED]
Linux-SLUG [EMAIL PROTECTED]
Linux-SLUG [EMAIL PROTECTED]
Linux-SLUG "sender:[EMAIL PROTECTED]"
Linux-SLUG "sender:[EMAIL PROTECTED]"
(No, I'm not using procmail.) So that's 5 different To: patterns and two
Sender: patterns.
--
Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/
The problem with elections is that the government always wins.
- Chris Rudram <[EMAIL PROTECTED]>
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
