'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Scanner to Email Fails When Sending to Exchange Recipient
Question details
The user needs to resolve an issue where scanned documents sent via a scanner using Gmail SMTP fail to deliver to Microsoft Exchange or Microsoft 365 mailboxes, despite appearing in the Sent folder.
- Product
- Microsoft Exchange
- Device & OS
- not provided
- Scenario
- Sending scanned documents to an Exchange or Microsoft 365 mailbox via a scanner configured with Gmail SMTP.
- Observed behavior
- Messages successfully appear in the Gmail Sent folder without error but fail to arrive in the recipient's Exchange mailbox.
Ensure you have administrative access to your scanner's network settings and the Microsoft 365 or Exchange Admin Center to perform a message trace.
Enable SMTP Authentication and Run a Message Trace
Configure the scanner with proper SMTP credentials and run a message trace in Exchange to pinpoint where the delivery fails.
When using Gmail SMTP to send scans to an Exchange server, missing authentication or incorrect DNS records can cause the receiving server to silently drop the message.
Access your scanner's web interface or network configuration menu. Navigate to the Email or SMTP settings and ensure SMTP Authentication is enabled for the Gmail account.
Use a public DNS lookup tool (such as MXToolbox) to confirm that the recipient's domain has valid MX (Mail Exchange) records pointing to Microsoft 365 or their Exchange server.
Log into the Exchange Admin Center, go to 'Mail flow' > 'Message trace'. Enter the scanner's email address as the sender to determine whether the Exchange server received, rejected, or quarantined the message.
Handle Your Scanned Documents Easily with WPS Office
While resolving Exchange and Microsoft 365 email delivery issues, you can use WPS Office to edit, merge, and organize your scanned PDFs and documents. It is a lightweight, free alternative to Microsoft Office.
- 1. Download WPS Office: Visit the official WPS Office website and download the installer for your operating system.
- 2. Install the Software: Run the installer and follow the on-screen instructions to complete the setup.
- 3. Open Scanned Documents: Launch WPS Office and open your scanned PDFs or Word files directly to start editing.
Frequently Asked Questions
Why do scanned emails show in the Gmail Sent folder but never arrive in Exchange?
When using Gmail SMTP, the email is successfully handed off from the scanner to Google's servers, placing it in the Sent folder. However, strict spam filters, missing MX records, or Exchange mail-flow rules at the destination may block or drop the message before it reaches the inbox.
Do I need an App Password for Gmail SMTP on my scanner?
Yes. If your Gmail account has Two-Factor Authentication (2FA) enabled, standard passwords will fail. You must generate a unique App Password in your Google Account security settings and enter it into the scanner's SMTP configuration.
How long does it take for Exchange mail-flow changes to take effect?
Changes to internal mail-flow rules or connectors in the Exchange Admin Center typically apply within a few minutes. However, updates to external public DNS records (like MX or SPF) can take up to 24-48 hours to fully propagate globally.
