Looking at the logs on my mailservers, I have noticed messages like the following:
Nov 29 12:09:38 mta postfix/smtpd[8362]: connect from unknown[183.13.165.14]
Nov 29 12:09:39 mta postfix/smtpd[8362]: lost connection after AUTH from unknown[183.13.165.14]
Nov 29 12:09:39 mta postfix/smtpd[8362]: disconnect from unknown[183.13.165.14]
Nov 29 12:09:39 mta postfix/smtpd[8409]: connect from unknown[183.13.165.14]
Nov 29 12:09:40 mta postfix/smtpd[8409]: lost connection after AUTH from unknown[183.13.165.14]
Nov 29 12:09:40 mta postfix/smtpd[8409]: disconnect from unknown[183.13.165.14]
There are no SASL failures in these cases. There are SASL failures are logged at other times, but never with lost connection after AUTH
.
What is happening here, and should I do any about it?
These are not MXs, and already have smtpd_client_connection_rate_limit
set.
Possibly related:
The systems require either SMTPS or STARTTLS before AUTH is announced.
My log files were getting filled up, and it's a waste of cpu to even allow a connection from these jerks. I created a
fail2ban
rule.Contents of
/etc/fail2ban/jail.conf
Contents of
/etc/fail2ban/filter.d/postfix.conf
This is a botnet from China connecting to your box trying to deliver Spam. But the bot is too stupid to know what to do when being told to authenticate itself. The bot just stops delivering mail and then disconnects for attacking the next victim.
Absolutely nothing to worry about.
In
smtpd_recipient_restrictions
just setreject_unknown_client_hostname
like this:and this will result in rejecting clients and stray or dumb zombie bots with unknown host names. You logs will look like this when set:
I'm not sure if there's much to be worried about, basically a client/'someone' is connecting, issuing AUTH and disconnecting on their own accord. It could be an attempt to probe server capabilities from a mail client - or an attempt to case the daemon.
As long as you have sufficient security in place it's just another knock on the door from the world.