On 05/03/2008 5:44 AM, Johann Spies wrote:
> On Thu, Feb 28, 2008 at 02:44:02PM +0200, Johann Spies wrote:
>> On a new mailserver with 8Gb ram and 2xdual-core CPU's we get regular
>> messages in the log:
>>
>> Feb 28 12:52:43 mail2 spamd[32558]: prefork: child states: BIBBB
>> Feb 28 12:52:44 mail2
On Thu, Feb 28, 2008 at 02:44:02PM +0200, Johann Spies wrote:
> On a new mailserver with 8Gb ram and 2xdual-core CPU's we get regular
> messages in the log:
>
> Feb 28 12:52:43 mail2 spamd[32558]: prefork: child states: BIBBB
> Feb 28 12:52:44 mail2 spamd[459]: rules: failed to run TVD_STOCK1 test
On a new mailserver with 8Gb ram and 2xdual-core CPU's we get regular
messages in the log:
Feb 28 12:52:43 mail2 spamd[32558]: prefork: child states: BIBBB
Feb 28 12:52:44 mail2 spamd[459]: rules: failed to run TVD_STOCK1 test,
skipping:
Feb 28 12:52:44 mail2 spamd[459]: (child processing timeou
Tony Houghton wrote:
> Bob Proulx wrote:
> > Check /etc/resolv.conf for nameserver entries and modify or
> > change the file as needed to say 'nameserver 0.0.0.0' (okay to use
> > 'nameserver 127.0.0.1' with modern software too). See the wiki page
> > for general information.
>
> I hadn't heard o
Nigel Kendrick wrote:
Strangely enough I have been looking at why SA has suddenly started to act
up and I also seem to be having DNS timeout issues after years of faultless
operation. I am running a local caching nameserver, but spamassassin -D just
stops dead as follows:
Unless you hit ctrl+
Hm, it really is that easy. I've got used to this culture that complex
packages won't do anything useful until configured so that's why I was
reluctant to install bind, thinking it would take up a lot of time and
effort.
Anyway, it's helped. It seems to take about 5 seconds per message
instead
In <[EMAIL PROTECTED]>, Bob Proulx wrote:
> For your Debian machine it is very easy with the following commands.
>
> $ sudo apt-get update
> $ sudo apt-get install bind9
>
> The default package configuration is a caching nameserver and the
> above commands should be all that is needed to set
Strangely enough I have been looking at why SA has suddenly started to act
up and I also seem to be having DNS timeout issues after years of faultless
operation. I am running a local caching nameserver, but spamassassin -D just
stops dead as follows:
[8808] dbg: logger: adding facilities: all
[8
Tony Houghton wrote:
> Gary V wrote:
> > Tony Houghton wrote:
> > > Gary V wrote:
> > > > What OS are you running?
> > >
> > > Linux.
Sigh.
> > Exactly which distrubution and version of that distribution?
>
> Sorry, Debian unstable amd64.
Setting up a caching nameserver is documented for variou
In <[EMAIL PROTECTED]>, Gary V wrote:
> >Gary V wrote:
> >
> >> As mentioned twice, use a local caching DNS server (like bind for
> >> example). Even if configured to forward requests to your ISP's DNS
> >> server it may make a big difference. What OS are you running?
> >
> >Linux.
>
> Exactly
Gary V wrote:
> As mentioned twice, use a local caching DNS server (like bind for
example).
> Even if configured to forward requests to your ISP's DNS server it may
make
> a big difference. What OS are you running?
Linux.
--
TH * http://www.realh.co.uk
Exactly which distrubution and versio
In <[EMAIL PROTECTED]>, SM wrote:
> At 06:10 07-07-2007, Tony Houghton wrote:
> >SA used to kill a different router I used to have, but I don't think
> >that's the problem here. I temporarily pointed /etc/resolv.conf to my
> >ISP's servers and restarted spamd, which you'd expect to make at least
>
In <[EMAIL PROTECTED]>, Gary V wrote:
> As mentioned twice, use a local caching DNS server (like bind for example).
> Even if configured to forward requests to your ISP's DNS server it may make
> a big difference. What OS are you running?
Linux.
--
TH * http://www.realh.co.uk
At 06:10 07-07-2007, Tony Houghton wrote:
SA used to kill a different router I used to have, but I don't think
that's the problem here. I temporarily pointed /etc/resolv.conf to my
ISP's servers and restarted spamd, which you'd expect to make at least
some difference, but it didn't really. Beside
At 06:10 07-07-2007, Tony Houghton wrote:
SA used to kill a different router I used to have, but I don't think
that's the problem here. I temporarily pointed /etc/resolv.conf to my
ISP's servers and restarted spamd, which you'd expect to make at least
some difference, but it didn't really. Beside
Tony Houghton wrote:
> I switch my PC off overnight and I noticed the router would crash
> shortly after switching it back on and deduced it was because of the
> large volume of mail being fetched in one go. It was OK if I got my
> PC to use my ISP's DNS instead.
Strange. Frankly that just seems
In <[EMAIL PROTECTED]>, Bob Proulx wrote:
> Tony Houghton wrote:
> > SA used to kill a different router I used to have, but I don't think
> > that's the problem here.
>
> I don't see how even a low end router would have a problem with the
> amount of data from DNS lookups that could be generated.
Tony Houghton wrote:
> SA used to kill a different router I used to have, but I don't think
> that's the problem here.
I don't see how even a low end router would have a problem with the
amount of data from DNS lookups that could be generated. It must have
been something else.
> I temporarily po
In <[EMAIL PROTECTED]>, SM wrote:
> Hi Tony,
> At 15:01 06-07-2007, Tony Houghton wrote:
> >I just use the one built in to my ADSL router; I don't know whether it
> >caches. The one it forwards to at my ISP is probably bind.
>
> The DNS server on your ADSL router is built for residential
> usage
Hi Tony,
At 15:01 06-07-2007, Tony Houghton wrote:
I just use the one built in to my ADSL router; I don't know whether it
caches. The one it forwards to at my ISP is probably bind.
The DNS server on your ADSL router is built for residential
usage. If you are going to do a lot of DNS queries,
In <[EMAIL PROTECTED]>, James D. Rallo wrote:
> Are you running a local dns caching server?
I just use the one built in to my ADSL router; I don't know whether it
caches. The one it forwards to at my ISP is probably bind.
> Do manual queries to rbls take a long time? (Hint: Don't run the query
>
dns check.
Thanks,
James
> -Original Message-
> From: Tony Houghton [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 06, 2007 4:12 PM
> To: users@spamassassin.apache.org
> Subject: DNS timeout problem
>
> I'm having a problem with spamassassin taking ages due to DN
I'm having a problem with spamassassin taking ages due to DNS lookups
timing out. I could make the timeout shorter, but I'd rather try to find
out what it's failing on and stop it trying to do those lookups. I've
made a log of its debugging output (attached) but I don't understand it
well enough to
Hello,
I have problem with timeouts on FreeBSD 5.2 with milter-spamc-0.25
(spamass-milter-0.2.0_5 same problem too), p5-Mail-SpamAssassin-3.0.2 .
When I get spam with "X-SpamDetected:1" in header, I get following error
in my maillog :
milter-spamc[585]:timeout before input from SPAMD server
mi
24 matches
Mail list logo
