How to use Gmail as an SMTP relay for notification testing

Description

Aspera transfer servers, web apps and Console offer the feature of email notifications for transfer events.

In order to enable email notifications, you will need to specify the SMTP server that the Aspera product should use to send the emails, along with any credentials to the server if necessary.

Gmail is one possibility, as it offers 3 different SMTP servers for its users. This article will describe how to use the 2 SMTP servers that don’t require Google Apps in your Aspera products.

Note: These Gmail servers work well for testing, but may not be appropriate for long-term production use. This is a general reference and not meant to be a definitive guide or recommendation.



Gmail SMTP server

This SMTP server requires authentication and either TLS or SSL. Emails can be sent to any address as normal. There is a limit of 2,000 emails sent per day.

The configuration information is as follows:

Host/SMTP Mail Server
smtp.gmail.com
Port 465 (SSL) or 587 (TLS)
Connection/Use TLS if available Use TLS/Yes 
Authentication Password/login


For example, in Faspex your configuration might look like the following:

faspexgmail.jpg

 

Restricted Gmail SMTP server

This SMTP server does not require TLS or authentication. It is restricted because emails can only be sent to other Gmail addresses or Google apps users--therefore it may only make sense for testing within an internal network that uses Gmail or Google apps. Limits apply per recipient.

The configuration information is as follows:

Host/SMTP Mail Server
aspmx.l.google.com
Port 25
Connection/Use TLS if available Use TLS/Yes (optional but recommended)
Authentication Open



For example, on Enterprise Server your configuration might look like the following:

Google_SMTP_Relay_for_testing.png

Though not required, TLS is recommended so recipients don’t reject the email or send it to spam.

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk