Bulk email: sending mass email without landing in the spam folder

Bulk email is one message that goes to hundreds or thousands of recipients in a single send — a newsletter, an offer, an announcement to all your customers. It is also called mass email. Technically it is the same email as any ordinary message; what changes is how mailbox providers look at it. From a certain volume onwards it is no longer your words that count, but your sending pattern, your authentication and the way recipients react.

This page explains where sending limits come from, why you spread a large send over time, how reputation and warm-up work, and what Gmail, Yahoo and Microsoft expect from bulk senders.

Sending limits Throttled sending Reputation & warm-up Rules for bulk senders Frequently asked questions

Bulk email and sending limits: where do you hit the ceiling?

Every route you send email through has a limit. That limit is rarely in the software itself; it sits with whoever guards the sending.

You send through Who sets the limit What happens when you exceed it
Your mail client (Outlook, Gmail) Your mailbox provider, with a ceiling per day and per message. That service is built for personal correspondence, not for lists. The account is temporarily blocked from sending — including your ordinary emails. Repeat it and a permanent block follows.
The mail server of your web hosting Your hosting company, usually with a limit per hour. A shared server shares its IP reputation with every customer on it. Messages get stuck in the queue or are refused, and one bad neighbour on the same IP address can drag your delivery down with it.
An SMTP relay The volume of your subscription, and on top of that the pace the receiving providers accept from your domain. The relay holds messages back and offers them again spread over time, instead of letting them be refused.
A campaign platform The same two limits as with a relay, plus the requirement that every address is on the list with consent. Invalid addresses produce bounces, and recipients who never gave consent produce spam complaints. Both damage the reputation of your domain, for your next sends as well.

Anyone who tries "sending 1,000 emails through Outlook" usually only notices once their ordinary mail traffic grinds to a halt as well. Bulk email belongs on infrastructure built for it — with its own sending stream, separate from the mailbox you work with every day.

Mass email sending, throttled: why 10,000 emails do not leave in one minute

A receiving mail server accepts only a certain number of messages per unit of time from each sending domain. Offer more than that and it answers with a temporary refusal — a so-called deferral — and expects you to try again later. That is not an error, it is traffic control.

Sending software that ignores that signal and keeps pushing achieves the opposite of what it wants: the provider lowers the permitted pace further, or puts the domain on a blocklist for a while. Throttling is therefore not a restriction but a delivery strategy: a separate pace for each receiving provider, which rises as long as messages are accepted smoothly and drops as soon as deferrals come back.

In practice it means a bulk send of ten thousand messages takes anywhere from a few minutes to a few hours, depending on how the list is spread across the providers and how much history your domain has. If you schedule a send for a fixed time, allow for that lead time.

Reputation and warm-up at large volumes

Mailbox providers keep a reputation for each sending domain and each IP address. At small volumes you hardly notice it; with bulk email it decides whether your message reaches the inbox.

Warm-up for new domains

A domain without sending history that suddenly sends thousands of messages shows exactly the behaviour of a hijacked account. Volume has to grow over days to weeks, starting with the recipients who open most often.

Separate sending streams

Keep bulk email and transactional email apart. If a campaign draws spam complaints, that must not drag down the delivery of your order confirmations and password resets.

List hygiene

Every invalid address produces a hard bounce, and a high bounce rate is the clearest sign to providers of a purchased or outdated list. Remove bounces after every send, and inactive addresses periodically.

Spam complaints

A click on "this is spam" weighs far heavier than an unsubscribe. So make unsubscribing easier than complaining: a visible link in the message and the unsubscribe button that mail clients themselves show at the top.

What Gmail, Yahoo and Microsoft require from bulk senders

Since 2024 Gmail and Yahoo have applied explicit rules to anyone sending to their users in large numbers; Microsoft followed in 2025. They come down to the same thing: the sending domain must be demonstrably yours, recipients must be able to unsubscribe with one click, and the share of spam complaints must stay low. Senders who do not comply see their messages delayed first, then refused.

