Please do not top-post on this mailing list... On 16 January 2018 at 11:20, jin&hitman&Barracuda <jinhit...@gmail.com> wrote: > > I did not realize that nonexist host names. I believe they basically ignore > faults when they produce them but they keep pushing us to follow their > requirements. > > > On 16 Jan 2018 1:59 p.m., "Jim Reid" <j...@rfc1035.com> wrote: > > > > > On 16 Jan 2018, at 10:49, jin&hitman&Barracuda <jinhit...@gmail.com> wrote: > > > > We are having difficulties while delivering mails to Microsoft's domains > > like hotmail and outlook. > > They appear to have a DNS problem which is causing outbound mail to fail. > Their SMTP servers are using non-existent hostnames when they say HELO. This > DNS brokenness may well be wreaking havoc for those using SPF, DKIM, etc when > speaking to M$ mail servers or receiving email from them.
If you continue to have problems with your emails being dropped instead of delivered to Microsoft domains, see http://go.microsoft.com/fwlink/?LinkID=614866. It has worked for me and for others. The only problems I now have are with a very few receiving mailservers that use TRUSTManager, possibly because they are not updating their records. I haven't found a proper solution as this software seems to be used by organisations that are neither big enough nor small enough to care. My workaround is to use relaying (specified in transport file) once I have identified a domain with this problem.
