Delivery
Contents
Message Routing
Send all outbound email directly to the recipient's mail server
When this option is chosen, MDaemon will attempt to deliver mail directly instead of passing it to another host. MDaemon will place undeliverable messages into its retry system and continue to attempt to deliver them according to the parameters and time intervals that you set on the Retry Queue screen of the Mail Queues dialog.
Send all outbound email to a smart host
Select this option if you want outbound email, regardless of its destination domain, to be spooled to another host or server for routed delivery. If selected, outbound email will be sent to the Default Smart Host specified below. Typically, this feature is useful during high volume periods when direct message delivery would result in an excessive taxation of server resources. If a message cannot be delivered to the designated server then it will be moved into the retry system and MDaemon will continue to attempt to deliver it according to the parameters and time intervals that you set on the Retry Queue screen of the Mail Queues dialog.
Send all email directly first, and then to smart hosts if there are problems
This option is a combination of the previous two delivery options. First MDaemon will attempt to deliver outbound email directly to the server, but if it is unable to deliver it, it will instead send the email to the Default Smart Host specified below. Undeliverable mail is email destined for hosts that could not be resolved to an actual IP address (such as an unregistered gateway to a remote network) or email destined for a host that was resolved properly but could not be connected to directly or is refusing direct connections. Rather than return such mail to its sender, this option causes MDaemon to pass the message off to a more powerful MTA. Sometimes the mail system run by your ISP may have routed methods of mail delivery to which your local server may not have direct access. If, however, a message cannot be delivered to the designated smart host then it will be moved to into the retry system and MDaemon will continue to attempt to deliver it according to the parameters and time intervals that you set on the Retry Queue screen of the Mail Queues dialog. At each subsequent delivery attempt, MDaemon will again first try to deliver the message directly to its recipient and then to the designated smart host.
Default Smart Host
Default smart host
Specify your ISP or mail host's name or IP address here. This is generally the SMTP server on your ISP.
|
Do not enter MDaemon's Default Domain or IP addresses into this text box. This entry should be an ISP or other mail server that can relay mail for you. |
Treat default smart host as domain name and deliver to its MX hosts
Enable this option if you want MDaemon to treat the Default smart host as a domain name, querying its DNS record and delivering to its MX hosts.
Use SMTP authentication
Click this check box and enter your login credentials below if the Default Smart Host requires authentication. These login credentials will be used for all outbound SMTP messages sent to the smart host. If, however, you choose to use the Allow per-account authentication option below, then MDaemon will authenticate to the host separately for each message, using the sending account’s Smart Host Access credentials designated on the Mail Services screen of the Account Editor.
User name
Enter your user name or login here.
Password
Use this option to specify your smart host login password.
Perform a POP check first
If your smart host requires a POP3 check before it will accept messages from you, click this check box and enter your required credentials below.
Host or IP
Enter the host or IP address to which you wish to connect.
User name
This is the POP account's login or account name.
Password
This is the POP account's password.
Allow per-account authentication
Click this checkbox if you wish to use per-account authentication for outbound SMTP messages sent to the Default Smart Host specified above. Instead of using the User name and Password credentials provided here, each account’s Smart Host Access credentials, designated on the Mail Services screen, will be used instead. If no smart host credentials have been designated for a given account, the above credentials will be used instead.
If you wish to configure per-account authentication to use each account’s Email password instead of its optional Smart host password, then you can do so by editing the following key in the MDaemon.ini file:
[AUTH]
ISPAUTHUsePasswords=Yes (default No)
|
Enabling the ISPAUTHUsePasswords=Yes option will over time effectively communicate all your accounts’ local mail passwords to your smart host. This could pose a risk to mail security, since it is providing sensitive information to another server. You should not use this option unless you are using a smart host that you absolutely trust and you believe it is necessary to do so. Further, you should note that if you use this option and give your users permission to change their Email password via WorldClient or some other means, then changing the Email password will also effectively change the Smart host password. This could cause smart host authentication to fail for an account when its Email password is changed locally but the corresponding Smart host password isn't changed at your smart host. |
Abort delivery if SMTP RCPT command receives a 5xx error
Enable this option if you wish MDaemon to abort its attempt to deliver a message when it receives a 5xx fatal error in response to the SMTP RCPT command. This option is disabled by default.
Bounce message if receiving domain has no MX records
Ordinarily when MDaemon checks the receiving domain's DNS records, it will look for MX records and then for an A record when no MX records are found. If neither are found then it will bounce the message back to the sender as undeliverable. Click this option if you want MDaemon to immediately bounce the message when no MX record is found, instead of allowing it to then look for an A record also. This option is Disabled by default.
Bounce message on first 5XX error from any of receiving domain's MX hosts
When this checkbox is enabled, MDaemon will return/bounce the message when it receives a 5xx fatal error response from an MX host. Consequently, it won’t continue trying to deliver the message to any subsequent MX hosts that may be designated for the recipient’s domain. If this option is disabled, MDaemon won’t bounce the message as long as at least one of the MX hosts returns a 4xx non-fatal error response. This option is enabled by default.
Bounce message on 5xx errors from smart hosts
Use this option if you wish to return/bounce a message when it receives a 5xx fatal error response from your smart hosts.
See: