Mailing lists for Joomla sites
Postrider runs the mailing lists your Joomla site already needs — reading your real membership data, syncing every group automatically, and never billing you twice for a person who sits on twelve lists.
Lists
1,284 members · 12 lists
All Members — Announcements
Announcement · synced from Joomla
secretaries@
Reflector · moderated · daily digest
Committee — Formal Notices
Announcement · bypasses unsubscribe
Monthly Bulletin
Campaign · opt-in
Where Postrider wins
Each one is a structural difference a competitor would have to rebuild from the ground up, not a setting they could add to catch up.
01 — SEGREGATION
Global suppression (bounce/complaint) is account-wide; subscribe state is tracked per list. Opting out of one list never silently drops a member from another.
Mailchimp bills the same contact again for every audience it sits in.
02 — REFLECTOR LISTS
A member emails the list's own address; SES receiving redistributes it to every subscriber, with moderation, digests, reply-threading and attachments.
Neither Mailchimp nor the Mailster incumbent attempt this at all.
03 — DELIVERABILITY
One discrete SES call per recipient, with real event tracking (bounce, complaint, delivery, open, click) and RFC 8058 one-click unsubscribe built in from day one.
Mailster's own docs note tracking depends entirely on your SMTP provider.
04 — ISOLATION
AWS SES Tenants give each customer its own sending reputation on shared infrastructure — one customer's bounce spike can't sink another's inbox placement.
Cheaper and more elegant than a dedicated IP per customer at this scale.
05 — ABUSE PREVENTION
Every campaign is screened by an AI content check for spam, phishing, and scam intent before it goes out. Bounce and complaint rates are monitored per tenant against AWS's own reputation thresholds, with automatic suspension if they're crossed.
Most ESPs review abuse after the damage is done — this catches intent at send time, then backs it up with real delivery feedback.
06 — CMS-NATIVE
A first-class Joomla connector reads real membership data and keeps lists in sync automatically — push-on-save plus a scheduled resync — or syncs from any database table generically.
No mainstream ESP integrates this deeply with a membership CMS out of the box.
The inventory
Everything currently live in production, grouped the way a buyer would evaluate it.
How it works
1
The Joomla connector, Community Builder fields, or any database table — push-on-save plus a scheduled resync keeps lists eventually consistent even if a webhook is missed.
2
Every subscriber carries one global suppression state and independent per-list subscriptions — segment by field, run reflector lists, or both, without re-importing anyone.
3
Campaigns, reflector posts, and digests all go out through the same tracked SES pipeline — delivery, opens, clicks, bounces and complaints, per tenant.
Pricing
A member on five of your lists costs what a member on one list costs. Mailchimp's own pricing documentation confirms it bills again per audience a contact sits in, and again for contacts who've already unsubscribed.
Every paid tier includes a generous monthly send allowance; beyond that, overage is billed per 1,000 sends — never per contact, never per list.
Free
£0
no card required
Growth
£15
/mo
Scale
£39
/mo
Enterprise
Custom
negotiated, annual
Indicative pricing — final published rates are confirmed at checkout, in GBP.
Estimated total
£39 /mo
Overage beyond the included allowance is £0.95 per 1,000 sends.
Security & compliance
None of this is a policy document — it's the actual send path every message goes through, whether it's a campaign, a reflector post, or a digest.
One-click unsubscribe
RFC 8058, stateless per-recipient HMAC tokens — no separate token database to manage.
Automatic suppression
A bounce or complaint suppresses account-wide, enforced at send time on every send path.
Inbound authentication gate
SES's own DMARC/SPF/spam/virus verdicts, plus RFC 3834 mail-loop protection on reflector and digest sends.
AI content screening
Every campaign is checked for spam, phishing, and scam intent before it sends — a high-confidence flag blocks the send pending staff review, never silently through.
Reputation-based suspension
Bounce and complaint rates are monitored per tenant against AWS's own published thresholds; a tenant damaging shared sending reputation is suspended automatically.
Roles and audit
Owner/editor roles enforced server-side, with a full log of team changes, sends, and key rotation.
Account security
Generated temp password with forced change on first login, self-service reset, and TOTP two-factor.
Keys and API
A per-tenant API key, shown once and stored only as a hash, with a published reference generated from the real routes.
Register
Tell us about your organisation and we'll provision your tenant, verify your sending domain with you, and send a temporary password for first login.
Already a tenant?
Sign in to the admin →