Pat Traynor wrote:
> If this is a clueless newbie question, please just give me a few mild
> slaps.
I agree with the other comment that this is a procmail question. But
since you asked...
> :0
> * ^Subject.*lueberry*|\
> [EMAIL PROTECTED]|\
> ^Subject.*Business directory addition request*|\
> ^Subject.*Guestbook entry*
> ${DEFAULT}
Your trailing '*' characters in the lines above don't make any sense
to me. I think you want to remove them.
> Of course, my entire list is pretty long. But what I found is that if
> I leave it as one big long list, something breaks and no mail whatsoever
> gets through to me. What I have to do is to break the list down into
> multiple shorter lists (I go with about 30 items in a list).
You will be building a huge state machine if that list is very large
at all. I would imagine you could run out of memory. I am not sure
that is your problem. But managing a large list that way will be hard
anyway.
I would do it one of two different ways.
Option 1. Use the procmail score system. Suitable for a few patterns.
:0
* 1^0 ^Subject.*lueberry
* 1^0 [EMAIL PROTECTED]
* 1^0 ^Subject.*Business directory addition request
* 1^0 ^Subject.*Guestbook entry
$DEFAULT
Read 'man procmailsc' for details.
Option 2. Use an external grep. Suitable for large lists of patterns.
:0
* ? formail -X "" | grep -Eqsf $HOME/Mail/whitelist
$DEFAULT
'formail -X' extracts the header. If the grep returns zero then the
'?' considers the rule matched.
Bob
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
