Where an SMTP relay earns its keep
Cloud mail providers demand modern authentication. Half the hardware and software in a real office can't provide it. That gap is exactly where SMTP Hopper lives.
Scan-to-email from printers & MFPs
The classic. Copiers and multifunction printers rarely support modern Auth or modern TLS, and Microsoft 365 keeps deprecating what they do support. Point them at SMTP Hopper on port 587 — with per-device credentials or an IP whitelist entry — and scan-to-email just works again, on every model, from every vendor.
Legacy line-of-business apps
That ERP from 2009, the warehouse system, the practice-management software — they all send invoices, statements, and notifications over plain SMTP with basic auth (or none at all). SMTP Hopper accepts their mail locally and handles the modern TLS handshake with your provider, so nothing has to be rewritten.
Server, NAS & device alerting
UPS units, NAS boxes, backup jobs, hypervisors, camera NVRs, RAID controllers — infrastructure that emails you when something breaks. Give them one reliable local relay target, and have them use their own credentials without having to share acrosss device types (if you want that).
One egress point for compliance
Instead of dozens of devices each holding provider credentials and making their own outbound connections, consolidate all mail through one audited chokepoint. One place to control credentials, one place to watch the Refused Connections log, one IP to authorize with Microsoft 365.
Windows & compatible
Not everyone has linux experts on hand, so to make life easier this product is built for Windows. A familiar OS with straightforward services. Almost easy enough that anyone could manage it.
Isolated & locked-down networks
Manufacturing floors, labs, and secure facilities often allow only a single, tightly controlled path out. SMTP Hopper runs fully self-contained — no cloud dependencies, no nonsense.
A day in the life: the Friday invoice run
Why durable queueing matters more than raw speed.
4:55 PM — the batch starts
Your ERP fires 800 invoices at SMTP Hopper. Each one is written to disk the moment it's accepted — the ERP finishes its run and goes quiet for the weekend.
5:02 PM — the provider blips
Your upstream provider has a brief outage mid-batch. No errors reach the ERP, nothing is lost: undelivered messages simply wait in the queue while exponential backoff paces the retries.
5:20 PM — everything delivered
The provider recovers, the queue drains, and Monday's Analytics page shows the full picture: 800 accepted, 800 delivered, zero dead letters. Nobody got paged.
Is SMTP Hopper right for you?
✓ A great fit if you have…
- Printers, scanners, or MFPs that need scan-to-email through Microsoft 365 or another modern provider
- Legacy applications that only speak basic SMTP
- Infrastructure devices that send email alerts
- A Windows server (or VM) to host the relay
- A need to realiability prove internal mail is flowing
- Multiple sites or clients that have rotating IPs
→ Look elsewhere if you need…
- Bulk marketing email sending — that's a job for your provider directly, not a relay
- An inbound mail server (MX host) — SMTP Hopper relays outbound only
- Content filtering or DLP scanning of outbound mail
- A Linux-native package (SMTP Hopper is built for Windows)
Honest scoping up front saves everyone time — ask us if you're unsure.
Recognize your environment above?
Tell us about your devices and provider, and we'll show you exactly how SMTP Hopper would slot in.
Request a Demo