How to create multiple mailboxes on a single domain and what each method supports

RassamNov 16, 2026基础设施
How to create multiple mailboxes on a single domain and what each method supports

This article describes four methods that organizations use to create multiple mailboxes on a single domain. Each method supports a different set of capabilities, and two of the four methods cannot send outbound email at all. The article also describes the conditions under which a large number of mailboxes on one domain is appropriate for outbound sending.

Before you begin

The following terms are used throughout this article.

  • A mailbox is an account that can receive email, store messages, and send email under its own address.
  • An alias is an additional address that delivers to an existing mailbox. An alias does not create a separate account, a separate sent folder, or a separate authentication identity.
  • A sending identity is the combination of an address, a domain, and the IP addresses that are used to deliver the message. Receiving systems evaluate the domain and the IP addresses, not the number of mailboxes.

Methods for creating multiple mailboxes

The following table lists the four methods, their capabilities, and their principal limitations.

Method Can receive Can send Cost Principal limitation
Cloudflare Email Routing Yes No None Forwards messages; does not provide a mailbox or an outbound path
Aliases in Google Workspace Yes Yes Per user seat All aliases share one account, one identity, and one reputation
Self-hosted mail server (postfix, PowerMTA) Yes Yes, after configuration Server cost and staff time IP reputation, port 25 access, blocklist monitoring, and bounce handling remain the operator's responsibility
Managed sending infrastructure Yes Yes Per domain The IP addresses belong to the provider

About Cloudflare Email Routing

Cloudflare Email Routing accepts messages that are addressed to any address on a domain and forwards them to a destination mailbox. The service is free, and configuration requires approximately ten minutes.

The service does not provide an outbound path. Messages can be received and forwarded, but they cannot be sent from the domain through Cloudflare. The integration that previously allowed outbound sending through a third-party relay was discontinued, and documentation that describes the older configuration is no longer accurate.

If the requirement is to create 100 addresses and to send from those addresses, Cloudflare provides the addresses and none of the sending capacity. A separate SMTP provider is required, and the reputation of that provider becomes the reputation of the messages.

About aliases in Google Workspace

A Google Workspace user can hold up to 30 aliases, and an address that contains a plus sign, such as name+sales@example.com, provides an unlimited number of variants. Neither method creates a separate sender.

All aliases share the same mailbox, the same sent folder, and the same authentication. Gmail therefore records an increase in the volume that is sent by one account rather than the activity of 30 independent senders. Replies from all aliases arrive in one inbox, which complicates attribution unless additional tracking is configured.

Aliases are appropriate for routing, for example to separate sales@, partners@, and billing@. They are not a method for increasing sending volume.

About self-hosted mail servers

A self-hosted mail server, such as postfix or PowerMTA, provides complete control over addresses and delivery. The software itself is free, but the operational requirements are substantial.

  • Outbound port 25 is blocked by default on Amazon Web Services, Google Cloud, and Microsoft Azure. A relay or a support request is required, and some providers do not remove the restriction for cold outreach.
  • Reverse DNS must be configured. The pointer record must resolve to a hostname that resolves back to the sending IP address, and the operator must control the corresponding zone.
  • IP reputation begins at zero. A new address from a cloud provider has no history, and receiving systems treat an unknown address with suspicion.
  • Blocklist monitoring is manual. Spamhaus, Barracuda, and the blocklists operated by mailbox providers do not notify the sender when an address is added.
  • Bounce and complaint handling must be built. This includes feedback loop enrollment, an abuse mailbox, suppression lists, transport security, and DMARC reporting.
  • The operator becomes the abuse contact. When a recipient complains to the hosting provider, the provider suspends the server rather than the individual campaign.

A well-operated self-hosted server has a low cost per message and a high cost per hour. A poorly operated server is the fastest way to lose a domain that required several months to establish.

About managed sending infrastructure

With managed infrastructure, the provider operates the IP addresses and the delivery systems, and the number of mailboxes is a product decision rather than a configuration technique. In the case of ColdSend, each domain includes 100 mailboxes and 25,000 messages per month, and the sequence product enforces a limit of 100 messages per domain per hour.

The trade-off is explicit. The customer owns the domain, the mailboxes, the recipient list, and the campaign data, and can export all of it. The customer does not own the IP addresses. If ownership of the IP addresses is a firm requirement, self-hosting remains the appropriate choice, provided that the operational cost is included in the comparison.

How to determine whether multiple mailboxes on one domain are appropriate

The following procedure can be used to evaluate a proposed configuration.

  1. Determine whether the requirement includes outbound sending. If it does, exclude any method that cannot send.
  2. Determine the volume that each mailbox will send. A configuration in which each mailbox sends fewer than approximately 30 messages per day is generally supportable. A configuration in which each mailbox sends several hundred messages per day is not.
  3. Determine whether the content will differ between mailboxes. Identical content that is sent from many mailboxes is treated as a single campaign regardless of the number of accounts.
  4. Confirm that SPF, DKIM, and DMARC are configured for the domain, and that the domain has a sending history.
  5. Determine what will happen when an IP address is added to a blocklist. If the answer requires a migration, the proposal should be evaluated as a migration project rather than as infrastructure.

A domain with 100 mailboxes that each send a small and differentiated volume is treated as ordinary business correspondence. The same domain with 100 mailboxes that each send several hundred identical messages is treated as bulk mail, and the number of mailboxes does not change that assessment.

About ColdSend

ColdSend provides managed sending infrastructure with 100 mailboxes and 25,000 messages per domain per month. Azure IP addresses are pre-warmed and are replaced automatically when they are added to a blocklist. The first domain costs $99 per month, each additional domain costs $30 per month, and up to 20 domains can be attached to one account.

Got Questions? We’ve
Got Answers

A domain can contain any number of addresses. The relevant considerations are the volume that each mailbox sends and whether the domain has authentication and a sending history. A large number of mailboxes on one domain is a design decision, not a loophole.

Cloudflare Email Routing provides no outbound capability. It is a forwarding service that is suitable for receiving mail on a domain. Organizations that require outbound sending must use a separate provider.

Classification depends on behaviour rather than on the number of mailboxes. Identical content that is sent at high volume from a new domain will be filtered regardless of how many mailboxes are used. Differentiated, low-volume messages from an authenticated domain with a history are treated as normal business traffic.

Microsoft replaces the address automatically. This is the principal reason that a corporate IP pool is used instead of dedicated addresses, because the risk remains with the provider rather than with the campaign.

You Might Also Like