Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, July 17, 2019 7:05 PM
Mails from external senders were not received due to larger attachments , even though there are ways to increase the size limit in Exchange.
I would like to know if there is a way to receive a bounce back or notification mail that the mail was not sent/received due to the file size, at the receiving and sending end?
So that this way the sender/receiver could know a mail communication tried to happen and failed due to larger file size XX MB.
Please advise.
All replies (8)
Wednesday, July 17, 2019 9:07 PM
Mails from external senders were not received due to larger attachments , even though there are ways to increase the size limit in Exchange.
I would like to know if there is a way to receive a bounce back or notification mail that the mail was not sent/received due to the file size, at the receiving and sending end?
So that this way the sender/receiver could know a mail communication tried to happen and failed due to larger file size XX MB.Please advise.
The sender will get a NDR message for sure unless something is really broken.
The recipient will never get one because the message was never received by their recipients domain - because In most cases, an oversized message will be rejected during the SMTP conversation.
Thursday, July 18, 2019 7:09 AM
Hi,
Agree with Andy, if the message was rejected due to the message size limitation, only the sender will get a NDR.
If a message was blocked since the message size and the sender didn't get the NDR record, you can check the transports rules firstly to make sure if any rules will delete the large message without notification.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, July 24, 2019 1:45 AM
Just checking in to see if above information was helpful. If you have any questions or need further help on this issue, please feel free to post back.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Saturday, August 3, 2019 9:17 PM
Sorry for the delay. Had to check with the recipients and it seems they did get the NDR but did not know what it was. Is there any way for all NDR's to be forwarded to an internal mailbox so that we can see all NDR's that were sent to recipients and if necessary notify the sender of the problem/fix at our end.
Sunday, August 4, 2019 11:16 AM
Sorry for the delay. Had to check with the recipients and it seems they did get the NDR but did not know what it was. Is there any way for all NDR's to be forwarded to an internal mailbox so that we can see all NDR's that were sent to recipients and if necessary notify the sender of the problem/fix at our end.
Not for oversize messages. Your org rejected the message before it was accepted so it was actually the sending server that generated the NDR, not yours. The recipients dont get a NDR, the senders get them.
This old method will probably still work for other NDRs
/en-us/previous-versions/office/exchange-server-2007/bb400930(v=exchg.80)
Monday, August 5, 2019 8:27 AM
Thanks for the info. If that is the case then is there a way to strip the offending attachment and have the email go through to the recipient with a note that the attachment has been stripped out?
Monday, August 5, 2019 5:07 PM
Thanks for the info. If that is the case then is there a way to strip the offending attachment and have the email go through to the recipient with a note that the attachment has been stripped out?
Not natively with Exchange.
Tuesday, August 13, 2019 1:45 AM
Just checking in to see if above information was helpful. Please let us know if you would like further assistance.
Regards,
Lydia Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].