You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by David Morton <mo...@dgrmm.net> on 2009/04/01 22:49:46 UTC

[OT] Re: SpamAssassin is EXTREMLY slow

Karsten Bräckelmann wrote:
> On Fri, 2009-03-27 at 23:59 +0200, Jari Fredriksson wrote:
>> I just hope that as good as SA is will be written in some programming
>> language, and not scripting language. Even Java would be better.
> 
> Dude, you just lost a credit point... ;)
> 
> Everyone, if you feel the urge to contribute to this thread any further,
> please first *do* check the list archives -- this pointless thread comes
> up like once a year. If you believe you can come up with a convincing
> argument that has *not* been mentioned and turned down before, and which
> takes "active contributors code Perl" into account... please try.

Agreed. Anytime anyone starts talking about speed and languages, I roll
my eyes.  Seriously, unless you are a developer and have actually run
code through a profiler to know what areas are running "slow", you are
not qualified to make such statements.

If you *have* run the code through a profiler and can prove that a
majority of time is spent inside a language construct and not on I/O or
a bad algorithm, then you are qualified... to submit a bug report to the
language developers so they can fix it.  Anything else is just bogus.


Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by DAve <da...@pixelhammer.com>.
alexus wrote:
> On Wed, Apr 1, 2009 at 4:49 PM, David Morton <mo...@dgrmm.net> wrote:
>> Karsten Bräckelmann wrote:
>>> On Fri, 2009-03-27 at 23:59 +0200, Jari Fredriksson wrote:
>>>> I just hope that as good as SA is will be written in some programming
>>>> language, and not scripting language. Even Java would be better.
>>> Dude, you just lost a credit point... ;)
>>>
>>> Everyone, if you feel the urge to contribute to this thread any further,
>>> please first *do* check the list archives -- this pointless thread comes
>>> up like once a year. If you believe you can come up with a convincing
>>> argument that has *not* been mentioned and turned down before, and which
>>> takes "active contributors code Perl" into account... please try.
>> Agreed. Anytime anyone starts talking about speed and languages, I roll
>> my eyes.  Seriously, unless you are a developer and have actually run
>> code through a profiler to know what areas are running "slow", you are
>> not qualified to make such statements.
>>
>> If you *have* run the code through a profiler and can prove that a
>> majority of time is spent inside a language construct and not on I/O or
>> a bad algorithm, then you are qualified... to submit a bug report to the
>> language developers so they can fix it.  Anything else is just bogus.
>>
>>
> 
> okay, we like really far away from original thread, i said that
> SpamAssassin runs really slow for me and on top of that I even found
> which plugin causing that, which is this:
> 
> loadplugin Mail::SpamAssassin::Plugin::DNSEval
> 
> I had to disable it, if someone can suggest something in order to make
> it work faster i'm all ears
> 

We run four servers with SA and check every message. After blocking, we 
see 30k to 50k a day actually make it to SA testing. Each of those 
servers use a local DNS cache witch is cycling around every 15 minutes. 
The local DNS cache is reaching out to a common DNS cache inside the 
same network which is doing all the outside DNS lookups for mail 
services. The common cache is cycling around once an hour.

SA routinely takes less than a second per message with several URLs in 
the message. Does that help?

DAve


-- 
"Posterity, you will know how much it cost the present generation to
preserve your freedom.  I hope you will make good use of it.  If you
do not, I shall repent in heaven that ever I took half the pains to
preserve it." John Quincy Adams

http://appleseedinfo.org


Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by John Hardin <jh...@impsec.org>.
On Thu, 2 Apr 2009, Benny Pedersen wrote:

> On Wed, April 1, 2009 23:22, alexus wrote:
>> loadplugin Mail::SpamAssassin::Plugin::DNSEval
>>
>> I had to disable it, if someone can suggest something in order to
>> make it work faster i'm all ears
>
> apt-get install bind
> change /etc/resolv.conf to have just
> nameserver 127.0.0.1

We've already determined that a local nameserver is in use and is 
responding quickly to non-SA requests.

-- 
  John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
  jhardin@impsec.org    FALaholic #11174     pgpk -a jhardin@impsec.org
  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
   W-w-w-w-w-where did he learn to n-n-negotiate like that?
-----------------------------------------------------------------------
  71 days since Obama's inauguration and still no unicorn!

Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by Benny Pedersen <me...@junc.org>.
On Wed, April 1, 2009 23:22, alexus wrote:
> loadplugin Mail::SpamAssassin::Plugin::DNSEval
>
> I had to disable it, if someone can suggest something in order to
> make it work faster i'm all ears

apt-get install bind
change /etc/resolv.conf to have just
nameserver 127.0.0.1

restart bind

test with

dig google.com

is 127.0.0.1 listed as nameserver ?, then its solved

if youi use other os then you are on your own :)

-- 
http://localhost/ 100% uptime and 100% mirrored :)


Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by John Hardin <jh...@impsec.org>.
On Wed, 1 Apr 2009, Chris wrote:

> Using a local caching nameserver with 127.0.0.1 as my nameserver, BIND
> 9.5.0-P2, Net::DNS 0.65. I notice that the slowest one shows:
>
> [14035] dbg: dns: Net::DNS version: 0.63
>
> and the faster one shows:
>
> [17352] dbg: dns: Net::DNS version: 0.65
>
> Why the difference in skip list. These may sound like lame questions but 
> I'm really curious now that I see a marked difference between two 
> messages in lookup times.

