Andy Heinzer Atlassian Team

I found only 2 email addresses on that domain that had current suppressions. The original SMTP bounce message was 550: 550 5.1.1 Recipient unknown ...@... And that timestamp of the first event was 2022-10-20T14:27:41.000Z. There was also one more, but that bounce was from 5 months ago. I have removed all the suppressions…

Hi Rick, Could you please let me know the email addresses of the user(s) that are not receiving notifications? With that information I can check to see if these addresses are being suppressed. Cheers, Andy

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…

@knyce I found there was an SMTP error of 452 Too many recipients received this hour from your mail server. Which appears to have delayed at least one message sent to your from our cloud services. However it appears that this was delivered on a second attempt.

Hi, I found there was a suppression on your email address within our system. This sometimes happens when trying to send to an address that does not yet have a mailbox setup yet. I have removed this suppression from our side. Try to resend the verification email once more, you should receive it now. Cheers, Andy

Hi, I created a support case on your behalf in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-814380 Please approve the data access so that our team can investigate the details of your site further here. Andy

Hi James, I took a closer look at your site, but from what I can see all the users invited have delivered events in the SMTP logs. None of these email addresses I have found, including your own, show any kind of suppression message that we would typically see if an email server was rejecting or bouncing a message from our…

Hi, I've created a support case for this over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-813911 Regards, Andy

Hi @İ_ Burak Tanrıkulu I found there was a suppression listed for that email address: 554 5.7.1 : Recipient address rejected: Access denied I have removed this suppression from our side

Hi, I found that our SMTP received the following bounce message: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 https://support.google.com/mail/?p=NoSuchUser…

Hi @monissiddiqui1 I found the following error when our services were trying to send to your account: 451 4.7.650 The mail server [192.174.81.98] has been temporarily rate limited due to IP reputation. For e-mail delivery information, see https://postmaster.live.com (S775)…

Hi @Shyam Kukreja It appears that the previous free plan cloud site was inactive for a period beyond 120 days. For Free plan sites, when this happens the site is deactivated. That appears to have happened on August 1st. From that point we only kept the existing data for a period of 60 days per our data retention policy. As…

Hi @Christof Hurst It appears that you are not using Jira Software in this site, but rather the features of Jira Work Management. If that is correct, then you should be aware of this known issue JWMCLOUD-210 On Business projects (which have their own boards), the issues will be set to Done, but not have a resolution value…

It appears that you went over the free limit of 10 users. When that happens, Jira automatically will upgrade your site to the next level as part of an evaluation of the standard support offering. Looking at it now, you appear to have since reduced the number of licensed users below 11 again. In which case, your site also…

Hi @Pat Ryan Sorry to hear about this problem. There is actually an existing bug ticket for this behavior over in https://jira.atlassian.com/browse/CONFCLOUD-74659 There is a work-around noted in that bug ticket: Use the Team Calendar macro to embed calendars to pages. I hope this helps. If not, then I would still…

Hi @Tim Pfeifer While it is still possible to request the use of the legacy editor within Confluence cloud, this is not possible to do for sites that are using our Free subscription plans. You could upgrade your subscription to a paid plan or start an evaluation trial of a paid subscription of Confluence. Once that has…

Hi @Jan Neger yes that is a real email from our services. I can see it was sent to Gemma, who is the billing contact for that site. We don't have billing details for that account (ie there are no credit card details on file). This lack of payment details could result in the site being deactivated or suspended due to lack…

Hi Michele, It appears that you already found an answer to this over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-808165 But for anyone else that might have this same question: For Jira Cloud site-renames like this, I expect that you won't have to do much here. Our services will actually have a…

Hi @Mauricio Pintado Sorry to hear about this problem. I have created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-809578

Hi @Sami Shaik I can't seem to find any recent support tickets where you account has created or has access to since July. If you have an existing support ticket please share the issue number with us. Are you using a different email address for that other correspondence?

@Christos Frantzis Hi, I found there was a suppression on your account. There were SMTP bounce messages of 554 5.7.1 [internal] recipient address was suppressed due to customer policy I have removed this suppression.

I mean, it's a valid address from which Atlassian sends mail. But it's a no_reply, so it's not expected that you would be able to send to that address. And that is not to say that someone might have spoofed the sender, or that someone is abusing one of our Cloud services that sends email. Care to share what the email you…

Short of unlinking the entire repo from within Jira, you can't do this from Jira's side. Instead I'd recommend going to the source of the pull request/commit/branch and trying to make the change there. This would typically be Bitbucket, Github, or whatever tool you use to track development work. We have a feature request…

Hi Miguel, I believe someone from our Channel team has reached out to you about this. Thanks for flagging this to us @Nic Brough -Adaptavist- 

Hi, I removed the suppression for this address. Please try to resend the invitation once more.

It might be worth trying to load an incognito or private browser session to see if you can reproduce this problem. If you can, then I suggest trying to generate a HAR file. You can post that to the support ticket we created, that might help us to better understand what is causing this behavior. Andy

Hi David, I created a support case on your behalf. Please see https://support.atlassian.com/requests/JST-807697/ I am not certain why you might not be able to create this yourself, but I will be raising another issue with my support team to investigate the errors you saw here. Andy

Hi, If you are using the DVCS within Jira Cloud, then Jira should be syncing those repos to then look for any references to specific issues keys mentioned in those repos that match any issues in that Jira instance. In this case, I'd recommend creating a support case in order for our support teams to take a closer look at…

Hi Asif, I found only a single message sent your address recently: 2022-10-02T09:10:36.000Ze53b3a60-0200-40d5-b747-0530d642a3cd noreply+13391b0165a7abb77609a0c49744702058dc1d413a5538182eec3468@am.atlassian.comw****************@gmail.comdelivery But this was delivered. I would check the spam or junk mail filters to see if…

Hi, Thanks for providing that detail. I found this error on one account under that domain: 554-ironport.lcit.com 554 Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means. We are…