SOLVED

Email from notify@mstechcommunity.microsoft.com rejected due to unresolvable domain

%3CLINGO-SUB%20id%3D%22lingo-sub-226773%22%20slang%3D%22en-US%22%3EEmail%20from%20notify%40mstechcommunity.microsoft.com%20rejected%20due%20to%20unresolvable%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-226773%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Microsoft%20Tech%20Community%20site%20is%20attempting%20to%20send%20me%20notification%20emails%20with%20an%20envelope%20From%3A%20address%20of%20%22notify%40mstechcommunity.microsoft.com%22.%20However%2C%20our%20mail%20server%20is%20correctly%20rejecting%20these%20messages%20because%20mstechcommunity.microsoft.com%20is%20not%20a%20resolvable%20domain.%20Perhaps%20someone%20needs%20to%20update%20this%20address%20in%20the%20forum%20configuration.%3C%2FP%3E%3CP%3EIf%20it%20is%20helpful%2C%20these%20connection%20attempts%20are%20originating%20from%20IP%20208.74.204.9.%20A%20reverse%20lookup%20on%20this%20address%20resolves%20to%26nbsp%3Bsv3-smtp2.lithium.com.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-228766%22%20slang%3D%22en-US%22%3ERe%3A%20Email%20from%20notify%40mstechcommunity.microsoft.com%20rejected%20due%20to%20unresolvable%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-228766%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Allen%2C%20thanks%20for%20following%20up.%20I%20will%20point%20out%20that%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fsecuritycompliance%2Fanti-spam-protection-faq%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft's%20own%20outbound%20mailing%20best%20practices%3C%2FA%3E%20indicate%20that%20the%20sending%26nbsp%3Bdomain%20of%20an%20email%20should%20resolve%20in%20DNS.%20But%20if%2C%20as%20you%20say%2C%20that%20is%20not%20possible%2C%20I%20will%20see%20if%20we%20can%20whitelist%20this%20domain.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-228271%22%20slang%3D%22en-US%22%3ERe%3A%20Email%20from%20notify%40mstechcommunity.microsoft.com%20rejected%20due%20to%20unresolvable%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-228271%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F80266%22%20target%3D%22_blank%22%3E%40Ryan%20Steele%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20the%20post%2C%20you%20must%20get%20this%20allot.%20We%20do%20not%20have%20an%20A%20record%20because%20there%20is%20no%20IP%20address%20to%20be%20resolved%20on%20that%20domain%20and%20due%20to%20technical%20limitations%20the%20email%20can%20not%20be%20sent%20from%20the%20same%20sub%20domain%20as%20where%20the%20community%20resides.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20am%20afraid%20the%20only%20solution%20I%20could%20offer%20at%20this%20point%20would%20be%20to%20ask%20your%20network%20admin%20to%20whitelist%20emails%20from%20the%20Tech%20Community.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-227920%22%20slang%3D%22en-US%22%3ERe%3A%20Email%20from%20notify%40mstechcommunity.microsoft.com%20rejected%20due%20to%20unresolvable%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-227920%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Sergei%2C%20thanks%20for%20your%20report.%20I%20suspect%20our%20spam%20filter%20is%20configured%20to%20be%20more%20strict%20than%20others%20in%20this%20regard.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpon%20further%20inspection%2C%20it%20appears%20the%20mstechcommunity.microsoft.com%20does%20have%20a%20TXT%20record%20for%20SPF%2C%20just%20no%20A%20record.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-227272%22%20slang%3D%22en-US%22%3ERe%3A%20Email%20from%20notify%40mstechcommunity.microsoft.com%20rejected%20due%20to%20unresolvable%20domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-227272%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Ryan%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJust%20in%20case%2C%20never%20had%20such%20issues%2C%20all%20notifications%20are%20in%20my%20inbox.%26nbsp%3BSpam%20filter%20exists%2C%20I'm%20inside%20corporate%20environment.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Regular Contributor

The Microsoft Tech Community site is attempting to send me notification emails with an envelope From: address of "notify@mstechcommunity.microsoft.com". However, our mail server is correctly rejecting these messages because mstechcommunity.microsoft.com is not a resolvable domain. Perhaps someone needs to update this address in the forum configuration.

If it is helpful, these connection attempts are originating from IP 208.74.204.9. A reverse lookup on this address resolves to sv3-smtp2.lithium.com.

4 Replies

Hi Ryan,

 

Just in case, never had such issues, all notifications are in my inbox. Spam filter exists, I'm inside corporate environment.

Hi Sergei, thanks for your report. I suspect our spam filter is configured to be more strict than others in this regard. 

 

Upon further inspection, it appears the mstechcommunity.microsoft.com does have a TXT record for SPF, just no A record.

best response confirmed by Ryan Steele (Regular Contributor)
Solution

@Ryan Steele

 

Thanks for the post, you must get this allot. We do not have an A record because there is no IP address to be resolved on that domain and due to technical limitations the email can not be sent from the same sub domain as where the community resides.

 

I am afraid the only solution I could offer at this point would be to ask your network admin to whitelist emails from the Tech Community. 

Hi Allen, thanks for following up. I will point out that Microsoft's own outbound mailing best practices indicate that the sending domain of an email should resolve in DNS. But if, as you say, that is not possible, I will see if we can whitelist this domain.