ArtiePublic
asked on
Exchange 2010 Email Address Spamming
Hi, yesterday we found that a domain user was receiving "Undeliverable" emails in her inbox, 5000 of them about. We use a Cisco IronPort device to filter and found that her email address had sent 33k emails during the day yesterday. I worked with Cisco to adjust our outgoing policy to state that if any emails are scanned as spam or a threat, drop them. It was set to deliver them...
Cisco stated that the emails are still being sent from our mail server, so i need to find out how. I tried with doing a "get-messagetrackinglog" with the header of a spam email and it tells me the sender (which i already knew). How do i stop exchange from sending on behalf of this user, what could it be? any tips on this are greatly appreciated.
thanks
Cisco stated that the emails are still being sent from our mail server, so i need to find out how. I tried with doing a "get-messagetrackinglog" with the header of a spam email and it tells me the sender (which i already knew). How do i stop exchange from sending on behalf of this user, what could it be? any tips on this are greatly appreciated.
thanks
Arjun Vyavahare
If you know the sender then can you go to his machine and perform Antivirus scan and also meantime can you remove that user's machine from the network for a while and monitor outgoing email traffic? This may resolve your issue.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Simon, your exactly right. I did do the steps though above prior to what he stated, but how do you suggest i go about finding this smtp engine?
First you should have port 25 blocked at the firewall for everything but the Exchange server. If you get an infected machine it will show in the logs very quickly.
That will allow you to identify which machine has the malware. Then I would find it and wipe it. If it belongs to the user in question then it will teach them a lesson about responding to phishing or using simple passwords. While you can run malware detection tools, malware is a moving beast and you cannot guarantee that you have removed it all.
Simon.
That will allow you to identify which machine has the malware. Then I would find it and wipe it. If it belongs to the user in question then it will teach them a lesson about responding to phishing or using simple passwords. While you can run malware detection tools, malware is a moving beast and you cannot guarantee that you have removed it all.
Simon.
ASKER
Port 25 is blocked for sure. What logs do you mean, the header info in the email or exchange event viewer logs? Yes, i removed the machine and so far so good but like you said it might have moved on to someone else.
To clarify - Simon is suggesting you block port 25 outbound for all but the exchange server. If you've done that, then the theoretical local smtp engine on the compromised system can no longer send email.
If in fact, the mail is flowing via authentication through your mailserver, then you should be able to review outbound messages using the tracking log explorer.
Or, if your user is willing, setup a transport rule on the HT server that redirects all of their sent mail to a local mailbox. If a bunch of spam shows up, then you know the account is compromised.
At any rate, you should change the password soonest.
If in fact, the mail is flowing via authentication through your mailserver, then you should be able to review outbound messages using the tracking log explorer.
Or, if your user is willing, setup a transport rule on the HT server that redirects all of their sent mail to a local mailbox. If a bunch of spam shows up, then you know the account is compromised.
At any rate, you should change the password soonest.
ASKER
Right, the password for the user has been changed. Its been two days now and i dont have anymore spam messages generating. Im going to assume this is gone or at least stopped by me restricting port 25 for outbound, as well as updating my outgoing policy on my Ironport. Thank you.