Sign up for Office 365
Learn more about Office 365
You can populate entries in the Safe Senders list for Outlook clients via an AD GPO.
This works for on-premise mailboxes (Exchange 2003 backend), however cloud users have the entries erased from the Outlook client after a short time. For Office 365 users, the Safe Sender entries are being pushed down from the users personal online-stored Safe Senders list (which can be edited via OWA also)
So what would be the solution to globally ensure a domain name is populated in the online users Safe Sender list (which would make sure emails from firstname.lastname@example.org will never be caught in the Junk Email folder)?I don't want each Office 365 user to have to add @domain.com to their SAfe Sender list, I want to add it in globally for everyone.
FOPE filters and policies are going to be your best bet here. Alternatively, you could use remote PowerShell to set up transport rules, but FOPE is the easier choice.
We have application servers that send smtp email as email@example.com which often show up in Office 365 users Junk Email folder. So if I add an allow FOPE rule to match sender: *@domain.com, you are thinking that potentially will prevent those emails from showing up in the Office 365 users Junk Email folder?
vs. writing @domain.com into the Safe Senders junk email list of all Office 365 users
Pretty much. Back in BPOS, the Safe Sender list in the MOAC was just an extension of FOPE filtering. You can set up whitelisting manually in FOPE for Office365.
Whitelisting the domain in FOPE would allow for someone to impersonate anyone on that domain from outside the account and allow spoofing. The best thing would be to use an application that supports TLS or filter it through IIS so that it can authenticate properly as a user such as the Outlook Client would.