Perhaps the older Net::DNS on the slower one is a factor?

-- 
  John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
  jhardin@impsec.org    FALaholic #11174     pgpk -a jhardin@impsec.org
  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
   USMC Rules of Gunfighting #9: Accuracy is relative: most combat
   shooting standards will be more dependent on "pucker factor" than
   the inherent accuracy of the gun.
-----------------------------------------------------------------------
  71 days since Obama's inauguration and still no unicorn!

Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by Chris <cp...@embarqmail.com>.
On Wed, 2009-04-01 at 15:23 -0700, John Hardin wrote:

> 
> So /etc/resolv.conf has 127.0.0.1 as the only resolver?
> 

Semi-related to this thread, why when running two different spams
through "spamassassin -D -t do I get widely different lookup times:

[17232] dbg: async: timing: 0.042 . NS:spamhaus.org
[17232] dbg: async: timing: 0.043 .
DNSBL:dob.sibl.support-intelligence.net:spamhaus.org
[17232] dbg: async: timing: 0.043 . NS:barracudacentral.org
[17232] dbg: async: timing: 0.044 . DNSBL:multi.uribl.com.:spamhaus.org
[17232] dbg: async: timing: 0.044 .
DNSBL:dob.sibl.support-intelligence.net:barracudacentral.org
[17232] dbg: async: timing: 0.045 .
DNSBL:multi.uribl.com.:barracudacentral.org
[17232] dbg: async: timing: 0.046 . NS:rhyolite.com
[17232] dbg: async: timing: 0.049 . DNSBL:multi.uribl.com.:rhyolite.com
[17232] dbg: async: timing: 0.051 . NS:dnswl.org
[17232] dbg: async: timing: 0.053 .
DNSBL:dob.sibl.support-intelligence.net:dnswl.org
[17232] dbg: async: timing: 0.054 . DNSBL:multi.uribl.com.:dnswl.org
[17232] dbg: async: timing: 0.057 . DNSBL:multi.surbl.org.:rhyolite.com
[17232] dbg: async: timing: 0.078 . DNSBL:multi.surbl.org.:dnswl.org
[17232] dbg: async: timing: 0.084 .
DNSBL:multi.surbl.org.:barracudacentral.org
[17232] dbg: async: timing: 0.886 . A:ns6.gandi.net.
[17232] dbg: async: timing: 0.886 . A:zone-ns2.dnswl.org.
[17232] dbg: async: timing: 0.887 . A:ns.morenines.net.
[17232] dbg: async: timing: 0.888 . A:dnswl1.chaosreigns.com.
[17232] dbg: async: timing: 0.888 . A:ns2.sorbs.net.
[17232] dbg: async: timing: 0.889 . A:ns0.sorbs.net.
[17232] dbg: async: timing: 0.890 . A:zone-ns.dnswl.org.
[17232] dbg: async: timing: 0.891 . A:ns1.sorbs.net.
[17232] dbg: async: timing: 0.907 . A:ns4.nameresolve.com.
[17232] dbg: async: timing: 0.908 . A:ns1.nameresolve.com.
[17232] dbg: async: timing: 0.909 . A:ns2.nameresolve.com.
[17232] dbg: async: timing: 0.909 . A:ns3.nameresolve.com.
[17232] dbg: async: timing: 0.909 . A:ns1.isc-sns.net.
[17232] dbg: async: timing: 0.910 . A:ns.rhyolite.com.
[17232] dbg: async: timing: 0.910 . A:ns2.spamhaus.org.
[17232] dbg: async: timing: 0.912 . A:ns.dcc-servers.net.
[17232] dbg: async: timing: 0.913 . A:ns2.isc-sns.com.
[17232] dbg: async: timing: 0.913 . A:ns3.xs4all.nl.
[17232] dbg: async: timing: 0.914 . A:ns.dns-oarc.net.
[17232] dbg: async: timing: 0.914 . A:ns4.surfnet.nl.
[17232] dbg: async: timing: 0.915 . A:ns8.spamhaus.org.
[17232] dbg: async: timing: 0.915 . A:ns3.spamhaus.org.
[17232] dbg: async: timing: 0.916 . A:ns20.ja.net.
[17232] dbg: async: timing: 0.970 . DNSBL:multi.surbl.org.:spamhaus.org
[17232] dbg: async: timing: 0.977 .
DNSBL:dob.sibl.support-intelligence.net:rhyolite.com
[17232] dbg: async: timing: 21.769 . DNSBL:sbl.spamhaus.org.:1.2.103.38
[17232] dbg: async: timing: 21.770 .
DNSBL:sbl.spamhaus.org.:230.151.75.62
[17232] dbg: async: timing: 21.772 .
DNSBL:sbl.spamhaus.org.:29.14.169.209
[17232] dbg: async: timing: 21.775 .
DNSBL:sbl.spamhaus.org.:35.51.15.203
[17232] dbg: async: timing: 21.776 .
DNSBL:sbl.spamhaus.org.:125.246.106.87
[17232] dbg: async: timing: 21.776 .
DNSBL:sbl.spamhaus.org.:101.9.109.194
[17232] dbg: async: timing: 21.777 . DNSBL:sbl.spamhaus.org.:1.71.52.72
[17232] dbg: async: timing: 21.779 .
DNSBL:sbl.spamhaus.org.:196.117.94.64
[17232] dbg: async: timing: 21.780 .
DNSBL:sbl.spamhaus.org.:227.254.236.62
[17232] dbg: async: timing: 21.804 .
DNSBL:sbl.spamhaus.org.:226.92.198.88
[17232] dbg: async: timing: 21.805 .
DNSBL:sbl.spamhaus.org.:3.61.188.192
[17232] dbg: async: timing: 21.806 .
DNSBL:sbl.spamhaus.org.:66.28.183.69
[17232] dbg: async: timing: 21.806 .
DNSBL:sbl.spamhaus.org.:110.31.94.64
[17232] dbg: async: timing: 21.807 .
DNSBL:sbl.spamhaus.org.:40.152.71.64
[17232] dbg: async: timing: 21.808 .
DNSBL:sbl.spamhaus.org.:239.216.94.82
[17232] dbg: async: timing: 21.809 .
DNSBL:sbl.spamhaus.org.:40.177.70.217
[17232] dbg: async: timing: 21.810 .
DNSBL:sbl.spamhaus.org.:65.58.20.149
[17232] dbg: async: timing: 21.812 .
DNSBL:sbl.spamhaus.org.:5.224.241.207
[17232] dbg: async: timing: 21.813 .
DNSBL:sbl.spamhaus.org.:101.124.169.195
[17232] dbg: async: timing: 21.814 .
DNSBL:sbl.spamhaus.org.:6.174.82.194
[17232] dbg: async: timing: 21.816 .
DNSBL:sbl.spamhaus.org.:82.83.251.63
[17232] dbg: async: timing: 21.817 .
DNSBL:sbl.spamhaus.org.:200.94.150.192
[17232] dbg: async: timing: 21.819 .
DNSBL:sbl.spamhaus.org.:132.161.150.66

