Migrating from Forward Email to FolioInbox: Deliverability, DKIM, and Domain Cuts

Price Arithmetic: Forward Email vs FolioInbox for Multiple Domains

Cost calculations look very different when evaluated by single operators who run three, five, or ten domains compared to enterprise procurement teams. Most corporate platforms charge per user per month. If you manage five distinct domains on Google Workspace, standard configurations push you toward five separate user licenses at a measurable budget or more per month, quickly totaling a measurable budget monthly just to maintain five separate corporate addresses. Some operators use alias hacks inside a single Workspace user, but sending identity and signature isolation quickly collapse under that approach.

Forward Email offers an open-source forwarding base with paid tiers for enhanced forwarding and outbound SMTP relay features. However, once you add outbound SMTP configuration, custom storage, and multi-domain setups, the administrative overhead rises while outbound DKIM signing remains dependent on external SMTP credentials. In contrast, FolioInbox pricing plans are structured on a flat per-tier basis designed specifically for solo operators, with no per-seat billing and unmetered storage included on every tier.

When comparing forward email vs folioinbox , the math is straightforward. If you operate three client brands or holding entities, Folio Solo costs a measurable budget per year total, covering up to 3 domains with 1,000 direct sends per month. If you are an operator with six to ten Shopify stores or consulting projects, the Studio plan runs a measurable budget per month billed annually (a measurable budget per year) for 10 domains and 6,000 sends per month. For broad portfolios, the Holding Co. plan at a measurable budget per month billed annually (a measurable budget per year) offers unlimited domains and 30,000 monthly sends.

Folio is a proprietary, hosted service; its source code is not public. Unlike open-source scripts requiring server maintenance, it operates on managed infrastructure. Operators who want an exact financial comparison can review our detailed breakdown for multi-LLC owners to evaluate domain consolidation costs without recurring seat penalties.

Pre-Migration Audit: Exporting Rules, Aliases, and Verifying MX Records

A smooth domain transition requires methodical preparation. If you swap MX records without an inventory of active aliases, legitimate inbound mail can bounce immediately. Complete these four audit steps before altering your DNS settings.

1. Inventory Existing Aliases and Catch-Alls

Log in to your Forward Email dashboard and export or transcribe every configured alias for each domain you plan to cut over. Common addresses include:

• contact@domain.com and hello@domain.com for general inquiries.
• billing@domain.com or invoices@domain.com for payment gateways and accounting.
• System-level aliases like admin@, support@, or developer notifications.

Determine whether you rely on a catch-all alias. If you actively receive critical messages across arbitrary prefixes, you will need to map these inside your direct mailbox dashboard immediately upon connection.

2. Audit Outbound Volume Against Send Caps

Direct mailboxes maintain strict sending thresholds to safeguard IP reputation. Evaluate your current monthly volume across all domains:

• Solo Plan: 1,000 sends per month (ideal for low-volume consultants and legal holding entities).
• Studio Plan: 6,000 sends per month (suitable for multiple active service businesses).
• Holding Co. Plan: 30,000 sends per month (designed for active portfolio operators).

These caps apply to transactional and day-to-day conversational business emails. If you run bulk promotional newsletters containing tens of thousands of marketing recipients, those should remain on dedicated newsletter platforms like Mailchimp or Klaviyo. Direct business mailboxes should be reserved for human-to-human correspondence, client billing, and operational notices.

3. Check Message Size and Attachment Constraints

FolioInbox enforces a message attachment limit of 15 MiB per email. Forwarding proxies sometimes attempt to stream larger payloads, though destination providers like Gmail cap total message size at 25 MiB. If your regular workflow involves sending uncompressed 50 MiB design files or massive video assets via email attachments, transition those workflows to cloud storage links prior to cutover.

4. Check Current Domain Health

Before modifying DNS records, establish a baseline of your existing DNS authentication health. Review your current SPF strings, any legacy DKIM TXT records from older SMTP providers, and your current DMARC enforcement level. Identifying syntax errors or abandoned TXT records now prevents unexpected authentication failures during cutover.

Step-by-Step DNS Cutover: Moving Domains Safely Without Dropped Inbound

The cutover process involves updating your domain registrar or DNS host records. Following a disciplined sequence ensures that incoming mail does not bounce while DNS changes propagate across global resolvers.

