I'm using `atlassian/email-notify:0.4.2` and trying to set build notifications using office365 but I am getting following error.
Failed to send email to $BUILD_NOTIFY_USERNAME. Check your configuration settings: (535, b'5.7.3 Authentication unsuccessful [BY3PR05CA0008.namprd05.prod.outlook.com]'
Credentials are correct however I'm not sure what 'HOST' value should be used. I have tried it with following host values with no difference in the result
As per IT team we don't allow external SMTP connections to O365 because Microsoft recommends against this for security reasons. We suspect this failure is because of it.
1. By default Bitbucket sends notification email to only commit author when pipeline fails. Is it possible to configure this field to a list of email addresses either at repository or workspace level?
2. Can someone recommend what is the best practice if we want to use O365 to send build notifications considering the recommendation from Microsoft?
3. Any guidance on what HOST value should be used for office365?
Thanks in advance.
Hi @a2l and welcome to the Community!
1. By default Bitbucket sends notification email to only commit author when pipeline fails. Is it possible to configure this field to a list of email addresses either at repository or workspace level?
Such notifications can be enabled by each user themselves, the following way:
When a user does this, they'll get an email notification when a Pipelines build fails in this repo.
2. Can someone recommend what is the best practice if we want to use O365 to send build notifications considering the recommendation from Microsoft?
For this I am not sure, as it's something I've never set up myself, so I'll leave it for someone else to reply who has experience with this.
3. Any guidance on what HOST value should be used for office365?
As per Microsoft documentation here the value for HOST should be smtp.office365.com
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.