Short answer: when copier scans land in Junk, get quarantined as phishing, or bounce back with a policy notice, the copier is almost always sending in a way that fails email authentication (SPF, DKIM and DMARC), or a mailbox setting is overriding your filtering. Check the user’s own Blocked Senders list first, then look at how the copier sends. The lasting fix is to send scans through an authenticated route (a relay service, OAuth or SMTP AUTH) rather than relying on an IP allow list or a spam bypass rule.
A customer’s accounts team contacted us because every scan from the office copier had started arriving as a quarantine notice instead of a PDF. Check Point Harmony Email had flagged the scans as phishing, and the same scans had been delivered without trouble a few weeks earlier. The cause turned out to be a change to the office’s public IP address. The copier sent its scans straight to Microsoft 365 from the office connection, failed SPF and DMARC every time, and had only ever been delivered because the old IP address was on an allow list. At another business, scans kept going to one person’s Junk folder even after we added a filtering exception, because the copier’s address had been added to her personal Blocked Senders list. Here is how to work out which problem you have and how to fix each one.
Fixed by Rohan Colley, Elliot Munro and Kenn Cruz at GCIT. Written up by Elliot Munro, CISO.
Symptoms
Scan to email from a multifunction printer (MFP) seems to work at the copier, but the scan never reaches the inbox. You will usually see one of these three patterns.
1. Scans land in the Junk Email folder
The scan arrives, but in Junk. When you open it, Outlook shows warnings such as:
Links and other functionality have been disabled in this message. To turn on that functionality, move this message to the Inbox.
Outlook blocked access to the following potentially unsafe attachments

2. Scans are quarantined as phishing
Instead of the scan, staff receive a quarantine notice. With Check Point Harmony Email it reads:
An email has just been received from scanner@yourbusiness.com.au and is suspected to be a “Phishing” email. The email message is safely quarantined.
The detection reasons typically include “Missing email authentications protocol signature”, “Email authentications signature check failed” and “Email is marked as spam by O365”. Microsoft Defender for Office 365 can quarantine the same scans as spam or phishing, and you will find them in the Microsoft Defender portal under Quarantine.

