Enterprise Vault.cloud™ Lync Connector Administration Guide
- About Lync Connector
- Requirements for Lync Connector
- Steps for setting up archiving with Lync Connector
- Installing Lync Connector
- Configuring Lync Connector
- Managing archiving with Lync Connector
- Managing SIP address substitution
- Lync Connector workflow
- Lync Connector reports and logged events
- Lync Connector advanced settings
- Troubleshooting Lync Connector issues
SMTP server issues
SMTP-related issues can vary depending on whether the SMTP routing is direct to Enterprise Vault.cloud or indirect, through an on-premises SMTP server.
See SMTP routing options.
The most likely reasons for issues with direct SMTP routing are as follows:
A firewall is blocking outgoing access to the Internet on port 25.
DNS lookups on the journal address domain fail.
The most likely reasons for issues with indirect SMTP routing are as follows:
A firewall is blocking the connection to the on-premises SMTP server.
The on-premises SMTP server TLS configuration does not match the SMTP TLS configuration setting you specified in Lync Connector.
The on-premises SMTP server authentication configuration does not match the SMTP authentication configuration details you specified in Lync Connector.
The on-premises SMTP server does not allow relaying. Or relaying is restricted by IP address and the computer on which Lync Connector is installed is not on the allow list.
The on-premises SMTP server is unable to relay emails to Enterprise Vault.cloud, for example because DNS lookups on the journal address domain are failing.
The SMTP server has a messages size limit that is smaller than the configured maximum email size in Lync Connector.
See Failure reason: "Message size exceeds fixed maximum message size".
More Information