-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Email alerts failed to be sent out at 9:39 on Wednesday #211
Comments
Before the scheduled task run at 9:30, there are a number of emails which were sent from [email protected] to [email protected], which caused the 'too many login attempts' error. in mail.log.1: Since 06:49 - ( the first error stored in logs) , emails was continuously sent to and then, it started causing "Too many login attempts" after 07:04:19 in mail.log.2, the first error happened at Apr 23 06:05
After reviewing 3 logs, there is a common thing: The error of 'relay limit exceeded' happened after an email was sent to [email protected] and [email protected] |
Further analysis: When we send alerts out, the client is 'localhost' :
However, the emails to [email protected] and [email protected], there is a cleanup process with
|
Waiting for AWS SES plugin @brucehyslop |
Email alerts are likely to be successfully sent out on other days.
May 1 09:30:58 aws-alerts-test-2022 postfix/smtp[368269]: 67DDC7EBFA: to=<[email protected]>, relay=smtp-relay.gmail.com[142.251.175.28]:587, delay=2.8, delays=0/0/2.8/0, dsn=4.7.0, status=deferred (SASL authentication failed; server smtp-relay.gmail.com[142.251.175.28] said: 454-4.7.0 Too many login attempts, please try again later. For more information,?454-4.7.0 go to?454 4.7.0 https://support.google.com/mail/answer/7126229 dc21-20020a05690c0f1500b0061b1e8153easm1475111ywb.34 - gsmtp)
The text was updated successfully, but these errors were encountered: