How to configure an email alert using in GPDB6 using GPCC:

Products

• VMware Tanzu Greenplum

Issue/Introduction

This Knowledge Base (KB) article covers how to configure an email alert in Greenplum Database (GPDB) 6 using Greenplum Command Center (GPCC). 
 

While configuring the alert email, you encounter some issues. 

You may see an error message similar to the one below:

"GPCC encountered a problem when sending the confirmation email. Please check your SMTP settings and try again."

 

Environment

Product Version: 6.7

Resolution

Note: If you had configured the email alert, you do not need to configure the gp_email_smtp_server anymore. In the GPDB 6, the GUC is obsolete. 

 

To troubleshot and resolve this issue, follow the steps below:

1. We need to make sure the SMTP service can be accessed through the telnet as below:

telnet 192.###.#.# 25 

220 mail.finet.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at
 Fri, 16 Apr 2010 15:16:48 +0800
helo （remember, it is helo, not hello, the fix format to establish connectioon）
250 mail.finet.com Hello [192.168.1.92]
mail from:###_###@###.com   (the sender mailbox)
250 2.1.0 ###_###@###.com.cn....Sender OK
rcpt to : ###_###@###.com       (the receiver mailbox)
250 2.1.5 ###_###@###.com
data                (the command to input data)
354 Start mail input; end with <CRLF>.<CRLF>
Subject:mail test         （the subject of the email）
test test test!!!!!!!!!!!!!!!!!!          (the email content)
. (a period to end and enter)
250 2.6.0 MAIL##########9@mail.####.com Queued mail for delivery
quit           (exit)

 

2. If the above works, but you still cannot configure the SMTP through GPCC, you need to look into the GPCC's log to see what the error message is. The most common error message is the following:

2020/07/10 11:28:17.525 [E] [base.go:78] x509: cannot validate certificate for 10.##.#.## because it doesn't contain any IP SANs 
2020/07/10 11:28:56.243 [E] [base.go:78] x509: cannot validate certificate for 10.##.#.## because it doesn't contain any IP SANs 

The reason for the above error message is we had used the IP of the SMTP server, in stead of the STMP server's name.

3. Sometimes you may see an error similar to the one below as well:

2020/07/10 12:10:09.509 [E] [base.go:78] 550 5.7.54 SMTP; Unable to replay recipient in non-accepted domain

This error is given because we are sending the email to the external address.

You must make sure the receiver can be reached through the SMTP server.