Export Mailboxes to Icemail and Launch Campaigns in 30 Minutes

How long does it actually take to export mailboxes to Icemail?

Moving Google Workspace or Microsoft 365 mailboxes into Icemail, checking DNS, configuring authentication, and sending your first campaign takes about 30 minutes of active work, assuming your CSV, mailbox access, and DNS login are already in hand.

Here's what makes up that estimate: exporting and formatting the mailbox CSV from Google Workspace or Microsoft 365 takes about 5 to 10 minutes. Importing that CSV and connecting accounts via OAuth or SMTP/IMAP takes another 5 to 10 minutes. Verifying SPF, DKIM, and DMARC in Icemail's automated checker takes 5 to 10 minutes. Importing the prospect CSV and launching the first sequence takes a final 5 to 10 minutes. Altogether, that's roughly 20 to 30 minutes of total hands-on time.

One thing worth separating out clearly, the 30-minute figure is configuration time inside Icemail and your DNS dashboard. It doesn't include DNS propagation. New or edited SPF, DKIM, and DMARC records can take anywhere from a few minutes to 24 to 48 hours to fully propagate, depending on your DNS host and existing TTL settings. If you're working with a brand-new domain, build an extra day into your timeline before your first real send, even though the setup steps themselves only take half an hour.

If you already have mailboxes and a clean CSV on hand, the whole job breaks down into four parts: export, connect, verify, send.

A few failure points are worth watching before you start:

● A misconfigured Microsoft 365 login can trigger a 5.7.57 error

● More than one SPF record on a domain will hurt delivery, not help it

● New inboxes sent at full volume too early get filtered faster

● Dirty lead lists can push bounce rates above 2%, with 5%+ considered a danger zone

Step 1: Export your mailbox list from Google Workspace or Microsoft 365

Icemail only needs enough detail to match each sender: email address, display name, domain, and connection settings.

Export Google Workspace users to CSV In Google Admin Console, go to Directory > Users and export the user list as a CSV file.

Export Microsoft 365 mailboxes to CSV

In the Microsoft 365 admin center, go to Users > Active Users, then export users to CSV. That file includes User Principal Names (UPNs), which serve as the main email address for each mailbox. If you're still deciding which provider to standardize on before you export mailboxes to Icemail, our comparison of Google Workspacebreaks down the practical differences for outreach senders.

If you're managing a larger team, PowerShell is usually faster:

Get-Mailbox -ResultSize Unlimited | Select-Object UserPrincipalName | Export-Csv -Path "export.csv"

You'll also need to enable SMTP AUTH for each mailbox, under Users > Active Users > [select user] > Mail > Manage email apps. Turn on IMAP for SMTP/IMAP logins, and use a 16-character app password for any account with MFA enabled. Skip that step and Icemail will reject the login with a 5.7.57 error.

Format the CSV so Icemail can map it without issues

Once you've exported the raw data, reshape it to match Icemail's schema before uploading. The email_address field is the primary sending email, for example user@yourdomain.com. display_name is the sender name shown in the "From" field, such as Sarah Johnson. provider_type identifies the email service provider, either Google or Microsoft 365. domain is the sending domain itself, like yourdomain.com. smtp_host is the outgoing mail server address, typically smtp.office365.com or smtp.gmail.com, and smtp_port is the outgoing mail server port, usually 587. imap_host is the incoming mail server address, typically outlook.office365.com or imap.gmail.com, and imap_port is the incoming mail server port, usually 993. smtp_password_or_app_password holds the account password or app password, formatted like aaaa-bbbb-cccc-dddd, and reply_to is a separate reply-to address if one differs from the sending mailbox, for example replies@yourdomain.com. Save the file in UTF-8 encoding so accented characters and special characters don't get mangled. Before you upload it, remove extra commas inside cells, delete duplicate rows, and fix inconsistent date formats.

Step 2: Import mailboxes into Icemail and connect sending accounts

Start by importing the mailbox CSV, then connect each sending account.

Upload the CSV and map mailbox fields

Go to Icemail's mailbox provisioning section, upload the CSV, and map each row to the correct sending domain, display name, and workspace.

Double-check every mailbox before you confirm the import. This is the easiest point to catch a mismatched domain, sender name, or workspace. Icemail runs one workspace per domain, which keeps mailboxes isolated by domain, so a flagged account on one domain doesn't spill over into the others.

Connect inboxes with OAuth or SMTP/IMAP For Google Workspace or Microsoft 365, use OAuth and connect accounts from the admin panel with 2FA enabled on the domain. If you need direct server control instead, use SMTP/IMAP and enter the host, port, and app password for each mailbox. Icemail checks the login during setup, so a bad credential shows up immediately instead of after your first send.

Step 3: Verify SPF, DKIM, and DMARC before you launch

