An SMTP2GO alternative for scanners and copiers on Microsoft 365

At a glance

Sources: SMTP2GO, Pricing (read October 31, 2026); SMTP2GO, Verified Senders: Sender Domain vs Single Sender Emails (read October 31, 2026); SMTP2GO, Quick Start Guide (read October 31, 2026); SMTP2GO, Scan to Email: How to Set It Up and How to Fix It When It Breaks (read October 31, 2026); Microsoft Learn, How to set up a multifunction device or application to send email using Microsoft 365 or Office 365 (read October 31, 2026)

Where the mail goes out from

SMTP2GO

Your copier signs in to mail.smtp2go.com with an SMTP user you create in your SMTP2GO account (its scan-to-email guide suggests you “add a user just for this device”), and SMTP2GO delivers the message from its own servers. In SMTP2GO's words: “You’re using SMTP2GO’s infrastructure, not Microsoft’s SMTP servers.” The From address has to be one you've verified with it: “To be allowed to send through your account, you must send from a verified sender.”

CopierBridge

Your copier signs in to smtp.copierbridge.com with the username and password CopierBridge created for it, on port 587 with STARTTLS or 465 with TLS. CopierBridge then hands the message to Microsoft 365 as the mailbox you connected: through Microsoft's own SMTP service, signed in with OAuth and permission to send only, or, if you turn it on, through Microsoft Graph for messages up to 3 MB. Microsoft 365 sends it from that mailbox. Microsoft, on client SMTP submission, the first of those routes: “The email address of the mailbox appears as the message sender.” We pass each message to Microsoft and don't keep it.

Sources: SMTP2GO, Scan to Email: How to Set It Up and How to Fix It When It Breaks (read October 31, 2026); SMTP2GO, Microsoft 365 SMTP AUTH Basic Auth Ending: Timeline & Alternatives (read October 31, 2026); SMTP2GO, Verified Senders: Sender Domain vs Single Sender Emails (read October 31, 2026); Microsoft Learn, How to set up a multifunction device or application to send email using Microsoft 365 or Office 365 (read October 31, 2026)

DNS records

SMTP2GO. To send from your domain, you verify it in SMTP2GO, which gives you “three CNAME records to add to the domain's DNS settings. The three records are for SPF, DKIM and tracking (opens, clicks & unsubscribes).” Your existing SPF record stays as it is: “You do not need to update your domain's existing SPF record.” You can verify a single address by email instead, but then, SMTP2GO notes, “the domain will not align with SPF and DKIM”, and that option isn't available for a domain that has DMARC set up.

CopierBridge. None. Each message goes out from Microsoft 365 as your mailbox, so the records you already have for Microsoft 365 cover it. Microsoft, on custom domains: “The Microsoft 365 enrollment process already required you to create or modify the SPF TXT record in DNS for your custom domain to identify Microsoft 365 as an authorized mail source.” DKIM works the same way as for the rest of that mailbox's mail: Microsoft 365 signs outbound mail from your domain once DKIM is set up for it in Microsoft 365 (before that, Microsoft notes, “Currently, no DKIM signing occurs for outbound mail from custom domains”).

Sources: SMTP2GO, Verified Senders: Sender Domain vs Single Sender Emails (read October 31, 2026); Microsoft Learn, Set up SPF to identify valid email sources for your Microsoft 365 domain (read October 31, 2026); Microsoft Learn, How to use DKIM for email in your custom domain (read October 31, 2026)

A copy in Sent Items

Every message CopierBridge relays is also saved in the Sent Items folder of the mailbox you connected. Microsoft documents that for both ways CopierBridge hands mail to Microsoft 365. Its comparison of the options for devices marks “Saves to Sent Items folder” Yes for client SMTP submission, the route CopierBridge uses first (and No for a connector relay, Direct Send and High Volume Email). And for Graph's sendMail, the opt-in route: “This method saves the message in the Sent Items folder.” Large scans add up there, so keep an eye on that mailbox's size.

