Seems that bamboo doesn't use it's FQDN when sending email, which causes issues with our SMTP server. (and, I suspect would do the same for others)
error shown is:
The mail settings you entered were not valid. Error thrown was: javax.mail.SendFailedException: Invalid Addresses; nested exception is: com.sun.mail.smtp.SMTPAddressFailedException: 504 5.5.2 <bamboo>: Helo command rejected: need fully-qualified hostname
Could this be enabled, or could you suggest a workaround?
It seems sensible for bamboo to use a FQDN when sending email.
Well, if anyone else is looking for a fix, something like this would work:
sudo postconf -e "smtpd_helo_restrictions = permit_mynetworks reject_invalid_helo_hostname reject_non_fqdn_helo_hostname" sudo postfix reload
the key section is 'permit_mynetworks' - I needed to add the bamboo IP to 'mynetworks'
But it would be great if Atlassian would make bamboo use a FQDN when sending emails.
Invalid Addresses; nested exception is: com.sun.mail.smtp.SMTPAddressFailedException: 550 5.1.1 <Ampptech@crest.in>: Recipient address rejected: address does not exist in this domain I have facing this issue on windows 2008 R2 Virtual Server, Can you suggest why this is happening.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot