Solved

How can I use bounce-back error message to determine delivery problem

Posted on 2015-01-08
2
145 Views
Last Modified: 2015-01-14
Background Info: I am Exchange Server admin for two office buildings, both with onsite, single-server Exchange setups. Sender at office A is trying to send to Recipient at office B an email with 25MB attachment.  I have verified using the get-sendconnetor and get-receiveconnector commands on both servers that: all connectors are set with MaxMessageSize of 50MB.

Problem: Sender at office A receives the following bounce-back error, which I have edited for privacy purposes.  My edits are with either double << >> or double (( )) designations:
--------------------------------------------
From: postmaster2@tbylaw.com [mailto:postmaster2@tbylaw.com]
Sent: Thursday, January 08, 2015 11:53 AM
To: Joshua Payne
Subject: Undeliverable: FW: RE: BET Transportation and David McDonald

Delivery has failed to these recipients or groups:

<<recipient email address>>
This message is too large to send. To be able to send it, make the message

smaller, for example, by removing attachments.

Diagnostic information for administrators:

Generating server: <<.local name of receiving server>>

<<recipient email address>>
#< #5.2.3 smtp;550 5.2.3 RESOLVER.RST.SendSizeLimit; message too large for this

sender> #SMTP#

Original message headers:

Received: from <<.com name of sending server>> ((internal ip of firewall at

receiving office)) by <<.com name of receiving server>>
 ((internal ip of receiving server)) with Microsoft SMTP Server (TLS) id

8.2.254.0; Thu, 8 Jan
 2015 11:50:43 -0700
Received: from <<.local name and MAC id from sending server>> with mapi id
 14.03.0224.002; Thu, 8 Jan 2015 11:50:10 -0700
From: Joshua Payne <<sender email address>>
To: <<recipient email address>>
Subject: FW: RE: BET Transportation and David McDonald
Thread-Topic: RE: BET Transportation and David McDonald
Thread-Index: AdAp33d9Ez/FAIGTSaaTKlqnWlIUnQBk7ivw
Date: Thu, 8 Jan 2015 18:49:53 +0000
Message-ID: <80EF4E30B0006743ACA0808854D655A33C5DA0A9@<<.local name of sending

server>>>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [[internal ip of sender computer]]
Content-Type: text/plain
MIME-Version: 1.0
Return-Path: <<sender email address>>
Received-SPF: SoftFail (<<.local name of receiving server>>: domain of

transitioning
 <<sender email address>> discourages use of <<internal ip of firewall at

receiving office>> as permitted sender)
-----------------------------------

The message is coming from the recipient mail server, but seems to be saying that the sender does not have permission to send that size of message, which I do not understand.  I also am confused about the use of the .local and .com server names.

Please help me to decipher this error, and figure out where the failure is occurring and how I can correct it so the email attachment size will not prevent its delivery.

Thanks - Rob
0
Comment
Question by:Rob Grinage
2 Comments
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 40538979
If you have only changed the send/receive connectors then you haven't done everything. There are other places where the restriction could be set.
This article on the Exchange Wiki outlines where you need to change things.

http://social.technet.microsoft.com/wiki/contents/articles/22765.step-by-step-exchange-2013-email-message-size-restriction-detail.aspx

The NDRs will have the server's real name in them, that is to be expected.

Simon.
0
 
LVL 1

Author Closing Comment

by:Rob Grinage
ID: 40549542
This was the solution - it showed me the Global settings were not set correctly.
0

Featured Post

Are end users causing IT problems again?

You’ve taken the time to design and update all your end user’s email signatures, only to find out they’re messing up the HTML, changing the font and ruining the imagery. What can you do to prevent this? Find out how you can save your signatures from end users today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
Read this checklist to learn more about the 15 things you should never include in an email signature.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now