and the other one shows:

[17352] dbg: async: timing: 0.048 .
DNSBL:dob.sibl.support-intelligence.net:150.54.13.69
[17352] dbg: async: timing: 0.050 . A:ns2.lax.propagation.net.
[17352] dbg: async: timing: 0.051 . A:ns1.lax.propagation.net.
[17352] dbg: async: timing: 0.052 . A:vns1.propagation.net.
[17352] dbg: async: timing: 0.053 . A:ns3.propagation.net.
[17352] dbg: async: timing: 0.053 . DNSBL:multi.uribl.com.:150.54.13.69
[17352] dbg: async: timing: 0.053 . DNSBL:multi.surbl.org.:150.54.13.69
[17352] dbg: async: timing: 0.053 . A:ns.propagation.net.
[17352] dbg: async: timing: 0.057 . NS:circularsolutions.net
[17352] dbg: async: timing: 0.058 .
DNSBL:dob.sibl.support-intelligence.net:circularsolutions.net
[17352] dbg: async: timing: 0.059 .
DNSBL:multi.uribl.com.:circularsolutions.net
[17352] dbg: async: timing: 0.059 . A:ns4.propagation.net.
[17352] dbg: async: timing: 0.062 . A:ns2.propagation.net.
[17352] dbg: async: timing: 0.063 . A:vns0.propagation.net.
[17352] dbg: async: timing: 0.066 . A:dns2.stabletransit.com.
[17352] dbg: async: timing: 0.069 . A:dns1.stabletransit.com.
[17352] dbg: async: timing: 0.070 . NS:peakperformancesalestraining.com
[17352] dbg: async: timing: 0.071 . A:ns2.isc-sns.com.
[17352] dbg: async: timing: 0.073 . A:ns3.nameresolve.com.
[17352] dbg: async: timing: 0.076 . A:ns.dcc-servers.net.
[17352] dbg: async: timing: 0.080 . A:ns1.nameresolve.com.
[17352] dbg: async: timing: 0.080 . A:ns4.nameresolve.com.
[17352] dbg: async: timing: 0.080 . A:ns.rhyolite.com.
[17352] dbg: async: timing: 0.080 . A:ns2.nameresolve.com.
[17352] dbg: async: timing: 0.081 . A:ns2.ipower.com.
[17352] dbg: async: timing: 0.081 .
DNSBL:multi.uribl.com.:peakperformancesalestraining.com
[17352] dbg: async: timing: 0.082 . A:ns1.isc-sns.net.
[17352] dbg: async: timing: 0.084 . NS:rhyolite.com
[17352] dbg: async: timing: 0.085 . A:ns1.ipower.com.
[17352] dbg: async: timing: 0.085 . DNSBL:multi.surbl.org.:rhyolite.com
[17352] dbg: async: timing: 0.086 . NS:peakperformancellc.com
[17352] dbg: async: timing: 0.087 . NS:barracudacentral.org
[17352] dbg: async: timing: 0.090 .
DNSBL:multi.uribl.com.:peakperformancellc.com
[17352] dbg: async: timing: 0.091 . NS:mailmailer.com
[17352] dbg: async: timing: 0.094 .
DNSBL:dob.sibl.support-intelligence.net:rhyolite.com
[17352] dbg: async: timing: 0.096 .
DNSBL:dob.sibl.support-intelligence.net:barracudacentral.org
[17352] dbg: async: timing: 0.100 .
DNSBL:multi.uribl.com.:mailmailer.com
[17352] dbg: async: timing: 0.100 .
DNSBL:dob.sibl.support-intelligence.net:peakperformancesalestraining.com
[17352] dbg: async: timing: 0.104 .
DNSBL:dob.sibl.support-intelligence.net:peakperformancellc.com
[17352] dbg: async: timing: 0.105 .
DNSBL:multi.surbl.org.:barracudacentral.org
[17352] dbg: async: timing: 0.120 .
DNSBL:dob.sibl.support-intelligence.net:mailmailer.com
[17352] dbg: async: timing: 0.192 . DNSBL:sbl.spamhaus.org.:150.54.13.69
[17352] dbg: async: timing: 0.210 .
DNSBL:multi.surbl.org.:circularsolutions.net
[17352] dbg: async: timing: 0.223 .
DNSBL:multi.surbl.org.:peakperformancesalestraining.com
[17352] dbg: async: timing: 0.245 .
DNSBL:multi.surbl.org.:peakperformancellc.com
[17352] dbg: async: timing: 0.260 .
DNSBL:multi.surbl.org.:mailmailer.com
[17352] dbg: async: timing: 1.120 . DNSBL:sbl.spamhaus.org.:1.2.103.38
[17352] dbg: async: timing: 1.127 . DNSBL:sbl.spamhaus.org.:211.72.20.69
[17352] dbg: async: timing: 1.131 .
DNSBL:sbl.spamhaus.org.:196.117.94.64
[17352] dbg: async: timing: 1.134 .
DNSBL:sbl.spamhaus.org.:10.160.221.216
[17352] dbg: async: timing: 1.141 . DNSBL:sbl.spamhaus.org.:110.31.94.64
[17352] dbg: async: timing: 1.144 .
DNSBL:sbl.spamhaus.org.:204.128.249.63
[17352] dbg: async: timing: 1.146 .
DNSBL:sbl.spamhaus.org.:144.254.254.65
[17352] dbg: async: timing: 1.147 . DNSBL:sbl.spamhaus.org.:1.193.34.66
[17352] dbg: async: timing: 1.154 .
DNSBL:sbl.spamhaus.org.:109.142.96.66
[17352] dbg: async: timing: 1.155 . DNSBL:sbl.spamhaus.org.:1.104.97.216
[17352] dbg: async: timing: 1.158 .
DNSBL:sbl.spamhaus.org.:106.162.221.216
[17352] dbg: async: timing: 1.159 .
DNSBL:sbl.spamhaus.org.:29.14.169.209
[17352] dbg: async: timing: 1.160 . DNSBL:sbl.spamhaus.org.:2.193.34.66
[17352] dbg: async: timing: 1.162 . DNSBL:sbl.spamhaus.org.:1.71.52.72
[17352] dbg: async: timing: 1.164 . DNSBL:sbl.spamhaus.org.:3.61.188.192
[17352] dbg: async: timing: 1.165 . DNSBL:sbl.spamhaus.org.:82.83.251.63
[17352] dbg: async: timing: 1.167 . DNSBL:sbl.spamhaus.org.:1.105.97.216
[17352] dbg: async: timing: 1.177 .
DNSBL:sbl.spamhaus.org.:102.166.61.65
[17352] dbg: async: timing: 1.180 .
DNSBL:sbl.spamhaus.org.:132.161.150.66
[17352] dbg: async: timing: 1.190 .
DNSBL:sbl.spamhaus.org.:203.128.249.63
[17352] dbg: async: timing: 1.451 . DNSBL:multi.uribl.com.:rhyolite.com
[17352] dbg: async: timing: 1.480 .
DNSBL:multi.uribl.com.:barracudacentral.org

