Not an issue there, but it wouldn't take long if it's been run recently.
I'm guessing that your problem was probably a specific email message
tying up spamdyke, and changing the spamdyke timeout should fix it.
Let us know if you have this problem again.
Noel Rivera (Border Less) wrote:
[r...@mailserver ~]# time sa-learn -u vpopmail --force-expire
real 0m3.761s
user 0m3.439s
sys 0m0.122s
-----Original Message-----
From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert
Sent: Jueves, 04 de Junio de 2009 02:02 p.m.
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] another problem
Try running (as root):
# time sa-learn -u vpopmail --force-expire
What is the result?
When you're done with that command, be sure to run
# chown vpopmail:vchkpw /home/vpopmail/.spamassassin/bayes_toks
to fix ownership back on your bayes database.
Noel Rivera (Border Less) wrote:
I run spamdyke 4.0.10
And I'm sorry I don't understand you the second question....
I received duplicate mails any 5 minutes....
-----Original Message-----
From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert
Sent: Jueves, 04 de Junio de 2009 11:30 a.m.
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] another problem
Looks like you rarely have more than one scan at a time going on. That's
good. Your system might have spiked when you had the problem, but I
would guess not. You'd need to look at the log for that exact time to
tell for sure.
Which version of spamdyke are you running?
How long does the expire script take when you run it?
Noel Rivera (Border Less) wrote:
When I run the qmlog -g '"child states"' spamd I have that one:
06-04 10:46:18 [12105] info: prefork: child states: II
06-04 10:46:24 [12105] info: prefork: child states: II
06-04 10:46:58 [12105] info: prefork: child states: II
06-04 10:47:06 [12105] info: prefork: child states: II
06-04 10:48:01 [12105] info: prefork: child states: II
06-04 10:48:08 [12105] info: prefork: child states: II
06-04 10:48:44 [12105] info: prefork: child states: II
06-04 10:48:47 [12105] info: prefork: child states: II
06-04 10:49:31 [12105] info: prefork: child states: II
06-04 10:49:40 [12105] info: prefork: child states: II
06-04 10:50:44 [12105] info: prefork: child states: II
06-04 10:52:22 [12105] info: prefork: child states: II
06-04 10:53:03 [12105] info: prefork: child states: BI
06-04 10:53:05 [12105] info: prefork: child states: II
06-04 10:53:14 [12105] info: prefork: child states: BI
06-04 10:53:15 [12105] info: prefork: child states: II
06-04 10:53:22 [12105] info: prefork: child states: II
06-04 10:53:35 [12105] info: prefork: child states: II
06-04 10:53:41 [12105] info: prefork: child states: II
06-04 10:53:57 [12105] info: prefork: child states: BI
06-04 10:54:06 [12105] info: prefork: child states: II
06-04 10:54:18 [12105] info: prefork: child states: II
06-04 10:55:07 [12105] info: prefork: child states: II
And I my file /etc/qmail/control/concurrencyincoming have a number 20
-----Original Message-----
From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert
Sent: Jueves, 04 de Junio de 2009 11:07 a.m.
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] another problem
How many concurrent smtp sessions are typically running?
# qmlog -g '"child states"' spamd
How many Bs do you typically see at once? (Each B indicates a busy child
that's scanning a message)
Noel Rivera (Border Less) wrote:
Processor: AMD Athlon 1.3 GHZ
Memory : 2 GHZ RAM
System: Centos 5.3
-----Original Message-----
From: Jake Vickers [mailto:j...@qmailtoaster.com]
Sent: Jueves, 04 de Junio de 2009 10:40 a.m.
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] another problem
Eric Shubert wrote:
I use 660. There used to be a bug in the 3.x versions where some
rather large (15M or so) emails would time out. I thought it was
fixed, but still use 660 just to be safe. ;)
Also, you might want to check to see if you have bayes_auto_expire
turned on on /etc/mail/spamassassin/local.cf. That can take over 5
minutes (depending on your cpu) when it kicks in, causing timeouts.
Better to handle that in a daily cron job:
#!/bin/sh
# written 11/17/06 by Eric 'shubes' <e...@shubes.net>
# force journal sync and expiration of spamassassin bayes database
#
sa-learn -u vpopmail --force-expire
chown vpopmail:vchkpw /home/vpopmail/.spamassassin/bayes_toks
Hey Jake, does the stock spamassassin-toaster still have this enabled?
Might be better to include this cron job in the package instead, and
have it turned off.
This should be the default local.cf:
# These values can be overridden by editing ~/.spamassassin/user_prefs.cf
# (see spamassassin(1) for details)
# These should be safe assumptions and allow for simple visual sifting
# without risking lost emails.
ok_locales all
skip_rbl_checks 1
required_score 5
report_safe 0
rewrite_header Subject ***SPAM***
use_pyzor 1
use_auto_whitelist 1
use_bayes 1
use_bayes_rules 1
bayes_auto_learn 1
----------------------------
I've never had an issue with it myself. Out of curiosity, what hardware
do you run?
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
