Microsoft Tech Community Live:  Microsoft Teams Edition
November 09, 2021, 08:00 AM - 12:00 PM (PST)

Unable to send email to Teams channel

%3CLINGO-SUB%20id%3D%22lingo-sub-312534%22%20slang%3D%22en-US%22%3EUnable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312534%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20owner%20of%20the%20Teams.%20I%20get%20the%20fol%20error%20msg%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ERemote%20Server%20returned%20'554%205.4.182%20Problem%20occurred%20during%20the%20delivery.%20Exception%20Message%3AThe%20remote%20server%20returned%20an%20error%3A%20(400)%20Bad%20Request.'%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ECan%20anyone%20help%20%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-312534%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312986%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312986%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Vesa%2C%3C%2FP%3E%3CP%3Ethanks%20for%20your%20reply.%3C%2FP%3E%3CP%3EWill%20try%20re-creating%20the%20email%20address%2C%20but%20I%20think%20I%20will%20also%20open%20a%20ticket%20with%20MS%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312985%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312985%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Chris%2C%3C%2FP%3E%3CP%3Ethanks%20for%20your%20reply.%3C%2FP%3E%3CP%3EYes%20all%20those%20settings%20are%20ok.%3C%2FP%3E%3CP%3EThink%20will%20open%20ticket%20with%20MS.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312834%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312834%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20are%20two%26nbsp%3Bplaces%20where%20email%20settings%20exist%3C%2FP%3E%0A%3CP%3E1.%20Teams%20Admin%20center.%20Check%20that%20you%20have%20no%20domains%20there%20(or%20you%20are%20sending%20email%20from%20allowed%20domain)%3C%2FP%3E%0A%3CP%3E2.%20Channel%20email%20settings%20(advanced)%20as%20Chris%20stated%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnd%20have%20you%20tried%20removing%20the%20email%20address%20for%20the%20channel%20and%20recreating%20it%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20might%20be%20also%20worth%20trying%20to%20send%20email%20from%20different%20clients%2Faccounts%2Fsystems%20to%20check%20if%20it%20is%20sender%20or%20receiver%20related.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312832%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312832%22%20slang%3D%22en-US%22%3EAssume%20you%20are%20sending%20email%20to%20the%20channel%20from%20your%20internal%20domain%20email%3F%20Or%20from%20an%20external%20domain%20to%20the%20team%3F%20If%20external.%20Right%20click%20channel%20and%20get%20email%20and%20there%20should%20be%20an%20advanced%20link%20%2F%20tab%20where%20you%20can%20edit%20to%20allow%20more%20than%20just%20internal.%20Might%20not%20be%20it.%20But%20worth%20checking%20the%20setting%20to%20see.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312602%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312602%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20your%20response%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Econnector%2Fwebhook%20...%20not%20my%20speciality%20...%20Will%20ahve%20to%20look%20into%20another%20tool.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312584%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312584%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20functionality%20has%20always%20been%20borked%2C%20for%20example%20the%20last%20test%20email%20I%20sent%20to%20one%20of%20my%20teams%20few%20days%20back%20is%20yet%20to%20arrive%2C%20and%20I%20haven't%20received%20any%20NDRs%20either.%20Message%20trace%20of%20course%20shows%20it%20being%20handed%20to%20the%20emea-teams-ms.mail.protection.outlook.com%20MTA%2C%20and%20that's%20it%2C%20black%20hole.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'd%20recommend%20using%20a%20connector%2Fwebhook%20instead%2C%20where%20possible.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312583%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312583%22%20slang%3D%22en-US%22%3EIt%20should%20mean%20all!%20No%20input%20required!%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312561%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312561%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Adam%20for%20your%20reply%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%20I%20have%20and%20it%20is.%20Do%20you%20know%20if%20we%20have%20to%20specify%20accepted%20SMTP%20domains%20or%20if%20we%20leave%20it%20blank%2C%20it%20means%20%22All%22%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312555%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312555%22%20slang%3D%22en-US%22%3EHave%20you%20verified%20this%20is%20allowed%20in%20settings%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312551%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312551%22%20slang%3D%22en-US%22%3E%3CP%3EI%20get%20this%20error%20when%20I%26nbsp%3Bsend%20email%20to%20Teams%20channel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312546%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312546%22%20slang%3D%22en-US%22%3ENot%20much%20we%20can%20do%20here...when%20do%20you%20get%20that%20error%3F%20I%20would%20recommend%20you%20to%20open%20a%20support%20ticket%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1523827%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1523827%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20you%20been%20able%20to%20find%20a%20solution%3F%20We%20are%20having%20the%20same%20mysterious%20problem%20as%20well.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F75429%22%20target%3D%22_blank%22%3E%40Chantal%20Belanger%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1711096%22%20slang%3D%22fr-FR%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1711096%22%20slang%3D%22fr-FR%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F75429%22%20target%3D%22_blank%22%3E%40Chantal%20Belanger%3C%2FA%3E%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F729512%22%20target%3D%22_blank%22%3E%40bingobongo%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22tlid-translation%20translation%22%3E%3CSPAN%20class%3D%22%22%3Eis%20your%20problem%20resolved%3F%3C%2FSPAN%3E%20%3CSPAN%3Eand%20how%3F%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22%22%3EI%20have%20the%20same%20error%20message%20when%20I%20redirect%20an%20external%20mail%20to%20a%20Teams%20channel%20(via%20the%20automatic%20exchange%20mail%20redirect)%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1782413%22%20slang%3D%22de-DE%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1782413%22%20slang%3D%22de-DE%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F808287%22%20target%3D%22_blank%22%3E%40LionelPS%3C%2FA%3E%20%3CBR%20%2F%3E%20Have%20you%20found%20a%20solution%3F%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ESame%20problem%20here%20when%20redirecting%20external%20mails%20to%20Teams%20channel.%3CBR%20%2F%3ESupport%20%3CSPAN%20class%3D%22tlid-translation%20translation%22%3E%3CSPAN%20class%3D%22%22%3Erecommended%3C%2FSPAN%3E%3C%2FSPAN%3E%20to%20whitelist%20the%20Sender-IP%20of%20the%20used%20mail%20server%20in%20Security%20Center%2C%20but%20hasn't%20take%20any%20effect.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1785209%22%20slang%3D%22fr-FR%22%3ERe%3A%20Unable%20to%20send%20email%20to%20Teams%20channel%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1785209%22%20slang%3D%22fr-FR%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F833124%22%20target%3D%22_blank%22%3E%40cgrd_Ole%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eno%2C%20aresolved%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I am owner of the Teams. I get the fol error msg:

 

