SMTP failed exception 500 bad request
    profile: standard #####
    smtp.port: 80
    smtp.auth: true
    smtp.starttls.enable: true
    smtp.user: ####
    smtp.password: ####

[o.e.x.w.a.e.ExecutableEmailAction] [4SpMsfD] failed to execute action [af66e8af-c288-4b56-be3e-1d149c6018d8/email_1] javax.mail.MessagingException: failed to send email with subject [Watch [geo_datasource_getconnection_success_latency] has exceeded the threshold] via account [mail1] at ~[?:?] at ~[?:?] at ~[?:?] at org.elasticsearch.xpack.core.watcher.actions.ActionWrapper.execute( [x-pack-core-6.7.0.jar:6.7.0] at org.elasticsearch.xpack.watcher.execution.ExecutionService.executeInner( [x-pack-watcher-6.7.0.jar:6.7.0] at org.elasticsearch.xpack.watcher.execution.ExecutionService.execute( [x-pack-watcher-6.7.0.jar:6.7.0] at org.elasticsearch.xpack.watcher.execution.ExecutionService.lambda$executeAsync$5( [x-pack-watcher-6.7.0.jar:6.7.0] at org.elasticsearch.xpack.watcher.execution.ExecutionService$ [x-pack-watcher-6.7.0.jar:6.7.0] at org.elasticsearch.common.util.concurrent.ThreadContext$ [elasticsearch-6.7.0.jar:6.7.0] at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:?] at java.util.concurrent.ThreadPoolExecutor$ [?:?] at [?:?] Caused by: com.sun.mail.smtp.SMTPSendFailedException: 500 Bad request (syntax error or unrecognized) [@sm190201] at com.sun.mail.smtp.SMTPTransport.issueSendCommand( ~[?:?] at com.sun.mail.smtp.SMTPTransport.mailFrom( ~[?:?] at com.sun.mail.smtp.SMTPTransport.sendMessage( ~[?:?] at ~[?:?] at ~[?:?] ... 11 more

Aug 7, 2019, 12:26:07


please be so kind to also properly format your exceptions as code, this just makes it so much more readable...

If you look at that exception, there is some piece of information carefully hidden beneath it

failed to send email with subject [Watch [geo_datasource_getconnection_success_latency] has exceeded the threshold] via account [mail1]

the important part here is the fact that this is a MessagingException, which basically means, that this error was returned from the SMTP server side of things, where the alerting code tried to send the message to. Is the stack trace bigger by any chance and you could it off, maybe there is more information, why the SMTP server on the other side rejected the message.

Maybe you can also check the SMTP server logs?


@spinscale Thanks for your suggestion i will make sure i attach the logs in a proper format.
We are actually using smtp server of a managed cloud service, i have raised a request to them to look into this.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.