Exchange mail flow guides › Inbound: POP3 and IMAP retrieval

Catch-all (multidrop) mailbox vs one POP3 mailbox per user — which works better with Exchange?

A catch-all (multidrop) mailbox receives every message for a domain in one POP3 account and relies on the connector reading recipient headers to route each message to the right Exchange mailbox; individual mailboxes make routing exact but cost one account per user. In practice the choice is decided by two things: whether your provider preserves the original recipient in the message headers, and how many users and mailing lists you have. This guide compares both setups and shows how POPcon handles each.

Updated on 2026-09-15

Both models end in the same place: a connector service downloads the provider mailbox on a schedule and submits each message to Exchange over SMTP (the setup is in How to download POP3 and IMAP mailboxes into Exchange 2016, 2019 and SE). The difference is how the connector learns who the message is for.

Definitions

Catch-all mailbox. The provider delivers mail for anyone@yourcompany.com into a single POP3 or IMAP account. The connector examines the headers of every downloaded message (To:, CC: and a list of non-standard fields the providers add) to determine the intended recipients, and delivers each message to the corresponding Exchange mailbox. Some providers call this a multidrop, domain or wildcard mailbox.

Individual (single-user) mailbox. The provider keeps one POP3 or IMAP account per address. The connector delivers everything from that account to one Exchange recipient you configure, regardless of the addresses in the message headers.

Catch-all vs individual mailboxes: the comparison

Criterion	Catch-all (multidrop) mailbox	One mailbox per user
Routing accuracy	Depends on the headers the provider preserves; correct for normal To:/CC: mail, uncertain for BCC and lists	Exact: every message goes to the configured recipient
BCC recipients	Only routable if the provider records the original recipient in a header such as X-Original-To or Delivered-To; otherwise unroutable	Always delivered
Mailing lists	The list server often removes the subscriber address; such mail lands with the postmaster	Always delivered; the list subscription can get its own mailbox
Mail sent to several of your users	The provider may store one copy per recipient; the connector must recognise the copies and deliver once	Each user’s mailbox holds their own copy
Recipients outside your domain in the same message	Must be filtered out through the accepted recipient domains list, or Exchange bounces them	Not an issue: the recipient is fixed
Unknown recipients in your domain	The connector must decide: re-route to the postmaster, or let Exchange send a non-delivery report	Cannot occur: the provider only accepts existing addresses
Accounts to manage	One account, no change when users join or leave	One account per user, created at the provider and in the connector
Cost at the provider	One mailbox	One mailbox per user, depending on the provider’s plan
Configuration in the connector	One account with the accepted recipient domains and, optionally, a re-route address	One account per user with the target Exchange address

Why catch-all routing can fail: BCC, mailing lists and stripped headers

A catch-all mailbox only works as well as the headers the provider hands over. Two cases break it regularly, and neither is specific to any one connector:

• BCC. The BCC recipient is, for obvious reasons, not mentioned in the visible standard headers. Most provider mail servers keep the original recipient in a special, non-standard header field, and a connector that knows that field routes the message correctly. But under some circumstances (mail servers in between and their configuration) the BCC information is stripped completely before the message reaches the connector. Then no POP3 connector can distribute it (knowledge base: BCC recipients do not receive the email).
• Mailing lists. Many list servers do not show the recipient address in the To: field, and the subscriber address can be removed on the way. If no header field carries a recipient in your domain, the message has no local recipient and goes to the postmaster (knowledge base: mailing-list mail is not distributed correctly).

The practical test is to open the headers of one misrouted message (in Outlook: File › Properties, the Internet headers box) and look for a field that still names the intended recipient. If there is one, the connector can usually be told to read it; if there is none, the only fix is an individual mailbox for that user or that list.

What happens to messages the connector cannot place

With a catch-all mailbox the connector must also handle two situations that a single-user mailbox never sees. The first is a message addressed to several people, some outside your domain: the SMTP handover needs every recipient decoded, and Exchange would answer with a complaint to the postmaster, or an automatic reply to the sender, for every address it does not own. That is what the accepted recipient domains list is for: the connector hands Exchange only the recipients in domains you declare yours (why the accepted domains matter). A message with no recipient in any accepted domain at all goes to the postmaster with the log entry that it has no local recipients (knowledge base article).

The second is a message for an address in your domain that does not exist in Exchange, for example a former employee or a typo. Exchange has no option to accept all mail for a domain, so it bounces such messages. A connector can instead re-route mail to unknown recipients to a mailbox of your choice, such as the postmaster or an administrator (knowledge base article). Which you prefer is a policy decision: a non-delivery report tells the sender at once, a re-route lets a person look at the message first.

Recommendation

1. Individual mailboxes when the provider offers them at reasonable cost. Routing is exact, BCC and mailing lists work, and there is nothing to filter. The price is one account per user and a little more administration when users change.
2. Catch-all only with a provider that adds a delivery header. If the provider records the original recipient in a header such as X-Original-To, Delivered-To or X-RCPT-TO, a catch-all mailbox routes correctly for almost all mail and is far less work to maintain. Test it with a BCC message before you rely on it.
3. Mix the two where needed. A catch-all account for the domain plus single-user accounts for a mailing-list subscription, or for the one user whose mail keeps arriving without recipient headers, is a normal configuration.

How POPcon handles each mailbox type

In POPcon every POP3 or IMAP account has a mailbox type. A single-user mailbox delivers all mail retrieved from that account to one internal recipient, regardless of the addresses in the headers. A catch-all mailbox is examined message by message: POPcon does not only evaluate the To: and CC: fields, because these frequently do not contain the real recipient, but a longer list of header fields, among them X-Original-To, Delivered-To, X-RCPT-TO, X-Envelope-To and Received; the complete list is shown on the Advanced configuration page. POPcon PRO added X-FORWARDED-FOR to that list in version 4.6.2 (version history).

For catch-all accounts you enter your domain, without the @, in the Accepted recipient domains box; only recipients in those domains are forwarded to Exchange. A re-route address on the same page receives messages whose recipients cannot be resolved in Exchange, while the postmaster from the General tab receives messages that have no recipient in any accepted domain. If a message arrives in several copies because it was sent to several of your users, POPcon delivers it to all of them from the first copy and discards the later copies with the same message ID.

One catch-all detail from the knowledge base: the catch-all address itself (catchall@yourcompany.com) tends to appear in the headers as well and is a valid address in your domain, so each message would also be delivered to that mailbox. The knowledge base describes the Advanced-page option that removes that address from the recipients found in the headers.

If you are setting this up for the first time, the four steps, including the accepted domains and the receive connector on the Exchange side, are in the guide How to download POP3 and IMAP mailboxes into Exchange 2016, 2019 and SE; the trial is on the POPcon download page.

Frequently asked questions

More on inbound mail flow in the Exchange mail flow guides, or in the knowledge base. Auf Deutsch: Catch-all-Postfach oder ein POP3-Postfach pro Benutzer?.