Has anyone experienced problems when trying to forward Teams meeting invites? We have our Exchange setup in Office 365, and our email rules require that all incoming mail comes through our Fortimail appliance's whitelisted IP or originates from our organization's own mailboxes. Apparently, when users attempt to forward a Teams invite, the original sender's information remains in the email headers. This confuses our rules because it appears as though the email is coming from an external source, leading to it being rejected.
We can work around this issue, but it's frustrating for some users who find the extra steps cumbersome. I'm curious if anyone else has faced a similar problem and how you resolved it.
3 Answers
Consider reaching out to Fortinet support. This seems more like a setup issue — I’ve not come across anyone whose rules stop internal forwards without any problem.
Have you checked the tracking logs? If you do an enhanced search, it might show you which rule rejected the email, giving you a better idea of the problem.
You might want to adjust your mail rules. Forwarding meeting invites is standard and shouldn’t be restricted like this. It sounds like a misconfiguration on your end.
It feels more like a quirk with Exchange itself though. I’ve noticed that when you forward other types of emails, the original sender’s header doesn't stick; it's only a problem with Teams invites.