Using a local caching nameserver with 127.0.0.1 as my nameserver, BIND
9.5.0-P2, Net::DNS 0.65. I notice that the slowest one shows:

[14035] dbg: dns: is Net::DNS::Resolver available? yes
[14035] dbg: dns: Net::DNS version: 0.63
[14035] dbg: dns: name server: 127.0.0.1, LocalAddr: 0.0.0.0
[14035] dbg: dns: resolver socket rx buffer size is 112640 bytes
[14035] dbg: dns: dns_available set to yes in config file, skipping test
[14035] dbg: uridnsbl: domain spamcop.net in skip list
[14035] dbg: uridnsbl: domain sf.net in skip list
[14035] dbg: uridnsbl: domain spamcop.net in skip list
[14035] dbg: uridnsbl: domain spamcop.net in skip list
[14035] dbg: uridnsbl: domain sf.net in skip list
[14035] dbg: uridnsbl: domains to query: barracudacentral.org dnswl.org
rhyolite.com spamhaus.org

and the faster one shows:

[17352] dbg: dns: is Net::DNS::Resolver available? yes
[17352] dbg: dns: Net::DNS version: 0.65
[17352] dbg: dns: name server: 127.0.0.1, LocalAddr: 0.0.0.0
[17352] dbg: dns: resolver socket rx buffer size is 112640 bytes
[17352] dbg: dns: dns_available set to yes in config file, skipping test
[17352] dbg: uridnsbl: domain sf.net in skip list
[17352] dbg: uridnsbl: domains to query: barracudacentral.org
mailmailer.com peakperformancellc.com rhyolite.com
peakperformancesalestraining.com circularsolutions.net 69.13.54.150

