SMTP / Scan-to-Email

How to Configure Custom SMTP server SMTP on a Canon Printer

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

What this guide covers

Configure Custom SMTP server SMTP for scan-to-email on a Canon printer.

Step-by-step

Get the SMTP server details from your provider (server name, port, encryption, username, password).
On the Canon printer web admin: Network → Email → SMTP Server.
Enter the values supplied by the provider.
Common ports: 25 (unencrypted, often blocked), 465 (SSL), 587 (STARTTLS).
Save and send a test mail. Check the printer's email log for any rejection.

What you'll need

Your printer + power
Brand mobile app or printer web admin access (printer IP via panel network info page)
For enterprise / cloud / SMTP: credentials supplied by your IT team or service provider
For purchase guides: clear understanding of your monthly print volume and colour vs mono needs

Troubleshooting

Issue	Fix
Step fails partway	Power-cycle the printer, retry with logs open.
Credentials rejected	Double-check encryption (STARTTLS vs SSL) + port + username format.
Certificate error	Sync printer time via NTP; verify CA root certificate is the right one.
Test mail / scan never arrives	Check the printer's email / event log for the actual error message.

Frequently asked questions

Does this guide apply to my specific model?

The procedure is the standard one for the brand. Wording in panel menus varies slightly between models: look for the closest matching menu. Vendor support sites have model-specific articles.

Is the configuration retained after a firmware update?

Usually yes, but enterprise WiFi credentials sometimes get cleared. Document your settings before any update.

Can I script this for a fleet of printers?

Most brands expose a SOAP or REST API on the embedded web server. Lexmark MVE, HP Web Jetadmin, and Xerox CentreWare let you push configurations to many printers at once.

Where do I see the brand's authoritative procedure?

The brand support site indexed for your exact model. Wording in panel menus varies between models.

More printer fixes → /printers/
Install / setup guides → /printers/section/install_guides.html

Related guides worth a look while you sort this one out:

References

Brand support documentation for your model

Reference material, not professional advice. When in doubt, call brand authorised service.

Why this matters for your day-to-day

this hardware that's misbehaving costs more than the fix itself: lost productivity, missed calls, security risk, even safety risk in some categories. Treating the symptom quickly with a documented procedure is cheaper than letting it persist. The steps above are written to get you back to working in under an hour where possible, and to flag clearly when escalation is the right call.

Before you start

A few things to confirm so this device fix goes cleanly:

Latest firmware downloaded if you're going to update.
Warranty + support contract status checked, opening sealed parts may void it.
Backup of current configuration (where applicable) taken.
Spare parts on hand if you anticipate replacement.
Adequate workspace, lighting, and time. rushing causes regressions.

Quick verification

Before you walk away from the affected device fix, run through:

1. Reproduce the original trigger, does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.

When to call How support instead

Escalate if:

The same symptom returns within 24 hours of a clean fix.
You see physical damage (burn marks, swollen battery, cracked PCB).
The device is in warranty and a hardware replacement is the cheaper outcome.
Repair requires specialised tools you don't own (alignment jigs, calibration software).
Following the official path keeps the warranty intact, which matters more than the time spent.

Topology deep dive: how this fits the rest of your setup

Before you touch the Canon inkjet and laser side of this, sketch the data path on a napkin. For imageCLASS MF3010, the flow is: trigger source (user at panel, app on phone, host PC) -> printer firmware logic -> network stack (WiFi NIC or LAN port) -> upstream (router / switch / firewall) -> the actual destination service (mail relay, file share, cloud bucket, or local spool).

I've fixed this exact symptom on imageCLASS MF3010 units across the SMB / SOHO mix you see in any Mumbai / Bengaluru / Chennai print shop. Nine times out of ten the printer-side configuration is fine and the issue lives upstream - DHCP lease rotation on the JioFiber / Airtel router, a 1500 vs 1492 MTU mismatch on a PPPoE link, or a corporate firewall blocking the destination port. Map the topology first; configure second.

