Software

Ask something
Discussion Locked

Message from Exchange

0 helpful
3 replies

by don_pham

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,
I just currious that anyone has any information about the weird messages from system administrator to send to user and says that
" your message did not reach some or all of the intended recipients.
Username blah blah on 09-17-20003 9:56 AM
The recipient was unavailable to take delivery of the message.
The MTS-ID of the original message is: so on and so on......."
Even though that user did not send anything out or did send a correct address still get a same message. I have users say that they did not send anything and others say that they are sure that send correct address. We lately get alot of message from system admistrator states that "UNDELIVERABLE" mail.
My boss just came down and ask me WHY, i have no clue why it does that. Does any one know how to narrow down what cause and why; i would really appreciate it.
-Cheers

3 replies

by timwalsh

Two answers:
1. For bounce messages related to emails the sender claims they didn't dend - chances are about 95% that this is a result of the SOBIG.F worm. SOBIG had the capability of spoofing sender addresses. The spoofed addresses came form any files (including address books) on an infected computer. This doesn't necessarily mean any of your computers were infected. Your user's email address could have been in an address book on an infected computer on the other side of the world. Since all the target addressee has to go on is the From address in the email it ends up bouncing back to you (where the spoofed address really exists). This type of email for intents and purposes is spam. There really isn't anything you can do to stop it.

2. For those bounce messages related to emails where the sender SWEARS they entered the correct address, I usually take the tack of "OK, I believe you, but let's check anyway." First, check and see if the bounce message is actually coming from the email domain of the supposed recipient. Next, check the the address on the original email as it was sent out and have the sender verify the spelling of the recipients name (it's amazing how much havoc transposed letters will cause). Lastly, in a small percentage of cases, there may actually be problems on the receiving end, either with that particular mailbox, or with the server itself.

This discussion is closed to new replies.