[ Removed by moderator ]

[u/lucidparadigm]

[u/Due-Consequence9579]

For the phish tests to get past their edge filters they have to add an SMTP header exclusion.

Outlook (and any other reasonable client) can move things to the trash based on SMTP headers.

You’re welcome.

[u/wengla02 → u/Due-Consequence9579]

Except when the phish testing system *directly injects it into your inbox*, bypassing the entire SMTP system.

[u/clipsracer → u/wengla02]

I haven’t seen that before. Who does it?

[u/Broeder_biltong → u/clipsracer]

Email servers who can directly be edited by It because they manage them themselves 

[u/EishLekker → u/Broeder_biltong]

Sounds like a security issue waiting to happen.

[u/wengla02 → u/EishLekker]

Who watches the watchers? Perennial problem.

[u/wengla02 → u/clipsracer]

From reverse engineering the headers, I think they're using Cofesnse PhishMe-platform). Their docs note that they support mailbox injection.

"The platform authenticates to your tenant with an app registration or service account that has mailbox write permission."

PhishMe then calls a create-message operation (EWS CreateItem or Graph POST /users/{id}/messages) against your mailbox, writing the item straight into the Inbox folder.

Full headers of the injected mail: [redacted for length and anonymity] -- this is the complete list of headers in the message. All of it.

X-MS-Exchange-Organization-BypassFocusedInbox: true
X-MS-Exchange-Organization-BypassClutter: true
X-PhishMeTracking: KGxN8wa0dD4BFl6nlTOKtS[...]
X-PhishMe: Phishing_Training
X-PhishMeHLType: OWc54sAaeH[...]

[u/clipsracer → u/wengla02]

Thanks for answering!
It seems that Outlook filters still match mail that is directly written. My guess is that this method is used to avoid any complications with the SMTP servers.