Connect SMTP Relay

PreviousUnderstanding the 'White Label Tracking Link'NextConnect Mailgun API

Last updated 1 year ago

Was this helpful?

Connect SMTP Relay

Watch our SMTP Relay introduction video then read through our easy to follow documentation with more details below:

SMTP Relay is a flexible and universal standard for using any email service provider or 3rd party MTA software as an email delivery engine.

All ESPs like SMTP.com or Elastic Email and software such as PowerMTA or MailerQ should be fully compatible.

SMTP Relay is only unidirectional

This means when we pass the message off to your relay service, the delivery progress and reporting is handled entirely on their end. Use the SMTP Relay platform's interface to monitor delivery as no data is relayed back to your platform.

API integrations are bidirectional

To track real-time delivery progress natively in your platform including bounce and complaint rates, use an API implementation such as Mailgun, Sparkpost, or Amazon SES.

Velocity MTA also tracks real-time delivery over your own IP Addresses, which comes free with your platform.

While logged in to the backend as administrator, click the connect menu, select SMTP Relay, then click Add SMTP Relay.

Name

Give your SMTP Relay connection an internal name, this will only be seen by you and is for management purposes only.

Hostname

Enter the hostname your SMTP Relay service accepts connections on. Look this up in their documentation or ask their support team.

EHLO

Use the domain name you'll be sending your email from here, not your admin_url domain used for your emaildelivery.com platform management, unless they're the same.

Enable Authentication

Most of the time you'll be authenticating using a username and password when using SMTP Relay, however, there are advanced cases where you may authenticate by using your platform's IP address or other methods.

SMTP Relay Authentication

You'll need to check with your SMTP Relay service documentation or support team to find your username and password, as every service uses a different format.

Examples: Sendgrid requires username 'apikey', SparkPost requires username SMTP_Injection, Elastic Email requires your email address as the username.

Some services use an API key as your password, some use a password set by you, etc.

Encryption

Check with your SMTP Relay service documentation or support team on supported forms of encryption. Using encryption is always better where possible, but sometimes disabling it may be necessary for troubleshooting purposes.

Encryption

Check with your SMTP Relay service documentation or support team on which port to use with your chosen encryption method.

White-label tracking links

Unless you change your link domain, your admin_url domain will be used for your tracking links in your email messages. You can add a custom link to automatically match your domain branding for mail sent through this SMTP relay connection, no further action is required beyond this step.

Make sure you point a DNS A record at your platform IP Address for your tracking link or it will not work

Add additional headers

This is an advanced feature you can safely ignore unless you really know what you're doing. It's common for SMTP Relay implementations to allow additional commands and configuration to be executed by including a special email header with instructions in it.

Below is an example from SparkPost's documentation, showing how to enable their open and click tracking on your messages:

You normally wouldn't want to do this which is why SparkPost has it disabled by default; open and click tracking is already done through your emaildelivery.com platform.

PowerMTA Support

The most common way to tell PowerMTA how to handle your mail is by including an X-Virtual-MTA header in your messages, like so:

Message throttling

Ignore this setting unless instructed otherwise by your SMTP Relay service.

Next Steps