SOLVED

Some users can't e-mail a Team channel

%3CLINGO-SUB%20id%3D%22lingo-sub-480361%22%20slang%3D%22en-US%22%3ESome%20users%20can't%20e-mail%20a%20Team%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480361%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20an%20interesting%20problem%20that%20I've%20been%20working%20on%20for%20a%20few%20weeks.%20My%20organization%20is%20using%20Teams%20across%20the%20board%20-%20we're%20in%20%22Teams%20Only%22%20Coexistence%20Mode.%20We%20have%20a%20large%20number%20of%20teams%20and%20channels%20across%20several%20departments.%20Recently%2C%20a%20team%20was%20created%20solely%20for%20the%20purpose%20of%20sending%20e-mails%20to%3B%20think%20of%20it%20as%20a%20central%20point%20for%20notifications%20for%20our%20Marketing%20department.%26nbsp%3B%3C%2FP%3E%3CP%3ENow%2C%20our%20Teams%20Org-wide%20settings%20dictate%20that%20users%20are%20allowed%20to%20send%20e-mails%20to%20a%20channel%20address.%20We%20also%20are%20set%20to%20accept%20channel%20e-mail%20from%20the%20domain%20names%20in%20our%20organization.%20Guest%20access%20is%20turned%20off%2C%20but%20the%20team%20in%20reference%20is%20internal%20use%20only.%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20a%20hybrid%20environment%20-%20users%20authenticate%20via%20on-prem%20AD%2C%20but%20e-mail%20is%20hosted%20in%20365.%20All%20users%20have%20O365%20Enterprise%20E3%20licenses.%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20here's%20where%20it%20gets%20weird.%20I%20can%20send%20an%20e-mail%20to%20the%20channel%20successfully.%20I'm%20a%20member%20of%20the%20team.%20I%20also%20had%20another%20user%20in%20my%20department%20send%20an%20e-mail%20to%20the%20channel%2C%20who%20was%20not%20a%20member%20of%20the%20team%2C%20and%20it%20was%20also%20successful.%20However%2C%20there%20are%20some%20users%20who%20get%20a%20NDR%20e-mail%20from%20365%20when%20they%20attempt%20to%20email%20the%20channel.%20The%20channel%20e-mail%20settings%20are%20set%20to%20allow%20e-mails%20sent%20by%20anyone%20within%20our%20domain%2C%20regardless%20of%20whether%20they%20are%20a%20member.%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20team%20owner%20himself%20gets%20a%20bounce-back%20e-mail%20-%20see%20the%20attached%20image.%3C%2FP%3E%3CP%3EThis%20is%20very%20confusing%2C%20seeing%20as%20our%20org-wide%20settings%20do%20not%20prohibit%20anyone%20from%20e-mailing%20a%20channel.%20Even%20more%20strange%20is%20the%20fact%20that%20some%20users%20are%20able%20to%20e-mail%20a%20channel%2C%20while%20others%20get%20a%20NDR.%26nbsp%3B%3C%2FP%3E%3CP%3ERunning%20a%20message%20trace%20on%20the%20unsuccessful%20attempts%20shows%20a%20status%20of%20%22Delivered%22.%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20insights%20here%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-480361%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministrator%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480417%22%20slang%3D%22en-US%22%3ERe%3A%20Some%20users%20can't%20e-mail%20a%20Team%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480417%22%20slang%3D%22en-US%22%3EAre%20your%20e-mails%20being%20routed%20to%20some%20kind%20of%203rd%20party%20spam%20filtering%20or%20other%20service%20before%20getting%20to%20Teams%20e-mail%20address%3F%20On-prem%20mailboxes%20at%20all%20or%20are%20they%20all%20365%3F%20What%20happens%20when%20you%20use%20the%20%22Allow%20all%22%20for%20permisisons%20to%20send%20to%20channel%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480620%22%20slang%3D%22en-US%22%3ERe%3A%20Some%20users%20can't%20e-mail%20a%20Team%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480620%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3BNo%20third%20party%20tools%3B%20we%20have%20ATP%20enabled%20for%20safe%20attachments.%20However%2C%20there%20are%20no%20attachments%20in%20these%20e-mails.%20The%20policy%20is%20not%20very%20restrictive%20from%20what%20I%20can%20see.%20And%20the%20fact%20that%20my%20messages%20get%20through%20is%20very%20odd.%20All%20mailboxes%20are%20365.%20I'm%20not%20seeing%20an%20%22Allow%20All%22%20option%20in%20the%20channel%20settings.%3C%2FP%3E%3CP%3EWe%20currently%20have%20it%20set%20to%20allow%20anyone%20within%20the%20domain%20scope.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20569px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F109830iB6DCDBB5A1FB558E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22teamserror2.png%22%20title%3D%22teamserror2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480622%22%20slang%3D%22en-US%22%3ERe%3A%20Some%20users%20can't%20e-mail%20a%20Team%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480622%22%20slang%3D%22en-US%22%3EProbably%20because%20in%20the%20admin%20center%20under%20Team%20Settings%20you%20guys%20have%20domains%20restricted%20there.%20If%20you%20don't%20set%20that%20you%20can%20allow%20all%20domains%20and%20or%20restrict%20it%20per%20Team.%20I'd%20try%20removing%20that%20out%20of%20Admin%20center%20and%20testing%20with%20allow%20all%2C%20then%20try%20restricting%20per%20Team.%20If%20that%20works%2C%20maybe%20revisit%20setting%20org%20wide%20if%20necessary%2C%20the%20formatting%20may%20be%20off%20or%20may%20be%20a%20bug%20there%2C%20but%20might%20be%20a%20work%20around%20for%20you%20for%20now.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480624%22%20slang%3D%22en-US%22%3ERe%3A%20Some%20users%20can't%20e-mail%20a%20Team%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480624%22%20slang%3D%22en-US%22%3E%3CP%3EI%20will%20give%20that%20a%20try!%20Thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482886%22%20slang%3D%22en-US%22%3ERe%3A%20Some%20users%20can't%20e-mail%20a%20Team%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482886%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3BThis%20solved%20the%20issue.%20I%20had%20to%20remove%20the%20entries%20that%20were%20in%20our%20allowed%20domains.%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20very%20strange%2C%20considering%20the%20users%20attempting%20to%20send%20these%20e-mails%20were%20part%20of%20the%20allowed%20domains.%20As%20soon%20as%20I%20removed%20them%20and%20set%20it%20to%20%22Allow%20All%22%20it%20worked.%3C%2FP%3E%3CP%3EThanks%20for%20the%20suggestion!%20Cheers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482890%22%20slang%3D%22en-US%22%3ERe%3A%20Some%20users%20can't%20e-mail%20a%20Team%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482890%22%20slang%3D%22en-US%22%3EThere%20could%20be%20a%20bug%20there%20with%20that%20or%20something.%20Or%20the%20domain%20it's%20actually%20scanning%20might%20be%20onmicrosoft%20domain%20or%20another%20domain%20you%20have%20set%20in%20your%20aliases%20possibly.%20Something%20you%20could%20play%20around%20with%2C%20but%20if%20you%20don't%20really%20need%20to%20restrict%20domains%2C%20just%20try%20it%20at%20the%20Team%20level%20instead%20of%20org%20and%20you%20might%20be%20good%20there.%3C%2FLINGO-BODY%3E
New Contributor

