Issue with SMTP Server (Exim) Receiving Mail, 550 Administrative Prohibition
I'm currently experiencing issues with inbound mail not getting passed the EHLO / HELO step during an inbound SMTP transaction.
I have tried toggling the "Require HELO before MAIL" option on and off (Service Configuration>Exim Configuration Manager>All), as well as restarting the service, rebooting the server, and rebuilding exim, but unfortunately none of these worked.
Please see the below SMTP output (Port 25 of below hostname)
Has anyone experienced this before? What did you do to fix this?
220-eha.domain.com ESMTP Exim 4.85 #2 Sat, 19 Sep 2015 03:06:56 -0500
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
HELO google.com
550 Administrative prohibition
quit
221 eha.domain.com closing connection
Has anyone experienced this before? What did you do to fix this?
-
Hello :) Do you have any custom options enabled in the /etc/exim.conf.local file on this system? Does this happen when using HELO names other than google.com? Thank you. 0 -
Hi, I haven't enabled any custom options for exim, and yes it happens for other HELO values. 0 -
Can you see if anything helpful shows if you # tail -f /var/log/maillog /var/log/exim_mainlog
while sending a test email0 -
New Hi, I haven't enabled any custom options for exim, and yes it happens for other HELO values.
Hello :) You can search for one of the email addresses that's failing to proceed past the HELO check in the Exim logs with commands such as:exigrep user@domain /var/log/exim_mainlog exigrep user@domain /var/log/exim_rejectlog
Do you notice any particular output that helps clarify the reason for the rejection? Thank you.0 -
Thanks for everyone's help, I reviewed the exim settings and found a HELO reject subroutine which was anticipated to prevent connections at HELO from a specific host. It appeared to be causing the issue, as after removing the aforementioned subroutine, the SMTP system returned to normal. Thanks again everyone. 0 -
I am happy to see the issue is now resolved. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
6 comments