Queued, Deferred, and Bounced Messages FAQ
Applies to: Office 365 for professionals and small businesses, Office 365 for enterprises, Live@edu, Forefront Online Protection for Exchange
Topic Last Modified: 2012-04-05
This topic provides answers to frequently asked questions about messages that have been queued, deferred, or bounced during the Forefront Online Protection for Exchange (FOPE) filtering process.
A. Messages are queued, or deferred, if the FOPE service is unable to make a connection to the recipient server for delivery. It will not defer messages if a 500-series error is returned from the recipient network.
A. Messages will be held when a connection to the recipient server cannot be made and the recipient’s server is returning a “temporary failure” such as a connection time-out, connection refused, or a 400-series error. If there is a permanent failure, such as a 500-series error, then the message will be returned to the sender.
A. Messages in deferral will be held for up to five days before returning to the sender. An attempt will be made to resend messages approximately every twenty minutes during this period. If a 500-series error/permanent failure is returned, the message will be removed from the deferral queue and will be immediately returned to the sender.
A. A notification indicating that the recipient has not received the email will be emailed to the sending party after two hours of a message being in deferral. This is the only notification sent until the final return after five days.
A. The monitor tool in the Admin Center may be used to send warning emails to out-of-band email addresses after a predefined threshold of messages in deferral has been reached. These notifications will be sent every 30 minutes, as long as the number of messages in queue remains above the predefined threshold.
A. It is not necessary to notify FOPE of any server outages. Messages will begin to defer as soon as temporary failures are returned.