I have seen this behavior before where it hits the client's web hosting company on IMAP/POP3 instead of just doing a straight autodiscover and finding. The computer resolves autodiscover to as it should. There are two SRV records, but those are for Skype for Business.

There is no recommended SRV record for email. I have searched Google and cannot find the I don't know what you mean by 'autoconfig client DNS and SRV records.' If you are talking about all of the recommended Office 365 DNS entries, yes, as I mentioned, they already exist. Is the default A record for on GoDaddy the issue? That record is needed to find the domain in a browser without putting www in front of it. WHY would an Office 365 account not just find the autodiscover and set itself up, but go to GoDaddy instead? However, the new account setup screen in the Contro Panel Mail applet hangs after setting up the network connection at the second step of looking for the account settings for the email address, and I see traffic being blocked (as it should) by the firewall trying to go out IMAP 143/993 and POP3 110/995 ports and going to theġ84.168.221.16 IP, which is GoDaddy (ip-184-168-221-16.ip.). Running an nslookup for the domain on that computer returns , so when Outlook tries to set up the new account, I expect it to go look for the autodiscover entry, then go off to and configure itself. The domain and DNS are on GoDaddy and have all the Office 365 entries, along with the default GoDaddy A record pointing to 184.168.221.16 IP address.

I am trying to set up an Office 365 account on a computer sitting behind my WatchGuard T35-W with egress filtering enabled and IMAP/POP3 not allowed out.

Godaddy email setup outlook 2017 imap