For the past two wks our all JIRA emails have been flagged by Gmail as spam. As such, no one in our company is receive ANY JIRA emails in their Inboxes.
I have the JIRA email address in my addressbook, but it still flags all JIRA email.
Try this:
1.- Create a filter with 'from:sample@test.com' on Gmail. In example, edit the following filter: https://mail.google.com/mail/u/0/#create-filter/from=noreply%40atlassian.com&sizeoperator=s_sl&sizeunit=s_smb
2.- Click on 'Create filter with this search'.
3.- Select the checkbox 'Never send to Spam'.
4.- Click on the button 'Create filter'.
This is the summary of possible causes why Gmail might be flagging as spam those emails.
Try entering the email message and remove the label 'spam' being shown on the top-right corner.
Hopefully, this actions prevents from flagging as spam new messages from the same remittent.
As @Ignacio Pulgar mentioned, there is a link for possible causes.
If the filtering is being too aggressive, you can configure a whitelist, see here: https://support.google.com/a/answer/60751?hl=en
@Ignacio Pulgar I've added the Jira email address used to deliver our messages to my Contacts and manually marked ALL Jira emails as Not Spam to no avail. All Jira emails are still being sent directly into my spam folder.
@David Chan [Atlassian] Whitelisting does look like it would work, but that would require me to upgrade and incur additional costs for Google for Work just so we could properly receive Jira emails.....which obviously is not ideal. If I already had a good reason for upgrading to Google for Work it wouldn't be a problem, but in this case the upgrade would be exclusively to receive Jira emails. Any other thoughts?
Solution found here: https://support.google.com/mail/answer/6579
That did the trick. I don't think the solution is appropriate for larger organizations, as it's quite manual....but it does allow my team to finally receive Jira email updates until Jira finally addresses the issue for themselves to protect other clients from this same issue.
Yes, that solution should only be a workaround, while keeping on solving the origin of that undesired behaviour. Best regards.
It looks like you're new here. Sign in or register to get started.
