Undeliverable email messages via Office 365 Exchange

%3CLINGO-SUB%20id%3D%22lingo-sub-169803%22%20slang%3D%22en-US%22%3EUndeliverable%20email%20messages%20via%20Office%20365%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-169803%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20have%20been%20getting%20messages%20that%20mail%20delivery%20has%20failed.%20Evidently%20the%20error%20code%20is%204.4.7.%20They%20look%20like%20this%3A%3C%2FP%3E%0A%3CP%3E--------------------------------------------------------------------------------------------%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CSPAN%3EDelivery%20has%20failed%20to%20these%20recipients%20or%20groups%3A%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22mailto%3Atools2242%40gmail.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Etools2242%40gmail.com%3C%2FA%3E%3CBR%20%2F%3E%3CSPAN%3EYour%20message%20couldn't%20be%20delivered.%20Despite%20repeated%20attempts%20to%20contact%20the%20recipient's%20email%20system%20it%20didn't%20respond.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E--------------------------------------------------------------------------------------------%3C%2FP%3E%0A%3CP%3EWe%20have%20not%20sent%20any%20emails%20to%20tools2242%40gmail.com.%20I%20have%20no%20idea%20what%20that%20address%20is.%20The%20emails%20are%20getting%20through%20to%20their%20intended%20recipients%20and%20then%2C%20a%20few%20days%20later%2C%20we%20get%20these%20messages.%20Not%20all%20the%20emails%20we%20send%20result%20in%20this%20message%20but%20we%20get%20many%20of%20these%20every%20day%20and%20it%20is%20becoming%20a%20nuisance.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20checked%20all%20possible%20connections%20with%20our%20CRM%2C%20Google%20Calendar%20etc.%20and%20none%20of%20them%20could%20be%20doing%20this.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhy%20is%20Office%20365%20Exchange%20trying%20to%20send%20our%20mails%20to%20this%20gmail%20address%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20in%20advance%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERob%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-169803%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-170132%22%20slang%3D%22en-US%22%3ERe%3A%20Undeliverable%20email%20messages%20via%20Office%20365%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-170132%22%20slang%3D%22en-US%22%3EWhat%20does%20message%20trace%20in%20EAC%20say%3F%20If%20that%20still%20doesn't%20show%20any%20clues%2C%20it%20may%20be%20time%20to%20open%20a%20support%20ticket%20with%20Microsoft.%20Use%20'Start-HistoricalSearch'%20with%20-MessageTraceDetail%20parameter%20to%20generate%20a%20full%20MTL%20for%20them.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-170131%22%20slang%3D%22en-US%22%3ERe%3A%20Undeliverable%20email%20messages%20via%20Office%20365%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-170131%22%20slang%3D%22en-US%22%3E%3CP%3EDouble-check%20that%20your%20SPF%20is%20tight.%20Publish%20DKIM%20and%20DMARC%20records%20if%20you%20haven't%20yet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-170100%22%20slang%3D%22en-US%22%3ERe%3A%20Undeliverable%20email%20messages%20via%20Office%20365%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-170100%22%20slang%3D%22en-US%22%3E%3CP%3EI%20thought%20of%20that.%20However%2C%20all%20NDR%20messages%20are%20for%20emails%20we%20have%20actually%20sent%20to%20real%20recipients%2C%20and%20which%20have%20got%20through.%20Somehow%2C%20Office%20365%20Exchange%20is%20trying%20to%20send%20our%20legitimate%20emails%20to%20a%20non-existent%20address.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20the%20suggestion%20of%20blocking%20all%20NDR%20messages.%20It%20will%20certainly%20lower%20the%20rate%20of%20complaints%20I%20am%20getting%20about%20them.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EA%20further%20mystery%20is%20that%20both%20affected%20people%20use%20different%20mail%20clients.%20One%20uses%20Outlook%20and%20I%20use%20a%20Web%20based%20service%20to%20send%20and%20receive.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20any%20case%20we%20are%20all%20moving%20to%20Zoho%20mail%20soon.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERob%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-170059%22%20slang%3D%22en-US%22%3ERe%3A%20Undeliverable%20email%20messages%20via%20Office%20365%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-170059%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20having%20the%20same%20issue%20as%20well.%20Thanks%20for%20raising%20it%20up%3C%2FP%3E%0A%3CDIV%20id%3D%22selenium-highlight%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-170051%22%20slang%3D%22en-US%22%3ERe%3A%20Undeliverable%20email%20messages%20via%20Office%20365%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-170051%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20most%20likely%20a%20case%20of%20%22backscatter%22%20as%20detailed%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fblogs.msdn.microsoft.com%2Ftzink%2F2014%2F11%2F22%2Fimproving-backscatter-detection-with-boomerang%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.msdn.microsoft.com%2Ftzink%2F2014%2F11%2F22%2Fimproving-backscatter-detection-with-boomerang%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1781247%22%20slang%3D%22en-US%22%3ERe%3A%20Undeliverable%20email%20messages%20via%20Office%20365%20Exchange%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1781247%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F126660%22%20target%3D%22_blank%22%3E%40Robert%20Keith%3C%2FA%3E%26nbsp%3BHow%20is%26nbsp%3B%20ZOHO%20mail%20going%20for%20you%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi,

 

We have been getting messages that mail delivery has failed. Evidently the error code is 4.4.7. They look like this:

--------------------------------------------------------------------------------------------

Delivery has failed to these recipients or groups:

 

tools2242@gmail.com
Your message couldn't be delivered. Despite repeated attempts to contact the recipient's email system it didn't respond.

--------------------------------------------------------------------------------------------

We have not sent any emails to tools2242@gmail.com. I have no idea what that address is. The emails are getting through to their intended recipients and then, a few days later, we get these messages. Not all the emails we send result in this message but we get many of these every day and it is becoming a nuisance.

 

I have checked all possible connections with our CRM, Google Calendar etc. and none of them could be doing this.

 

Why is Office 365 Exchange trying to send our mails to this gmail address?

 

Thanks in advance,

 

Rob

 

 

 

 

 

 

6 Replies
Highlighted
Highlighted

I'm having the same issue as well. Thanks for raising it up

 
Highlighted

I thought of that. However, all NDR messages are for emails we have actually sent to real recipients, and which have got through. Somehow, Office 365 Exchange is trying to send our legitimate emails to a non-existent address.

 

Thanks for the suggestion of blocking all NDR messages. It will certainly lower the rate of complaints I am getting about them.

 

A further mystery is that both affected people use different mail clients. One uses Outlook and I use a Web based service to send and receive.

 

In any case we are all moving to Zoho mail soon.

 

Rob

Highlighted

Double-check that your SPF is tight. Publish DKIM and DMARC records if you haven't yet.

Highlighted
What does message trace in EAC say? If that still doesn't show any clues, it may be time to open a support ticket with Microsoft. Use 'Start-HistoricalSearch' with -MessageTraceDetail parameter to generate a full MTL for them.
Highlighted