For the longest I've been seeing average scan times like this:

Email: 35  Autolearn:     0  AvgScore:  13.34  AvgScanTime: 14.78 sec
Spam:  14  Autolearn:     0  AvgScore:  38.43  AvgScanTime: 15.16 sec
Ham:   21  Autolearn:     0  AvgScore:  -3.38  AvgScanTime: 14.53 sec

Why the difference in skip list. These may sound like lame questions but
I'm really curious now that I see a marked difference between two
messages in lookup times. 

-- 
KeyID 0xE372A7DA98E6705C


Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by John Hardin <jh...@impsec.org>.
On Wed, 1 Apr 2009, alexus wrote:

> On Wed, Apr 1, 2009 at 5:52 PM, John Hardin <jh...@impsec.org> wrote:
>
>> How fast are non-SA DNS queries on that box? If they take ten seconds 
>> to return an answer, SA is not the culprit.
>
> without dns they are 0.1 - 1.5s, with DNS they are ~7s

...what precisely do you mean by "with DNS" and "without DNS"?

>> Review your /etc/resolv.conf to see if the first resolver listed is
>> responding quickly. You may want to rearrange them.
>
> I use local caching, so it's as fast as it gets

So /etc/resolv.conf has 127.0.0.1 as the only resolver?

-- 
  John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
  jhardin@impsec.org    FALaholic #11174     pgpk -a jhardin@impsec.org
  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
   For those who are being swayed by Microsoft's whining about the
   GPL, consider how aggressively viral their Shared Source license is:
   If you've *ever* seen *any* MS code covered by the Shared Source
   license, you're infected for life. MS can sue you for Intellectual
   Property misappropriation whenever they like, so you'd better not
   come up with any Innovative Ideas that they want to Embrace...
-----------------------------------------------------------------------
  Today: April Fools' day

Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by John Hardin <jh...@impsec.org>.
On Wed, 8 Apr 2009, alexus wrote:

> On Sat, Apr 4, 2009 at 5:48 AM, Matus UHLAR - fantomas
> <uh...@fantomas.sk> wrote:
>>> On Wed, Apr 1, 2009 at 5:52 PM, John Hardin <jh...@impsec.org> wrote:
>>>> How fast are non-SA DNS queries on that box? If they take ten seconds to
>>>> return an answer, SA is not the culprit.
>>
>> On 01.04.09 17:53, alexus wrote:
>>> without dns they are 0.1 - 1.5s, with DNS they are ~7s
>>
>> by "non-SA DNS" he did not mean SA without DNS, but DNS without SA... just
>> FYI.
>
> what I meant is SA without this:
>
> v320.pre:loadplugin Mail::SpamAssassin::Plugin::DNSEval

Are your scan times still bouncing around? Or did you turn DNS off again?

(The story so far: offlist we verified a local DNS cache was being used 
and SA was brought up-to-date - dsbl was still being queried, sa-update 
fixed that. Now the scan times are inconsistent - some short
~1sec, some long ~6sec.)

-- 
  John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
  jhardin@impsec.org    FALaholic #11174     pgpk -a jhardin@impsec.org
  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
   You can't reason a person out of a position if he didn't use
   reason to get there in the first place.   -- Kristopher, at Marko's
-----------------------------------------------------------------------
  5 days until Thomas Jefferson's 266th Birthday

Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by alexus <al...@gmail.com>.
On Wed, Apr 8, 2009 at 12:04 PM, Matus UHLAR - fantomas
<uh...@fantomas.sk> wrote:
>> On Wed, Apr 8, 2009 at 11:21 AM, Matus UHLAR - fantomas
>> <uh...@fantomas.sk> wrote:
>> >> On Sat, Apr 4, 2009 at 5:48 AM, Matus UHLAR - fantomas
>> >> <uh...@fantomas.sk> wrote:
>> >> >> On Wed, Apr 1, 2009 at 5:52 PM, John Hardin <jh...@impsec.org> wrote:
>> >> >> > How fast are non-SA DNS queries on that box? If they take ten seconds to
>> >> >> > return an answer, SA is not the culprit.
>> >> >
>> >> > On 01.04.09 17:53, alexus wrote:
>> >> >> without dns they are 0.1 - 1.5s, with DNS they are ~7s
>> >> >
>> >> > by "non-SA DNS" he did not mean SA without DNS, but DNS without SA... just
>> >> > FYI.
>> >
>> > On 08.04.09 10:21, alexus wrote:
>> >> what I meant is SA without this:
>> >>
>> >> v320.pre:loadplugin Mail::SpamAssassin::Plugin::DNSEval
>> >
>> > what HE (Josh Hardin) meant, is:
>> >
>> > dig www.microsoft.com.
>> > dig 66.36.168.195.zen.spamhaus.org
>> > dig mx surbl.org
>> >
>> > and look at the "Query time" result.
>
> On 08.04.09 11:40, alexus wrote:
>> root@mx1 ~ 503$ time dig www.microsoft.com.
>> ;; Query time: 0 msec
>
>> root@mx1 ~ 504$ time dig 66.36.168.195.zen.spamhaus.org
>> ;; Query time: 288 msec
>
>> root@mx1 ~ 505$ time dig mx surbl.org
>> ;; Query time: 80 msec
>
> seems good. But I think that your problem has been solved or am I wrong?
> At least you have learned what means "dns without spamassassin" :-)--

