91 votes10 comments · Office 365 Security & Compliance » Spam & Phishing · Flag idea as inappropriate… · Admin →
The Junk Email Reporting Add-in is our current solution for Outlook users. You can get the download for it, and learn more here:
We do absolutely triage these submissions and use them to improve EOP.
If you aren’t using Outlook, simply create a new mail to junk [AT] office365.microsoft.com and attach the entire message, including headers (see https://technet.microsoft.com/library/jj723151(v=exchg.150).aspx). We are looking at better reporting options for Mac and mobile users. What might be helpful here is commenting with which applications you use most.
Administrators can also now go to http://aka.ms/FixSpam and troubleshoot their users’ most persistent spam issues.
If you continue having difficulties, we recommend a support ticket to investigate current samples. It is frequently the case that a simple configuration issue is to blame — and support can help you figure this out.Matt Griffiths supported this idea ·
23 votes4 comments · Office 365 Security & Compliance » Spam & Phishing · Flag idea as inappropriate… · Admin →
We highly recommend using DKIM and DMARC in addition to just SPF. That said, this may be best worked via a support ticket so individual messages can be analyzed. As mentioned, it is completely possible that the issue is because of a whitelist or rule.
An error occurred while saving the commentMatt Griffiths commented
We have had a similar issue, and found it was because SPF was being overridden by a transport rule whitelisting the sender address (ourselves in this case).
14 votesMatt Griffiths shared this idea ·