Skip to content

Newsletter setting perMinute caps emails sent per minute - #3

Merged
arjunpredev merged 1 commit into
mainfrom
feat/newsletter-per-minute-cap
Oct 23, 2026
Merged

arjunpredev merged 1 commit into
mainfrom
feat/newsletter-per-minute-cap

Conversation

@arjunpredev

Copy link
Copy Markdown
Contributor

Why

A send goes out as fast as the provider takes it (batches of 100, about 1,300 a minute). Gmail defers a burst from a sender that is still building reputation, so a big send can sit undelivered for hours.

Change

  • newsletter.perMinute in site settings: each processSends run stops at that many emails (sent plus failed), shrinking the last batch to fit; the next cron run, a minute later, continues. Unset, nothing changes.
  • Documented in docs/configuration.md.

Checked

bun run typecheck, admin build, leak guard. Staging smoke runs on deploy.

🤖 Generated with Claude Code

Unset keeps today's behavior (as fast as the provider takes them). With a cap,
each run of the send loop stops at that many emails and the next cron run picks
up the rest, so a big send spreads out. Mailbox providers defer mail that
arrives in a burst from a sender still building its reputation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@arjunpredev
arjunpredev merged commit 778af3f into main Oct 23, 2026
1 check passed
@arjunpredev
arjunpredev deleted the feat/newsletter-per-minute-cap branch October 23, 2026 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant