Sending limits
Daily limit
Section titled “Daily limit”Set it in Project settings → Sending, under Sending limits. Rowsend then sends at most that many emails in any 24 hours, across every campaign in the project. Leave it empty for no limit, which is the default.
Emails over the limit don’t fail. They wait, and go out as the window frees up. If a campaign reaches 4,000 contacts and the limit is 500, it goes out over 8 days, 500 a day. The send dialog says how many days a campaign will take, and the campaign page shows when the next emails go out.
Set a limit when your provider caps daily sending. Without one, a big campaign runs into the cap partway through, and the rest fail. Common caps:
| Provider | Daily cap |
|---|---|
| Gmail login over SMTP | about 500 |
| Google Workspace over SMTP | about 2,000 |
| Amazon SES sandbox | 200. After production access, the SES console’s Account dashboard shows your own cap |
How Rowsend counts
Section titled “How Rowsend counts”- The 24 hours roll. An email sent at 9:14 on Tuesday frees a slot at 9:14 on Wednesday. Gmail and SES count the same way.
- Every campaign in the project shares the limit, and so does Retry failed. Test sends don’t count.
- Each project has its own limit. Two projects sending through the same Gmail login each get the full limit, so set each one to its share.
- Changing the limit applies straight away, including to emails already waiting.
The computer has to be on
Section titled “The computer has to be on”Each day’s emails go out from the companion. In local mode it runs inside Rowsend, so a campaign spread over several days only moves while Rowsend is open on this computer. If it’s closed, the emails wait until you open it again. Nothing fails.
With Rowsend Cloud or your own server, turn on Send while this computer is off in the same settings, and each day’s emails go out on time without the computer.
Warm-up
Section titled “Warm-up”A new domain, or one that has been quiet for a while, has no sending history, and mailbox providers send a sudden flood from it to spam. Warm-up starts small and sends a little more each day until it reaches your daily limit.
Turn on Warm up this domain under Sending limits. It needs a daily limit, which is where it stops. Then choose:
- Start at: how many emails go out on the first day. 50 is a safe start for a new domain.
- Grow each day by: ×1.25, ×1.5, ×1.75 or ×2. Starting at 50 and doubling reaches 2,000 a day in 7 steps. Slower growth takes longer and is gentler on a brand-new domain.
How it moves:
- Each step lasts 24 hours from its first email.
- A step only counts once it has sent at least half its share. Send 5 emails on a 200 day and the next day is 200 again, not 400. A week with no campaigns doesn’t skip the warm-up ahead either.
- Every campaign in the project shares the warm-up, along with Retry failed. Test sends don’t count.
- Emails over the day’s share wait for the next step, like emails over the daily limit.
The settings show which step you’re on, its share and when the next one starts. Finish warm-up skips straight to the daily limit, for a domain that’s already warm. Once the warm-up reaches the daily limit, it’s done and the limit alone applies.
Start it over when the domain goes cold:
- After 30 days with nothing sent, the settings suggest Restart warm-up. Nothing changes until you click it.
- Saving a different provider or from-address domain offers Restart warm-up for the new domain, ticked. A new key or password for the same domain keeps the progress.
With sending while the computer is off, the warm-up keeps going without the computer, and Rowsend picks up where it got to the next time it’s open.
Bounce protection
Section titled “Bounce protection”Rowsend pauses a campaign on its own when too many of its emails bounce or get marked as spam. Providers watch these rates closely, and a campaign to a stale or bought list can get a sending account suspended in a few hours.
Pick how strict it is under Pause a campaign when bounces or complaints get too high:
| Setting | Pauses at |
|---|---|
| Careful | 2% bounces or 0.05% complaints |
| Balanced (the default) | 3% bounces or 0.07% complaints |
| Relaxed | 5% bounces or 0.1% complaints |
It works on every campaign, with or without a daily limit:
- Rowsend checks once a campaign has sent 200 emails, so a couple of early bounces can’t pause a big send.
- Only that campaign pauses. Other campaigns in the project keep sending.
- The campaign page says why it paused, and Rowsend shows a notification.
- It never resumes on its own. Check the audience, then click Resume. From then on, only emails sent after the resume count, so bounces from before can’t pause it again straight away.
- Only hard bounces count. A full mailbox or a server that’s down for a while doesn’t.
It only sees what reaches Rowsend. Complaints often arrive hours after the email. SMTP reports no complaints at all, and its bounces only reach Rowsend through a bounce domain, so SMTP without one gives bounce protection nothing to go on.
Agents
Section titled “Agents”An AI app can change the daily limit, warm-up and bounce protection with set_sending_limits, and restart or finish a warm-up. The Sending settings show which app changed them until you save them yourself. An AI app can’t resume a campaign that Rowsend paused for bounces or complaints. Only you can, in the app.