Guides /

How the daily cap and the queue work

Postfaro is built so that you can send a big campaign in one go — from your CRM, Outlook or newsletter plugin — without worrying about limits. This page explains what happens behind the scenes.


The daily cap: 5,000 emails per sending domain

  • Your plan includes up to 5,000 emails per day for its sending domain.
  • The cap is per sending domain, shared by all sender addresses on that domain. If news@ sends 3,000 and events@ sends 2,000, the day is full.
  • A second sending domain is a second plan with its own 5,000 per day, its own queue and its own warm-up.
  • Each recipient counts as one email. A message to 3 recipients counts as 3.
  • A day runs from 00:00 to 24:00 UTC.
  • Use it or lose it: unused capacity does not carry over. If you send nothing on Monday, you still have 5,000 on Tuesday — not 10,000.
  • Addresses on your cancelled addresses list are dropped before sending and do not use up your cap.

What happens when you send more than that

Nothing breaks. Postfaro accepts every message your tool sends and puts the ones that don’t fit today into a queue. Each day, the next 5,000 are sent, until the queue is empty.

Example — 22,000 emails sent on a Monday morning (after warm-up):

Day Sent Still queued
Monday 5,000 17,000
Tuesday 5,000 12,000
Wednesday 5,000 7,000
Thursday 5,000 2,000
Friday 2,000 0

As soon as the messages are queued, we email you a summary: “22,000 emails queued — last send expected on Friday, 20 March.” The queue sends every day, including weekends; messages for a later day are released from 06:00 UTC.

Your tool sees success immediately. From your CRM’s point of view, every message was accepted. The waiting happens at Postfaro. That also means you can switch your tool back to its normal mail server right after it has handed over the campaign (see the Vtiger guide).

Order: messages are sent in the order we received them, across all your sender addresses. If you start a second campaign while the first is still queued, the second one waits for the first.

Following and cancelling the queue

In the customer panel, Queue shows each batch: how many were accepted, sent, waiting and dropped, and the expected last send date.

You can cancel a batch (or everything still waiting) at any time — for example if you spot a mistake in the campaign. Cancelled messages are deleted and are not sent. Messages already delivered cannot be recalled.

We accept messages up to 60 days ahead. A message that cannot be delivered within 5 days of its planned sending day expires and is reported as not delivered.

Warm-up: why your first weeks have a lower limit

Mailbox providers such as Gmail and Microsoft distrust a brand-new sender that suddenly sends thousands of emails. Reputation is built gradually. That’s why each new sending domain goes through warm-up: the daily limit starts low and rises step by step to 5,000.

Schedule (also shown in your panel):

Day Path A — new domain registered through us Paths B and C — your own domain or a subdomain
1 100 1,000
2 200 1,500
3 400 2,500
4 600 3,500
5 800 4,500
6 1,000 5,000
7 1,300 5,000
8 1,600 5,000
9 2,000 5,000
10 2,500 5,000
11 3,000 5,000
12 3,500 5,000
13 4,000 5,000
14 4,500 5,000
15 and after 5,000 5,000
  • Warm-up takes 15 days for a new domain and 6 days for your own domain or a subdomain. Your own domain (path B) follows the 15-day schedule if it was registered less than 30 days before warm-up starts.
  • If more than 1% of your messages bounce because the address does not exist, the daily limit of each of your sending domains is halved until the rate falls.
  • You can send any amount during warm-up — it simply queues for longer. The “Batch queued” email always shows the realistic last send date.
  • Tip: during warm-up, send first to your most engaged contacts (recent customers, people who opened recently). Good early engagement builds your domain’s reputation with mailbox providers.

Pacing within the day

Even within your daily limit, we don’t send everything in the same minute. We pace delivery per receiving provider (Gmail, Microsoft, Yahoo, others), the way those providers prefer. A message accepted at 09:00 may be delivered later in the day. This is normal and protects your reputation.

Your first days count most

We measure bounces, complaints and refusals over the last 3 days, starting with your very first message. A dirty list — many non-existent addresses, or a bought or scraped list — is therefore usually stopped on its first day, before it damages your new domain’s reputation.

Automatic pause

Sending pauses automatically, at any time, if over the last 3 days (today and the two days before):

  • more than 2% of your messages hard-bounce because the address does not exist (measured once at least 100 messages have been sent), or
  • more than 0.1% of delivered messages are reported as spam (measured once at least 500 messages have been delivered), or
  • more than 5% of your messages are refused by receiving servers for policy or spam reasons — a permanent rejection other than “address does not exist” (measured once at least 100 messages have been delivered, bounced or refused).

Refusals caused by our own infrastructure (for example a blocklist listing our IP address) are never counted against you.

Separately, messages with links through URL shorteners are rejected, and messages with links to bare IP addresses are held for review. When we confirm phishing or malware, we stop the account at once.

These limits are stricter than the mailbox providers’ own (Gmail, for example, expects spam complaint rates to stay below 0.3%). Stopping early protects your domain before providers start rejecting your mail.

While paused:

  • queued messages wait — nothing is lost;
  • new messages from your tool get a temporary “try again later” response (SMTP 451). Most tools retry for a while; if the pause lasts long, your tool may eventually report those messages as failed;
  • you receive an email explaining the reason and what to do (usually: remove bad addresses and check where the list came from). Our team reviews the account before sending resumes.

Receiving domains that refuse your email

Some organisations — universities and public bodies, for example — refuse bulk email or accept it only from senders they know. If one recipient domain refuses 3 of your emails within 24 hours for policy or spam reasons, and none of your emails to it got through in that time, we stop sending your emails to that domain for 7 days:

  • emails to that domain are accepted from your tool but not sent, and they don’t use your daily limit;
  • emails to that domain already in the queue are cancelled;
  • emails to all other domains go out as usual;
  • each domain counts on its own (students.example.edu is separate from example.edu).

You receive an email with the server’s answer. In the panel, Cancelled addresses → Receiving domains that refuse your email shows the domain, the answer, the end date and how many emails were not sent. After 7 days sending resumes by itself; if the domain refuses again, it stops again for 7 days. The addresses are not added to your cancelled addresses. To reach these recipients, contact them another way or ask them to allow your sending domain.

If the same domain refuses emails from 3 different Postfaro customers within 24 hours, we treat it as a problem with our servers: nobody’s sending to it is stopped, and our team investigates.

Cancelled addresses

Some addresses are never sent to again:

Reason What it means
Hard bounce The receiving server says the address does not exist. Blocked for all Postfaro customers
Complaint The recipient marked your email as spam. Blocked for your account
Unsubscribed The recipient used the one-click unsubscribe button. Blocked for your account

Messages to these addresses are accepted from your tool but not delivered, and they do not count toward your daily limit. You find them in the panel under Cancelled addresses, with the reason and date, and you can export them as CSV. We don’t change anything in your CRM or plugin, so we recommend removing or opting out these addresses in your own tool regularly.

Not for urgent email

Because of the queue, Postfaro is not the right path for email that must arrive within seconds: order confirmations, password resets, two-factor codes, or day-to-day correspondence. Keep those on your existing mail server. Our setup guides show how to route only campaign email to Postfaro.