Allow Settings for Message Expiration Timeout Interval and NDR
For some error codes related to sending mails, the senders may receive the NDR immediately. However, for some other error codes, the mail server marks the undeliverable messages as a temporary error and the senders doesn't immediately receive an NDR. Instead, Exchange Online repeatedly tries to deliver the message over two days. Only after two days of unsuccessful delivery attempts does the sender receive this NDR.
For some time critical businesses this is not acceptable. The user has to be informed very quickly (<6 hours) that his Mail was not delivered by now. Then the user can phone the recipient or sent the mail to another address. I do not care if exchange online continues trying to send the message after 6 hours, but the user has to be informed.
Exchange Server 2016 an older allowed customization of the Message Expiration Timeout Interval and NDR Settings. Please add this to ExchangeOnline
Today, based on feedback, we’ve lowered the timeout to 24 hours. In the future, we are planning more improvements, although we do not have any dates or details to share at this time. Thank you for the continued feedback.
Chris Sharpe commented
Hi Admin. Can you tell me if these recommendations have been taken on board for aqdmin to adjust times of NDR. '550 5.4.316 Message expired, connection refused(Socket error code 10061). The email was sent 2 days ago but no notifications to the sender that there was a problem. We now have a very annoyed customer that did not receive their information on time.
Can you advise if this feature has now been added to 365 Admin? Many Thanks
2 days is too long. we had a legal deadline expire during this time and it was assumed the client received the email.
To admin: I understand what you're saying with regards to balancing. But, at the very least, the user who has sent it should receive immediate notice that the message was non-deliverable. That way the impetus is on them to either contact the recipient or the admin depending on how time-critical the message is.
I agree with David Duarte - need to receive an immediate notice that something is amiss. 2 days later is 2 days too late.
David Duarte commented
Initial warning of delayed mails should be standard. We have had a number of critical emails, eventually not delivered for various reasons, and the sending users assuming that the email was received. If they had received a warning then at least they could have phoned the recipients, at that point, instead of finding out 48hrs later that the mail had not gone.
Dan Stonier commented
Needing the ability to change this value seems like a no-brainer. 2 days is a LONG time for many customers to find out that a message couldn't go anywhere.
I get that this rule has applied to servers in the past, but if you can't make this apply per tenant, at LEAST make the default time out value lower? If it times out "prematurely" - resend the message!
Mike Dunn commented
Having the ability to notify admins/users when a messages is queued would be great. Having the ability to re-queue the messages would be even better
M Hatami commented
This is an urgent critical request. Thanks for your post
This is very good idea
Please provide this setting as soon as possible to prevent lost of communication, lost of profit and lost of service level for our company
Some of our company users or senders found that we cannot receive email or recipient cannot receive their email for a long period, we just know their email status is in pending. Some important email can deliver to recipient within a short period, it can induce lost of sales order or degrade our service level.
We cannot accept the sender will receive the deliver failed report after 24 or 48 hours later after sent out his email
Please allow us to adjust the NDR report response time when email pending was happened.
Dan Votkevich commented
allow admins to adjust the time that an undelivered email stays in the deferral queue - two days is too long.