I am using qmail-scanner-1.20rc1 with qmail-1.03, clamav-0.60, and
Mail-SpamAssassin-2.55. Everything has worked perfectly until yesterday.
Mail stopped flowing yesterday morning and I saw the following:

Mar 17 12:03:51 server2 X-Qmail-Scanner-1.20rc1:
[server2.example.com107954543145531004] Requeuing: Maximum time exceeded.
Something cannot handle this message. at
/var/qmail/bin/qmail-scanner-queue.pl line 370.

(Okay, okay, the above is actually from this morning--it happened again.)

To get mail flowing again I had to do this:

# killall /usr/bin/perl
# /var/qmail/qmailctl stop
# /var/qmail/qmailctl start
# /etc/rc.d/init.d/clamd stop
# /etc/rc.d/init.d/clamd start
# /etc/rc.d/init.d/spamd stop
# /etc/rc.d/init.d/spamd start

At that point mail started flowing again.

Unfortunately, this problem has occured twice now, once yesterday and again
today.

So I wonder if there is a message in our qmail deferred queue that is
causing qmail-queue.pl to punt?

I wish the log was more detailed.

Is there a way to find out which message is doing this?

Is this clamd or spamd taking too long?

How can I tell?




-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Qmail-scanner-general mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general

Reply via email to