https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7070
Bug ID: 7070
Summary: Timers misbehave with SpamAssassin
Product: Spamassassin
Version: 3.4.0
Hardware: PC
OS: Windows 7
Status: NEW
Severity: normal
Priority: P2
Component: Score Generation
Assignee: [email protected]
Reporter: [email protected]
While dealing with DNS issue, I've found that the various timers do not
function correctly in SpamAssassin.
For example, I have
pyzor_timeout 60
razor_timeout 60
rbl_timeout 90 60
SpamAssassin routinely ABORTS lookups long before any of these timers expire.
For example:
Jul 15 16:37:18.773 [33838] dbg: async: aborting after 23.433 s, deadline
shrunk: URIBL_PH_SURBL, URI-DNSBL, DNSBL:iglobalmall.net:multi.surbl.org
Not only did this abort the DNSBL lookup, it also aborted the RAZOR LOOKUP.
This caused scoring to be incorrect. After running the spam through SA *3
times* it finally got correct scoring:
X-Spam-Status: No, score=4.7 required=5.0 tests=HTML_FONT_LOW_CONTRAST,
HTML_MESSAGE,RAZOR2_CF_RANGE_51_100,RAZOR2_CF_RANGE_E8_51_100,RAZOR2_CHECK,
RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,RP_MATCHES_RCVD,UNPARSEABLE_RELAY
autolearn=no autolearn_force=no version=3.4.0
I.e., the timer does not apply uniquely to EACH RBL lookup, and despite saying
I want a MINIMUM of 60 seconds to be used for RBL lookups, it still aborted
after 23 seconds. 23 seconds is clearly not REMOTELY CLOSE to 60 seconds.
Yes, I realize DNS is a mess in my environment. I've been struggling with it
for 9 months, since I have ZERO control over the network environment that's
causing the problem. I need to be able to have SA *honor* its configuration.
--
You are receiving this mail because:
You are the assignee for the bug.
