Atomicorp

Hello to all,

After the installation of qmail scanner on yesterday and everything went ok. But today morning my client call me say they can't send email because Symantec report the following error:

Your email message was unable to be sent because your mail server rejected the message:
451 qq temporary problem (#4.3.0)

After I try it by myself, I got the exact same error too. May I know what is wrong in my box? I try to restart Qmail, Freshclam, Spamassasin and Clamd. All success except Clamd. I try to stop Clamd, also failed. Please advice on how to fix this error please. Thank you.

Regards,
Dumb

I had the same problem today after updating.
I ran: qmail-scanner-reconfigure
and than
I ran: /usr/local/psa/admin/sbin/mchk -v

Email is now working great.
I'm no expert so I hope this helps.

Hi sharmin,

Thanks for trying to help. But no luck, I followed your steps but it's not working and have the same error.

Now I've removed qmail scanner and my mail can be sent out again. So now I do not have qmail scanner installed. Can someone please help. Thank you.

Regards,
Dum

Hi,

Not an expert also but try to remove Clamav and reconfigure qmail scanner.

If emails goes out, then reinstall clamav and reconfigure qmail scanner and everything should be ok (I've already had the same problem...).

Regards,

Kilgore

Hi kilgore,

I tried to remove ClamAV, then reconfigure qmail scanner, it works. But when I reinstall ClamAV and then reconfigure qmail scanner, the problem comes back.

So, it's quite clear that it's ClamAV's problem. Anyone have any idea what is wrong and how to correct it? Please advice, thank you.

Regards,
Dum

Make sure clamd is actually running, thats generally what that means.

Hi Scott,

I tried to stop clamd, it's failed. I'm not sure why it can't be stop. When I try to restart, it says clamd is running. But I try reconfigure qmail scanner and send mail again, the error is still there.

What should I do? or What should I check, I'm a newbie. Please advice, thank you.

Regards,
Dum

Look for it with ps (never trust an init script), and if you have to kill it. Then try restarting it. If all else fails we offer commercial support on this kind of thing.