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
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
I found a single user on your domain that was on our email suppression list. The error message was
|550: 550 5.1.1 ...@... Recipient address rejected: ... in virtual alias table||2022-06-17T09:29:22+00:00|
I have removed that address from the suppression list. Please try to resend the verification or invite again to this user. They should receive this now.
I found there was a bounce message of
550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [BMXIND01FT027.eop-IND01.prod.protection.outlook.com]
I have cleared this suppression from our side. However I would ask that you please review https://community.atlassian.com/t5/Jira-articles/Unblocking-Office365-emails-for-Atlassian-Cloud/ba-p/1870108 it contains some steps that you can follow if you use Office 365 to help prevent these kinds of suppressions in the future.
Hi @gauss I found only one account on your domain that was not receiving mail. There was an error of
550: 550 5.1.1 Requested action not taken: mailbox unavailable 2022-11-02T12:56:48+00:00
I have cleared the suppression from our side. I would recommend to make sure that this user's mailbox is setup to receiving email from external senders. Once that is confirmed, try to resend the invite from our services, it should work now.
I recommend that you reach out to your mail administrator. It appears that this address is repeatedly getting a bounce message:
|550: 550 5.1.1 ...@... Recipient address rejected: ... in virtual mailbox table||2022-09-02T10:25:03+00:00|
I have removed this suppression from our side, but if the receiving mail server continues to generate bounce errors such as this one, our system will flag the address as being invalid and stop trying to send messages to it.