Postfix/amavisd - connect to 127.0.0.1[127.0.0.1]:10024: Connection refused

Want to support HowtoForge? Become a subscriber!
 
Submitted by falko (Contact Author) (Forums) on Thu, 2011-08-18 11:33. :: Errors

Error: Postfix/amavisd - connect to 127.0.0.1[127.0.0.1]:10024: Connection refused

You use a Postfix setup with amavisd-new and get the following errors in your mail log:

Aug 17 14:58:33 server1 postfix/smtp[5993]: F0C57124E77: to=<info@example.com>, relay=none, delay=2524, delays=2524/0.27/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)

Or:

Aug 17 09:42:24 server1 postfix/error[7809]: 15D54124E53: to=<info@example.com>, relay=none, delay=269, delays=0.49/269/0/0.04, dsn=4.4.2, status=deferred (delivery temporarily suspended: conversation with 127.0.0.1[127.0.0.1] timed out while receiving the initial server greeting)

 

Solution

Please restart both amavisd-new and Postfix and then check with

netstat -tap

that both are running on the ports

25 and 10025 (postfix)

and

10024 (amavisd-new).


Please do not use the comment function to ask for help! If you need help, please use our forum.
Comments will be published after administrator approval.
Submitted by Altair Mentzingen (not registered) on Thu, 2014-02-06 23:02.

Thank you thank you!

 I just needed search for part of error to find this amazing and simple solution.

I forgot about the Amavis and you  helped me!

Best regards 

Submitted by djh-compnet (registered user) on Mon, 2013-10-28 15:39.

Starting amavisd: hostname: Name or service not known
  The value of variable $myhostname is "", but should have been
  a fully qualified domain name; perhaps uname(3) did not provide such.
  You must explicitly assign a FQDN of this host to variable $myhostname
  in /etc/amavis/conf.d/05-node_id, or fix what uname(3) provides as a host's
  network name!
(failed).

 When you receive this error make sure you edit your /etc/hosts file for your server like this (with your details):

[..]
192.168.0.100   server1.example.com     server1
[..]

and /etc/hostname:

[..]
server1.example.com
[..]

Submitted by Anonymous (not registered) on Fri, 2013-05-31 08:47.
Thank you very much for this. I was getting this issue because amavis wasn't actually running. 
Submitted by Anonymous (not registered) on Thu, 2014-07-31 00:22.

yes, starting the amavis was the solution...

 

thanks

Submitted by Jeroen (not registered) on Wed, 2014-09-10 14:49.
What if the problem is repeating itself after about 5 days?
What causes these services to stop? Logging gives no clue (because there isn't any) 
I have to restart the mail server every now and then. It's a production system with lots of users. Very inconvenient.
System: Debian Wheezy 

 

 

Submitted by AndreasK (not registered) on Tue, 2014-11-18 08:35.
Did you get a solution for the postfix/amavis hangs? I got exactly the same Problem. Every few days i have to restart postfix and amavis...
Submitted by admin (registered user) on Wed, 2014-09-10 15:56.
If you like to get help with your problem, then please post in our porum. (See yellow box above the comment section on this page "Please do not use the comment function to ask for help! If you need help, please use our Forum.".