Business Continuity Settings
Continuity mode is made up of three options:
Optional - this mode may be helpful to organisations with a large number of remote users. The decision of whether to work in business continuity mode is left to the users.
Disabled - this mode is the default mode. It signals that the email system is working as expected and email flows from the email client to the email system and finally through Mailsphere.
Enabled - this mode is used by the domain administrator to force all their Outlook users into business continuity mode. This may be as a result of an email server failure or a network issue. Â Once selected and saved the Outlook clients will switch from sending email through the email system to sending email through the Mailsphere MTA's. Â The users will not need to do anything for this to become active.
When an organisation is suffering from an email outage it may be desirable to disable the delivery failures to external senders if your email users are able to receive and send email via Mailsphere Business Continuity. Â The configuration here allows the following options:
Enabled - this is the default setting. Â This complies with the SMTP standards and notifies the sender if their email cannot be delivered due to a temporary or permanent failure.
Disabled - this option allows delivery failures to be disabled, regardless of whether the email system is operating correctly or suffering from an outage.
Disabled when on Continuity - this option only disables delivery failure messages when the Continuity mode is Â in an Enabled state. Â Mailsphere will continue to send delivery failures if the continuity mode is either Disabled or Optional.
The different error codes that make up Temporary and Permanent policies are listed below:
400-series SMTP codes (Temporary) - the email was not accepted for delivery by a remote server. Â However, the error condition is temporary and the email may be resent for another delivery attempt.
500-series SMTP codes (Permanent) - the email could not be delivered because of a terminal error.Â The sender-SMTP is discouraged from repeating the exact request for delivery (in the same sequence). Even some"permanent" error conditions can be corrected (i.e., a typo in the recipient address), so check the accuracy of the address.Â
Temporary Codes - these invoke a retry for the delivery of the email that will continue for 5 days:
421 Service not available, closing transmission channel [This may be a reply to any command if the service knows it must shut down] 450 Requested mail action not taken: mailbox unavailable [E.g., mailbox busy] 451 Requested action aborted: local error in processing 452 Requested action not taken: insufficient system storage
Permanent Codes - these result in a confirmed failure and a retry will not be attempted
500 Syntax error, command unrecognised [This may include errors such as command line too long] 501 Syntax error in parameters or arguments 502 Command not implemented 503 Bad sequence of commands 504 Command parameter not implemented 550 Requested action not taken: mailbox unavailable [E.g., mailbox not found, no access] 551 User not local; please try <forward-path> 552 Requested mail action aborted: exceeded storage allocation 553 Requested action not taken: mailbox name not allowed [E.g., mailbox syntax incorrect] 554 Transaction failed
The availability alerts allow for two different thresholds to be set; one for hourly and a second for 24 hour thresholds.
To configure an alert:
- Add the number of errors you wish to trigger the alert and then save.
- Add an email address to send the alert to. You can add multiple email addresses and / or use email addresses not managed by Mailsphere.
- To remove an email address from the alert subscription simply click the 'Remove' button next to the email address.
Additional configuration for Office365
If you are using Office365 with Mailsphere and wish the Availability alerts and monitoring to operate with your email system you will need to disable the non-delivery reports using the following option:
Exchange Admin Center - mail flow - remote domains
Edit the remote domains and ensure that Allow non-delivery reports is unchecked.