yeah, my spam assassin seems to be acting up all right.... go figure ;-)

> Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
> Warning: I wish NOT to receive e-mail advertising to this address.
> Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
> Fighting for peace is like fucking for virginity...
>



-- 
http://alexus.org/

Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by Matus UHLAR - fantomas <uh...@fantomas.sk>.
> On Wed, Apr 8, 2009 at 11:21 AM, Matus UHLAR - fantomas
> <uh...@fantomas.sk> wrote:
> >> On Sat, Apr 4, 2009 at 5:48 AM, Matus UHLAR - fantomas
> >> <uh...@fantomas.sk> wrote:
> >> >> On Wed, Apr 1, 2009 at 5:52 PM, John Hardin <jh...@impsec.org> wrote:
> >> >> > How fast are non-SA DNS queries on that box? If they take ten seconds to
> >> >> > return an answer, SA is not the culprit.
> >> >
> >> > On 01.04.09 17:53, alexus wrote:
> >> >> without dns they are 0.1 - 1.5s, with DNS they are ~7s
> >> >
> >> > by "non-SA DNS" he did not mean SA without DNS, but DNS without SA... just
> >> > FYI.
> >
> > On 08.04.09 10:21, alexus wrote:
> >> what I meant is SA without this:
> >>
> >> v320.pre:loadplugin Mail::SpamAssassin::Plugin::DNSEval
> >
> > what HE (Josh Hardin) meant, is:
> >
> > dig www.microsoft.com.
> > dig 66.36.168.195.zen.spamhaus.org
> > dig mx surbl.org
> >
> > and look at the "Query time" result.

On 08.04.09 11:40, alexus wrote:
> root@mx1 ~ 503$ time dig www.microsoft.com.
> ;; Query time: 0 msec

> root@mx1 ~ 504$ time dig 66.36.168.195.zen.spamhaus.org
> ;; Query time: 288 msec

> root@mx1 ~ 505$ time dig mx surbl.org
> ;; Query time: 80 msec

seems good. But I think that your problem has been solved or am I wrong? 
At least you have learned what means "dns without spamassassin" :-)-- 
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Fighting for peace is like fucking for virginity...

Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by alexus <al...@gmail.com>.
On Wed, Apr 8, 2009 at 11:21 AM, Matus UHLAR - fantomas
<uh...@fantomas.sk> wrote:
>> On Sat, Apr 4, 2009 at 5:48 AM, Matus UHLAR - fantomas
>> <uh...@fantomas.sk> wrote:
>> >> On Wed, Apr 1, 2009 at 5:52 PM, John Hardin <jh...@impsec.org> wrote:
>> >> > How fast are non-SA DNS queries on that box? If they take ten seconds to
>> >> > return an answer, SA is not the culprit.
>> >
>> > On 01.04.09 17:53, alexus wrote:
>> >> without dns they are 0.1 - 1.5s, with DNS they are ~7s
>> >
>> > by "non-SA DNS" he did not mean SA without DNS, but DNS without SA... just
>> > FYI.
>
> On 08.04.09 10:21, alexus wrote:
>> what I meant is SA without this:
>>
>> v320.pre:loadplugin Mail::SpamAssassin::Plugin::DNSEval
>
> what HE (Josh Hardin) meant, is:
>
> dig www.microsoft.com.
> dig 66.36.168.195.zen.spamhaus.org
> dig mx surbl.org
>
> and look at the "Query time" result.

root@mx1 ~ 503$ time dig www.microsoft.com.

; <<>> DiG 9.4.2-P2 <<>> www.microsoft.com.
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61055
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 9, ADDITIONAL: 4

;; QUESTION SECTION:
;www.microsoft.com.             IN      A

;; ANSWER SECTION:
www.microsoft.com.      3586    IN      CNAME   toggle.www.ms.akadns.net.
toggle.www.ms.akadns.net. 287   IN      CNAME   g.www.ms.akadns.net.
g.www.ms.akadns.net.    287     IN      CNAME   lb1.www.ms.akadns.net.
lb1.www.ms.akadns.net.  287     IN      A       207.46.19.254
lb1.www.ms.akadns.net.  287     IN      A       207.46.19.190

;; AUTHORITY SECTION:
akadns.net.             172786  IN      NS      use3.akadns.net.
akadns.net.             172786  IN      NS      zc.akadns.org.
akadns.net.             172786  IN      NS      use4.akadns.net.
akadns.net.             172786  IN      NS      usw2.akadns.net.
akadns.net.             172786  IN      NS      za.akadns.org.
akadns.net.             172786  IN      NS      asia9.akadns.net.
akadns.net.             172786  IN      NS      zd.akadns.org.
akadns.net.             172786  IN      NS      zb.akadns.org.
akadns.net.             172786  IN      NS      eur1.akadns.net.

