On May 9, 2006, at 12:47 PM, qqqq wrote:
X-Spam-Report:
* -0.0 SPF_HELO_PASS SPF: HELO matches SPF record
* 1.7 EXCUSE_6 BODY: Claims you can be removed from the list
* 3.0 URIBL_BLACK Contains an URL listed in the URIBL blacklist
* [URIs: goldenpalace_MUNGE.com]
* 1.5 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist
* [URIs: goldenpalace_MUNGE.com]
X-Spam-Status: Yes, score=6.3 required=5.5 tests=EXCUSE_6=1.746,
SPF_HELO_PASS=-0.001,URIBL_BLACK=4,URIBL_WS_SURBL=1.533
autolearn=disabled version=3.1.0
Subject:[ReveNews] - 5 New Entries
This was a mailing list a paying customer signed up for.
Keep in mind that the FP's are real low, I may just keep the scores
as is and deal with these
mailing lists as they pop up.
One thing you could try is: a rule that looks to see if it's definitely
from the mailing list in question, and definitely to the customer in
question, then lower the score by lots of points (may 100, just like it
was a "whitelist" entry).
The advantage: only the user who requested this will get a lower score,
and only for that mailing list; every other user (or that use with
similar emails not from that list) wont see a lowering of scores.
The disadvantage: you've just gotten in the business of
per-customer/per-sender whitelisting, and you need to come up with a
decent way of managing such a list of rules.
Or, if you're just making the messages and not
rejecting/bouncing/blocking/intercepting them, then just tell the
customer how to do their own semi-whitelisting (how to sort the message
into its own folder before whatever spam-sorting rule they use (in
procmail, in their client, etc.)). The advantage here is that it is
the customer who manages their own mechanism for this, but it requires
users who are willing to "take action" to control things instead of
just being whiners.
