Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies. Only from Platform Scholar.
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?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
2
-
2
- +1
6 Comments
Active 2 days ago
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 today
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.
Active 6 days ago
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
Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Cloud-based technologies and services will continue to grow in popularity in 2017 thanks to the simple, scalable and cost-effective solutions they deliver. Here are three areas where cloud adoption is poised to really take off.
Microsoft is moving in-place eDiscovery & hold from ECP to EOP console under Content Search in Search and Investigation Options. In this post, I will be showing you how to export emails to a PST file using the Content Search Options.
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it.
The vast majority of email clients display l…
In this video I am going to show you how to back up and restore Office 365 mailboxes using CodeTwo Backup for Office 365.
Learn more about the tool used in this video here: http://www.codetwo.com/backup-for-office-365/ (http://www.codetwo.com/ba…
Suggested Courses
Course of the Month10 days, 15 hours left to enroll
718 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.