>...
>>
>> I'll mention this again since i have yet to come up with a solution.
>> While the above works great for people using procmail, does anyone have
>> a solution that works without procmail? Im stuck passing all list
>> traffic through SA because of this. Just this morning someone on this
>> list posted a spam that they received. It was autolearned as ham on my
>> system because it came across on the list. Then the message gets popped
>> down to my workstation and i cant even get the original message back to
>> the server to re-learn it. Theres gotta be a solution out there for the
>> non-procmail people. Surely somebody is doing it??
>>
>> Qmail/qmail-scanner/clamav/spamassassin on rh9
>>
>> -Jim
>
>Use dedicated e-mail addresses for mail lists.
>
>As mail for that address arrives, don't send it through whatever filtering you
>have.
>
>Alan
>
Not a good idea (track@ gets the most spam of any account at my site
and is my personal account for mailing lists only. Now, maybe is you're just
a "lurker" whose address is never harvested that *might* work. The "solution"
I've just begun to use, is to use a "private" header name X-something-xxx and
filter on that instead; also whitelist_from_rcvd is helpful but not enough
when others on the list quote SA output from spam (and I certainly do think
that is a practice that is both appropriate and useful - just remember do munge
or check at least that the message is less than 10 pts.).
Unfortunately, you still have to account for several possible mail
servers at apache.org.
Paul Shupak
[EMAIL PROTECTED]
