I've noticed the past few versions that spam going to sendAllSpam is not always
being prepended with spamTag even though spamTagCC is checked.
Example. Sometimes subject is prepended with [MessageLimit] and other times
it's not even though the header shows X-Assp-Spam-Reason: Message Limit.
MessageLimit is not the only one this occurs will.
I've seen the same with all of the Regex's, URIBL, SPF and Bayesian. The
headers show the proper reason but most of the time the reason is not being
prepended to the subject.
Looking back through my copy's of spam I noticed the following even though the
headers show proper spam reason. In all cases the problem started with
1.3.4(15), All of them were working properly with 1.3.4(14):
BombData has not had a single prepend of Subject.
BombHeader has been sporadic with only about 20% getting the prepend.
BombRaw has not had a single prepend.
MessageLimit sporadic with the prepend however 90%+ have the prepend.
SPF I only had set to 1 for about a day then switched to scoring but out of 13
fails none got prepended.
URIBL has similar results as MessageLimit a bit over 90% getting the prepend.
Bayesian is same as URIBL, and MessageLimit.
I believe this is only affecting CC Mail. However the only thing that goes
through to Recipients is Bayesian all others only go to CC Mail.
____________________________________________________________________________________
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news,
photos & more.
http://mobile.yahoo.com/go?refer=1GNXIC
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user