I have an interesting problem that I've been working on for a few weeks. My organization is using Teams across the board - we're in "Teams Only" Coexistence Mode. We have a large number of teams and channels across several departments. Recently, a team was created solely for the purpose of sending e-mails to; think of it as a central point for notifications for our Marketing department. 

Now, our Teams Org-wide settings dictate that users are allowed to send e-mails to a channel address. We also are set to accept channel e-mail from the domain names in our organization. Guest access is turned off, but the team in reference is internal use only. 

We are a hybrid environment - users authenticate via on-prem AD, but e-mail is hosted in 365. All users have O365 Enterprise E3 licenses. 

So here's where it gets weird. I can send an e-mail to the channel successfully. I'm a member of the team. I also had another user in my department send an e-mail to the channel, who was not a member of the team, and it was also successful. However, there are some users who get a NDR e-mail from 365 when they attempt to email the channel. The channel e-mail settings are set to allow e-mails sent by anyone within our domain, regardless of whether they are a member. 

The team owner himself gets a bounce-back e-mail - see the attached image.

This is very confusing, seeing as our org-wide settings do not prohibit anyone from e-mailing a channel. Even more strange is the fact that some users are able to e-mail a channel, while others get a NDR. 

Running a message trace on the unsuccessful attempts shows a status of "Delivered". 

Any insights here?

6 Replies
Are your e-mails being routed to some kind of 3rd party spam filtering or other service before getting to Teams e-mail address? On-prem mailboxes at all or are they all 365? What happens when you use the "Allow all" for permisisons to send to channel?

@Chris Webb No third party tools; we have ATP enabled for safe attachments. However, there are no attachments in these e-mails. The policy is not very restrictive from what I can see. And the fact that my messages get through is very odd. All mailboxes are 365. I'm not seeing an "Allow All" option in the channel settings.

We currently have it set to allow anyone within the domain scope.

teamserror2.png

best response confirmed by micahsmith (New Contributor)
Solution
Probably because in the admin center under Team Settings you guys have domains restricted there. If you don't set that you can allow all domains and or restrict it per Team. I'd try removing that out of Admin center and testing with allow all, then try restricting per Team. If that works, maybe revisit setting org wide if necessary, the formatting may be off or may be a bug there, but might be a work around for you for now.

I will give that a try! Thank you!

@Chris Webb This solved the issue. I had to remove the entries that were in our allowed domains. 

This is very strange, considering the users attempting to send these e-mails were part of the allowed domains. As soon as I removed them and set it to "Allow All" it worked.

Thanks for the suggestion! Cheers.

There could be a bug there with that or something. Or the domain it's actually scanning might be onmicrosoft domain or another domain you have set in your aliases possibly. Something you could play around with, but if you don't really need to restrict domains, just try it at the Team level instead of org and you might be good there.
www.000webhost.com