Re: Boost up Spamassassin option
> On another paw, more memory is generally a good way to speed up the > spamassassin operation. A good DNS setup is also required so that you > do not get delays in DNS lookups. Do not select DNS tests for sites > that no longer exist. That is a major slow down. > sorry, i cant follow you, where can i read something about this topic? > Now, when you complain about speeds how about some numbers. What is > the processor speed, what is the amount of memory, what other things > run on the computer, how long is "spamassassin --lint" taking, how > long is a typical message processing take, and so forth. Give us > something to work with. THen we can tell you what is wrong. Of > particular interest are non-stock things you are doing. Did you add > additional DNS tests, for example? > first of all im not complaining, this is a misunderstanding. i just want to help a little in the development of SA. im new in this list, so never heard about this idea before ;) here are the facts: amd3000+, 512 MB, desktop pc, lint takes 5 secs, id guess a typical messages takes about 25 secs. im using the standard configuration file, so from my side i didnt add any other tests like dns. theres no nameserver running on my pc. just thougt, it would be very simple to stop testing at the right moment, but it seems like i know to few about this filtering process. -- MUM, CAN I GO OUT AND CODE TONIGHT?
Boost up Spamassassin option
Hi, does anyone know about a option which speeds up spamassassin extremly: order the tests: fastest first, getting slower , slowest is the last test in the list (dns perhaps, razor, pyzor, dcc). and now: stop testing the mail, as soon as spamscore is greater than needed to be marked as a spam mail. i dont want to know if this mail has got 30 points, im just interested in a decision between spam and not spam. regards s. -- "UNIX ist benutzerfreundlich - es ist nur etwas wählerisch..." (Walter Misar)
Re: [solved] DNS lookup fails
Am Sonntag, 12. Juni 2005 09:09 schrieb Stefan Ewert: > Am Sonntag, 12. Juni 2005 01:39 schrieb Thomas Cameron: > > On Sat, 2005-06-11 at 18:41 +0200, Stefan Ewert wrote: > > > but as you can see im using dns version 0.51 and it doesnt work for me. > > > so if anyone has another suggest id happy to hear about it ;) > > > > 0.51 didn't work for me, either on RHEL 2.1. I had to downgrade to > > http://www.net-dns.org/download/Net-DNS-0.48_01.tar.gz. 0.48_3 was > > b0rken for me, too. > > ok i downgraded to 0.48_1 and now it works for me too. should i file a > bugreport or did anyone of you already do this? hi, one add from me: i upgraded to Net::DNS 0.49 (the last one thats working AFAIK) and changed in my /etc/nsswitch.conf the following: hosts: files dns to hosts: dns files now the first nameserver in resolv.conf isnt localhost anymore and dhcp is working fine too! have a nice week
Re: DNS lookup fails
Am Sonntag, 12. Juni 2005 01:39 schrieb Thomas Cameron: > On Sat, 2005-06-11 at 18:41 +0200, Stefan Ewert wrote: > > but as you can see im using dns version 0.51 and it doesnt work for me. > > so if anyone has another suggest id happy to hear about it ;) > > 0.51 didn't work for me, either on RHEL 2.1. I had to downgrade to > http://www.net-dns.org/download/Net-DNS-0.48_01.tar.gz. 0.48_3 was > b0rken for me, too. > ok i downgraded to 0.48_1 and now it works for me too. should i file a bugreport or did anyone of you already do this? -- Microsoft's biggest and most dangerous contribution to the software industry may be the degree to which it has lowered user expectations.
Re: DNS lookup fails
Am Samstag, 11. Juni 2005 19:13 schrieb Kenneth Porter: > --On Saturday, June 11, 2005 7:03 PM +0200 Stefan Ewert <[EMAIL PROTECTED]> > > wrote: > > here ist my resolv.conf: > > > > nameserver 127.0.0.1 > > nameserver 217.237.151.161 > > nameserver 217.237.151.33 > > > > after every reboot, localhost is in first place, so every querie takes > > some time before the second nameserver is asked. > > how do i cache values? i can run spamassassin --lint -D as often as i > > want, nothing changes in this issue. > > Why are you listing anything besides 127.0.0.1? That's only useful if your > local nameserver is down. In that case just make another resolve.conf to > install until you fix your nameserver. this is a single pc, so i think its better to use a nameserver from the www. i dont have a local nameserver running( i think ;). do i need a local nameserver? the problem is every time i delete this 127.0.01 and i reboot this line is there again.
Re: DNS lookup fails
Am Samstag, 11. Juni 2005 18:43 schrieb [EMAIL PROTECTED]: > Hi, > > I noticed exactly the same yesterday, and when I tried again it worked. > So I would assume that Net::DNS uses some timeouts which are rather short, > to retrieve data from my local dns cache Second time through, it will get > cached values sooperfast and be happy > here ist my resolv.conf: nameserver 127.0.0.1 nameserver 217.237.151.161 nameserver 217.237.151.33 after every reboot, localhost is in first place, so every querie takes some time before the second nameserver is asked. how do i cache values? i can run spamassassin --lint -D as often as i want, nothing changes in this issue. -- "UNIX ist benutzerfreundlich - es ist nur etwas wählerisch..." (Walter Misar)
Re: DNS lookup fails
Am Samstag, 11. Juni 2005 18:03 schrieb Stefan Ewert:
> Hi,
> im running spamassassin --lint -D and get the following error:
> debug: is Net::DNS::Resolver available? yes
> debug: Net::DNS version: 0.51
> debug: trying (3) motorola.com...
> debug: looking up NS for 'motorola.com'
> debug: NS lookup of motorola.com failed horribly => Perhaps your
> resolv.conf isn't pointing at a valid server?
> debug: All NS queries failed => DNS unavailable (set dns_available to
> override)
> debug: is DNS available? 0
>
> I got SA version 3.0.3 and the nameserver in resolv.conf are ok.
> can u tell me where to search for the problem.
> NET::DNS works also, i tried this with a small perl script:
> #!/usr/bin/perl -w
>
> use Net::DNS;
>
> $domain = $ARGV[0] || die "usage: $0 domain";
>
> $resolver = new Net::DNS::Resolver;
>
> # MX-Record abfragen
> @mx = mx($resolver, $domain);
>
> if (@mx) {
> # Erfolg! Über alle Resource Records iterieren
> foreach $rr (@mx) {
> print $rr->preference, " ",
>$rr->exchange, "\n";
> }
> } else {
> # Leere Liste, Fehler!
> print "Kein MX-Record für $domain: ",
>$resolver->errorstring, "\n";
> }
>
i got the following answer (pm):
Hi,
As was mentioned yesterday on the list, Net::DNS 0.50 seems to be
broken. If you are running 0.50, upgrade to 0.51 or downgrade to 0.48
end of mail
but as you can see im using dns version 0.51 and it doesnt work for me. so if
anyone has another suggest id happy to hear about it ;)
DNS lookup fails
Hi,
im running spamassassin --lint -D and get the following error:
debug: is Net::DNS::Resolver available? yes
debug: Net::DNS version: 0.51
debug: trying (3) motorola.com...
debug: looking up NS for 'motorola.com'
debug: NS lookup of motorola.com failed horribly => Perhaps your resolv.conf
isn't pointing at a valid server?
debug: All NS queries failed => DNS unavailable (set dns_available to
override)
debug: is DNS available? 0
I got SA version 3.0.3 and the nameserver in resolv.conf are ok.
can u tell me where to search for the problem.
NET::DNS works also, i tried this with a small perl script:
#!/usr/bin/perl -w
use Net::DNS;
$domain = $ARGV[0] || die "usage: $0 domain";
$resolver = new Net::DNS::Resolver;
# MX-Record abfragen
@mx = mx($resolver, $domain);
if (@mx) {
# Erfolg! Über alle Resource Records iterieren
foreach $rr (@mx) {
print $rr->preference, " ",
$rr->exchange, "\n";
}
} else {
# Leere Liste, Fehler!
print "Kein MX-Record für $domain: ",
$resolver->errorstring, "\n";
}
thanks for help
stefan
--
The remaining work to finish in order to reach your goal increases as
the deadline approaches
-- Murphy's Laws of Computation n°1