;; ADDITIONAL SECTION:
za.akadns.org.          21587   IN      A       213.254.204.197
zb.akadns.org.          21587   IN      A       12.183.125.5
zc.akadns.org.          21587   IN      A       124.40.52.133
zd.akadns.org.          21587   IN      A       204.2.178.133

;; Query time: 0 msec
;; SERVER: 64.237.55.72#53(64.237.55.72)
;; WHEN: Wed Apr  8 15:38:53 2009
;; MSG SIZE  rcvd: 377


real    0m0.006s
user    0m0.000s
sys     0m0.006s
root@mx1 ~ 504$ time dig 66.36.168.195.zen.spamhaus.org

; <<>> DiG 9.4.2-P2 <<>> 66.36.168.195.zen.spamhaus.org
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34009
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;66.36.168.195.zen.spamhaus.org.        IN      A

;; AUTHORITY SECTION:
zen.spamhaus.org.       150     IN      SOA     need.to.know.only.
hostmaster.spamhaus.org. 2009040862 3600 600 432000 150

;; Query time: 288 msec
;; SERVER: 64.237.55.72#53(64.237.55.72)
;; WHEN: Wed Apr  8 15:38:58 2009
;; MSG SIZE  rcvd: 112


real    0m0.294s
user    0m0.000s
sys     0m0.006s
root@mx1 ~ 505$ time dig mx surbl.org

; <<>> DiG 9.4.2-P2 <<>> mx surbl.org
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48545
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 1

;; QUESTION SECTION:
;surbl.org.                     IN      MX

;; ANSWER SECTION:
surbl.org.              3600    IN      MX      10 mx1.prolexic.com.
surbl.org.              3600    IN      MX      20 mx2.prolexic.com.
surbl.org.              3600    IN      MX      30 mx3.prolexic.com.

;; AUTHORITY SECTION:
surbl.org.              45747   IN      NS      ns201.surbl.org.
surbl.org.              45747   IN      NS      ns200.surbl.org.
surbl.org.              45747   IN      NS      ns101.surbl.org.
surbl.org.              45747   IN      NS      ns100.surbl.org.

;; ADDITIONAL SECTION:
ns201.surbl.org.        45747   IN      A       192.42.119.21

;; Query time: 80 msec
;; SERVER: 64.237.55.72#53(64.237.55.72)
;; WHEN: Wed Apr  8 15:39:05 2009
;; MSG SIZE  rcvd: 195


real    0m0.086s
user    0m0.000s
sys     0m0.006s
root@mx1 ~ 506$


> --
> Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
> Warning: I wish NOT to receive e-mail advertising to this address.
> Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
> "One World. One Web. One Program." - Microsoft promotional advertisement
> "Ein Volk, ein Reich, ein Fuhrer!" - Adolf Hitler
>



-- 
http://alexus.org/

Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by Matus UHLAR - fantomas <uh...@fantomas.sk>.
> On Sat, Apr 4, 2009 at 5:48 AM, Matus UHLAR - fantomas
> <uh...@fantomas.sk> wrote:
> >> On Wed, Apr 1, 2009 at 5:52 PM, John Hardin <jh...@impsec.org> wrote:
> >> > How fast are non-SA DNS queries on that box? If they take ten seconds to
> >> > return an answer, SA is not the culprit.
> >
> > On 01.04.09 17:53, alexus wrote:
> >> without dns they are 0.1 - 1.5s, with DNS they are ~7s
> >
> > by "non-SA DNS" he did not mean SA without DNS, but DNS without SA... just
> > FYI.

On 08.04.09 10:21, alexus wrote:
> what I meant is SA without this:
> 
> v320.pre:loadplugin Mail::SpamAssassin::Plugin::DNSEval

what HE (Josh Hardin) meant, is:

dig www.microsoft.com.
dig 66.36.168.195.zen.spamhaus.org
dig mx surbl.org

and look at the "Query time" result.

-- 
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"One World. One Web. One Program." - Microsoft promotional advertisement
"Ein Volk, ein Reich, ein Fuhrer!" - Adolf Hitler

Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by alexus <al...@gmail.com>.
On Sat, Apr 4, 2009 at 5:48 AM, Matus UHLAR - fantomas
<uh...@fantomas.sk> wrote:
>> On Wed, Apr 1, 2009 at 5:52 PM, John Hardin <jh...@impsec.org> wrote:
>> > How fast are non-SA DNS queries on that box? If they take ten seconds to
>> > return an answer, SA is not the culprit.
>
> On 01.04.09 17:53, alexus wrote:
>> without dns they are 0.1 - 1.5s, with DNS they are ~7s
>
> by "non-SA DNS" he did not mean SA without DNS, but DNS without SA... just
> FYI.

what I meant is SA without this:

v320.pre:loadplugin Mail::SpamAssassin::Plugin::DNSEval


> --
> Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
> Warning: I wish NOT to receive e-mail advertising to this address.
> Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
> There's a long-standing bug relating to the x86 architecture that
> allows you to install Windows.   -- Matthew D. Fuller
>



