Exchange Connection Problems

How to Troubleshoot Microsoft 365 SMTP Scanning from a Printer

John WilsonJohn Wilson Oct 28, 2026 868 views

Question details

The user needs to resolve an issue where a multifunction printer fails to send scan emails via Microsoft 365 using an MX endpoint on port 25.

How to Troubleshoot Microsoft 365 SMTP Scanning Failures on Printers
Product
Microsoft 365 / Exchange Online
Device & OS
not provided
Scenario
Setting up scan-to-email on a multifunction printer using the organization's Microsoft 365 MX endpoint as a relay host.
Observed behavior
The printer fails to send emails. The MX hostname resolves to an IP address, but ping requests time out, and the printer reports the hostname is inaccessible despite SMTP AUTH being disabled.
Before you start

Ensure you have the correct MX record for your Microsoft 365 organization and that you have administrative access to your network's firewall and DNS settings.

Solution 1Recommended

Verify Network Configuration and Port 25 Access

Direct send to Microsoft 365 requires outbound access on port 25. Network blockages are the most common cause of SMTP failures when using an MX endpoint.

When bypassing SMTP AUTH to relay messages directly to your Microsoft 365 MX endpoint, the connection relies heavily on standard network configurations. Firewalls and ISPs frequently block port 25 by default to prevent spam, which will instantly cause scan-to-email failures.

1
Check firewall settings

Log into your network firewall or router administration panel and ensure outbound traffic on port 25 is explicitly allowed for the printer's local IP address.

2
Verify ISP restrictions

Contact your Internet Service Provider to confirm they are not blocking outbound port 25 traffic on your connection.

3
Test SMTP connectivity

Use a computer connected to the same network as the printer to run a Telnet or PowerShell test (e.g., Test-NetConnection -ComputerName yourdomain-com.mail.protection.outlook.com -Port 25) to verify the port is reachable.

Verify Network Configuration and Port 25 Access
Ping Requests Do Not Verify SMTP: Microsoft 365 MX endpoints generally block ICMP (ping) traffic for security reasons. A ping timeout is entirely normal and does not indicate a failed SMTP connection on port 25.
Free Microsoft Office alternative

Discover a Lightweight Microsoft 365 Alternative

Complex Exchange configurations and IT setups can be frustrating. If you are looking for an easier, cost-effective way to manage your daily documents, WPS Office provides a complete, lightweight suite that requires minimal setup and offers exceptional compatibility.

  1. 1. Download the software: Visit the official WPS Office website to download the free installer for your operating system.
  2. 2. Install WPS Office: Run the installation file and follow the straightforward on-screen instructions to complete the setup.
  3. 3. Open and edit documents: Launch WPS Office to instantly view, edit, or create documents with a familiar user interface.
Highly compatible with standard Microsoft Office formats including .docx, .xlsx, and .pptx.Lightweight architecture ensures fast installation and minimal system resource usage.Built-in PDF tools make it easy to manage scanned documents, sign forms, and convert files directly.
microsoft office alternative - wps office

Frequently Asked Questions

Why does pinging the Microsoft 365 MX record time out?

Microsoft 365 servers often block ICMP traffic (ping requests) for security purposes. Therefore, a ping timeout is expected behavior and does not prove that SMTP communication on port 25 is failing.

Do I need SMTP AUTH for a printer using direct send?

No. If your printer relies on Direct Send (relaying emails directly to the Microsoft 365 MX endpoint on port 25), SMTP AUTH is not required and can remain disabled for the scanning mailbox.

Why are scan-to-email messages being marked as spam or rejected?

If emails from your printer are marked as spam when using Direct Send, it is likely because your network's public IP address has not been added to your domain's SPF record. Updating the SPF record helps Microsoft 365 verify that your IP is an authorized sender.