Remote Server returned '554 5.4.182 Problem occurred during the delivery. Exception Message:The remote server returned an error: (400) Bad Request.'

 

Can anyone help ?

 

Thanks

 

19 Replies
Not much we can do here...when do you get that error? I would recommend you to open a support ticket

I get this error when I send email to Teams channel

Have you verified this is allowed in settings?

Thanks Adam for your reply,

 

Yes I have and it is. Do you know if we have to specify accepted SMTP domains or if we leave it blank, it means "All" ?

It should mean all! No input required!

Adam

That functionality has always been borked, for example the last test email I sent to one of my teams few days back is yet to arrive, and I haven't received any NDRs either. Message trace of course shows it being handed to the emea-teams-ms.mail.protection.outlook.com MTA, and that's it, black hole.

 

I'd recommend using a connector/webhook instead, where possible.

Thanks for your response,

 

connector/webhook ... not my speciality ... Will ahve to look into another tool.

Assume you are sending email to the channel from your internal domain email? Or from an external domain to the team? If external. Right click channel and get email and there should be an advanced link / tab where you can edit to allow more than just internal. Might not be it. But worth checking the setting to see.

There are two places where email settings exist

1. Teams Admin center. Check that you have no domains there (or you are sending email from allowed domain)

2. Channel email settings (advanced) as Chris stated

 

And have you tried removing the email address for the channel and recreating it?

 

It might be also worth trying to send email from different clients/accounts/systems to check if it is sender or receiver related.

 

Hello Chris,

thanks for your reply.

Yes all those settings are ok.

Think will open ticket with MS.

Hello Vesa,

thanks for your reply.

Will try re-creating the email address, but I think I will also open a ticket with MS

Have you been able to find a solution? We are having the same mysterious problem as well. @Chantal Belanger 

@Chantal Belanger  @bingobongo 

is your problem resolved? and how ?

I have the same error message when I redirect an external mail to a Teams channel (via the automatic exchange mail redirect)

@LionelFp_fr 
Have you found a solution?

Same problem here when redirecting external Mails to Teams-Channel.
Support recommended to whitelist the Sender-IP of the used Mailserver in Security Center, but hasn't take any effect.

@cgrd_Ole 

no, unresolved issue.

@LionelFp_fr 

Hi, your problem is resolved? If resolved, please tell how resolve 

 

10x

not solved on our side.

In my environment, spf = softfail was happening, but solving it solved the problem.