Tag Archives: Bounce Back

How to read a email bounce back KB10392116

Email Bounce Back Example: This is just one example and bounce backs can vary server to server so keep that in mind while viewing yours.

Delivery has failed to these recipients or distribution lists:

automated reply
Your message wasn’t delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.

The following organization rejected your message: mx.siteprotect.com.
Diagnostic information for administrators:

  1. Generating server: server.domain-name.local
  2. do-not-reply-user@anoher-domain-name.com
  3. siteprotect.com #550 5.7.1 <do-not-reply-user@anoher-domain-name.com>:
  4. Recipient address rejected: Invalid recipient ##

Original message headers:

5.  Received: from server.domain-name.local ([192.168.160.205]) by server.domain-name.local ([192.168.160.206]) with mapi; Thu, 2 Jul 2015 15:00:11 -0400From:        =?Windows-1252?Q?Company_Name=99_Helpdesk?=        <Support@domain-name.com>To: automated reply <do-not-reply-user@anoher-domain-name.com>Date: Thu, 2 Jul 2015 15:00:10 -0400Subject: *** Please do not reply to this Email ***Thread-Topic: *** Please do not reply to this Email ***

  1. The server sending the bounce, so we know where it came from
  2. The email address sent to, to help verify the correctness and destination
  3. Bounce code, see below for common codes
  4. Bounce Reason, what the server reports as going wrong
  5. The server sending the bounce, where did it come from

Common Codes:

421 <domain> Service not available, closing transmission channel
450 Requested mail action not taken: mailbox unavailable (e.g., mailbox busy)
451 Requested action aborted: error in processing
452 Requested action not taken: insufficient system storage
500 The server could not recognize the command due to a syntax error.
501 A syntax error was encountered in command arguments.
502 This command is not implemented.
503 The server has encountered a bad sequence of commands.
504 A command parameter is not implemented.
550 User’s mailbox was unavailable (such as not found)
551 The recipient is not local to the server.
552 The action was aborted due to exceeded storage allocation.
553 The command was aborted because the mailbox name is invalid.
554 The transaction failed for some unstated reason.

 

Reading bounce back messages KB1039151

KB1039151

Reading Bounce Back Messages:

Legend Color Code:
Sent By
Recipient
Blocked By
Errors

Most bound back messages will just have the following message:

Example Person
An error occurred while trying to deliver this message to the recipient’s e-mail address. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.

The following organization rejected your message: seg-node-chi-02.trustwave.com.

Sent by Microsoft Exchange Server 2007

This is sometimes enough to diagnose the issue at a quick glance.  In this case, the email is being blocked by Mailmax, This can be told by the highlighted green portion.  Mailmax requires the user to be added to the employee list to be able to receive email.  Also, sometimes spam filters will block senders based on IP Reputation or otherwise known was “Black Listings”.
The next section contains an example of an email header.  You can view these within outlook, and copy them to a notepad//word document for easier reading.  In order to find out how to do this just google “View email header” for the version of outlook you are currently working with.  Follow the Color legend at the top of the page to follow along.

Diagnostic information for administrators:

Generating server: server.domain-name.local

example@example.com – (Who the Tech is trying to send to)
seg-node-chi-02.trustwave.com #550 <example@example.com> Relaying denied ## – This message is basically saying that since Mailmax denied the email, that it wasn’t able to send the message to the recipient.  When in doubt about the error, google the error code, in this case do a search for “email error 550” or can do “550 relaying denied” and it will turn up some results for you to understand why it’s being denied.

Original message headers:  **This just describes the contents of who send and who was supposed to receive**

Received: from server.domain-name.local ([192.168.160.205]) by server.domain-name.local ([192.168.160.206]) with mapi; Mon, 23 Jun 2014 09:05:31 -0400From: Tech Person <tech@domain-name.com>To: Example Person <example@example.com>Date: Mon, 23 Jun 2014 09:05:29 -0400Subject: TestThread-Topic: TestThread-Index: Ac+O487DFT9EGha4RGi1EdaBDQZJ7Q==Message-ID: <78FA061836D2304F91004264954DB84BBBB477D0EA@v>Accept-Language: en-USContent-Language: en-USX-MS-Has-Attach: yesX-MS-TNEF-Correlator:acceptlanguage: en-USContent-Type: multipart/related;        boundary=”_004_78FA061836D2304F91004264954DB84BBBB477D0EAEx2k7MBX01goc_”;        type=”multipart/alternative”MIME-Version: 1.0