Hi,
> The reported stackdump just shows a routine that was executing at
> the time when timer expired. It often shows the problem section
> (like a database access), but may just show an innocent bystander
> code which happened to be normally executing at the time.
Great, thanks. How about from a
Alex,
> I have a server that's frequently pretty busy during the day, and just
> started to notice these messages periodically:
>
> Jun 8 13:35:39 mail01 amavis[28784]: (28784-272) SA TIMED OUT,
> backtrace: at /usr/lib/perl5/5.6.0/i386-linux/IO/Select.pm line
> 104\n\tI
Hi,
I have a server that's frequently pretty busy during the day, and just
started to notice these messages periodically:
Jun 8 13:35:39 mail01 amavis[28784]: (28784-272) SA TIMED OUT,
backtrace: at /usr/lib/perl5/5.6.0/i386-linux/IO/Select.pm line
104\n\tIO::Select::can_read('IO::Se
wild_oscar schrieb:
> I might leave it at that. The problem that I've been scratching my head
> about is why does it work when using the nameserver directly but not when
> using the router's IP address, which is forwarding to the same address.
> It might be a problem with the router, although it
same address.
It might be a problem with the router, although it is a brand new d-link
dva-g3170i.
--
View this message in context:
http://www.nabble.com/dns-query-timed-out-while-sa-update-tp21604925p25909141.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
>> On Wed 14 Oct 2009 07:57:35 PM CEST, Jari Fredriksson wrote
>>> This is how I have it, I have a local bind, and OpenDNS as forwarders.
> 14.10.2009 21:48, Benny Pedersen kirjoitti:
>> dont put all eggs in one basket :)
>>
>> (remove opendns forwards in bind)
>>
>> after i learned bind more i fo
14.10.2009 21:48, Benny Pedersen kirjoitti:
On Wed 14 Oct 2009 07:57:35 PM CEST, Jari Fredriksson wrote
This is how I have it, I have a local bind, and OpenDNS as forwarders.
dont put all eggs in one basket :)
(remove opendns forwards in bind)
after i learned bind more i found that its stu
On Wed 14 Oct 2009 08:12:24 PM CEST, Jari Fredriksson wrote
zone "uribl.com" in {
# uribl blocks calls from OpenDNS
type forward;
forwarders {};
};
this one is silly :)
remove forwarders in options section in named.conf solves it
On Wed 14 Oct 2009 07:57:35 PM CEST, Jari Fredriksson wrote
This is how I have it, I have a local bind, and OpenDNS as forwarders.
dont put all eggs in one basket :)
(remove opendns forwards in bind)
after i learned bind more i found that its stupid to add forwards to
all non known domains
On Wed, 2009-10-14 at 20:57 +0300, Jari Fredriksson wrote:
> 14.10.2009 20:51, Karsten Bräckelmann kirjoitti:
> > On Wed, 2009-10-14 at 13:44 -0400, Terry Carmen wrote:
> > > It's entirely possible his ISP is intercepting his DNS requests. This
> > > has become all too common for all sorts of reas
14.10.2009 20:57, Jari Fredriksson kirjoitti:
If I'm not mistaken, it is always good to run a local nameserver when
using SpamAssassin anyway, and not use any router for that.
This is how I have it, I have a local bind, and OpenDNS as forwarders.
And a special zone like this, as uribl.com
14.10.2009 20:51, Karsten Bräckelmann kirjoitti:
On Wed, 2009-10-14 at 13:44 -0400, Terry Carmen wrote:
Karsten Bräckelmann wrote:
However, the single point of failure is your router -- assuming you
actually are using its DNS.
It's entirely possible his ISP is intercepting his DNS request
On Wed, 2009-10-14 at 13:44 -0400, Terry Carmen wrote:
> Karsten Bräckelmann wrote:
> > However, the single point of failure is your router -- assuming you
> > actually are using its DNS.
>
> It's entirely possible his ISP is intercepting his DNS requests. This
> has become all too common for al
he timeout.
So the DNS TXT query timed out before. Then you changed "your router's"
forwarding DNS, and it still times out. Don't point at others DNS, look
closer to your own environment.
The answer (especially the one opendns gives) should be short enough to
fit
On Wed, 2009-10-14 at 09:00 -0700, an anonymous Nabble user wrote:
> I don't know...why does it only not work with "txt"? Bare in mind I added
> the opendns DNS's exactly because my auto-assigned (probably ISP's) DNS
> addresses were giving me the timeout.
So
DNS's exactly because my auto-assigned (probably ISP's) DNS
addresses were giving me the timeout.
--
View this message in context:
http://www.nabble.com/dns-query-timed-out-while-sa-update-tp21604925p25893880.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
wild_oscar wrote:
McDonald, Dan wrote:
On Wed, 2009-10-14 at 05:03 -0700, wild_oscar wrote:
I have the same problem when I run the sa-update.
Has the original poster (or someone else) managed to make it work?
What do you get when you try
$ dig 5.2.3.updates.spamassassin.org txt
to be correctly configured, I can't pass the
dig timeout. This happens only if I add "txt" to the dig command, without it
it works. Do you know why, how to solve it or perhaps just help me
understand why it fails only with txt ?
--
View this message in context:
h
05/updates_spamassassin_org.pre
> >> ;; query(5.2.3.updates.spamassassin.org, TXT)
> >> [1237] dbg: dns: query failed: 5.2.3.updates.spamassassin.org => query
> >> timed
> >> out
> >> [1237] dbg: channel: no updates available, skipping channel
> >> [1237] dbg: diag
pre
>> ;; query(5.2.3.updates.spamassassin.org, TXT)
>> [1237] dbg: dns: query failed: 5.2.3.updates.spamassassin.org => query
>> timed
>> out
>> [1237] dbg: channel: no updates available, skipping channel
>> [1237] dbg: diag: updates complete, exiting with code 1
&g
"Mark Martinec" wrote:
trouble spot. If it hapens very rarely, you can ignore it, it can be
treated
as as warning only.
This error message is present everyday and in each day is present six/seven
many times in my log file.
Now in this situation with this frequency I can ignore this error or
Sasa,
> Hi, in log file I have this error with SA-3.2.5 and MySQL-5.0.77 (with
> amavisd-new, postfix, maia):
>
> Jul 23 11:03:35 mail amavis[6329]: (06329-02-2) SA TIMED OUT, backtrace: at
> /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/BayesStore/MySQL.pm
> line 492\n\
..sorry but pheraps this isn't a problem about SA ?
Thanks.
--
Salvatore.
- Original Message -
From: "Sasa"
To:
Sent: Thursday, July 30, 2009 4:13 PM
Subject: Timed Out
Hi, in log file I have this error with SA-3.2.5 and MySQL-5.0.77 (with
amavisd-new
Hi, in log file I have this error with SA-3.2.5 and MySQL-5.0.77 (with
amavisd-new, postfix, maia):
Jul 23 11:03:35 mail amavis[6329]: (06329-02-2) SA TIMED OUT, backtrace: at
/usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/BayesStore/MySQL.pm line
492\n\teval {...} called at
/usr/lib
At 15:16 16-02-2009, Kalil Costa - Brasilsite wrote:
Next, I have a full qmailtoaster (qmail, Vpopmail, simscan, clamav,
spamassassin, etc.) and this occurs the following error in maillog
connect to spamd on 127.0.0.1 failed, retrying (# 1 of 3):
Connection timed out
Based on the error
On Mon, 2009-02-16 at 20:16 -0300, Kalil Costa wrote:
> I am new in the list and [...]
No, you are not (yet). :) Your post has been delayed and held for
moderation, as can be seen from the headers.
Delivered-To: moderator for users@spamassassin.apache.org
To avoid unnecessary work for the mo
ction timed
out
connect to spamd on 127.0.0.1 failed, retrying (# 1 of 3): Connection timed
out
connect to spamd on 127.0.0.1 failed, retrying (# 1 of 3): Connection timed
out
And so just locking the requisition smtp and the spamd is in the stalk.
Someone went through this problem?
T
kr
McDonald, Dan wrote:
On Thu, 2009-01-22 at 06:14 -0800, prkr wrote:
Hi,
/var/lib/spamassassin/3.002005/updates_spamassassin_org.pre
;; query(5.2.3.updates.spamassassin.org, TXT)
[1237] dbg: dns: query failed: 5.2.3.updates.spamassassin.org => query timed
out
[1237] dbg: channel: no updates
On Thu, 2009-01-22 at 06:14 -0800, prkr wrote:
> Hi,
> /var/lib/spamassassin/3.002005/updates_spamassassin_org.pre
> ;; query(5.2.3.updates.spamassassin.org, TXT)
> [1237] dbg: dns: query failed: 5.2.3.updates.spamassassin.org => query timed
> out
> [1237] dbg: channel:
Hi,
I am using Spamassassin 3.2.5 on a Big Endian PowerPC system and when I
run sa-update I get the following message
dbg: dns: query failed: 5.2.3.updates.spamassassin.org
<http://5.2.3.updates.spamassassin.org> => query timed out
On packet capture I can see the response for the
Hi,
I am using Spamassassin 3.2.5 on a Big Endian PowerPC system and when I run
sa-update I get the following message
dbg: dns: query failed: 5.2.3.updates.spamassassin.org => query timed out
On packet capture I can see the response for the DNS query.
I have tried using Net::DNS 0.64 as well
Hello list,
I'm using spamassassin 3.2.4 (running on PERL 5.8.3) with amavisd-new 2.5.4
and IP::Country 2.23. From time to time (~ twice a day) I see the following
error in my logfile:
amavis[9384]: (09384-07) (!)SA TIMED OUT, backtrace:
at /usr/lib/perl5/site_perl/5.8.3/IP/Country/Fa
On Thu, 2008-05-01 at 15:57 -0400, Jean-Paul Natola wrote:
>
> -Original Message-
> From: Ross Boylan [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 01, 2008 3:33 PM
> To: Jean-Paul Natola
> Cc: [EMAIL PROTECTED]; SpamAssassin
> Subject: RE: Connection timed out
&g
-Original Message-
From: Ross Boylan [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 01, 2008 3:33 PM
To: Jean-Paul Natola
Cc: [EMAIL PROTECTED]; SpamAssassin
Subject: RE: Connection timed out
On Thu, 2008-05-01 at 13:54 -0400, Jean-Paul Natola wrote:
> OPTIONS="--create-pre
Ross Boylan wrote:
On Thu, 2008-05-01 at 13:54 -0400, Jean-Paul Natola wrote:
OPTIONS="--create-prefs --max-children 5 --helper-home-dir \
--username=mail --socketpath=/var/run/spamd/socket"
I'm running on a Pentium 4 with hyperthreading, which appears as 2 CPU's
to the OSs. T
On Thu, 2008-05-01 at 13:54 -0400, Jean-Paul Natola wrote:
> OPTIONS="--create-prefs --max-children 5 --helper-home-dir \
> --username=mail --socketpath=/var/run/spamd/socket"
>
> >I'm running on a Pentium 4 with hyperthreading, which appears as 2 CPU's
> >to the OSs. There's really only 1
OPTIONS="--create-prefs --max-children 5 --helper-home-dir \
--username=mail --socketpath=/var/run/spamd/socket"
>I'm running on a Pentium 4 with hyperthreading, which appears as 2 CPU's
>to the OSs. There's really only 1 CPU. I wonder if that could have
>something to do with the troubl
Almost every night between 1 and 4am I get a few messages like this:
2008-04-29 01:39:23 1JqlKN-0007RA-TD spam acl condition: error reading
from spamd socket: Connection timed out
2008-04-29 01:42:35 1JqlMT-0007RQ-L8 spam acl condition: error reading
from spamd socket: Connection timed out
2008-04
On Thu, 2007-11-01 at 16:28 -0400, Daryl C. W. O'Shea wrote:
> Robert Fitzpatrick wrote:
> > I have the following error message in the logs, didn't even notice until
> > tracking down an email for a user today, but been happening in all my
> > logs back the last week. All three servers running mai
Robert Fitzpatrick wrote:
I have the following error message in the logs, didn't even notice until
tracking down an email for a user today, but been happening in all my
logs back the last week. All three servers running mail filtering to
pgsql db have this error including the server which hosts t
what exactly is the issue at hand? Thanks in advance.
Nov 1 14:43:31 esmtp amavis[64574]: (64574-02) SA TIMED OUT, backtrace:
at /usr/local/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/BayesStore/PgSQL.pm
line 679\n\teval {...} called at
/usr/local/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/Bayes
08:08:30 1I3QfW-0002IM-O6 spam acl condition: error reading
from spamd socket: Connection timed out
2007-06-27 08:08:31 1I3Qfd-0002IY-6O spam acl condition: error reading
from spamd socket: Connection timed out
2007-06-27 08:08:32 1I3Qfg-0002Iy-Hk spam acl condition: error reading
from spamd soc
rg
> Subject: SpamAssassin timed out and was killed
>
>
> Hello,
>
> The following package for my company mail-gateway:
>
> Centos 4.4
> spamassassin-3.2.0-1.el4.rf
> clamd-0.90.2-1.el4.rf
> MailScanner-perl-MIME-Base64-3.05-5
> postfix-2.2.10-1.RHEL4.2
>
> I
llowing message:
>
> May 16 10:29:01 mailgateway MailScanner[7437]: SpamAssassin timed out and
> was killed, failure 6 of 10
>
> Is my computer not enough RAM to process spamassassin ?
>
Odds are Mailscanner killed it during bayes expiry.
Check for several left over bayes_*.
]: SpamAssassin timed out and
was killed, failure 6 of 10
Is my computer not enough RAM to process spamassassin ?
Thanks
--
View this message in context:
http://www.nabble.com/SpamAssassin-timed-out-and-was-killed-tf3762251.html#a10634766
Sent from the SpamAssassin - Users mailing list archive
On Tue, Dec 05, 2006 at 06:42:01PM +0100, Stefan Jakobs wrote:
> Here an other hint:
> Every day I execute the following command and force an expire of the Bayes DB:
> /usr/bin/sa-learn --dbpath /var/amavis/.spamassassin
> -p /var/amavis/.spamassassin/user_prefs -u vscan --force-expire
>
> In l
Am Dienstag, 5. Dezember 2006 18:16 schrieb Theo Van Dinter:
> On Tue, Dec 05, 2006 at 06:11:56PM +0100, Stefan Jakobs wrote:
> > > > 71\n\tMail::SpamAssassin::Locker::jittery_one_second_sleep('Mail::Spa
> > > >mAss assin::Locker::UnixNFSSafe=HASH(0x9747010)')
> > >
> > > Are you using NFS? If not
On Tue, Dec 05, 2006 at 06:11:56PM +0100, Stefan Jakobs wrote:
> > > 71\n\tMail::SpamAssassin::Locker::jittery_one_second_sleep('Mail::SpamAss
> > >assin::Locker::UnixNFSSafe=HASH(0x9747010)')
> >
> > Are you using NFS? If not, switch to flock.
>
> No, I don't use NFS. What do you mean with "swit
Am Dienstag, 5. Dezember 2006 16:12 schrieb Theo Van Dinter:
> On Tue, Dec 05, 2006 at 04:06:17PM +0100, Stefan Jakobs wrote:
> > Dec 5 15:32:58 server amavis[23505]: (23505-01-24) SA TIMED OUT,
> > backtrace: at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Locker.pm
>
On Tue, Dec 05, 2006 at 04:06:17PM +0100, Stefan Jakobs wrote:
> Dec 5 15:32:58 server amavis[23505]: (23505-01-24) SA TIMED OUT, backtrace:
> at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Locker.pm line 71\n\teval
> {...} called at /usr/lib/perl5/site_perl/5.8.0/Mail/Spa
Hello list,
I use a mailrelay with postfix, amavisd-new 2.3.3 and Spamassassin 3.1.7.
I get the following failure ca. 25 times a day:
Dec 5 15:32:58 server amavis[23505]: (23505-01-24) SA TIMED OUT, backtrace:
at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Locker.pm line 71\n\teval
Simon,
> Looks like ive solved one issue, and another crops up!... I think that
> i may need to move to a mysql storage engine here? approx 17,000
> messages a day incoming on this server.
> Any pointers here? - Thanks!!
>
> Nov 4 11:39:40 mx1 amavis[32148]: (32148-07) SA TI
Hi There,
Looks like ive solved one issue, and another crops up!... I think that
i may need to move to a mysql storage engine here? approx 17,000
messages a day incoming on this server.
Any pointers here? - Thanks!!
Nov 4 11:39:40 mx1 amavis[32148]: (32148-07) SA TIMED OUT, backtrace:
at /usr
Hi There,
Looks like ive solved one issue, and another crops up!... I think that
i may need to move to a mysql storage engine here? approx 17,000
messages a day incoming on this server.
Any pointers here? - Thanks!!
Nov 4 11:39:40 mx1 amavis[32148]: (32148-07) SA TIMED OUT, backtrace:
at /usr
On 11/3/06, Mark Martinec <[EMAIL PROTECTED]> wrote:
On Friday November 3 2006 05:23, Matt Kettler wrote:
> I believe the option is $sa_timeout
> Not sure what the default is, probably 30. Which should be enough to
> prevent that problem, unless you have a LOT of sa instances contending
> for the
On Friday November 3 2006 05:23, Matt Kettler wrote:
> I believe the option is $sa_timeout
> Not sure what the default is, probably 30. Which should be enough to
> prevent that problem, unless you have a LOT of sa instances contending
> for the AWL database.
> Try adding a $sa_timeout = 60 to your
on the AWL
>> database to update it before amavis killed it.
>>
>> Provided you don't have your bayes or AWL stored on an NFS share, you
>> might consider switching to lock_method flock. That will speed up
>> lock/release operations.
>>
>> However
Is your amavis set with an abnormally short timeout for SA?
Hmm.. Where do find this setting in my amavis conf file?
The default is 30 seconds (at least in older versions of amavisd-new). You
can add:
$sa_timeout = 50;
As Matt says, 'lock_method flock' will also help. Are you using Pyzor?
AWL stored on an NFS share, you
might consider switching to lock_method flock. That will speed up
lock/release operations.
However, it's very strange that it timed out locking the AWL.. Normally
SA processes aren't in the AWL very long.
Is your amavis set with an abnormally short timeout f
ethod flock. That will speed up
lock/release operations.
However, it's very strange that it timed out locking the AWL.. Normally
SA processes aren't in the AWL very long.
Is your amavis set with an abnormally short timeout for SA?
go with this one?
Thanks
Simon
Nov 3 16:14:46 mx1 amavis[4765]: (04765-05) SA TIMED OUT, backtrace:
at /usr/share/perl5/Mail/SpamAssassin/Locker.pm line 70\n\teval {...}
called at /usr/share/perl5/Mail/SpamAssassin/Locker.pm line
70\n\tMail::SpamAssassin::Locker::jittery_one_second_sleep('
Gary V wrote:
spamassassin -D --lint is giving me an error:
[2533] warn: config: failed to parse line, skipping: dcc_timeout 18
BTW, as Matt says, your DNS may be slow. If DCC doesn't respond within
10 seconds, I would imagine it's unlikely it will respond - so I
wouldn't waste time waiting a
e and the error is gone now.
(2)
In the logs I'm seeing a good number of the following type of entry:
Oct 27 15:40:21 moe amavis[2548]: (02548-01-2) (!)SA TIMED OUT,
backtrace: at <...>
I've checked the archives and maybe I missed something, but I wasn't
able to find any
.
This was indeed the problem. Error gone now.
(2)
In the logs I'm seeing a good number of the following type of entry:
Oct 27 15:40:21 moe amavis[2548]: (02548-01-2) (!)SA TIMED OUT,
backtrace: at
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/DnsResolver.pm line
363\n\teval {...}
spamassassin -D --lint is giving me an error:
[2533] warn: config: failed to parse line, skipping: dcc_timeout 18
BTW, as Matt says, your DNS may be slow. If DCC doesn't respond within 10
seconds, I would imagine it's unlikely it will respond - so I wouldn't waste
time waiting around another 8
7;m seeing a good number of the following type of entry:
Oct 27 15:40:21 moe amavis[2548]: (02548-01-2) (!)SA TIMED OUT, backtrace:
at <...>
I've checked the archives and maybe I missed something, but I wasn't able
to find anything that seemed relavent.
Thanks for any pointers
gless to SA.
>
>
> (2)
> In the logs I'm seeing a good number of the following type of entry:
> Oct 27 15:40:21 moe amavis[2548]: (02548-01-2) (!)SA TIMED OUT,
> backtrace: at
> /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/DnsResolver.pm line
> 363\n\teval {
t 27 15:40:21 moe amavis[2548]: (02548-01-2) (!)SA TIMED OUT,
backtrace: at
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/DnsResolver.pm line
363\n\teval {...} called at
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/DnsResolver.pm line
363\n\tMail::SpamAssassin::DnsResolver::poll_respo
t 27 15:40:21 moe amavis[2548]: (02548-01-2) (!)SA TIMED OUT,
backtrace: at
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/DnsResolver.pm line
363\n\teval {...} called at
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/DnsResolver.pm line
363\n\tMail::SpamAssassin::DnsResolver::poll
On Tue, May 03, 2005 at 11:55:44AM +0200, Jaskula Thomas wrote:
>> I deleted /usr/lib/perl5/site_perl/5.8.0/Mail/ but when I try to
reinstall
>> SpamAssassin I have following errors. How can I reinstall it ?
>I'd also get rid of /usr/share/spamassassin fwiw.
ok
>> Failed Test Stat Wstat To
On Tue, May 03, 2005 at 11:55:44AM +0200, Jaskula Thomas wrote:
> I deleted /usr/lib/perl5/site_perl/5.8.0/Mail/ but when I try to reinstall
> SpamAssassin I have following errors. How can I reinstall it ?
I'd also get rid of /usr/share/spamassassin fwiw.
> Failed Test Stat Wstat Total Fail
OK
Running make install
make test had returned bad status, won't install without force
Thanks
-Message d'origine-
De : Jaskula Thomas [mailto:[EMAIL PROTECTED]
Envoyé : mardi 3 mai 2005 10:24
À : 'Theo Van Dinter'; users@spamassassin.apache.org
Objet : RE: ERROR: SA
05 10:08
À : users@spamassassin.apache.org
Objet : Re: ERROR: SA TIMED OUT, backtrace ...Message.pm line 116
On Tue, May 03, 2005 at 09:47:50AM +0200, Jaskula Thomas wrote:
> I noticed that my installation of SpamAssassin (3.0.2) has some problems
> that make my system slow down. Here is
On Tue, May 03, 2005 at 09:47:50AM +0200, Jaskula Thomas wrote:
> I noticed that my installation of SpamAssassin (3.0.2) has some problems
> that make my system slow down. Here is my /var/log/mail/info content :
>
> 116\n\tMail::SpamAssassin::Message::new('Mail::SpamAssassin::NoMailAudit')
> calle
ystem slow down. Here is my /var/log/mail/info content :
May 3 08:57:38 infalinux amavis[14582]: (14582-07) SA TIMED OUT, backtrace:
at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Message.pm line
116\n\teval {...} called at
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Message.pm line
1
I am using Postfix 2.1.5-3 with SA 3.0.1 and amavisd-new 2.1.2 on RH9.
I just saw on my logs the following :
Apr 18 08:42:37 ndar amavis[2553]: (02553-02) SA TIMED OUT, backtrace:
at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/BayesStore/DBM.pm
line 1758\n\teval {...} called at
/usr/lib
PROTECTED]>
<- snip ->
Nov 4 15:46:08 amavis[11932]: (11932-08) SA TIMED OUT,
backtrace: at
/usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/BayesStore.pm line
376\n\teval {...} called at
/usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/BayesStore.pm line
376\n\tMail::SpamAssas
At 03:25 PM 10/23/2004, Justin Mason wrote:
> > In the longer term, here's some suggestions I use on my own MailScanner
> > server: (I use all of these together)
>
> Matt
>
> I wanted to personally say thanks! We too had time out issues with the new
> 3.0 and MS. Certain spams happened to sneak in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Thurman writes:
> On 10/20/04 8:40 AM, "Matt Kettler" wrote:
>
> > Mailscanner is inappropriately impatient with SpamAssassin. It's timeouts
> > were designed in the pre-bayes era, and are not designed to accommodate
> > bayes housekeeping chor
On 10/20/04 8:40 AM, "Matt Kettler" wrote:
> Mailscanner is inappropriately impatient with SpamAssassin. It's timeouts
> were designed in the pre-bayes era, and are not designed to accommodate
> bayes housekeeping chores like expiry and journal syncs.
>
> In the short term, you can help by runnin
At 04:04 PM 10/20/2004 +0530, Rakesh wrote:
I am using spamassassin + (Razor, DCC and URI checks) with MailScanner.
Not always but i usually get an error of SpamAssassin timed out and was
killed in my maillogs. I am not sure about the exact reason but i feel
that this has something to do with
Hii
I am using spamassassin + (Razor, DCC and URI checks) with MailScanner.
Not always but i usually get an error of SpamAssassin timed out and was
killed in my maillogs. I am not sure about the exact reason but i feel
that this has something to do with Bayes Database as I have observed
that
At 06:11 PM 9/10/2004 -0400, Kevin Old wrote:
Anyone have ideas why I'd be seeing these messages all of a sudden on
a 2.64 installation with no changes?
Sep 10 18:07:49 s15111287 MailScanner[28540]: SpamAssassin timed out
and was killed, failure 13 of 20
Sep 10 18:07:50 s15111287 MailScanner[
Kevin Old wrote on Fri, 10 Sep 2004 18:11:59 -0400:
> I'm using SURBLare there problems with the SURBL servers?
>
Probably not. Run an "sa-learn -D --sync" to see if it's bayes-related. We
are getting the same and it's somehow related to the journal. I just saw a
170 MB journal which sounds
Hello,
Anyone have ideas why I'd be seeing these messages all of a sudden on
a 2.64 installation with no changes?
Sep 10 18:07:49 s15111287 MailScanner[28540]: SpamAssassin timed out
and was killed, failure 13 of 20
Sep 10 18:07:50 s15111287 MailScanner[28540]: Virus and Content
Sca
85 matches
Mail list logo
