• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2660
  • Last Modified:

Rejected mail notice not getting to sender.

I have a limit of 6mb for attachment size setup on our 2003 exchange server. As far as I can tell, it's sending out e-mail to the sender notifying them of the  rejected e-mail. The problem is that, either it's not sending out, or the sender is somehow blocking the rejection. The intended recipient does not receive notification. We have clients following up a week later asking about an e-mail they sent that they thought was received.  What cab I check on the sever, change or work around to rectify this? Am I missing a setting or should I modify the way the notification is sent?
1 Solution
Our system is similar, and we constantly have people not read the error messages or cannot understand what the message is telling them. My only suggestion is to attempt to make the notification as plain English as possible, i.e. ask your Mom (or any other person over 50) if she can understand the message you want to send out.
Under Global Settings > Internet Message Formats > Righ Click the "Default" on the right window and select properties. Then the advanced TAB.
At the bottom are options for responses to the Internet. Are they checked?
If you send an email to one of your exchange 2003 mailbox, from gmail or similar account, with a 7 MB attachment, do you get the bounced back message ?

In message tracking, can you see the flow of events that happened ? and are you able to see messages sent out ?

also, is your exchange 2003 server set to send out NDR's ?

To disable NDRs, follow these steps:
Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
Expand the Global Settings container in the left pane, click Internet Message Formats, right-click the Default object, and then click Properties.
Click the Advanced tab.
Click to clear the Allow non-delivery reports check box, and then click OK.
To specify who can receive copies of NDRs, follow these steps:
Under Administrative Groups, expand First Administrative Group, expand Servers, expand servername, expand Protocols, expand SMTP, and then open the Default SMTP Virtual Server properties.
Click the Messages tab, and then add an address to the Send copy of non-delivery report to field.
Stop, and then restart the MS Exchange Routing Engine and SMTP services.
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

wlamoreAuthor Commented:
All the boxes are checked in the advanced tab. I, as the administrator am receiving the notices but I don't think anything is going to the recipient ( Our employees). They are not aware of the message not getting to them , so they can't even contact the sender to let them know. Should there be a way to strip the attachment and send on the message with a notice that the attachment was stripped?
Is this happening with anyone on the outside? if its just one company it could be a setting on their side.
Have you tested from Gmail, etc?
Easiest test: Just make up an email address. JustATest@myco.com. Don't worry about an attachment, just see if you can get a bounce.
wlamoreAuthor Commented:
I tested without an attachment and got a returned e-mail message on the bad address. I'm sending a large attachment from my private account now to see if I get anything.It might take a little while.
wlamoreAuthor Commented:
Update - I'm still wating for the e-mail or any notification to come through on either end.
Have done message tracking to see if it is coming in? Or maybe a SPAM gateway you could check?

Here is an interesting tid-bit about size limits and NDRs:
"If a remote server supports Extended Simple Mail Transfer Protocol (ESMTP), it will detect the advertised maximum message size value when it connects to the SMTP virtual server and won't attempt to deliver any messages that exceed the limit. Instead the remote server will simply send an NDR to the sender of an oversized message. A remote server that doesn't support ESMTP will try to send a message that exceeds the size limit, but will still end up sending an NDR to the sender when the message doesn't go through."
wlamoreAuthor Commented:
Well, I'm stumped.
 I have all the setting in exchange as referenced, but upon testing from my private accounts, the e-mail and large attachment arrive through my spam filter with no errors. The email is then pushed my mail server. I'm not getting the email or any NDRs on either side, sender or recipient.
wlamoreAuthor Commented:
Seems to have started working again, I took off any of the restriction I had placed on the SMTP protocol and just went with the global settings. Seemed to work
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now