From: Randy Ramsdell (no email)
Date: Wed Jul 02 2008 - 10:20:03 EDT
Richard Foley wrote:
> On Wednesday 02 July 2008 15:51:32 Otandeka Simon Peter wrote:
>
>> Foley,
>>
>> The main trouble causer is amavisd. It should have failed to start up at
>> all. Check its status.It could be even corrupt.
>>
>>
> I think you're probably right. I'll have to fix this quite soon too - at the
> moment I am being swamped with spam...
>
>
This actually happens to us all the time so the following steps may help.
1. Check to see if amavisd is taking 100% cpu. Sometimes is hangs on a
message and will not clear even after restarting. We change the
parameter "$sa_mail_body_size_limit = 200*1024" to
"$sa_mail_body_size_limit = 1*1024" for a a few minutes or until the
message it was hung on gets through.
2. When using /etc/init.d/amavis restart: Sometimes the amavis process
wont stop and therefore does not restart, but it is reported as stoping
and starting. Kill amavis with the kill command. Then restart is as normal.
3. After performing one of the above steps, it may be necessary to
restart postfix. We have to do this occasionally.
|
|
|