email-notify pipe not working with smtp.azurecomm.net

[Benedikt Nerb]

I am trying to send mails via Azure as lined out here.

I can successfully send mails manually via cURL and via python's sendmail.

The email-notify pipe (v.0.13.2) however fails, as it seems like the SMT server (smtp.azurecomm.net) does not support noop. The log with the debug mode enabled shows

reply: b'250 2.6.0 72a61f1a-199e-401d-b228-5dba15b0d9ee Queued mail for delivery\r\n'
reply: retcode (250); Msg: b'2.6.0 72a61f1a-199e-401d-b228-5dba15b0d9ee Queued mail for delivery'
data: (250, b'2.6.0 72a61f1a-199e-401d-b228-5dba15b0d9ee Queued mail for delivery')
send: 'noop\r\n'
reply: b'502 5.3.3 Command not implemented\r\n'
reply: retcode (502); Msg: b'5.3.3 Command not implemented'
send: 'quit\r\n'
✖ Failed to send email to <target>. : response (502, b'5.3.3 Command not implemented')
reply: b'221 2.0.0 Service closing transmission channel\r\n'
reply: retcode (221); Msg: b'2.0.0 Service closing transmission channel'

 Any advice?

[Theodora Boudale]

Hi Benedikt and welcome to the community!

I have reached out to the pipes team regarding this issue.

In the meantime, if you can successfully send emails using curl, you can use the curl command in your bitbucket-pipelines.yml file, in your pipeline step's script, instead of using the pipe. The Docker image that you use as a build container for this step will need to have curl preinstalled, or (if it doesn't) you could install curl by adding the necessary commands on your step's script.

Kind regards,
Theodora