Hi,

Email relaying is using an email server to send email that did not originate on the email server. Companies set up email relaying to:

• Route all email through their own email servers to avoid the appearance of email spoofing by Salesforce. Email spoofing is the forging of email headers to make messages appear as if they came from someone other than the original sender.
• Store copies of all email as required by government regulations in various industries.
• Apply existing content filters that scan messages for data and content that is not approved to be sent out through company email.
• Run outbound email through antivirus software before sending it to customers.
• Append data such as company-wide disclaimers at the bottom of email messages.

You can set up email relaying for Salesforce-generated email by configuring Salesforce to automatically route email through your company's Simple Mail Transfer Protocol (SMTP) server. Contact salesforce.com to enable email relaying for your organization.

Steps to configure email relaying:

1. Click Your Name | Setup | Email Administration | Email Relay Activation.

    2.  Configure the following settings:

      I. Email Host: - The host name or IP address of your company's SMTP server. Obtain this information from your email administrator.   <mail server>.<domain>.<domain extension> For example:   mail.acme.com

   II. Port:-The port number of your company's SMTP server. Obtain this information from your email administrator. Email  relaying is supported on port numbers 25, 587, 10025, and 11025.

 III. TLS Setting:-Specifies whether Salesforce uses TLS for SMTP sessions. Select one of the following options:

  Preferred (default): If the remote server offers TLS, Salesforce upgrades the current SMTP session to use TLS. If TLS is unavailable, Salesforce continues the session without TLS.

  Required: Salesforce continues the session only if the remote server offers TLS. If TLS is unavailable, Salesforce terminates the session without delivering the email.

 Preferred Verify: If the remote server offers TLS, Salesforce upgrades the current SMTP session to use TLS. Before the session initiates, Salesforce verifies the certificate is signed by a valid certificate authority, and that the common name presented in the certificate matches the domain or mail exchange of the current connection. If TLS is available but the certificate is not signed or the common name does not match, Salesforce disconnects the session and does not deliver the email. If TLS is unavailable, Salesforce continues the session without TLS.

IV. Required Verify: Salesforce continues the session only if the remote server offers TLS, the certificate is signed by a valid certificate authority and the common name presented in the certificate matches the domain or mail exchange to which Salesforce is connected. If any of these criteria are not met, Salesforce terminates the session without delivering the email.

  V.  Restrict:  Relay to Domains   Specifies whether to restrict the email relaying functionality to certain domains. If you select this option, enter the names of those domains separated by commas in the text field below. (The asterisk (*) wildcard is allowed; for example, *.subdomains.com matches john@aco.subdomains.com and john@bco.subdomains.com (but not john@subdomains.com)). This causes Salesforce to route email to your company's SMTP server only if the email is addressed to one of the listed domains. If you select the checkbox but do not list any domains, Salesforce routes all email to your company's SMTP server.

VI. Active: Enables email relaying for your organization. If you deselect this checkbox, Salesforce keeps the email relay configuration but does not route email to your company's email server.

3. Click Save.

Did this answer your question? If not, let me know what didn't work, or if so, please mark it solved.