3. Scans sent to another organisation are rejected
When the scan is emailed to an outside business, such as a pathology lab or a supplier, the sender gets a notification back from the other organisation:
Your email message conflicts with a policy in your organization. Your email message conflicts with one or more of the recipient’s organization policies. Please take corrective actions as necessary.
People also describe these problems as “scanner emails going to spam”, “scan to email quarantined”, “copier emails marked as phishing” or “scans not arriving in Outlook”.
Affected Software
- Devices: Any copier or MFP that scans to email, including Canon, Fujifilm, Kyocera, Ricoh, Konica Minolta, Brother, HP and Sharp
- Platform: Microsoft 365 (Exchange Online Protection and Microsoft Defender for Office 365), Outlook for Windows, Mac and the web
- Related Services: Third-party email filtering such as Check Point Harmony Email, SPF, DKIM and DMARC records, SMTP relay services such as SMTP2GO
Cause
There are three separate causes, and it is worth knowing which one you have before changing anything.
- The copier sends unauthenticated email as your own domain. Many copiers use “Direct Send”: they connect straight to your Microsoft 365 MX endpoint and send as an address such as scanner@yourbusiness.com.au, without signing in. The message does not come from a server listed in your SPF record and it is not DKIM signed, so it fails DMARC. If your domain has a strict DMARC policy (
p=quarantineorp=reject), filters treat the scan exactly like a spoofed phishing email. Some offices got away with this for years because their office IP address was on the IP Allow List in the connection filter policy. When the internet connection or router changes, the IP changes, and every scan is suddenly quarantined. Messages Microsoft rates as high confidence phishing are quarantined regardless of any allow list. - The copier’s address is on the user’s Blocked Senders list. Outlook’s personal Blocked Senders list lives inside the mailbox. Microsoft honours these entries even when an administrator has created a rule to bypass spam filtering, so the scan still goes to Junk. It is easy to add an address to this list by accident with a right-click on Block Sender, or by reporting a scan as junk.
- The recipient’s organisation is blocking it. If the notice says the message conflicts with the recipient’s organisation policies, your system delivered it and the other business rejected it. This is usually a data loss prevention (DLP) policy or mail flow rule on their side, often triggered by attachments with health or financial information. A message trace will show the message left your tenant successfully.
Resolution
Step 1: Confirm which problem you have
- Find a recent failed scan and note the sender address, the time and who it was sent to.
- In the Exchange admin centre, go to Mail flow > Message trace and search for that sender. If the scan was delivered to the Junk folder, the trace shows it as delivered. If it was quarantined, the trace shows it. If the trace shows it went out to an external recipient successfully and the bounce came from their organisation, skip to Step 5.
- Open the message details or headers. In the
Authentication-Resultsheader,spf=fail,dkim=noneanddmarc=failmean the copier is sending unauthenticated (Step 3).SFV:BLKin theX-Forefront-Antispam-Reportheader means the sender is on the user’s Blocked Senders list (Step 2).
Step 2: Check the user’s Blocked Senders list
If only one person’s scans go to Junk, check this first. It takes a minute.
- In classic Outlook for Windows, go to Home > Junk > Junk E-mail Options > Blocked Senders. In new Outlook or Outlook on the web, go to Settings > Mail > Junk email > Blocked senders and domains.
- Remove the copier’s sending address (and its domain, if listed).
- An administrator can check the same list with Exchange Online PowerShell:
Get-MailboxJunkEmailConfiguration -Identity user@yourbusiness.com.au | Select-Object -ExpandProperty BlockedSendersAndDomains. - Send a test scan. If it now lands in the Inbox, you are done. This is what fixed the case in our introduction, where a filtering exception had made no difference.
Step 3: Release the quarantined scans
- In the Microsoft Defender portal, go to Email & collaboration > Review > Quarantine, find the scans and release them to the original recipients. If you use Check Point Harmony Email or another filter, release them from that portal instead, or ask your IT provider to.
- Look back to the date the problem started. Scans that were quarantined before anyone noticed are still there, and staff often need them.
Step 4: Fix how the copier sends (the lasting fix)
Adding the office IP address back to the IP Allow List or creating a rule that sets the spam confidence level to bypass filtering will make scans flow again, but it is fragile and weakens your protection. It breaks the next time the IP changes, and anyone who can send from that IP or spoof that address skips your spam filtering. Use it only as a short-term measure while you do one of these:
- Send through an authenticated relay service. A service such as SMTP2GO gives the copier its own username and password. Add the service to your SPF record and publish its DKIM records, so scans pass DMARC. This also works for offices without a static IP address, and it is the fix we applied for the customer above.
- Sign the copier in to Microsoft 365. Newer copiers support OAuth for Microsoft 365. Older ones use SMTP AUTH to
smtp.office365.comon port 587. Microsoft is turning off basic authentication for SMTP AUTH by default at the end of December 2026, so prefer OAuth or a relay. Our article on the scan to email SMTP authentication error covers the options. - Use a Microsoft 365 connector. If the office has a static IP address, an inbound connector in the Exchange admin centre that accepts mail from that IP lets the copier relay through Microsoft 365 with the message treated as coming from your organisation.
Once the copier sends through an authenticated route, remove any old IP Allow List entries or spam bypass rules you created for it. If you use a third-party filter like Check Point Harmony Email, an allow entry for the scan address may still be needed for its own checks, but scope it to that exact address.
While you are in DNS, check your SPF record. If it is at or over the limit of 10 DNS lookups it returns a permanent error, which makes every authentication problem worse. Remove services you no longer use.
Step 5: If the recipient’s organisation rejected the scan
- Run a message trace to confirm the message left your tenant and was delivered to the other organisation’s mail server.
- Contact the recipient and ask their IT team to check their DLP policies and mail flow rules, and to add your sending address as a trusted sender if appropriate. You cannot fix this from your side.
- If the rejection is intermittent, it is usually a content rule that only matches some documents. Send them the exact time and subject of a rejected message so they can find it in their logs.
Important Notes
- Do not turn off DMARC to fix a copier. A strict DMARC policy is what stops criminals sending email as your business. Fix the copier, not the policy.
- Avoid allowing your whole domain. Microsoft specifically warns against bypass rules that use your own domain as the only condition, because attackers spoof it.
- Use a dedicated sending address. Something like scanner@yourbusiness.com.au makes scans easy to identify, filter and trace, and it does not break when a staff member leaves.
- Check every device after an internet change. A new router, NBN upgrade or provider change can break scan to email, accounting software notifications and alarm systems that relied on the old IP address.
Related Resources
- Microsoft Learn: Create allowlists in Microsoft 365
- Microsoft Learn: Set up a multifunction device or application to send email using Microsoft 365
- Microsoft Learn: Configure junk email settings on cloud mailboxes
- Fix: Scan to Email “SMTP Authentication Error” in Microsoft 365
- Check Point Harmony Quarantined Email: How to Request a Release
- Fix: Legitimate Emails Going to Junk in Outlook
- How to set up Scan To Email for Office 365
- GCIT Microsoft 365 support
- Fix: DocuSign Emails Not Received (Stuck in Quarantine)
If your scans keep going missing or you want your copiers moved to a secure sending method, get in touch with our team.