encrypted email address wasn't found at gmail.com

%3CLINGO-SUB%20id%3D%22lingo-sub-1998020%22%20slang%3D%22en-US%22%3Eencrypted%20email%20address%20wasn't%20found%20at%20gmail.com%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1998020%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20one%20user%20whose%20Office%20365%26nbsp%3BMessage%26nbsp%3BEncryption%26nbsp%3B(OME)%26nbsp%3Bmessage%20sent%20to%20any%20gmail%20accounts%20bounce%20back%20with%20%22your%20message%20to%20xyz%40gmail.com%20couldn't%20be%20delivered.%20XYZ%20wasn't%20found%20at%20gmail.com%22.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1998020%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1998478%22%20slang%3D%22en-US%22%3ERe%3A%20encrypted%20email%20address%20wasn't%20found%20at%20gmail.com%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1998478%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20seems%20like%20a%20standard%20%22recipient%20not%20found%22%20NDR%2C%20it%20should%20have%20nothing%20to%20do%20with%20encryption.%20Make%20sure%20you%20are%20using%20the%20correct%20address%2C%20and%20you%20can%20always%20run%20a%20message%20trace%20to%20get%20some%20additional%20info%20just%20in%20case.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

We have one user whose Office 365 Message Encryption (OME) message sent to any gmail accounts bounce back with "your message to xyz@gmail.com couldn't be delivered. XYZ wasn't found at gmail.com". 

1 Reply

That seems like a standard "recipient not found" NDR, it should have nothing to do with encryption. Make sure you are using the correct address, and you can always run a message trace to get some additional info just in case.