1. Lower DNS TTL Values (T-Minus 24 Hours):

   Locate your current MX and TXT records at your DNS host (e.g., Cloudflare, Namecheap, GoDaddy). Change their Time to Live (TTL) value from 86400 (24 hours) or Automatic down to 300 seconds (5 minutes). This ensures that when you swap the routing records tomorrow, recursive resolvers worldwide dump their cache and query the new records within minutes.

2. Authenticate with FolioInbox:

   Sign in to your account. FolioInbox uses modern, credential-free authentication: sign-in is handled via magic link or secure WebAuthn passkey; there is no account password to maintain or leak.

3. Initiate Domain Connection:

   Domain setup in FolioInbox is handled on a single screen. For registrars that support the Domain Connect protocol, DNS records can be published automatically with a single authorization click. If you manage DNS manually via Cloudflare or an unsupported registrar, FolioInbox provides explicit records to paste.

4. Remove Forward Email MX Records:

   Delete the existing Forward Email MX records:

   mx1.forwardemail.net (Priority 10)
   mx2.forwardemail.net (Priority 10)

   Simultaneously remove any Forward Email verification TXT records (e.g., forward-email-site-verification=...).

5. Publish Direct Mailbox MX Records:

   Enter the authoritative FolioInbox MX records provided in your dashboard. Set primary and secondary priorities as indicated on the connection screen.

6. Deploy Dedicated 2048-bit DKIM Keys: In your DNS management console, create the dedicated CNAME or TXT record for your DKIM selector. FolioInbox generates an isolated 2048-bit cryptographic key pair for every single domain. rarely share DKIM selectors between distinct corporate entities.
7. Update Your SPF TXT Record: Update your domain's root SPF record. If your domain previously only sent mail through Forward Email's proxy, replace that include mechanism with the Folio direct sending host. If you also dispatch invoices through an external tool like Xero or Stripe, merge the records cleanly using proper SPF syntax: v=spf1 include:_spf.folioinbox.com ~all rarely publish more than one SPF TXT record on a single root domain, as multiple SPF strings instantly invalidate SPF validation under RFC 7208.
8. Publish or Verify DMARC Policy:

   Ensure a TXT record exists at _dmarc.yourdomain.com. For initial cutover, monitor your deliverability using a relaxed policy:

   v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com;

   Once your DKIM keys pass validation and outbound traffic aligns cleanly, you can escalate this policy to p=quarantine or p=reject to prevent domain spoofing.

9. Restore Default TTLs:

   After testing confirms that inbound and outbound messages route properly, return your DNS TTL values back to 3600 or 86400 seconds to reduce DNS query load.

Post-Migration Verification: Per-Domain Signatures and Outbound Deliverability

Once DNS records propagate, complete outbound deliverability and interface checks to ensure each identity behaves like an independent company.

Isolating Outbound Signatures and Identities

Inside FolioInbox, each connected domain functions with its own authenticated sender identity. Navigate to your domain settings and configure distinct email signatures for each brand:

• Entity A (Consulting LLC): Professional sign-off including company registration details, legal disclosures, and advisory credentials.
• Entity B (E-commerce Store): Clean customer service signature including support operating hours and help desk references.
• Entity C (Holding Entity): Minimalist corporate identity for investor and banking communications.

When composing an email, selecting the sending address automatically binds the corresponding outbound signature and instructs the mail engine to sign the outgoing envelope with that specific domain's DKIM private key.

Validating Cryptographic Headers

Send a test message from each migrated domain to external mailboxes on Gmail, Outlook, and iCloud. Inspect the full raw message headers of the received email:

• Authentication-Results: Verify that dkim=pass appears with your specific domain name in the header.d= tag.
• SPF Alignment: Confirm that spf=pass aligns with the sending envelope domain.
• DMARC Status: Ensure dmarc=pass confirms both SPF and DKIM alignment.
• No Sender Relaying Artefacts: Check that no on behalf of or external proxy routing notices appear in the user interface.

Security and Spam Filtering Architecture

