Enterprise Vault.cloud™ Lync Connector Administration Guide
- About Lync Connector
- Introduction to Enterprise Vault.cloud Lync Connector
- Changes in Lync Connector version 1.2.2
- Lync Connector release history
- Lync Connector architecture
- The components of Lync Connector
- About Lync Connector synchronizations
- Conference transcript availability options
- About SIP address substitution
- About the format of the archived transcripts
- About the archiving of historical data
- Lync Connector evaluation mode
- About the Lync Connector Console
- Requirements for Lync Connector
- Steps for setting up archiving with Lync Connector
- Installing Lync Connector
- Configuring Lync Connector
- Configuring Lync Connector
- Configuration wizard page 1: Enterprise Vault.cloud credentials
- Configuration wizard page 2: Lync archiving database
- Configuration wizard page 3: Working folder
- Configuration wizard page 4: File management
- Configuration wizard page 5: Active Directory
- Configuration wizard page 6: SMTP
- Configuration wizard page 7: Sender email address
- Configuration wizard page 8: Conference transcript availability
- Configuration wizard: Configuration complete page
- Viewing or changing the credentials of the Lync Connector service account
- 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
- About troubleshooting Lync Connector issues
- Use of Lync 2013 clients with a Lync 2010 server
- Lync archiving database export failure errors
- Synchronization failures
- Transcript processing failures
- SMTP server issues
- Failure reason: "Message size exceeds fixed maximum message size"
- About the Lync Connector trace logs
- Accessing the trace logs
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