Outlook not sending or receiving messages

The administrator of blueridgedna.com must correct the domain’s inbound mail routing or make its receiving mail server reachable; this Gmail timeout is not an Outlook client sending failure.

Gmail attempted to connect to [IP Address] and [IP Address], but neither accepted a connection. Gmail will keep retrying for the stated 47 hours. Reinstalling Outlook, changing Outlook profiles, or modifying Gmail permissions will not resolve this specific error.

If you administer blueridgedna.com

First determine where the domain’s email is supposed to be hosted.

If the mailboxes are hosted in Microsoft 365

1. Sign in to the Microsoft 365 admin center.
2. Go to Settings → Domains and select blueridgedna.com.
3. Open Required DNS settings, then select Check DNS.
4. Correct the MX record shown as required by Microsoft 365.
5. Confirm that only the supported Microsoft 365 MX record is configured. It will normally target a Microsoft mail-protection hostname rather than the website’s IP address.
6. After updating DNS at the domain’s DNS provider, allow time for propagation and send another external test message.

Microsoft documents this MX-verification procedure and notes that DNS changes can take up to 72 hours to propagate.^1^

Also check Microsoft 365 admin center → Setup → Domains. Review the domain’s Status; if an issue appears, select the three-dot menu and Check health to see which DNS records require correction.^2^

If email is hosted elsewhere

At the DNS host and mail provider:

1. Check the public MX records for blueridgedna.com.
2. Confirm they point to the inbound servers specified by the email provider—not merely to the domain’s website or parked-domain addresses.
3. If the MX records intentionally resolve to the reported IP addresses, ask the hosting provider to verify that its SMTP service is reachable publicly on TCP port 25.
4. Remove stale MX records left by a previous email provider.
5. Verify that the recipient mailbox exists after routing is restored.

The two reported IP addresses alone do not establish the domain’s intended email provider; the current authoritative MX records determine where inbound mail should be delivered. Incorrect MX records are a documented cause of Microsoft 365 mail-flow failures.^3^

If you do not administer blueridgedna.com

Contact the recipient through another method and send them the complete Gmail diagnostic. Ask them to forward it to whoever manages their domain DNS or email hosting. A comparable connection failure generally has to be fixed by the recipient’s email administrator.^4^

Meanwhile:

• Let Gmail continue retrying; repeated manual sends will encounter the same unreachable destination.
• Test sending to an unrelated domain. If that succeeds, the failure is isolated to blueridgedna.com.
• If Outlook also cannot send to or receive from any domain, treat that as a separate Outlook/account issue; the quoted Gmail timeout does not diagnose it.

References

1. Fix NDR error "550 5.1.10" in Exchange Online
2. Find and fix issues after adding your domain or DNS records
3. Troubleshoot mail flow in Exchange Online
4. DELIVERY HAS FAILED TO THESE RECIPIENTS OR GROUPS ERROR MESSAGE - Microsoft Q&A