Icemail automates DNS checks for connected mailboxes, but it's worth understanding what's actually being verified before you send a single email.

Confirm SPF, DKIM, and DMARC records

At minimum, you need:

● One SPF record per domain. If a domain already has one, edit that record instead of publishing a second SPF entry.

● A valid DKIM selector, copied exactly as shown during setup.

● DMARC set to p=none during validation. Choosing the wrong policy here is one of the more common ways senders accidentally block their own mail.

This layered approach isn't Icemail-specific guidance. It mirrors the federal recommendations in NIST Special Publication 800-177, Trustworthy Email, which sets out SPF, DKIM, and DMARC as the standard mechanisms for authenticating a sending domain. A small mistake here, like an extra SPF record or a mistyped DKIM value, tends to snowball into delivery problems fast.

Run a deliverability check before you import your list Verify your prospect list with a tool like ZeroBounce or MillionVerifier before importing it. It's a small step that saves you from hard bounces, spam complaints, and wasted sends.

Use these thresholds as your launch checklist: keep your bounce rate under 2%, treating anything above 5% as high risk. Keep spam complaints under 0.1%, and treat anything above 0.2% as critical. Aim for an inbox placement rate above 80%, and investigate if it drops below 90%. Cap your daily sending limit at 30 to 50 emails per inbox per day, since exceeding that range puts the mailbox at risk of suspension.

If an inbox is new, ramp it gradually: start at 5 emails per day, add 5 more per day over about three weeks, until you're near the 50-email cap. That gradual increase makes the inbox look like normal human activity instead of a switch flipped from zero to full volume overnight.

Set sending windows and mailbox limits Inside Icemail's campaign settings, set a daily cap per inbox and lock sending to U.S. business hours for U.S.-focused outreach. Keep 3 to 4 mailboxes per domain and don't exceed 5. If you're planning to scale past a handful of domains, scaling cold email with multiple mailboxes covers how to grow sending volume without tripping the same filters that catch newer senders.

Step 4: Import prospects and launch your first Icemail campaign

With mailboxes connected and limits in place, the last step is straightforward: bring in your prospect list and turn on your first sequence.

Upload your prospect CSV and map contact fields Your prospect CSV needs an email column plus any fields you want for personalization. Clean the file, keep formatting consistent, and make sure column headers are unambiguous before you upload. Use Icemail's field mapper to match each header to the right contact property, and check the mapping carefully. A single mismatched column can pull the wrong name or company into a live send, which is an easy mistake to make and an annoying one to fix mid-campaign.

Build a short first sequence and launch safely

Keep the first sequence short, choose your connected mailboxes as the sending pool, turn on reply, bounce, and unsubscribe handling, and launch with a small batch before scaling up.

Frequently asked questions

What is the recommended daily sending limit for new mailboxes in Icemail? Start new mailboxes at 5 emails per day, then increase by 5 emails per day over about 3 weeks, working up to a final target of 30 to 50 emails per inbox per day. Don't exceed that range.

How many mailboxes per domain should I use when I export mailboxes to Icemail? Use 3 to 4 mailboxes per domain and stay under 5. Icemail runs one workspace per domain, so a flagged account stays isolated instead of affecting the rest of your infrastructure.

What causes the 5.7.57 error when connecting Microsoft 365 mailboxes to Icemail? That error appears when SMTP AUTH isn't enabled for the mailbox, or when a 16-character app password isn't used for an account with MFA on. Enable IMAP for SMTP/IMAP logins under Users > Active Users > Mail > Manage email apps in the Microsoft 365 admin center.

What bounce rate is considered dangerous when running cold email campaigns? Above 2% is high risk, and 5% or higher is a danger zone that can lead to real delivery problems. Verify your lead list with a service like ZeroBounce or MillionVerifier before you import it.

Should I use OAuth or SMTP/IMAP to connect mailboxes to Icemail? Use OAuth for Google Workspace or Microsoft 365, with 2FA enabled on the domain. Use SMTP/IMAP only if you need direct server control, entering the host, port, and app password for each mailbox.

Why does a domain need exactly one SPF record? More than one SPF record on a domain breaks authentication and hurts delivery instead of improving it. If a domain already has an SPF record, edit that one rather than publishing a second.

Does the 30-minute setup time include DNS propagation? No. The 30-minute estimate covers hands-on configuration inside Icemail and your DNS provider's dashboard. Propagation for SPF, DKIM, and DMARC changes runs separately and can take anywhere from a few minutes up to 24 to 48 hours.

What CSV fields are required to import mailboxes into Icemail? You need email_address, display_name, provider_type, domain, smtp_host, smtp_port, imap_host, imap_port, and smtp_password_or_app_password. Save the file in UTF-8 encoding to preserve accented characters in names.