You solve the first point with three DNS records. How they work and in which order you set them up is explained on the page about SPF, DKIM and DMARC; whether they are correct for your domain, you check for free with the SPF, DKIM and DMARC checker.

The second point is the List-Unsubscribe header in its one-click variant: a technical field in the message that makes Gmail and Outlook show an unsubscribe button next to the sender themselves. An unsubscribe link at the bottom of the email alone is no longer enough for bulk senders. The third point follows from everything above — and from a list people asked to be on themselves.

Sending bulk email with 2Mail

2Mail is built for these volumes. The platform sends at a fixed pace per major mailbox provider, and you spread a large send over batches yourself — up to 60, with an interval you choose — and schedule it by date and time. Bulk email and transactional email run over separate streams, hard bounces are processed automatically and excluded from the next sends, and every campaign email carries the List-Unsubscribe header with one-click unsubscribe. Everything runs on our own servers in Belgium; you pay per volume tier, not per message.

Want to know how to set up such a send, from address list to inbox? That is explained step by step on sending a mailing. What the platform does along the way — design, tracking, statistics — you can read on email marketing, and the technology behind arriving on deliverability. Not sure which volume you need? Work it out with the volume calculator.

Frequently asked questions about bulk email

Bulk email is one email message that goes to a large group of recipients in a single send: a newsletter, an offer or an announcement to all your customers. It is also called mass email; in Dutch the term is bulkmail. Technically it is no different from an ordinary email; the difference is the volume, and the requirements mailbox providers therefore set for authentication, unsubscribing and sending pace.
Consent. Bulk email goes to people who asked for it themselves or who are customers, contains a working unsubscribe link and comes from a recognisable sender. Spam goes to addresses that never gave consent. To a spam filter, however, a badly set up bulk send looks just the same — hence the importance of authentication, a clean list and a throttled pace.
We advise against it. A mailbox at Microsoft 365 or Google Workspace is built for personal correspondence and has a ceiling per day and per message. Exceed it and your account is temporarily blocked from sending, ordinary emails included. Unsubscribe link, bounce handling and statistics are missing as well. For mass email sending, use an SMTP relay or a campaign platform with its own sending stream.
From a few minutes to a few hours. Receiving providers accept only a certain pace per sending domain; a good sending infrastructure spreads the messages per provider and offers temporarily refused messages again later. A domain with a long, good sending history is allowed to go faster than a new domain. Allow for that lead time if you want to send at a fixed hour.
Throttling is deliberately limiting the number of messages per unit of time to one receiving provider. It prevents that provider from temporarily refusing your messages or slowing down your domain. At 2Mail that pace is fixed per major mailbox provider: Gmail, Microsoft, Yahoo, iCloud and a range of Belgian providers each have their own rhythm. On top of that you can send a campaign spread over batches if you wish.
Usually not. A dedicated IP address only makes sense with a large and regular volume, because an IP address without a constant flow builds no reputation. For most companies a well-managed shared IP address works better, provided the provider keeps abuse out strictly. More important than the IP address is the reputation of your own domain.
Three things: the sending domain must be authenticated with SPF, DKIM and a DMARC record, recipients must be able to unsubscribe with one click through the List-Unsubscribe header, and the share of spam complaints must stay low. Senders who do not comply see their messages delayed first and then refused. Microsoft has applied comparable rules since 2025.
Yes, provided you have a valid legal basis for every address. For commercial messages that is, as a rule, prior consent (opt-in); for existing customers there is an exception for similar products, as long as they can unsubscribe in every email. Purchased address lists never meet that requirement.

Sending large volumes that arrive

Tell us how much you send and from which domain; we help you set up the authentication and keep an eye on things while you build up the volume in a controlled way.

See the pricing Calculate your volume Ask your question
Call us
Send an email