|
Title: Emails stuck in the Queue Post by: ybjones72 on Thursday 28 February 2013, 11:37:17 am The SMTP proxy on my Endian Community 2.5.1 has stopped working. The mails just end up in the queue and have one of the following two errors:
Quote (host 127.0.0.1[127.0.0.1] said: 421 4.3.2 Service shutting down, closing channel (in reply to MAIL FROM command)) or Quote (delivery temporarily suspended: lost connection with 127.0.0.1[127.0.0.1] while sending RCPT TO) I have tried turning off spam and virus scanning yet they still stay stuck in the queue. Flushing the mail queue has no effect. The virus scanner and spam filter for SMTP are both running when it is enabled in the SMTP proxy. Freshclam, restarting clamd, and restarting amavisd are all successful (see below). Any help would be appreciated. Thanks in advance, Yancey Jones Quote root@ach-gw1:~ # freshclam ClamAV update process started at Wed Feb 27 19:25:03 2013 main.cvd is up to date (version: 54, sigs: 1044387, f-level: 60, builder: sven) Downloading daily.cvd [100%] [LibClamAV] *********************************************************** [LibClamAV] *** This version of the ClamAV engine is outdated. *** [LibClamAV] *** DON'T PANIC! Read http://www.clamav.net/support/faq *** [LibClamAV] *********************************************************** [LibClamAV] *********************************************************** [LibClamAV] *** This version of the ClamAV engine is outdated. *** [LibClamAV] *** DON'T PANIC! Read http://www.clamav.net/support/faq *** [LibClamAV] *********************************************************** daily.cvd updated (version: 16754, sigs: 860232, f-level: 63, builder: neo) bytecode.cvd is up to date (version: 214, sigs: 41, f-level: 63, builder: neo) [LibClamAV] *********************************************************** [LibClamAV] *** This version of the ClamAV engine is outdated. *** [LibClamAV] *** DON'T PANIC! Read http://www.clamav.net/support/faq *** [LibClamAV] *********************************************************** [LibClamAV] *********************************************************** [LibClamAV] *** This version of the ClamAV engine is outdated. *** [LibClamAV] *** DON'T PANIC! Read http://www.clamav.net/support/faq *** [LibClamAV] *********************************************************** Database updated (1904660 signatures) from db.local.clamav.net (IP: 69.163.100.1 4) Clamd successfully notified about the update. root@ach-gw1:~ # /etc/init.d/clamd restart Stopping clamd: [ OK ] Starting clamd: [ OK ] root@ach-gw1:~ # /etc/init.d/amavisd restart Shutting down Mail Virus Scanner (amavisd): [ OK ] Starting Mail Virus Scanner (amavisd): [ OK ] root@ach-gw1:~ # netstat -lntp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:10024 0.0.0.0:* LISTEN 17043/amavisd (mast tcp 0 0 127.0.0.1:10025 0.0.0.0:* LISTEN 5725/master tcp 0 0 0.0.0.0:2121 0.0.0.0:* LISTEN 4836/frox tcp 0 0 0.0.0.0:10443 0.0.0.0:* LISTEN 4759/httpd tcp 0 0 127.0.0.1:3310 0.0.0.0:* LISTEN 17010/clamd tcp 0 0 0.0.0.0:8110 0.0.0.0:* LISTEN 4188/p3scan tcp 0 0 127.0.0.1:783 0.0.0.0:* LISTEN 5232/spamd.pid tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 4759/httpd tcp 0 0 127.0.0.1:5555 0.0.0.0:* LISTEN 5775/openvpn tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 7672/dnsmasq tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 5725/master tcp 0 0 127.0.0.1:3131 0.0.0.0:* LISTEN 3880/emi tcp 0 0 127.0.0.1:2812 0.0.0.0:* LISTEN 2828/monit tcp 0 0 :::53 :::* LISTEN 7672/dnsmasq tcp 0 0 :::22 :::* LISTEN 3946/sshd tcp 0 0 :::222 :::* LISTEN 3946/sshd root@ach-gw1:~ # Title: Re: Emails stuck in the Queue Post by: ybjones72 on Thursday 28 February 2013, 04:17:13 pm If I disable the proxy and forward port 25 to my mail server, then emails flow just fine. Is there anyway to get the queued emails to be delivered when the SMTP proxy is turned off? I have tried postsuper -r ALL and it says they are requeued but they never get sent and if I turn the proxy back on, they are still there and even with SPAM and virus scanning turned off, and multiple reboots, I get the same errors. This is extremely frustrating.
|