Sources: Microsoft Learn, How to set up a multifunction device or application to send email using Microsoft 365 or Office 365 (read October 31, 2026); Microsoft Graph, user: sendMail (read October 31, 2026)

Price and limits

SMTP2GO has a free plan for 1,000 emails a month, up to 200 a day. Starter is $15 a month for 10,000 emails, and Professional is $75 a month for 100,000 emails with a dedicated IP address. Its pricing page's volume slider goes past 3 million emails a month, and volumes above 3 million are custom. “Get 2 months free by paying yearly.” Free accounts are also limited to 25 emails an hour until the sender domain is verified.

CopierBridge is $9 a device a month, and your first device is free for 14 days. Each copier, scanner or app with its own login is a device. Because mail goes out through your mailbox, Microsoft's limits for it apply: for client SMTP submission, “10,000 recipients per day. 30 messages per minute.”

So for one copier that sends fewer than 200 emails a day and 1,000 a month, SMTP2GO's free plan costs nothing, while CopierBridge costs $9 a month for that device after the free trial.

Sources: SMTP2GO, Pricing (read October 31, 2026); SMTP2GO, Sending Limits: The Complete Reference (read October 31, 2026); Microsoft Learn, How to set up a multifunction device or application to send email using Microsoft 365 or Office 365 (read October 30, 2026)

When SMTP2GO is the better pick

• Your company isn't on Microsoft 365, or your devices send as a domain that isn't. SMTP2GO “works identically across brands and doesn’t depend on which email provider your office uses”. CopierBridge sends only through a Microsoft 365 mailbox.
• You send more than a mailbox allows. Microsoft's limits for client SMTP submission: “10,000 recipients per day. 30 messages per minute.” SMTP2GO's plans run past 3 million emails a month, with a default top speed of 200,000 emails an hour.
• You'd rather not send as a mailbox. On SMTP2GO a device gets its own SMTP user: “No license, no mailbox, nothing for a password rotation to break.”
• Old devices or strict firewalls. “SMTP2GO also accepts TLS or unencrypted connections on 25, 2525, 8025, and 80, and SSL on 465, 8465, and 443.” CopierBridge takes 587 with STARTTLS or 465 with TLS, and nothing unencrypted.
• You want delivery tracking. SMTP2GO's Activity page logs every email with its delivery events, and its tracking covers opens, clicks and unsubscribes.
• Low volume, no budget. The free plan covers 1,000 emails a month.

Sources: SMTP2GO, Scan to Email: How to Set It Up and How to Fix It When It Breaks (read October 31, 2026); SMTP2GO, Sending Limits: The Complete Reference (read October 31, 2026); SMTP2GO, Quick Start Guide (read October 31, 2026); Microsoft Learn, How to set up a multifunction device or application to send email using Microsoft 365 or Office 365 (read October 30, 2026)

When CopierBridge fits

• Your devices already send as a Microsoft 365 mailbox and you want to keep it that way: nothing to add in DNS, mail goes out from Microsoft 365 as that mailbox, and a copy lands in its Sent Items folder.
• You want Microsoft's own sign-in between the relay and your mailbox. CopierBridge signs in with OAuth and, by default, asks only for permission to send (SMTP.Send) as the one mailbox you connect. That permission can't read, list or delete mail.
• Your copiers can only sign in with a username and password. They keep doing that, each with its own login that you can change or remove without touching the mailbox's password.

Moving a copier from SMTP2GO

1. Connect the mailbox. Sign in with your Microsoft 365 work account and connect the mailbox your devices will send as. The mailbox owner approves sending only, on Microsoft's own page. If your organization needs an admin to approve apps, the admin does it once on the admin approval page.
2. Turn on Authenticated SMTP for that mailbox (how). If it can't be turned on, allow the Graph route in your dashboard instead, for messages up to 3 MB.
3. Add the device in your dashboard and copy the username and password we create for it.
4. Change four settings on the copier: the server from mail.smtp2go.com to smtp.copierbridge.com, port 587 with STARTTLS (or 465 with SSL/TLS), and the new username and password. The From address becomes the mailbox you connected.
5. Send a test scan and check it arrives.

Common questions