You can configure your system to send emails directly to the recipient's SMTP server, so that you can track any bounce-backs from invalid email address via a Correspondence or Customer BI query using the Status and Correspondence: Status criteria respectively. For more information, refer to Business Intelligence and Reports Business Intelligence.
To set email correspondence to use the recipients SMTP server, complete the following:
- Open the Registry application from the AudienceView Desktop.
- Navigate to the:
- Registry::System::Configuration node (prior to AudienceView 6.3.2)
- System::Configuration node (AudienceView 6.3.2 and above)
- Select Yes from the 'UseRemoteSMTP' dropdown.
- In AudienceView 6.3.2 and above, enter the value that you want to appear in the email header in the 'FQDN' (fully qualified domain name) field.
- Click 'Apply'.
A window confirms that the application updated the Registry.
- Click 'OK'.
 |
Warning
- Sending emails directly to a remote SMTP server will require more time than sending them to a local server.
- Sending emails directly to a remote SMTP server may increase the risk of your messages being flagged as a spam. This could result in you being blacklisted.
For more information, refer to Email Marketing Best Practices.
- A single attempt will be made to resend soft bounces (e.g. the recipient’s inbox was full). No attempt will be made to resend hard bounces (e.g. the email was invalid).
- The remote site may have an SMTP server that acts as a proxy, buffering the emails and forwarding them to the actual servers. If this is the case, then error information will not be available for tracking.
|
 |
Hint
You can use an online content checker (e.g. isnotspam and lyris) to assess the likelihood that the content of your email correspondence will be considered spam. Some content checkers also provide reports, indicating how to improve the content so that it will not be assessed as spam. |