SMTP Authentication provides an enhanced level of security for inbound and outbound SMTP traffic.
It is recommended that you only apply SMTP Authentication to an inbound connection if TLS is enabled. If TLS is not enabled, SMTP Authentication credentials are carried in plain-text. |
Connections are unique configurations that determine how traffic is decrypted and authenticated. You can create multiple connections, and configure certificate recognition and inbound SMTP Authentication settings for each profile. See Create a connection for more information.
When setting up a Connection Profile for inbound SMTP authentication, user names apply across all Connection Profiles. You can also see if specific user names fail during authentication in message tracking. If the domain is not provided, the host name is automatically added to the Simple Authentication and Security Layer (SASL) user name. See Find and track a message for more information.
You can use a simple user name, for example user1, but you can also specify a domain name, for example user1@companyname.com. If you use a domain name as the user name, you need to provide this to the manager of the client MTA. Note that if you use a simple user name, when viewed in message tracking the user name has the host name appended but this is transparent to the client MTA. |
You can send outbound mail with the appropriate credentials for authentication by the client server. See Mail Domains and Routing for more information.
To find out more about configuring hosts and certification for a Connection Profile, see Create a Connection.
The
© 1995–2018 Clearswift Ltd.