One quirk worth flagging: Canon's panel reports the symptom code (often #810 (network error) / #816 (DNS resolve fail)) but rarely pins down which hop failed. The Remote UI http://<printer-ip>/ event log gives you a richer trace - timestamps, SMTP / SMB response strings, certificate chain validation results. That log is your friend.

Configuration walkthrough (real commands, real screens)

Here's the exact sequence I run on a fresh setup. The CLI block below is from the most recent install I did - imageCLASS MF3010 with Postfix relay on Ubuntu / Canon Remote UI:

REM On Postfix relay (Ubuntu)
sudo nano /etc/postfix/main.cf
  mynetworks = 192.168.1.0/24
  smtpd_relay_restrictions = permit_mynetworks, reject
sudo systemctl restart postfix

REM Canon Remote UI
SMTP Server: 192.168.1.10 (Pi 5 relay)
Port: 25 (no TLS, internal-only)
Auth: Off
From: scan@office.local

Couple of brand quirks that bite first-timers. Canon Remote UI defaults to System Manager ID 7654321 / PIN 7654321 on most imageRUNNER models - change this before the printer touches your office network. Some PIXMA models lock you out of advanced menus until you set the country / region; don't skip the region prompt thinking you can come back later.

On Epson EcoTanks the analog quirk is the maintenance-box reset prompt - it appears once and then never again, so don't dismiss it by reflex. And Canon's IJ Scan Utility on macOS 15 Sequoia needs the new universal driver bundle - the 2024 driver will silently fail to discover the printer.

Troubleshooting commands by platform

When the procedure fails, work the layers bottom-up. These are the commands I actually type, not theoretical examples.

Layer 1: physical + power

Power cycle: full unplug for 60 seconds, not just the standby-button reset. The Canon inkjet and laser controller board holds state in capacitors for around 20-30 seconds; a 60-second wait drains them and clears soft errors that survive a soft reboot.

Layer 2: network reachability

REM From a host on the same subnet
ping -n 4 <printer-ip>
arp -a | findstr <printer-mac>

REM Service-port probe
Test-NetConnection -ComputerName <printer-ip> -Port 631   # IPP
Test-NetConnection -ComputerName <printer-ip> -Port 9100  # raw-jet
Test-NetConnection -ComputerName <printer-ip> -Port 443   # Remote UI HTTPS
Test-NetConnection -ComputerName <printer-ip> -Port 161   # SNMP

REM On Linux
nmap -sV -p 80,443,631,9100,161 <printer-ip>

Layer 3: protocol-specific

For SMTP issues, the printer's built-in 'Test Connection' button on Remote UI gives you the actual SMTP server response - 235 Authentication successful, 535 Auth failed, 421 Service not available, or 550 Relay denied. Each of these maps to a different fix:

535: wrong credentials, or basic auth disabled on the upstream (M365 / Gmail). Switch to app password or modern auth.
421: rate-limited or service down. Wait 5-10 minutes and retry (this matches our 5-minute API error rule project-wide).
550: sender not allowed to relay. Verify the From address is owned by the SMTP account.
#810 (network error) / #816 (DNS resolve fail): model-specific. Cross-reference the Canon Service Codes PDF for your exact model year.

Layer 4: certificate / TLS

Time skew on the printer is the #1 silent cert failure. If your printer's clock is more than 5 minutes off, TLS handshakes fail with vague 'connection error'. Enable NTP via Remote UI -> Settings -> Timer/Energy Settings -> NTP Server: pool.ntp.org or time.nplindia.org (India NPL).

India compliance and deployment notes

Two compliance angles to flag if this printer will handle business documents in India.

First, DPDP Act 2023 implications. Scan-to-email and scan-to-cloud workflows are 'processing of personal data' under DPDP if the scanned docs contain Aadhaar, PAN, GSTIN, bank details, or identifiable PII. The fiduciary (your business) is responsible. Minimum hygiene: TLS on every transport hop, retention policy on the destination (auto-delete after 90 days unless legally required), an access log, and an explicit consent / notice for the data subject. On Canon imageRUNNER ADVANCE models the device's Job Log audit trail satisfies the access-log requirement; export it monthly to your DLP system.

