Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Solved
Office 365 Spam Filtering
Posted on 2016-09-27
Hello Everyone,
I am asking this question just to make sure that all bases are covered.
I have a client who has been in regular communication with a customer via email. One or two emails (out of dozens) haven't arrived. We look in the message tracking logs, do a variety of searches, and these emails do not appear in any log. Nothing in Quarantine, Junk Folder, anything.
If a message was received by the O365 servers and was blocked for any reason, shouldn't that show up in the log detailing why?
Is there some kind of 'perimeter' filter that may have blocked a message prior to it getting to a place where it shows up in my clients O365 logs?
The customer received no NDR, and when they resent (i.e. forwarded from their Sent Items) it did appear at my client.
The customer is at home and uses the email address supplied by her (big) ISP. Troubleshooting on that end is limited.
There isn't an issue with attachment size (one email had attachments, the other did not). The only thing that was a bit off was that it was a long email chain of a lot of replies back and forth. And, if it matters, there was some (very slight) language in the email.
Am I missing something here I don't know about O365?
I am asking this question just to make sure that all bases are covered.
I have a client who has been in regular communication with a customer via email. One or two emails (out of dozens) haven't arrived. We look in the message tracking logs, do a variety of searches, and these emails do not appear in any log. Nothing in Quarantine, Junk Folder, anything.
If a message was received by the O365 servers and was blocked for any reason, shouldn't that show up in the log detailing why?
Is there some kind of 'perimeter' filter that may have blocked a message prior to it getting to a place where it shows up in my clients O365 logs?
The customer received no NDR, and when they resent (i.e. forwarded from their Sent Items) it did appear at my client.
The customer is at home and uses the email address supplied by her (big) ISP. Troubleshooting on that end is limited.
There isn't an issue with attachment size (one email had attachments, the other did not). The only thing that was a bit off was that it was a long email chain of a lot of replies back and forth. And, if it matters, there was some (very slight) language in the email.
Am I missing something here I don't know about O365?
-
2
-
2
- +1
6 Comments
Active today
Yes, there is a perimeter filtering, but that should only block the most obvious spam messages and malware. Everything else should be visible in the message trace (well up to a certain date).
The other possibility is that the email never reached O365 servers. It's best if you ask the sending party to perform a trace on their end, if possible.
The other possibility is that the email never reached O365 servers. It's best if you ask the sending party to perform a trace on their end, if possible.
Active 5 days ago
It's possible the message was initially flagged by the malware filter. Messages that get dropped by that are usually killed before they hit any logs.
One way we ensure users can receive incoming email from known trusted senders when using Exchange Online Protection is to run a pair of Exchange PowerShell commands. The update then replicates up to Office 365 Azure AD and that mailbox will not block emails from these senders. It's really been working well. In case you may want to try, here is the snippet...
Also you can just put a theirDomain.com to blanket allow that company. Also we wrap this in a PowerShell GUI application to make it really easy to mass-manage this for many users or groups within the company, as that type of issue comes up pretty frequently.
Get-Mailbox -Identity "receiver@yourDomain.com" | Set-MailboxJunkEmailConfiguration -TrustedSendersAndDomains @{Add="sender@theirDomain.com"}
Also you can just put a theirDomain.com to blanket allow that company. Also we wrap this in a PowerShell GUI application to make it really easy to mass-manage this for many users or groups within the company, as that type of issue comes up pretty frequently.
Featured Post
Be seen. Boost your question’s priority for more expert views and faster solutions
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
With the emergence of Office 365 as a superior email communication platform, many organizations have started switching over to it. After migrating to Office 365, sometimes users, as well as organizations, will have to import PST files to Office 36…
WAP (Web Application Proxy) provides reverse proxy functionality for web applications in the corporate network which allows users on most devices to access internal web applications from external networks.
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…
A company’s greatest vulnerability is their email.
CEO fraud, ransomware and spear phishing attacks are the no1 threat to a company’s security. Cybercrime is responsible for the largest loss of money to companies today with losses projected to r…
- Ransomware
- Office 365
- The Email Laundry
- Microsoft Access
- Windows Server 2003
- Visual Basic Classic
Suggested Courses
Course of the Month5 days, 8 hours left to enroll
579 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.