Andy Heinzer Atlassian Team

@bgeron Please contact our abuse team at https://www.atlassian.com/trust/report-abuse This will notify our abuse team, no need to accept the invite. You will not receive any response from the abuse team, but this will notify them and give them the ability to investigate the site in more depth to be able to suspend it.

@Mennatallah_ah The response to that case doesn't come to me. I'm afraid your comments here in Community are not being posted to that support ticket. My teammate is the assignee of your support ticket. You should have received an email explaining why we require this level of documentation from Rodrigo on 10/Nov/23. In that…

Hi @Jake S Not all of our support teams offer phone support for all customers. That said, I recommend that you start a trial of a standard or premium service level for our Cloud products. Doing so will allow you to either open a support case if you're seeking help on a quote/trial, and/or create a technical support case if…

Thanks for reporting it, I'm flagging this to the anti-abuse team for review. Andy

@Abid Mehmood Thanks for that info. I was unable to find any mail events in our system for either account. Our mail logs here I believe only go back about 30 days here, so if the invites were sent before then, it might explain why we don't see any record of it. Try to re-invite these users. Steps to do so are in Invite a…

Thanks for reporting this to us. We have had several reports of this, such as in https://community.atlassian.com/t5/Announcement-questions/May-I-ask-if-there-is-available-Data-Entry-jobs/qaq-p/2521159#U2521174 This looks like a scam. Atlassian does not offer these kinds of roles, and Atlassian does not use the telegram…

Hi @Abid Mehmood I took a closer look at the email sent to users on your domain recently, I found that some of these messages appear to have had the destination SMTP server throw a delay response: 451 Internal resource temporarily unavailable - https://community.mimecast.com/docs/DOC-1369#451 [oUnZ-6v6N_q_XvUYJn72_g.au24]…

@Geronimo Pagador I created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-937389 Please use that support case to disclose the specific email addresses that you are attempting to invite to your site. This way our support team can investigate this further to…

@Colin Harrison I have cleared the suppression to accounts on your domain. I found a number of bounces that had this error: 550 5.4.1 Recipient address rejected: Access denied. [AM3PEPF0000A791.eurprd04.prod.outlook.com 2023-11-10T11:00:26.356Z 08DBDE36C4A7ED50] This bounce can be caused by your mail provider rejecting the…

I can see you created a support case for this over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-936882 I recommend following up on that request so that our team can investigate this further for you. Andy

If you use the top navbar to get to Projects > View all projects, this view doesn't have the Trashed projects view within it. Instead you need to go to the the Cog Icon (Setitngs) in the top right corner as a Jira Admin and select Projects, this will take you to the page to be able to see this. The URL will look like this…

@Embrenchia Snyman I created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-936610 It appears that the previous bug cited in https://jira.atlassian.com/browse/JRACLOUD-69324 was closed without a fix. The cause appears to have been a project key format customization…

Hi @Angela L I did not find any current suppression for your domain, but I have attempted to clear any blocks of it anyways. As for that test_notification tool, I am not familiar with it, but I found that our Trello support team is aware of the issue and is investigating this further. If you are still having difficulty…

For cases like this, when a user cannot perform an action and you do not know why, I recommend having a Jira Admin use the permission helper to check the permissions. This utility will prompt you for the user, an issue key, and an action. You can input those and submit to see if that user has that permission as this checks…

Hi Alan, I found there was a bounce message sent to your address. The SMTP mail server responded with: 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…

Hi Kyle, I found that your email address was on a suppression list. I have removed your address for that list. You should now be able to received email notifications once more from Jira and Bitbucket.

That is correct. It might not be needed in order to troubleshoot the problem, but in some cases it is helpful to have from a support perspective.

Hi @Joanna_Tang I created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-935715 Since you're account is not a site-admin, I've also included one of your site-admins who can grant data access should our support team need this in order to reproduce the behavior.

Hi @Willem Kalverda I found there was a suppression on your account. While I did not find the original bounce message, since you mentioned using office 365, I would suggest taking a look at this guide https://community.atlassian.com/t5/Jira-articles/Unblocking-Office365-emails-for-Atlassian-Cloud/ba-p/1870108 It explains…

I have cleared a suppression from our side. You should now be able to received notifications again.

@Mennatallah_ah I have just resent the initial email to that address, and re-opened that case. 

Hi @Jim Davidson I found the following bounce in our email logs: 550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [YT3CAN01FT027.eop-CAN01.prod.protection.outlook.com 2023-10-31T19:43:23.872Z 08DBDA338900F453] I have cleared the suppression for all the accounts on your domain, but this problem could…

Hi @Mennatallah_ah That particular account appears to have been deactivated. That user's email account should have received an email the body of: Dear Atlassian user, ​ U.S. law prohibits Atlassian, an Australian corporation with offices in the United States, from providing you with access to our products and services.…

I see someone has responded to your support case now. Sorry this took so long to respond. At the time I found the ticket it was within the customer advocate queue, which isn't the team that can directly help with this problem. Once I moved this to the Access support team, it was approximately 90 minutes before a response…

@Thomas Mazzola I created a support ticket on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/48/PCS-226179 @Wolfgang Maier I saw you had a support ticket already over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-934357

Hi @Nico Hidalgo-Toledo There was an outage for Bitbucket right about the time you posted this to community. We have more details about this over in https://bitbucket.status.atlassian.com/incidents/tv5szx9l36s6 Sorry for the inconvenience here. It appears to have been resolved now. As for directing support requests here to…

Hi @Thierry Bouvet I created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/48/PCS-225723 Please grant data access within that support case so that our support team can investigate this further to help out. Andy

HI Kevin, I found there was a bounced message when we tried to send you a notification. Details of that bounce: 2023-11-01T17:55:43.000Zbounce550 5.1.1 Requested action not taken: mailbox unavailable I have cleared the suppression from our side. Andy

@rajesh nair Did you receive a message from an atlassian.net address to join that site? If so, please forward that email to https://www.atlassian.com/trust/report-abuse We cannot respond to messages sent there, but I suspect that such a message would be against our terms of service and this can help to inform our abuse…

They won't be able to install any update released after their license has expired. Ignore the EOL date of the product version. It's not directly correlated here since Atlassian is continuing to support Data Center editions of these products in those versions. The focus is on the license. All server licenses are expiring on…