https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxOTc0IiwiaGFzaCI6IjVlZTg0YmU1LWRmZDQtNDA5OC05MjE2LTRlMTc5MTJjMWM0NCJ9
1-800-691-1991 | 9am - 8pm ET
EN

How to configure Email Notifications when using Gmail or Google Apps Mail

Purpose

You need to configure email notifications to be sent to a Gmail or Google Apps Mail account.

Cause

Use of port 587 is required for TLS when communicating with Gmail or Google Apps Mail.

Solution

For Veeam Backup and Replication please set the Port to 587 in Veeam Backup and Replication console > Menu > Options > Email Settings > Advanced.
For Veeam Availability Orchestrator please set the Port to 587 in VAO UI -> Configuration -> Email Settings -> Edit SMTP Settings.
For Veeam Availability Console please set the Port to 587 in VAC UI -> Configuration -> Portal Configuration: Notifications -> Email Settings

Ensure that both Connect using SSL and This SMTP server requires authentication checkboxes are checked.

More information

More information is available in this Google KB.

In some rare cases the ‘Access for less secure apps’ may need to be Turned On. For details, check this KB article.

 
KB ID:
1974
Product:
Veeam Availability Orchestrator, Veeam Backup & Replication
Version:
All
Published:
2014-12-08
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later