Mail relay to Office 365 from IIS SMTP Relay

%3CLINGO-SUB%20id%3D%22lingo-sub-40862%22%20slang%3D%22en-US%22%3EMail%20relay%20to%20Office%20365%20from%20IIS%20SMTP%20Relay%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-40862%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20about%20a%20month%20we%20cannot%20relay%20email%20from%20our%20IIS%20SMTP%20Relay%20to%20Office%20365.%20This%20has%20worked%20for%20a%20long%20time%2C%20therefore%20I%20do%20not%20get%20why%20it%20is%20not%20working%20anymore.%20The%20account%20used%20is%20still%20active%20and%20I%C3%A1m%20able%20to%20sign-in%20with%20the%20account.%20I've%20even%20completely%20reinstalled%20and%20reconfigured%20the%20SMTP%20relay%20role%20in%20IIS%20following%20this%20procedure%3A%3C%2FP%3E%3CP%3E%3CA%20title%3D%22here%22%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FHow-to-configure-IIS-for-relay-with-Office-365-eb57abd2-3859-4e79-b721-2ed1f0f579c9%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20getting%20the%20following%20warning%20in%20the%20eventvwr%3A%3C%2FP%3E%3CP%3E%3CEM%3EMessage%20delivery%20to%20the%20host%20'40.97.153.170'%20failed%20while%20delivering%20to%20the%20remote%20domain%20'%23%23%23%23%23%23%23%23%23%23.COM'%20for%20the%20following%20reason%3A%20The%20remote%20SMTP%20service%20rejected%20AUTH%20negotiation.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20you%20guys%20can%20help%20me%20out%20here.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-40862%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481473%22%20slang%3D%22en-US%22%3ERe%3A%20Mail%20relay%20to%20Office%20365%20from%20IIS%20SMTP%20Relay%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481473%22%20slang%3D%22en-US%22%3E%3CP%3EVerify%20you%20are%20not%20using%20%22Integrated%20Windows%20Authentication%22%20and%20you%20are%20using%20%22Basic%20Authentication%22%20for%20Outbound%20Security.%26nbsp%3B%20Also%20the%20%22Domain%20Name%22%20should%20not%20match%20your%20Email%20Domain%20since%20you%20want%20to%20email%20to%20send%20via%20the%20Smart%20Host.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-41136%22%20slang%3D%22en-US%22%3ERe%3A%20Mail%20relay%20to%20Office%20365%20from%20IIS%20SMTP%20Relay%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-41136%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9835%22%20target%3D%22_blank%22%3E%40Daniel%20Lentz%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3EHi%2C%20there%20have%20been%20made%20som%20changes%20starting%202017%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fexchange%2F2016%2F03%2F29%2Fimportant-notice-for-office-365-email-customers-who-have-configured-connectors%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fexchange%2F2016%2F03%2F29%2Fimportant-notice-for-office-365-email-customers-who-have-configured-connectors%2F%3C%2FA%3E%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EBe%20sure%20to%20read%20the%20scenarios%20very%20carefully%20as%20it%20doesn't%20apply%20to%20all%20IIS%20SMTP%20Relay%20setups.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-41132%22%20slang%3D%22en-US%22%3ERe%3A%20Mail%20relay%20to%20Office%20365%20from%20IIS%20SMTP%20Relay%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-41132%22%20slang%3D%22en-US%22%3E%3CP%3ENote%20that%20this%20will%20be%20forced%20only%20from%201st%20February%2C%20so%20the%20root%20cause%20is%20definitely%20different%20here.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-41108%22%20slang%3D%22en-US%22%3ERe%3A%20Mail%20relay%20to%20Office%20365%20from%20IIS%20SMTP%20Relay%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-41108%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20the%20same%20message.%3C%2FP%3E%3CP%3ESome%20mails%20wont%20get%20thru%20i%20thougt%20it%20was%20problem%20on%20the%20other%20side.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Elast%20week%20we%20had%20some%20problems%20.%3C%2FP%3E%3CP%3Ewe%20have%20a%20hybrid%20setup%20i%20think%20is%20setup%20right.%3C%2FP%3E%3CP%3Ehow%20come%20some%20mails%20work%20and%20others%20not%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-41055%22%20slang%3D%22en-US%22%3ERe%3A%20Mail%20relay%20to%20Office%20365%20from%20IIS%20SMTP%20Relay%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-41055%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20there%20have%20been%20made%20som%20changes%20starting%202017%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fexchange%2F2016%2F03%2F29%2Fimportant-notice-for-office-365-email-customers-who-have-configured-connectors%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fexchange%2F2016%2F03%2F29%2Fimportant-notice-for-office-365-email-customers-who-have-configured-connectors%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-41015%22%20slang%3D%22en-US%22%3ERe%3A%20Mail%20relay%20to%20Office%20365%20from%20IIS%20SMTP%20Relay%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-41015%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20is%20the%20handshake%20protocol%20being%20implemented%3F%26nbsp%3B%20Kerb%3F%26nbsp%3B%20CHAP%3F%2C%20etc....FS%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-40977%22%20slang%3D%22en-US%22%3ERe%3A%20Mail%20relay%20to%20Office%20365%20from%20IIS%20SMTP%20Relay%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-40977%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20Ronald%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20might%20want%20to%20checkout%20the%20article%20below%2C%20it%20has%26nbsp%3Bsome%20additional%26nbsp%3Btroubleshooting%20and%20configuration%20guidance.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ESetting%20up%20multifunction%20device%20or%20application%20to%20send%20email%20using%20Office%20365%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2FDn554323(v%3DEXCHG.150).aspx%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2FDn554323(v%3DEXCHG.150).aspx%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELet%20me%20know%20if%20it%20helps.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENick%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Since about a month we cannot relay email from our IIS SMTP Relay to Office 365. This has worked for a long time, therefore I do not get why it is not working anymore. The account used is still active and Iám able to sign-in with the account. I've even completely reinstalled and reconfigured the SMTP relay role in IIS following this procedure:

here

 

I'm getting the following warning in the eventvwr:

Message delivery to the host '40.97.153.170' failed while delivering to the remote domain '##########.COM' for the following reason: The remote SMTP service rejected AUTH negotiation.

 

Hope you guys can help me out here.

7 Replies
Highlighted

Hello, Ronald,

 

You might want to checkout the article below, it has some additional troubleshooting and configuration guidance.

 

Setting up multifunction device or application to send email using Office 365
https://technet.microsoft.com/en-us/library/Dn554323(v=EXCHG.150).aspx

 

Let me know if it helps. 

 

Nick

Highlighted

How is the handshake protocol being implemented?  Kerb?  CHAP?, etc....FS?

Highlighted
Highlighted

Hi,

 

We have the same message.

Some mails wont get thru i thougt it was problem on the other side.

 

last week we had some problems .

we have a hybrid setup i think is setup right.

how come some mails work and others not ?

 

Highlighted

Note that this will be forced only from 1st February, so the root cause is definitely different here.

Highlighted

@Daniel Lentz wrote:

Hi, there have been made som changes starting 2017

 

https://blogs.technet.microsoft.com/exchange/2016/03/29/important-notice-for-office-365-email-custom...


Be sure to read the scenarios very carefully as it doesn't apply to all IIS SMTP Relay setups.

Highlighted

Verify you are not using "Integrated Windows Authentication" and you are using "Basic Authentication" for Outbound Security.  Also the "Domain Name" should not match your Email Domain since you want to email to send via the Smart Host.