First-device rollout
Move one sender. Prove the path. Then repeat.
Keep the first change reversible. Prepare Windows and Microsoft 365 first; repoint one sender only after both sides are proven.
Preflight
Before installation
Gather the host, credentials and network details. Then configure one sender at a time.
- Windowssupported x64 host on the private network
- LicenseA Polar license key before accepting mail
- Microsoft 365normal user mailbox for relay
- Scope verificationa second mailbox that must be denied
- AdministrationWindows + appropriate Microsoft 365 admin access
- Networkexplicit private IPv4 address for the listener
Not sure about your Windows version? Ask us to check your setup →
Runbook
Install, verify, then change one sender.
Each step ends with something you can verify. If you cannot verify it, stop there.
- 01
Install the signed x64 MSI.
Get the current installer from SMTPReady Downloads.
msiexec /i .\smtpready-<version>-win-x64.msi /l*v .\smtpready-install.logThis is a Windows service, not a desktop application. Open a new elevated PowerShell window after installation so PATH includes the command. The installer creates the service, the protected ProgramData directory, SMTP firewall rules, and the local admin endpoint.
ProofService installedNo sender changed yet. - 02
Activate your license.
Get the key from your purchase receipt or the Polar customer portal. Paste it at the hidden-input prompt; automation may use deliberate bounded standard input.
smtpready license activate smtpready license statusPaste the key at the hidden-input prompt, not in shell history. Licensing controls new mail admission. Need a license?
ProofLicense activeNo sender changed yet. - 03
Bind only the private address you intend.
smtpready setup --listen-address 10.0.0.12SMTPReady never chooses
0.0.0.0automatically.ProofListener + host certsStill no sender changed. - 04
Provision Microsoft 365 and prove scope.
smtpready setup microsoft365Use the relay mailbox and a distinct mailbox that must be denied. Authorization can take time to propagate; passive
smtpready doctordoes not contact Microsoft. If you explicitly runsmtpready doctor --live, it contacts Microsoft and may send labelled diagnostic mail; this is optional and only checks the current provider state. Rerun setup to activate readiness.ProofRelay allowed · unrelated deniedDo not recreate the app while propagation is pending. - 05
Add exactly one sender.
smtpready device addBefore pointing it to SMTPReady, account for recipient presentation: accepted envelope recipients are sent with hidden Bcc presentation; original visible To/Cc headers are not preserved, which can change what recipients see when replying or using reply-all. Keep the previous SMTP target recorded so rollback is immediate.
ChangeOne device onlyRollback: restore its previous SMTP target. - 06
Prove a real message from the first sender.
smtpready status smtpready doctor smtpready queue list --limit 20Send a labelled test message from the actual sender, not just the Windows host. Confirm SMTP accepted it, record the
250 2.0.0 queued asUUID if the sender exposes the reply, and inspect queue status orsmtpready logs --since 30m. Establish Microsoft submission and, when needed, recipient delivery through Exchange Online message trace.smtpready test microsoft365 --to recipient@example.comis an optional direct-Graph diagnostic: it bypasses SMTP intake and the durable queue, and Microsoft HTTP 202 does not prove recipient delivery. Do not add senders while any required proof is missing.ExitOne real SMTP path verifiedThen repeat for the next sender.
Rollback
Return the sender to its previous SMTP target.
If the first sender fails, point it back to the previous SMTP target. Accepted messages already queued in SMTPReady remain visible to the operator; do not delete spool files manually.
Troubleshoot with smtpready doctor →