You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
There's new user my company and I invited him, however, this time the user hasn't received anything. I tried to resend in user management tab for several times, and he checked all the mail boxes, no invite mail.
It's possible removed those bounces for the notifications should work normally? My URL: celk.atlassian.net.
Hello @Cristiano Schwening,
Thank you for reaching out to the Atlassian Community!
Checking the details of your site, I found two domains and there were emails on the suppression list.
For the email domain ending with .net, there were 30 email addresses with bounces due to the following error:
550: 550 5.4.1 Recipient address rejected: Access denied. AS({hex}) [BN1NAM02FT043.eop-nam02.prod.protection.outlook.com]
550: 550 [internal] [oob] The recipient is invalid.
For the domain ending with .br, there were 27 affected email addresses:
550: 550 5.1.1 ...@... Recipient address rejected: ... in relay recipient table
550: 550 [internal] [oob] The recipient is invalid.
I removed those bounces and the notifications should work now.
Kind regards,
Angélica
More one user with this problem. It's possible removed those bounces for the notifications should work normally?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Cristiano Schwening I've just published an article showing how an Exchange admin can add a mail flow rule to prevent the "5.4.1 Recipient address rejected" error (on the .net domain mentioned): Unblocking Office365 emails for Atlassian Cloud . Angelica may have additional details to mention. The other error on that domain is either likely on an email address that has been deactivated in Office365 (such as a former employee, or the Atlassian Cloud invitation was sent before the user's mailbox was created in Outlook.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There were 3 affected users only (2 from the .net and 1 from the .br):
550: 550 [internal] [oob] The recipient is invalid.
550: 550 5.4.1 Recipient address rejected: Access denied. AS({hex}) [DM3NAM02FT063.eop-nam02.prod.protection.outlook.com]
I removed those bounces and it should work now.
Please, follow the steps mentioned by Daniel and you can also whitelist our domains and IPs (also mentioned in the article Daniel shared).
Kind regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
More one user with this problem now. It's possible removed those bounces for the notifications should work normally?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Cristiano Schwening,
I removed the bounces for both domains. For the .net domain, it returned 19 affected email addresses and for the .br it was 6.
550: 550 [internal] [oob] The recipient is invalid.
550: 550 5.4.1 Recipient address rejected: Access denied. AS({hex}) [BN1NAM02FT063.eop-nam02.prod.protection.outlook.com]
550: 550 5.1.1 ...@... Recipient address rejected: ... in relay recipient table
The notifications should work normally now.
Regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.