From: Gary V (no email)
Date: Wed Jul 02 2008 - 23:05:57 EDT
> 8CA46141702C 77984 Wed Jul 2 13:09:27 root
> (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:
> Connection refused)
So most likely amavisd-new has stopped or is otherwise not responding. Assuming you are not running an ancient version, grep your mail log for !.
grep ! /var/log/maillog
(or whatever your mail log is called) and look for errors that amavisd-new may have produced. You can increase $log_level to 5 in amavisd.conf for a short period of time and read the results of this detailed logging in your mail log. You can also stop amavisd-new and run it in debug mode (in the foreground) for a short period of time:
amavisd debug
If it dies while in debug mode, the last 5 or so lines may give some clues as to why. There is also a program called amavisd-nanny that you can run for a brief period that will monitor amavisd-new activity:
http://marc.info/?l=amavis-user&m=118955545631169
Amavisd-new does not use spamd, it loads the Mail::SpamAssassin Perl module directly. Unless you are scanning mail twice, you typically do not, and should not start up spamd.
It cannot be determined what the cause of the amavisd-new failure is without seeing log entries or the result of debugging.
I suggest that the result of what you find in the log or the debugging session is directed to the amavis mailing list.
Gary V
_________________________________________________________________
Enter the Zune-A-Day Giveaway for your chance to win — day after day after day
http://www.windowslive-hotmail.com/ZuneADay/?locale=en-US&ocid=TXT_TAGLM_Mobile_Zune_V1
|
|
|