marking emails as internal vs external when using mass mail provider

%3CLINGO-SUB%20id%3D%22lingo-sub-3256310%22%20slang%3D%22en-US%22%3Emarking%20emails%20as%20internal%20vs%20external%20when%20using%20mass%20mail%20provider%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3256310%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20folks%20!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20our%20tenant%2C%20we%20have%20activated%20a%20rule%20that%20warns%20users%20when%20received%20emails%20are%20from%20an%20external%20source%2C%20and%20this%20works%20quite%20well.%20However%2C%20we%20have%20departments%20that%20use%20external%20mass%20mail%20providers%20(like%20mailchimp)%20to%20reach%20out%20to%20both%20internal%20and%20external%20recipients.%20Is%20there%20some%20way%20I%20could%20construct%20a%20rule%20that%20would%20trust%20specific%20internal%20email%20addresses%20as%20being%20internal%20even%20when%20they%20are%20received%20from%20an%20external%20source%20and%20not%20trigger%20the%20external%20email%20rule%20%3F%20Obviously%20this%20would%20require%20specifying%20the%20sender%20organisation%20in%20some%20way...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAm%20I%20making%20any%20sense%20%3F%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3256310%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3257510%22%20slang%3D%22en-US%22%3ERe%3A%20marking%20emails%20as%20internal%20vs%20external%20when%20using%20mass%20mail%20provider%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3257510%22%20slang%3D%22en-US%22%3EYou%20can%20either%20use%20a%20transport%20rule%20to%20mark%20the%20traffic%20from%20this%20source%20as%20trusted%2C%20or%20user%20Enhanced%20filtering%20for%20connectors%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmail-flow-best-practices%2Fuse-connectors-to-configure-mail-flow%2Fenhanced-filtering-for-connectors%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fexchange%2Fmail-flow-best-practices%2Fuse-connectors-to-configure-mail-flow%2Fenhanced-filtering-for-connectors%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3256848%22%20slang%3D%22en-US%22%3ERe%3A%20marking%20emails%20as%20internal%20vs%20external%20when%20using%20mass%20mail%20provider%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3256848%22%20slang%3D%22en-US%22%3Eyou%20can%20add%20exclusion%20in%20your%20transport%20rule%20if%20the%20email%20sent%20by%20the%20specific%20email%20address%20and%20also%20you%20can%20add%20the%20specific%20email%20header%20from%20the%20value%20to%20exclusion%20in%20transport%20rule.%3C%2FLINGO-BODY%3E
New Contributor

Hi folks !

 

In our tenant, we have activated a rule that warns users when received emails are from an external source, and this works quite well. However, we have departments that use external mass mail providers (like mailchimp) to reach out to both internal and external recipients. Is there some way I could construct a rule that would trust specific internal email addresses as being internal even when they are received from an external source and not trigger the external email rule ? Obviously this would require specifying the sender organisation in some way...

 

Am I making any sense ? :)

 

2 Replies
you can add exclusion in your transport rule if the email sent by the specific email address and also you can add the specific email header from the value to exclusion in transport rule.
You can either use a transport rule to mark the traffic from this source as trusted, or user Enhanced filtering for connectors:

https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/use-connectors-to-configure-mail-...