When evaluating email providers, security mechanics matter. Folio encrypts mail in transit (TLS) and at rest, but is not end-to-end or zero-knowledge encrypted: mail is stored server-side and readable by Folio for spam filtering and search. This design choice is deliberate. Server-side search and content filtering allow the platform to catch phishing attacks, detect incoming malware, and provide immediate keyword search indexing across multiple domains without requiring local device decrypt keys.

For more architectural details on how direct authentication stops spoofing across corporate holdings, consult our resource on email authentication for holding companies of one.

What You Gain and What You Give Up When Migrating from Forward Email to FolioInbox

Switching email systems involves deliberate trade-offs. Here is a clear, unvarnished accounting of what changes when you move from Forward Email to FolioInbox.

What You Gain

• Direct Cryptographic Alignment: Outbound emails carry native 2048-bit DKIM signatures matching your exact domain, eliminating the delivery drops common to forwarding proxies and Gmail "Send as" configurations.
• Single Unified Inbox: Send and receive across up to three, ten, or unlimited domains without logging into multiple accounts or managing confusing client-side forwarding filters.
• Independent Brand Signatures: Every entity maintains its own outbound signature, preventing accidental cross-brand replies.
• Predictable Multi-Domain Pricing: Flat plan pricing covers multiple domains without paying incremental user fees for mailboxes used only by you.
• Streamlined Authentication: Fast, modern sign-in using passkeys or magic links without managing vulnerable account passwords.

What You Give Up

• No Free Tiers: Folio has no free plan. It offers a 14-day free trial and a no-credit-card preview, then flat paid plans (Solo, Studio, Holding Co.). If your budget is zero and you require free open-source forwarding for personal side projects, Forward Email's free tier remains the appropriate option.
• Attachment Size Ceilings: FolioInbox caps file attachments at 15 MiB per message. Operators handling oversized print files or raw video must use secure link sharing instead.
• Send Volume Limits: Direct sending mailboxes enforce caps (1,000, 6,000, or 30,000 messages per month depending on tier). If you send high-volume automated marketing blasts, you must keep those workflows on external transactional SMTP or newsletter providers.
• Single-Operator Boundary: Folio is a single-operator inbox, not a team or shared mailbox — there are no per-user seats and no team collaboration features. Folio is a fully hosted service and cannot be self-hosted or run on your own servers or infrastructure. If you plan to hire administrative staff who require separate accounts, assignable support tickets, or internal message tagging within the same mailbox, you will need a collaborative helpdesk platform instead.

To ensure content directly supports your implementation tasks without unnecessary friction, practical documentation should adhere to established clarity standards, such as Google guidance on creating helpful content. Clear DNS documentation helps operators complete technical cutovers accurately on the first attempt.

Frequently Asked Questions

Will migrating from Forward Email cause downtime for my existing business domains?

No, provided you lower your DNS TTL values to 300 seconds prior to cutover. When you replace Forward Email's MX records with FolioInbox's MX records, global DNS servers update quickly. During the short propagation window, sending servers will deliver to either Forward Email or FolioInbox without dropping incoming traffic. Inbound mail is rarely discarded during a standard MX record switch.

Can I keep receiving forwarded emails in my personal Gmail account?

While you technically could set up automated forwarding rules, doing so defeats the primary benefit of migrating. The goal of using a direct mailbox is to eliminate intermediate relay hops that break SPF and trigger downstream spam rejections. FolioInbox provides a dedicated web and mobile application (including an Android app on Google Play) to read and manage all your domains directly.

Does FolioInbox offer team accounts or shared inboxes for assistants?

Folio is a single-operator inbox, not a team or shared mailbox — there are no per-user seats and no team collaboration features. The product is built specifically for solo operators who own and run multiple brands independently. If your operational model requires delegating tickets among staff members, you should evaluate dedicated team helpdesks.

How does outbound DKIM signing differ between an email forwarding service and FolioInbox?

Email forwarding services generally do not store mail or provide a native webmail compose client; outbound mail is routed through third-party SMTP servers or via consumer Gmail interfaces, which often results in mismatched return paths and broken DKIM alignment. FolioInbox signs every outgoing email at the mail server level using a unique, dedicated 2048-bit DKIM private key tied directly to that domain's DNS selector.

Run your current domains through the free Deliverability Audit at /tools/domain-health to check your existing SPF and DKIM records before initiating your cutover.