http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3109
------- Additional Comments From [EMAIL PROTECTED] 2006-04-04 05:46 -------
Michael :
I appreciate your concern but how much time do need to review? And what are
your points of concern so that others who are hot on the patch can address them.
This has brought down the CPU usage on one of my servers considerably....I am
seriously considering putting it on all my mail servers.
Justin :
>> normally we'd do:
- start all DNSBL lookups (in the background)
- do head tests, body tests, etc. for several seconds
- wait several seconds for DNSBL results
- do meta tests
- AWL
- return
with the HARVEST_DNSBL_PRIORITY change it becomes
- start DNSBL lookups (in the background)
- wait several seconds for DNSBL results
- do head tests, body tests, etc. for several seconds
- start more DNSBL lookups (at another priority level)
- wait several seconds for those DNSBL results
- ...
I'm worried that that'll have pretty major knock-on effects on speed. :( So I
haven't applied that change to HARVEST_DNSBL_PRIORITY, and it's still at +500.
>>
Normally, the dsnbl checks can be done last.... the fastest sequence is as
follows
1. Banned attachments ... if it contains a banned attachment...mark as spam ..
SC
2. Clamav plug in ... if it contains a virus ... mark as spam .. SC
3. White list ... mark as ham .. SC
4. Blacklist ... mark as spam .. SC
5. Local tests ... mark as spam if need be ... SC only if score exceeds spam
threshold
6. dnsbl tests ... mark as ham/spam as normal.
I find that 60% of the incoming emails are sorted out by step 4....with very
little CPU usage by SA (except CLAMAV which takes quite a bit at step 2)
By knocking off the obvious banned attachments/viruses/whitelists and
blacklists, the loads on the network services can be brought down considerably.
Why do a dnsbl test on a virus? It is a waste of everybody's resources.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
