Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Andrew Stobart
Determine which Exchange Online connector an inbound message was attributed to
This is a quick tip for something that I'm asked quite often. The scenario is that you have created an inbound connector in Exchange Online and want to verify that mail which should be coming in through that connector really is; as opposed to mail coming in through a different custom connector or even the default hidden inbound connector. The quickest way I’ve found to do this is through PowerShell. First, find a message that was received by Exchange Online.
Use headers to determine which Exchange Online tenant a message was attributed to
Consider the following mail flow. On-premises environment --> Your Exchange Online tenant --> External Recipient With the above mail flow, you may find yourself in a situation where you need to validate that the outbound message was properly attributed to your Exchange Online tenant. I recently worked with an organization that controlled two Exchange Online tenants and found that their mail was not relaying out of the tenant they expected.
Did I get zapped by ZAP?
ZAP, also known as Zero-hour Auto Purge, is a protection feature in Exchange Online that can move spam, phish, or malware messages from users’ inbox to their junk folder. This feature works in the background and can often be forgotten about. If a message is delivered to a mailbox, and then at a later time it is determined to be junk, ZAP can reactively move the message to the users' junk folder. For more information about ZAP, check out Zero-hour auto purge – protection against spam and malware.
Figure out which spam filter marked a message as spam
It has been quiet around these parts as of late. Much too quiet. To put that to an end, I have a handy tip today that could help in your spam troubleshooting adventures. For various reasons, organizations sometimes need to create multiple spam filters in Exchange Online. When troubleshooting a false positive (an inbound message that was marked as spam incorrectly), it can be tricky to figure out which spam filter was used to process the message. Well, that changes today with this tip.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Andrew
Contact Andrew, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack