Bryan Hoover <[EMAIL PROTECTED]> writes:
> Harry Putnam wrote:
>
>> Maybe a little different approach wouldn't require as much huffing
>> and puffing:
>> header Spama X-BeenThere =~ spamassassin-.*@lists
>> score Spama -100
>>
>> So to get to spam status the score must go over +100.
>>
>> I haven't tested this much yet. Only started it when I say this
>> thread.
>
> Sure, that's a fine idea, or something like it. But it should not be
> neccessary. SA white listing should take care of it - that's what it's
> there for.
I'm not sure I see how whitelist_from or to will work, unless the
`from' is a reference to the berkely format `From ' (note the
missing :)
My spam_ass mail is never from the list address, nor to the list address.
So how does whitelisting_from `spamassassin' do any good? I don't
doubt that it does, or that I have a screwball conception of how it
works but I don't understand how it would work.
The approach I mentioned uses one rule to catch spama-talk
spama-devel and spama-{whatever}-request. Is that not less work?
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