-- 
http://alexus.org/

Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by Matus UHLAR - fantomas <uh...@fantomas.sk>.
> On Wed, Apr 1, 2009 at 5:52 PM, John Hardin <jh...@impsec.org> wrote:
> > How fast are non-SA DNS queries on that box? If they take ten seconds to
> > return an answer, SA is not the culprit.

On 01.04.09 17:53, alexus wrote:
> without dns they are 0.1 - 1.5s, with DNS they are ~7s

by "non-SA DNS" he did not mean SA without DNS, but DNS without SA... just
FYI.
-- 
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
There's a long-standing bug relating to the x86 architecture that
allows you to install Windows.   -- Matthew D. Fuller

Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by alexus <al...@gmail.com>.
On Wed, Apr 1, 2009 at 5:52 PM, John Hardin <jh...@impsec.org> wrote:
> On Wed, 1 Apr 2009, alexus wrote:
>
>> okay, we like really far away from original thread, i said that
>> SpamAssassin runs really slow for me and on top of that I even found which
>> plugin causing that, which is this:
>>
>> loadplugin Mail::SpamAssassin::Plugin::DNSEval
>>
>> I had to disable it, if someone can suggest something in order to make it
>> work faster i'm all ears
>
> How fast are non-SA DNS queries on that box? If they take ten seconds to
> return an answer, SA is not the culprit.

without dns they are 0.1 - 1.5s, with DNS they are ~7s

> Review your /etc/resolv.conf to see if the first resolver listed is
> responding quickly. You may want to rearrange them.

I use local caching, so it's as fast as it gets

> It's good practice to use a local caching DNS server. Are you resolving via
> a caching DNS server on your local network, or is the SA box resolving
> directly via your ISP DNS servers or other public DNS servers? If the
> latter, consider installing a caching DNS server on the SA box and use that
> for name resolution.
>
> --
>  John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
>  jhardin@impsec.org    FALaholic #11174     pgpk -a jhardin@impsec.org
>  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
> -----------------------------------------------------------------------
>  ...in the 2nd amendment the right to arms clause means you have
>  the right to choose how many arms you want, and the militia clause
>  means that Congress can punish you if the answer is "none."
>                                -- David Hardy, 2nd Amendment scholar
> -----------------------------------------------------------------------
>  Today: April Fools' day
>



-- 
http://alexus.org/

Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by John Hardin <jh...@impsec.org>.
On Wed, 1 Apr 2009, alexus wrote:

> okay, we like really far away from original thread, i said that 
> SpamAssassin runs really slow for me and on top of that I even found 
> which plugin causing that, which is this:
>
> loadplugin Mail::SpamAssassin::Plugin::DNSEval
>
> I had to disable it, if someone can suggest something in order to make 
> it work faster i'm all ears

How fast are non-SA DNS queries on that box? If they take ten seconds to 
return an answer, SA is not the culprit.

Review your /etc/resolv.conf to see if the first resolver listed is 
responding quickly. You may want to rearrange them.

It's good practice to use a local caching DNS server. Are you resolving 
via a caching DNS server on your local network, or is the SA box resolving 
directly via your ISP DNS servers or other public DNS servers? If the 
latter, consider installing a caching DNS server on the SA box and use 
that for name resolution.

-- 
  John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
  jhardin@impsec.org    FALaholic #11174     pgpk -a jhardin@impsec.org
  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
   ...in the 2nd amendment the right to arms clause means you have
   the right to choose how many arms you want, and the militia clause
   means that Congress can punish you if the answer is "none."
                                 -- David Hardy, 2nd Amendment scholar
-----------------------------------------------------------------------
  Today: April Fools' day

Re: [OT] Re: SpamAssassin is EXTREMLY slow

Posted by alexus <al...@gmail.com>.
On Wed, Apr 1, 2009 at 4:49 PM, David Morton <mo...@dgrmm.net> wrote:
> Karsten Bräckelmann wrote:
>> On Fri, 2009-03-27 at 23:59 +0200, Jari Fredriksson wrote:
>>> I just hope that as good as SA is will be written in some programming
>>> language, and not scripting language. Even Java would be better.
>>
>> Dude, you just lost a credit point... ;)
>>
>> Everyone, if you feel the urge to contribute to this thread any further,
>> please first *do* check the list archives -- this pointless thread comes
>> up like once a year. If you believe you can come up with a convincing
>> argument that has *not* been mentioned and turned down before, and which
>> takes "active contributors code Perl" into account... please try.
>
> Agreed. Anytime anyone starts talking about speed and languages, I roll
> my eyes.  Seriously, unless you are a developer and have actually run
> code through a profiler to know what areas are running "slow", you are
> not qualified to make such statements.
>
> If you *have* run the code through a profiler and can prove that a
> majority of time is spent inside a language construct and not on I/O or
> a bad algorithm, then you are qualified... to submit a bug report to the
> language developers so they can fix it.  Anything else is just bogus.
>
>

okay, we like really far away from original thread, i said that
SpamAssassin runs really slow for me and on top of that I even found
which plugin causing that, which is this:

loadplugin Mail::SpamAssassin::Plugin::DNSEval

I had to disable it, if someone can suggest something in order to make
it work faster i'm all ears

-- 
http://alexus.org/