SMTP Account details

In most situations its best to send emails out via the appropriate SMTP relay servers. But MultiSendcon also supports sending emails directly to the recipient servers without any relay server in between. Usually this is done only for systems that are on a fixed IP address that are also the target of the DNS MX records. Contrary to Microsoft Exchange, MultiSendcon also supports sending out on different local IPs for those systems that have multiple network cards with IP addresses installed.

Parameters on this page:

• Descriptive Name: Just a name that describes this account to yourself so you can find it again in the list of accounts.
• Local IP Address: In systems with more than one network card you can select the card used for this account by it's local IP address.
• HELO/EHLO domain: Domain name used to sign on to the SMTP server in the HELO or EHLO command. This is the same as the FQDN for HELO / EHLO in the Exchange send connector configuration.
• Minimum wait: Number of seconds that MultiSendcon waits between two emails sent through this account. This can be used to throttle throughput in order to accomodate slower relay servers. Set to 0 for no wait time, i.e. to use the full bandwidth.
• Use this account only for certain sender addresses: The sender addresses that this account will be used to send out emails for. Can be a single email address (user@domain.com) or a whole domain with wildcards (*@domain.com).
• Use this account only for certain recipient addresses: The recipient addresses that this account will be used to send out emails for. Can be a single email address (user@domain.com) or a whole domain with wildcards (*@domain.com).
• Replace sender addresses with a fixed sender address: New feature in v2.50: If activated will replace the sender email address in all outgoing emails with a fixed sender address.
• ..but not for emails tagged "private": Allows the users to override the sender replacement by setting the "Sensitivity" tag to "Private" in an email.