Forum Discussion
Firebase authentication emails are blocked by Office 365
This problem is currently affecting 74 of my business customers.
The way it looks now, setting up a different outbound server for these mails (serving only my domain for example) would be the only option?
Hi arnotixe,
Not sure if I got your question. But you have many options...
- Ask the provider to delist.
- Use another relay
- Request the recipients IT teams to whitelist you, ( probably rejected by the Security teams. Think that they have no control over the sender servers... You neither. Too risky ).
And probably other options depending on your environment and requirements.
The point is basically that O365 identifies your messages as SPAM/Phish and is quarantining all your messages.
- yeah this is still a problem (exclusively for Microsoft customers) even after having purchased a Dedicated IP to send with…
Hi arnotixe,
I just analyzed the new test message that you sent me and it passes the security scans and it's not identified as Bulk. The only problem is the SCL level, (5), and by default EOP will deliver those messages to the Junk email folder. ( Note that this can be modified by the Admins, so it's possible that in some cases it landes in the inbox folder and in other ones it will be quarantined ).
I'll share the message header with you in a private message. Finde here more information about the SCL value:
Spam confidence level - Office 365 | Microsoft Learn
Antispam stamps | Microsoft Learn
Anti-spam message headers - Office 365 | Microsoft Learn
I have a brand new app, that is also using Firebase and I am experiencing exactly the same issue. The Firebase Authentication service has pre-configured templates that it sends for user email verification and similar interactions. The Authentication product sends these communications by default from Firebase's own email service.
This issue will affect any developer who uses Firebase (of which there are many) and uses Firebase authentication. Seems like this is a new issue though as these emails were all still working at the beginning of Feb.
Given that this is a universal problem experienced by many users of the Firebase Service, how can this be addressed at a large scale, rather than everybody trying to address this individually?
