The Authenticated SMTP Connector lets you connect a non-Zendesk email server to your Zendesk Support instance. It is specifically designed for organizations that prefer to use their own email servers or cannot use third-party email servers due to internal corporate policies, data regulations, or encryption needs.
There are two different ways you can use the connector to meet the needs of your company: two-way authenticated relay or outbound-only authenticated relay. Each use case has a distinctive way of relaying email and is set up differently, so it is important to understand how you intend to use it.
Using the connector for two-way authenticated email relay
Use two-way authenticated relay to establish a secure and authenticated two-way connection between your email domain or service and Zendesk's servers. While this requires more setup and configuration, it is ideal for on-premise servers or domains with added security layers, such as Mimecast. Organizations with strict data compliance and security requirements may prefer this setup, as it keeps all email data within their controlled environment, reducing the risk of data breaches and non-compliance.
![](https://zen-marketing-documentation.s3.amazonaws.com/docs/en/email_SMTPAuth_flow.png)
- Improved tracking and management. You can better track interactions and manage email threads. This ensures all communications are logged and organized within your support system, improving the overall customer support experience. In addition, tags are added to tickets created by unauthenticated or authenticated email, allowing you to use ticket triggers to help track unauthenticated email.
- Better control over email policies. Organizations can implement their own email policies and controls when using their email servers to send and receive emails. This allows for greater flexibility in managing spam filters, security protocols, and other email-related settings.
- Simplified troubleshooting. When both sending and receiving are handled by the same system, troubleshooting can be simplified. Email delivery or reception issues can be diagnosed more efficiently when both processes are managed within the same environment.
For more information, see Setting up the Authenticated SMTP Connector for two-way email relay.
Using the connector for outbound-only authenticated email relay
Use outbound-only authenticated relay to allow for standard auto-forwarding of inbound email traffic to Zendesk, but an authenticated outbound connection with your email domain or service so all outbound sending for the connected addresses occurs through your domain or email service.
Although this option uses standard auto-forwarding, it requires a different setup that can't leverage existing addresses using standard auto-forwarding. Each support address must be newly added using the authenticated workflow.
![](https://zen-marketing-documentation.s3.amazonaws.com/docs/en/email_SMTPAuth_flow_outbound.png)
- Email service limitations. Setting up the connector this way allows for cloud-based email services that don’t offer authenticated outbound relays to other systems, like Exchange Online, Office365 Cloud, and G-Suite.
- Flexibility and scalability. Forwarding inbound email traffic allows organizations to use external email services to receive emails. This can provide greater flexibility and scalability, especially as the organization grows.
- Simplified Management. Using a third-party service for inbound emails can simplify management, as these services typically handle updates, security, and maintenance, allowing organizations to focus on other priorities.
For more information, see Setting up the Authenticated SMTP Connector for outbound-only email relay.
3 comments
mfg
Depending on how your business email server is set up, can it be configured to request/receive bounce, delivery, or read receipts?
3
Jorge - Leafworks
Hi! I am very interested in this new feature and I have actually the same question as the mfg user. Is this feature going to improve the handling of:
- Email bounces (mail could not be delivered, email address does not exist)
- OoO messages and other automatic answers
- The situation when a user sets the Zendesk Support E-Mail address on BCC
0
Sean Cusick
Hi Jorge and mfg,
Because this feature passes the responsibility of outbound sending over to your domain things like bounces, delivery reports and read receipts would happen at that sending domain (though read receipts require modifying the body of the email, which should be approached with caution and testing).
All other Zendesk functionality - like suspension causes for automated traffic and behavior around BCC submissions - would not change. Though you can choose to modify the structure of an inbound BCC'd email so that you can achieve the desired behavior at the forwarding domain.
We are tracking feature requests, so I would encourage you to test in a sandbox account and let us know what you think in the Product Feedback section of our Community pages.
0