Unable to successfully use Gmail SMTP server to send out alarms via email from I/A Series G3.
Various errors can be seen in the console output. Some of the errors are indicated below but they may not be limited to these.
- Error: BOutgoingAccount could not dequeue persistent email: 550 The address is not valid
- java.lang.Exception: Valid CryptoService not found
Enterprise Network Server / Enterprise Network Controller
- I/A Series G3 version 3.5 and above
- I/A Series G3 maintenance builds version 3.4.55 and above
Improper configuration of the EmailService's OutgoingAccount and missing CryptoService in the station.
Procedure and properties settings required when using the Gmail SMTP Server:
- Add the EmailService and CryptoService to the station's Services folder. If emails are to be sent from an ENC, ensure that the email and crypto modules (and their dependencies) are installed into the ENC.
- Add the OutgoingAccount to the EmailService.
- In the OutgoingAccount properties, configure the properties indicated below. Leave other properties as their default settings.
- Hostname: smtp.gmail.com
- Port: 465 (this is the TCP port SMTP over SSL uses)
- Account: firstname.lastname@example.org
- Password: Your Gmail account password
- Enabled: true
- Use Ssl: true (Gmail requires SSL)
- Transport: SMTP
- Use Authentication: true (Gmail requires authentication when sending out emails)
- You can test the functionality by right-clicking on the EmailService and selecting 'Actions' > 'Send' to send out an email.
- If you are still having an issue with authentication, it may need to allow less secure apps to access your Gmail account. Refer to https://support.google.com/accounts/answer/6010255?hl=en for details.
- CryptoService enables the SSL feature in the G3 station.
- The crypto module is included in the installation of I/A Series G3 version 3.6 but it was not included in earlier versions. You can download the crypto modules for earlier versions of G3 (crypto 3.4.64 / crypto 3.5.34) from The Exchange Download Center.
- Ensure that the station is licensed for crypto. You can look into your license file to check. Below is an example taken from a demo license.
feature expiration="2012-03-31" name="crypto" parts="ENS-DEMO" ssl="true"