-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Description
Elasticsearch version: 6.2+ but can be applied to previous and latest versions
JVM version: not relevant
OS version: not relevant
Description of the problem including expected versus actual behavior:
In case we have several recipient emails in a email action, the watcher is NOT successful until ALL emails are valid.
Should we notify about the invalid format?
Should we notify about the failed delivery?
Steps to reproduce:
- Install Elasticsearch and Kibana
- Add email settings for watcher (a valid smtp)
- Create a dummy watcher with an email notification and provide the several addresses as recipients
- Test with recipients below
FYI the emails below are redacted:
xxxxxxxxx@gmail.com is a valid address.
yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy@gmail.com is a not existing address.
xxxxxxxxx+ahaha@gmail.com is a valid address (will be sent to xxxxxxxxx@gmail.com)
Several tests
xxxxxxxxx@gmail.com, gudsauigdsagiusadsadui, lol.com, a@com, xxxxxxxxx+ahaha@gmail.com, yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy@gmail.com
The watcher fails completely, no mail sent.
xxxxxxxxx@gmail.com, a@com, xxxxxxxxx+ahaha@gmail.com, yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy@gmail.com
The watcher is successful, all mails sent by SMTP. The SMTP Delivery service will notify later 2 out (
a@comandyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy@gmail.com) of 4 emails cannot be delivered.
a@com, xxxxxxxxx+ahaha@gmail.com, yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy@gmail.com
The watcher is successful, all mails sent by SMTP. The SMTP Delivery service will notify later 2 out (
a@comandyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy@gmail.com) of 3 emails cannot be delivered.
a@com, x
The watcher fails completely, no mail sent.
x, xxxxxxxxx@gmail.com
The watcher fails completely, no mail sent.