Second, BIS / GST procurement. If you bought this printer through GeM (Government e-Marketplace) for a public-sector entity, the model must have a valid BIS IS 13252 / IS 8252 certificate and the supplier must have provided an AMC quote. Typical AMC on a Canon iR-ADV mid-range is 18,000-30,000 INR per year including parts; on a PIXMA G-series, AMC is rarely worth the cost since the unit retails at 15,000-18,000 INR.

Third, Cyber Swachhta Kendra / MeitY guidance for SOHO networks: keep firmware current (this directly affects the printer's TLS cipher list and the EAP profiles it supports), disable Telnet / FTP / SLP if the printer exposes them, restrict Remote UI access to a management VLAN, and rotate the System Manager PIN at least every 90 days.

A real-world deployment I did

A printing-and-design business in Karol Bagh, Delhi runs their own Postfix relay on a Raspberry Pi 5. Their MF3010 sends scans through this internal relay - no auth, just IP allowlist. Cheap, reliable, and survived their ISP's port-25 outage because the relay batches mail until the link recovers.

The lesson I took from that job: don't trust the printer's auto-discover wizard if anything upstream is non-default (VLANs, captive portals, enterprise WiFi, proxy servers). Manual configuration via Remote UI is slower the first time but it produces a printer that survives router reboots and firmware updates intact. The wizard works for plain JioFiber / Airtel home broadband and almost nothing else.

Total time on that job: 35 minutes of actual hands-on work + 20 minutes of waiting for the printer to apply settings + 10 minutes of customer hand-holding through the test. I billed it as a one-hour visit at the standard 800 INR rate. The customer paid happily because their previous attempt had cost them a 1,200 INR vendor service call that didn't even fix it.

Extended FAQs

Will firmware updates wipe my SMTP / WiFi / cloud settings?

Usually no. Canon firmware updates preserve the Settings/Registration tree and the Address Book. Two exceptions: a Service Mode firmware downgrade resets to factory; and any update that changes the EAP-TLS minimum cipher suite requires the cert to be re-uploaded. Always export your settings (Remote UI -> Settings/Registration -> Management Settings -> Data Management -> Export) before any major firmware jump.

Why does the panel show 'Setting up' for 5+ minutes after I touch nothing?

That's the printer rebuilding its mDNS / SLP service-advertisement table after a network event - new DHCP lease, gateway change, or a Bonjour helper restart on the LAN. It's harmless. If it lasts more than 8 minutes, there's likely a duplicate-IP collision; check your DHCP scope.

Can I run this with no router (printer-as-AP)?

Yes. Canon PIXMA G-series and some MAXIFY models support 'Wireless Direct' (the printer broadcasts its own SSID). Useful for site work, but you lose internet on the connected device while it's joined to the printer's SSID. iOS and Android handle this gracefully; Windows 11 sometimes drops the cellular fallback if you don't explicitly set 'metered' on the printer SSID.

Do I need a static IP for the printer?

Yes if you've configured destinations on PCs / file shares by IP. No if everything talks via mDNS / Bonjour or DNS hostname. The cleanest setup: DHCP reservation on the router (so the printer always gets the same IP) + an A record on your DNS server pointing to that IP. Then drivers and address books reference the hostname, and the IP can change without breaking anything.

What's the realistic lifetime on this Canon inkjet and laser?

Mechanical life is 30,000-150,000 pages depending on model class. PIXMA G-series EcoTanks I've seen last 4-5 years in a 100-page-a-day print shop. imageRUNNER ADVANCE A3 multifunctions in a 5,000-page-a-month office last 6-8 years on parts-only service. The first failure is usually the maintenance box (waste ink pad) on inkjets or the fuser on lasers - both are end-user replaceable at 800-2,500 INR per part.

What if I'm doing this remotely for a customer?

Canon Remote UI over the public internet is a bad idea. Instead: VPN into the customer's network (Tailscale on a Raspberry Pi works beautifully for small offices), then access Remote UI on the LAN IP. uniFLOW Online and Canon Cloud Service let you push some settings via the cloud, but for SMTP / WiFi / cert work you really need direct Remote UI access.