Queued delivery

NOTE: The option for direct delivery to the local email server is obsolete and is no longer available in NoSpamProxy since version 13. Delivery via queues is always applied.

NoSpamProxy first places the email in a queue after receipt and only then forwards the email to the configured smarthost(s). For the successful receipt of the email it is not relevant whether the next smarthost is available or not.

NOTE: If you select the queued delivery mode for the send connector, any existing configuration is replaced by the newly configured queued delivery mode. When you switch to queued delivery mode, the first SMTP connector is immediately configured.

NOTE: If you added to the local servers under Adding corporate email servers, an Office 365 connector will be displayed here. This connector is responsible for delivering local emails to Office 365. Apart from being bound to certain gateway roles, you cannot modify or delete this connector.

Settings

General settings Enter a name and select one or more Gateway Roles. Subsequently, determine the cost of the connector.

SMTP connections You can configure multiple smarthosts under SMTP connections. An attempt will be made to deliver the email to one of the configured smarthosts in turn. The sequence is neither configurable nor can it be influenced by the user. As soon as a smarthost receives the email, the email has been successfully delivered.

Configuring the smarthost The configuration of a smarthost for local delivery proceeds as described in the chapter Smarthost: Email Delivery via Dedicated Server. The send connector for local addresses uses a client identity for connection security.

DNS routing restrictions You define the restrictions for the namespace managed by the connector under DNS routing restrictions. The configuration of the restrictions for local delivery is done as described under DNS-Routing-Einschränkungen durch Konnektor-Namensräume.