Cold email and the rest of your mail should not share a domain. Inbox providers judge a domain by what arrives from it, and cold outreach, however careful, collects more rejections, spam complaints and unanswered mail than a newsletter people asked for or the replies your team sends every day. Keeping those histories apart keeps a bad week of outreach away from the mail you depend on.
Why the domain carries the history
Reputation attaches to the sending domain, not only to the mailbox. Every bounce, complaint and ignored message from sales@acme.com is counted against acme.com, and the newsletter you send from news@acme.com is read against the same record. Providers also watch how much a domain sends and how suddenly that changes; a cold campaign starting up looks nothing like a weekly newsletter.
Providers put up with cold email while the signals stay clean. When they stop being clean, the fix is to slow down, re-check the list and let the reputation recover. That is a workable fix for a domain that only sends cold email. It is a painful one for a domain that also sends invoices, newsletters and your team's own mail.
What happens if you send cold from the newsletter domain
- Your newsletter and your team's everyday mail start landing in spam alongside the outreach, and the audience that opted in is the first to notice.
- A block from one provider can apply to the whole domain, and nobody at the company may be able to reach that provider's users until it lifts.
- There is no clean way back. You cannot separate the two histories after the fact; the only remedy is to stop sending cold mail from that domain and wait.
- Your SPF record may break. SPF allows ten DNS lookups. A record that already lists a newsletter tool and a helpdesk may be near that limit, and putting cold mailboxes on yet another provider adds its include on top.
None of this is certain to happen on day one. It is a risk you take with every send, with the thing you can least afford to lose.
Choose a second domain or a subdomain
You have two options.
A second domain such as acme-outreach.com, tryacme.com or acmehq.com is the safer one. Providers treat it as fully separate from your main domain, and if it is ever damaged you register another. Pick something a recipient will recognise as yours and make it redirect to your main site, so a curious prospect who types it in lands somewhere real. Avoid anything that could be mistaken for another company.
A subdomain such as mail.acme.com or go.acme.com is quicker because you already own the domain. Providers treat a subdomain partly on its own and partly as a member of its parent, so it is a better separation than none and a weaker one than a second domain. If you choose this route, keep the newsletter on its own subdomain too, so nothing sends from the bare domain except your team.
Whichever you choose, add it to Google Workspace or Microsoft 365 as a domain and create the sending mailboxes there. Two or three mailboxes per domain, each sending a modest number of emails a day, keeps the volume per address low; see Sending limits and daily caps.
Authenticate it before the first send
A new domain has no history at all, so authentication is the first thing a receiving server checks. Publish SPF, DKIM and DMARC for the new domain before you connect a mailbox; the steps and example records are in Set up SPF, DKIM, and DMARC for your domain. Warmup waits until all three records resolve, so a domain without them does not get started. The free domain checker confirms them from outside the app.
Give warmup the time it needs
A fresh domain is the definition of a mailbox with no sending history. Connect the mailboxes, leave warmup on and do not add them to a campaign until each one reads ACTIVE. The ramp, and what decides when a mailbox graduates, are in What is domain warmup and how long does it take?. Plan in weeks rather than days, and register the domain as early as you can: a domain that has existed for a while is treated with a little less suspicion than one created last week.
Moving from a newsletter tool
If you are importing from MailerLite, keep the newsletter where it is, on the domain it is on. Fuzegenai is the cold layer next to it, not a replacement for it. The import brings across groups and subscribers so you can follow up with the people who never replied, and nothing in it touches your newsletter domain. The MailerLite Migration card, under Integrations → Migrations, asks for your newsletter domain and warns you if any connected mailbox sends from it. See Move from Instantly, Smartlead or MailerLite.
Checklist
- Register a second domain, or create a subdomain, for cold email only.
- Add it to your email provider and create two or three mailboxes on it.
- Publish SPF, DKIM and DMARC and confirm them from the DNS column on Email Accounts.
- Connect the mailboxes and let warmup run until each reads
ACTIVE. - Keep the newsletter, invoices and your team's mail on the domain they are on.
If a mailbox on your main domain is already connected, archive it before a campaign picks it up: on Email Accounts, open the mailbox's Edit dialog and set Status to Archived. If you are unsure which domain a mailbox is on, write to priority@fuzegenai.com with the address. More on what to do when mail is already going to spam is in Emails are landing in spam.