Affects Version/s: 2.2.0, 2.3.0, 2.3.1, 2.3.2, 3.0.0, Trunk
Fix Version/s: 3.0-M1
Environment:nothing fancy, but network latency may be a contributing factor
the following are sample mean timings from the InSpammerBlacklist matcher:
all requests were for 127.0.0.1
hostname - lookup count - mean timing - this lookup time
184.108.40.206.query.bondedsender.org. - 10.0 - 71.9 - 16.0
220.127.116.11.dnsbl.njabl.org. - 10.0 - 265.6 - 266.0
18.104.22.168.relays.ordb.org. - 10.0 - 20095.6 - 20172.0
As you can see they all take signifcant time, and ordb.org is painful.
Of course "success" of the matcher is !success of the lookup, which means that while we will cache the hits they are only the failures, and the good mail will have to perform a full ns lookup everytime.
We should think about caching the successes locally, or arranging these mailets in a separate processor and having independantly threaded processors.
In this case (ten mails) each thread paused for 20 seconds waiting for ordb and then continued, making the whole thing pause for 20. But because I was running 10 spool threads when I increased this to 20 mails the threads paused twice, meaning that the 21st message took 40+ seconds to complete its journey through the spoolmanager.
Workaround, don't use InSpammerBlacklist or set it up in a processor so that it is called by ToProcessor only on classes of mail for which the expense is justified (e.g. not on any outbound or on trusted IP's, senders or domains)
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|1091d 1h 55m||1||Norman Maurer||06/Jan/10 13:08|
|Workflow||Default workflow, editable Closed status [ 12566873 ]||jira [ 12581920 ]|
|Workflow||jira [ 12394044 ]||Default workflow, editable Closed status [ 12566873 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Fix Version/s||3.0-M1 [ 12314294 ]|
|Resolution||Fixed [ 1 ]|