Home

Support for RFC 7505

%3CLINGO-SUB%20id%3D%22lingo-sub-4240%22%20slang%3D%22en-US%22%3ESupport%20for%20RFC%207505%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4240%22%20slang%3D%22en-US%22%3E%3CP%3EHello%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20tere%20any%20news%20if%20(and%20when)%20Exchange%20Online%20plans%20to%20support%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7505%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ERFC%207505%3C%2FA%3E%20%3F%3C%2FP%3E%3CP%3ERFC%207505%20allows%20to%20define%20explicit%20null-mx%20record.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGmail%20is%20already%20supporting%20this.%3C%2FP%3E%3CP%3EWhen%20I%20email%20a%20domain%20with%20null-mx%20record%20I%20%3CSTRONG%3Einstantly%3C%2FSTRONG%3E%20get%20this%20nice%20looking%20NDR%3A%3C%2FP%3E%3CPRE%3EDelivery%20to%20the%20following%20recipient%20failed%20permanently%3A%0A%0A%20%20%20%20%20user%40domain.com%0A%0ATechnical%20details%20of%20permanent%20failure%3A%0ADNS%20Error%3A%2033796847%20DNS%20type%20'mx'%20lookup%20of%20domain.com%20responded%20with%20code%20NOERROR%0AThe%20domain%20domain.com%20doesn't%20receive%20email%20according%20to%20the%20administrator%3A%20returned%20Null%20MX%20https%3A%2F%2Fwww.rfc-editor.org%2Finfo%2Frfc7505%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEmail%20sent%20from%20Exchange%20Online%20will%20go%20into%20'normal'%20pending%2Fretry%20mode%20and%20%3CSTRONG%3Eafter%2048H%3C%2FSTRONG%3E%20generate%20standard%20%22host%20unreachable%22%20NDR.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-4240%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4244%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20for%20RFC%207505%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4244%22%20slang%3D%22en-US%22%3EHi%20Grezorgz%2C%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20appears%20not%20te%20be%20planned%2C%20as%20I%20could%20not%20find%20it%20on%20the%20roadmap%20nor%20on%20%3CA%20href%3D%22https%3A%2F%2Foffice365.uservoice.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foffice365.uservoice.com%3C%2FA%3E%20so%20my%20suggestion%20would%20be%20that%20you%20put%20it%20on%20%3CA%20href%3D%22https%3A%2F%2Foffice365.uservoice.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foffice365.uservoice.com%3C%2FA%3E%20and%20have%20some%20voters%20on%20it%20to%20get%20it%20to%20the%20attention%20of%20the%20engineering%20team.%20My%20experience%20is%20that%20Microsoft%20watches%20this%20closely%20so%20it%20should%20help%20you%20get%20this%20feature%20into%20Exchange%20Online.%3C%2FLINGO-BODY%3E
Grzegorz Wierzbicki
New Contributor

Hello

 

Are tere any news if (and when) Exchange Online plans to support RFC 7505 ?

RFC 7505 allows to define explicit null-mx record.

 

Gmail is already supporting this.

When I email a domain with null-mx record I instantly get this nice looking NDR:

Delivery to the following recipient failed permanently:

     user@domain.com

Technical details of permanent failure:
DNS Error: 33796847 DNS type 'mx' lookup of domain.com responded with code NOERROR
The domain domain.com doesn't receive email according to the administrator: returned Null MX https://www.rfc-editor.org/info/rfc7505

 

Email sent from Exchange Online will go into 'normal' pending/retry mode and after 48H generate standard "host unreachable" NDR.

1 Reply
Hi Grezorgz,

It appears not te be planned, as I could not find it on the roadmap nor on https://office365.uservoice.com so my suggestion would be that you put it on https://office365.uservoice.com and have some voters on it to get it to the attention of the engineering team. My experience is that Microsoft watches this closely so it should help you get this feature into Exchange Online.