Possibly you had this issue also the last couple of weeks, NDR’s for messages you don’t have send yourself. Together with one of my collegues we did some further research on it. This type of SPAM is called a Backscatter, at this moment there is not really a solution for it. BUt what is a backscatter exactly:
A spammer abuses an e-mail address, for example email@example.com and sends a lot of messages with firstname.lastname@example.org as sender to different domains, the change is really big that the recipient does not exist in the domain.
When a mailserver if configurered correctly it will check if the recipient adres does exist before accepting the message, the following shout happen:
MAIL FROM: email@example.com
RCPT TO: firstname.lastname@example.org
550 User unknown</em>
But when the server is not configurered to check if the recipient exists it will accept the mail and the mailserve will try to deliver it. The mailserver will find out that the recipient does not exist and a NDR will be generated and will be sended to the sender address, in this case email@example.com
When this happens to thousands of people there will be generated thousands of NDR which will be send back to the abused address.
At this time there is not a really good solution for it. It is advisable to activtae recipient filtering and when you run Exchange activate SMTP Tarpiting . Backscatter.org has developed a list of addresses from mailservers that are not configured OK accordin to them. The following text can be found on their website:
_Email servers should be configured to provide Non-Delivery Reports (bounces) to local users only.</p>
Unacceptable email from anywhere else should be rejected.</em>
In other words you shouldn’t permit NDR’s being send outside your company. Personaly I don’t think many companies will implement this. NDR’s are really usefull when someone receives a message from your mailserver that he has sended an e-mail to a non existing address and not waits for an answer that he will never receive.