Today lots of the email application such as Sendmail, Postfix, or even MS Exchange has been re-designed to reduce the possibility of becoming an 'spam-relay'. From our experience, most of the SMTP AUTH relay attack is caused by the compromised of the weakly password protected user accounts. Once the accounts discovered and been compromised. Spammer authenticate using the user credentials, they are granted to relay via the server, which is then used to send spam.

Below are the easy steps to stop these spam emails quickly and identify which account (s) has been compromised.

Step1: Stop on on hold mail queue .

Large amount of spam emails keep queuing your mail spool. What even worst is all the spam it fill up all your / var. Thus, it is always to hold the mail queue for temporary until you find out the which account has been exploited by spammer and send a large amount of emails.

Step2: Check your mail log.

Go to / var / log / maillog to have a quick look on the line with from: <>. You might see lots of email domain name there are not belong yo your organization. This is due to the spammer is faking the mail from: <>.

Step 3: Identify compromised account authenticating SMTP AUTH connection

Next, let us check those email accounts that have been exploited. Run a cat grep sasl_username and sort it. You should see a long list of the login attempt and session for those exploited account. You can also do a quick calculation by running wc -l command to see total sessions for a particular user.

Step4: Disable the exploited email account.

Once, we have SASL_username string, which is the user account. You are advised to disabled or change the password to complex password.

Step 5: Move the mail queue or delete the spam email

Now, we have to deal with our mail queue. Easier and faster way is to move your mail queue and do the housekeeping later. Or, you can delete those spam email using Bash script.

Step 6: Release Mail queue

Remember to release mail queue after our housekeeping process and keep on monitoring of the mail traffic.

Leave a Reply

Your email address will not be published. Required fields are marked *