Share via

Domain incorrectly flagged as phishing domain causing no emails to be received

Anonymous
2023-06-30T14:38:53+00:00

Hi,

We have an issue that has been ongoing for a week now, where Microsoft just closes the support ticket with no reason. This issue is starting to hurt us.

The issue is that our domain is somehow flagged as a phishing domain by Microsoft. As all our users have our URL in their signature, this causes our outgoing emails to be quarantined at the receiving end. The same goes for reply-emails with the original signature in the mail thread.

Removing the URL from the signature seems to solve the issue for outgoing emails, but it is a nightmare as all reply-emails have a thread below with our URL in every signature. It's also not great that we cannot link to our own website in emails.

We have created a Microsoft support ticket through our service provider 3 times now. And 3 times the ticket has just been closed with no reason or resolution.

I should also add that our service provider has one more customer with the same issue.

I turn to the community. What other causes of action do we have to get Microsoft's attention on the matter? We are really hurting from this issue. Not being able to send or receive replies for a week is less than ideal. Any help would be greatly appreciated!

Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

41 answers

Sort by: Most helpful
  1. Anonymous
    2023-07-05T07:18:47+00:00

    For anyone finding this thread through Google: We were able to resolve this issue yesterday, 12 days after the incident started.

    Our service provider was able to get a hold of somebody senior in Microsoft support that pulled some strings. After this, the issue was accepted by Microsoft support within 30 minutes, and the issue was confirmed solved after 4 hours.

    I have no insight into how they managed to get in touch with Microsoft support though the back channels, but I suspect personal relationships was used. I don't know how we would solve this issue without.

    The issue turned out a lot worse than first thought. As our domain was on a global list of phishing domains, this was the impact:

    • Every email we sent was quarantined at the receiving end of the receiver had Office365. Not because of the from address, but because we had our domain written in our email signature. We were in no way notified of this, and it took some time to realize this was happening, and that every user was affected. Removing any mention of our domain name from the signature was a temporary workaround.
    • But this issue was not only for us. Any email sent, from anybody in the world, that contained our domain name, was quarantined without the sender or receiver being notified, if the receiver had Office365.
    • We realized this also impacted a lot of automatic emails that randomly contained our domain name in the email body or subject, including our invoicing system, payslips, travel expenses, metabase reports, github integrations and so much more. Truly a business critical issue.

    For anyone stuck in the same situation, I would:

    1. File a support ticket, and start using your Microsoft network to get attention on the issue. If you are unlucky like us, we had 4 tickets, over 10 days, just being closed with no reason given.
    2. Figure out what triggers the quarantine. Is it the domain name, like for us?
    3. Start mapping our what systems you have that might be affected and see if you can remove the trigger-word. I guess email signature is an obvious one, but remember every other auto-email you may have.
    4. Whitelist the trigger word for incoming emails. This should resolve people emailing you. (and replying to your with your signature in the original email under the reply)
    5. Create lists of emails that have been sent that may have been blocked at the receiving end and work with the users to resend these emails without the trigger word. Our service provider did this for us, so I can't tell you the exact steps taken to produce these lists.
    6. Hope that your ticket gets acknowledged by Microsoft and resolved.

    Tagging this post with Phishing, MDO, blacklist.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-09-17T03:35:57+00:00

    Thank you. Email was sent, but wanted to confirm receipt since our issue revolves around emails being quarantined.

    Were you able to resolve your issue? It's been 2 weeks for me trying to figure out how to get my domain off a phish list that is causing all mail sent from my domain (or mail with my domain in it) to be sent to Quarantine for "High Confidence Phish". Extremely frustrating, as it's affecting a lot of my customers.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-07-13T04:16:48+00:00

    Thanks for posting this.

    We are day 6 of the same issue now. We are hitting up any and all Microsoft contacts.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-07-06T07:21:11+00:00

    As far as I have understood, phishing and spam is treated differently in O365.

    Spam looks at dmarc and the usual stuff and will block your domain.

    Phishing on the other hand, will not care about the domain you are sending to or from. I believe it is part of the safelinks framework (at least that's my theory). So it only cares if there is a link in the body of your email to a malicious domain.

    Meaning; we could send and receive emails if our domain was not mentioned in the email. (even when sending from the domain in question)

    But it also means that anybody in the world using O365 would get their email stopped if they mentioned our domain in the email.

    🤷‍♂️ Go figure. Glad we're out of the woods. For now.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-07-03T17:57:08+00:00

    You can try the Delist portal as mentioned here. https://learn.microsoft.com/en-us/microsoft-365/security/office-365-security/use-the-delist-portal-to-remove-yourself-from-the-office-365-blocked-senders-lis?view=o365-worldwide

    Be aware, these are automated systems and there's no one to call and no email address to send to.

    Couple things that you can try outside the Delist portal:

    1. Change the IP for your email server
    2. Change your domain

    Either of those sometimes solves the issue.

    Was this answer helpful?

    0 comments No comments