Is systeme.io Good for Email Marketing? Mind the Pool
systeme.io doesn't cap emails sent, but each account sends from an IP pool set by its own opens, complaints and bounces. How the pools work, who it suits.

5,000 emails and 14 days.
That's what systeme.io's help center says an account has to send, and how long it has to wait, before it can move out of its green, yellow or red sending pool. The rule is in an article on deliverability, and it changes how I'd answer the question in the title.
"With systeme.io, users are divided into pools, and each pool uses a different set of IP addresses." There are five: green, yellow, red, quarantine, and a gray pool for new accounts. Your account is placed by its own open rate, spam complaints and bounces, and it moves slowly. So systeme.io's email isn't one thing that every customer gets. The feature list is the same on every account; the lane your emails leave from isn't.
My answer: systeme.io is good for email marketing when your list can reach the green pool and stay there. A list you grow inside systeme.io, mailed weekly from your own authenticated domain to a few thousand people who asked for it, can climb in a few weeks. A 300-person list you email monthly, an old list you import in one go, or a list whose opens have sagged can spend months wherever its first sends put it.
What every plan gets
Before the pools, the toolkit. On systeme.io's pricing page every plan shows no cap on emails sent or on newsletters. What's counted is automation:
| Free | Startup | Webinar | Unlimited | |
|---|---|---|---|---|
| Price (monthly / yearly) | $0 | $17 / $170 | $47 / $470 | $97 / $970 |
| Contacts | 2,000 | 5,000 | 10,000 | No cap listed |
| Email campaigns (sequences) | 1 | 10 | 100 | No cap listed |
| Automation rules | 1 | 10 | 100 | No cap listed |
| Workflows | 1 | 5 | 20 | No cap listed |
| A/B tests | 1 | 10 | 50 | No cap listed |
A few things the plan table doesn't show:
- Newsletters go to tags, not lists. You pick tags, and contacts carrying them receive the email. Tags are counted per plan too; I've set out systeme.io's tag ceilings, plan by plan separately.
- You can resend a newsletter to non-openers once. The help article is explicit that there's no third attempt.
- Free accounts carry a footer badge. "Sent with systeme.io" is an affiliate link, and only paid plans can switch it off.
- There's no inbox. None of the email pages or help articles I read offers a mailbox for replies. The help center's instruction is to send from "a professional email address associated with your custom domain name," so replies land wherever that address is hosted. systeme.io said as much in an April 2025 reply to a Trustpilot review: "we do not offer email inbox hosting," so you'll need another tool to receive replies.
- You can send through your own SendGrid account, with systeme.io as the gateway, or connect ActiveCampaign. Other autoresponders connect through Zapier.
If you sell through systeme.io as well, what its checkout really costs per sale is worth reading next to this.
The feature list answers whether systeme.io can send your emails. The pool rules answer how they'll be sent.
The pool ladder
systeme.io's article on advanced deliverability, last updated March 25, 2026, lays out the pools and the thresholds between them. I've put them in one table:
| Pool | How an account gets there |
|---|---|
| Gray | New accounts. You leave once the account is at least 16 days old and has sent 500 emails. |
| Green (low risk) | Open rate above 20%, spam reports below 0.25%, bounce rate below 0.7% |
| Yellow (moderate risk) | Open rate 10–20%, spam reports 0.25–0.4%, bounces 0.7–1.8% |
| Red (high risk) | Open rate below 10%, spam reports 0.4–1%, bounces 1.8–5% |
| Quarantine | Immediately, if emails from the last 24 hours show spam reports above 1% or bounces above 5% |
The movement rules matter as much as the thresholds. "Users are allocated to different groups every morning," but an account can only move after at least 14 days in its current pool, and only after sending a minimum number of emails there: 500 to leave gray, 1,000 to leave quarantine, 5,000 to leave green, yellow or red. The statistics used stop five days short of the present, to give opens and complaints time to arrive. A second help article, updated June 29, 2026, repeats the entry rule in its own words: "If the account is over 16 days old and 500 emails have been sent," the account is classified in a high, medium or low risk group, and poor early results send it to quarantine instead. Separately, systeme.io says it monitors accounts daily and, if an indicator is abnormally high, "we suspend the sending of emails from the user's account as a security measure."
The help article puts the responsibility plainly: "the deliverability of your emails depends above all on your practices." The ladder is how that sentence is enforced. The reason for it is shared infrastructure: accounts share IP addresses, and the pools exist to keep the accounts with poor numbers away from the ones with good numbers.
How long a climb takes
The 5,000-email rule is the one I'd plan around, because its weight depends on your list. Here's the minimum time to leave yellow, red or green (5,000 emails and 14 days, whichever comes later), counting every email you send:
| List size | Emails a week | Weeks per move | Weeks to leave quarantine (1,000 emails, 14 days) |
|---|---|---|---|
| 300 | 1 | 16.7 | 3.3 |
| 500 | 1 | 10 | 2 |
| 1,000 | 1 | 5 | 2 |
| 1,000 | 2 | 2.5 | 2 |
| 2,000 | 1 | 2.5 | 2 |
| 5,000 | 1 | 2 | 2 |
Leaving gray takes about two and a third weeks for any of these lists, because the 16-day floor arrives before the 500th email does.
Read across the rows and the question changes. A 5,000-contact list mailed weekly can move a step every fortnight, as fast as the rules allow. A 500-person newsletter mailed weekly needs ten weeks per step, and a 300-person list needs four months. Sequences count toward the total, so a welcome series on top of a weekly newsletter speeds things up. A monthly newsletter to 300 people would need more than a year to send 5,000 emails.
The same rule holds an account in place on the way down, apart from the jump to quarantine, which happens at once. A green account that has one bad week doesn't drop to red the next morning. A small list that starts in red doesn't leave it quickly either.
On systeme.io, the first 500 emails deserve more care than anything else in the schedule, because for a small list the pool they lead to is the pool it'll have for a season.
Complaints are counted against opens
One line in the help article changes the arithmetic. Spam reports are defined as the number of contacts who report an email "as well as the percentage in comparison to the number of opened emails." Not emails sent. Opens.
That means a list with fewer opens trips the thresholds with fewer complaints. Taking the quarantine line (more than 1%) at face value:
| Emails sent | Open rate | Opens | Complaints that pass 1% | As a share of emails sent |
|---|---|---|---|---|
| 1,000 | 30% | 300 | 4 | 0.40% |
| 1,000 | 20% | 200 | 3 | 0.30% |
| 2,000 | 20% | 400 | 5 | 0.25% |
| 2,000 | 10% | 200 | 3 | 0.15% |
The red band (0.4% to 1%) carries a minimum of six reports; the quarantine rule, as published, checks at least 1,000 emails sent in the five days before. Either way, a sagging open rate is a problem twice: below 10% is the high-risk band in its own right, and fewer opens shrink the base that complaints are measured against.
systeme.io's answer is list cleaning, and its advice is brisk. "We recommend aiming for a minimum open rate of 20% to be among the top users of our email sending system," says its guide to cleaning a list manually, which then walks through filtering contacts with no open or click in the past month, deleting the non-customers among them and unsubscribing the customers. systeme.io's article on bounce management adds a removal of its own: fake or deactivated addresses are "automatically removed from your contact list once identified as fake or deactivated." Accounts also have a list-cleaning setting. In a reply to a February 2026 review, systeme.io explained that a customer's contacts "were automatically removed due to the list-cleaning setting that was active in your account." They were restored, and support then showed the customer how to filter them out for a resend.
A month is a short window for a list that hears from you monthly, and the guide itself says the date range should depend on how often you send. I'd set it to two or three sends, not to a calendar month, and I'd check whether automatic cleaning is switched on before the first newsletter goes out.
What has to be in place before your first email
systeme.io's own page about email says: "Most beginners are sending their first campaign within the first day of signing up." That's possible, after a few things are done, and the help center lists them.
An authenticated domain with a working website. "Authentication of a domain name is mandatory to send emails from systeme.io." You add three CNAME records and a DMARC record at your domain host. The domain needs an active website (if it leads to a 404 page, the help center warns, email providers may block your mail), and a domain can be authenticated in only one systeme.io account.
A sender address on that domain. Since July 16, 2024, "it is no longer possible to use an @gmail.com address to send emails to your list via systeme.io." The same article lists Yahoo, Zoho, ProtonMail and laposte.net addresses as prohibited, because of those providers' own policies. Outlook and Hotmail addresses are still technically allowed, and systeme.io advises against them. Each sender address has to be confirmed.
Patience with the first 500. A new account's first email goes to 100 contacts, then sending pauses while systeme.io reads the statistics. "This verification can last from a few minutes to six hours." Good results release the next 100, up to 500; poor ones send the account to quarantine.
A clean import, if you're bringing a list. "When a user imports a contact list, sending their emails may be temporarily paused" while systeme.io checks where the contacts came from, the condition of the addresses and the sending domain. Purchased or scraped lists are banned outright. Switching tools also resets your sender history: the help center's article on open rates after a move describes "a reset of your reputation." Even with the same domain, it says, a new sender profile takes time to establish.
These rules follow the inbox providers, and so far they've only tightened. Google's stricter sender requirements took effect on February 1, 2024, and systeme.io's Gmail ban followed on July 16. The article announcing it, dated April 9, 2026 in its latest version, still says "Currently, only certain Microsoft domains remain technically 'authorized'" and advises against using them. I'd treat that Outlook and Hotmail allowance as the next thing to go, and send from your own domain from day one.
Links that match your domain. Links should go to the same domain you send from, link shorteners are discouraged, and "Changing links that redirect to multiple pages depending on the click are prohibited." systeme.io reserves the right to block an email with a link it considers dangerous, and emails containing words it reads as spam can be held for a manual check.
Trustpilot is mostly praise for systeme.io. When I read its page on October 8, 2026, 94% of the 8,629 reviews were five-star and the TrustScore stood at 4.9. The email complaints I quote here show the gates from the customer's side, with the company's version underneath. In December 2024 a team that had tested 2,000 addresses on the Free plan, then upgraded to Unlimited, complained of repeated questions and blocked sending: "Total email sent is less than 1700 in 18 days." systeme.io's reply said "the actual total was 11,500" and that the list's spam rate was "exceeding Google's acceptable thresholds by 15 times". Those are the company's figures, and the two sides also disagree about money: the reviewer wrote that systeme.io wasn't refunding, and the reply says the plan was refunded in full. In summer 2024 a marketer described emails blocked in the middle of campaigns; systeme.io's reply put it down to "using different email domains to send messages to the same lists" and a domain used before its verification was finished. On the other side, a course seller wrote this October that two support staff "helped us immensely to get our email address and domain verified" over several hours of emails.
Two reviewers who wrote up their own setups on their own sites show the same gates. Softailed's reviewer (page updated June 8, 2026) found that "Systeme fully blocks these features unless you have your domain name and email address verified," with no button to force the check, and wrote that DNS propagation "literally delayed my review by a couple of days." Mia Elvasia, who calls email marketing her "bread and butter," wrote on BlogRecode that "deliverability is solid (my open rates stayed consistent)." Her review also shows how a disputed claim gets settled: in September systeme.io replied under it that her only support ticket "was answered in 7 minutes," and she corrected the article. On X, opinions split the way this page does. A UK systeme.io consultant posted in January 2025 that she'd used it since the previous summer "for newsletters, email campaigns, landing/squeeze pages, opt-in forms & more," while a marketing account advised in September keeping funnels on systeme.io and the newsletter on MailerLite "for maximum inbox deliverability."
These are individual accounts, I can't judge who was right in the disputed ones, and none of them measures inbox placement. They line up with the written rules, which is the part I can check.
Who it suits, and who I'd point elsewhere
On the rules above, systeme.io's email suits:
- A list you're building inside systeme.io, from its own opt-in forms (double opt-in is available and removes unconfirmed sign-ups after 24 hours), sent from a domain you've authenticated.
- A list of 1,000 or more that hears from you weekly, so the 5,000-email steps take weeks, not months.
- Sellers who want the email and the checkout in one account, and can live with the campaign and workflow counts on their plan.
I'd point these readers elsewhere, or at least slow them down:
- Someone migrating a large, older list in one go. The import check, the reset and the bounce line (a 1,000-email send with 51 dead addresses is past 5%) all land in the first week. If you do move, start by mailing the most engaged contacts, as systeme.io's own guidance suggests, and bring the rest in later. Users describe the same staging. In February 2024, someone in r/systeme_io on Reddit moving a very large list reported, "They told me it can take weeks to be approved to send to 150k." A systeme.io affiliate in the thread advised starting "with small mailing groups (1,000 or 2,000 people) with regular mailings so that they can classify you in a mailing group." That's the pool ladder described from the user's side.
- A small list mailed monthly. The ladder moves too slowly to fix a poor start.
- A sender with low opens who won't prune. The open-rate floor and the opens-based complaint rate both work against you.
- A sender who can't edit DNS records. Sending waits for an authenticated domain, and nothing in the help center offers a way to hurry the check.
For some of those readers the SendGrid option is the way to keep systeme.io's funnels and send from your own SendGrid account; you'd pay SendGrid separately and manage that account's reputation yourself. The help article doesn't say whether mail sent that way is sorted into systeme.io's pools, and I'd assume it isn't only after asking support. For others, a standalone email tool is simpler: GetResponse, which I've set against systeme.io in the tag comparison linked above, or Moosend, whose plans and support record are in my notes on Moosend today. I haven't tested inbox placement for any of them.
What the help center leaves open
- Which pool you're in. The help center describes the pools and thresholds. I haven't found an article that tells you where to see your account's current pool, so I'd ask support directly.
- The quarantine arithmetic. The rule checks the last 24 hours and also mentions at least 1,000 emails over five days. I've treated complaints as a percentage of opens because that's how the article defines spam reports; support could confirm whether quarantine uses the same base.
- Inbox placement. I don't run deliverability tests. Nothing here says your mail will land in an inbox on systeme.io or anywhere else; it describes the rules systeme.io has published about how your account is handled.
My answer, by list
- Growing a new list inside systeme.io, mailing weekly, own domain: yes. Start on Free and give the first 500 emails your best-qualified contacts.
- An established list of a few thousand with healthy opens: yes, on systeme.io Startup, which holds 5,000 contacts for $17 a month where Free stops at 2,000. Import in stages and expect a check on the first import.
- A list under 500 that you email monthly: it works, but you'll live with your first pool for a long time. Weigh that against the price before you commit.
- A large, old list with weak opens: clean it before choosing any tool. On systeme.io, a poor first week is expensive, because the climb back is slow.
FAQ
Is email really uncapped on systeme.io's free plan?
The pricing page sets no cap on emails sent or newsletters on any plan, Free included, up to 2,000 contacts. The counted items are sequences (one on Free), automation rules, workflows and A/B tests.
Why is my systeme.io email stuck as pending?
The help center gives four reasons: new-account checks after each batch of 100 emails up to 500, a pause after a contact import, a manual check of words that look like spam, and a short automatic check after very high newsletter volume. It says resending doesn't help.
Can I send from a Gmail address?
No. Since July 16, 2024, systeme.io doesn't allow @gmail.com sender addresses, and domain authentication is mandatory for sending.
What open rate does systeme.io expect?
Above 20% for the green pool. Between 10% and 20% is the yellow band, and below 10% puts an account in the high-risk pool.
Can I use my own email service with systeme.io?
You can send through your own SendGrid account, connect ActiveCampaign, or link other tools through Zapier.
Does importing my list cause problems?
It can pause sending while systeme.io checks the list's origin and quality. Purchased or scraped contacts aren't allowed.
About the author: Tess Morrow is the editorial pen name of the Email MK Tools research team. We price email marketing, funnel and course tools from each vendor's own pricing page, help center and terms, date every figure, and correct a guide when a price or rule changes. More about Tess.
Sources (checked October 8, 2026)
- systeme.io help, How to improve the deliverability of my emails (advanced tips), Mar 25, 2026: https://help.systeme.io/article/1643-how-to-improve-the-deliverability-of-my-emails-advanced-tips
- systeme.io help, Why aren't my emails being sent? (Jun 29, 2026): https://help.systeme.io/article/227-my-emails-are-not-being-sent
- systeme.io help, How to authenticate your domain name for email sending: https://help.systeme.io/article/316-how-to-authenticate-your-personal-domain-name
- systeme.io help, personal email addresses: https://help.systeme.io/article/272-is-it-possible-to-use-a-private-email-address-to-send-emails-from-systemeio
- systeme.io help, General guidelines for the first few days: https://help.systeme.io/article/4247-general-guidelines-and-best-practices-for-email-deliverability-during-the-first-few-days
- systeme.io help, How to manually clean your email list: https://help.systeme.io/article/139-how-to-manually-clean-your-email-list
- systeme.io help, Why did my open rate change after switching: https://help.systeme.io/article/3733-why-did-my-open-rate-change-after-switching-to-systeme-io
- systeme.io help, Which links are not allowed: https://help.systeme.io/article/3730-which-links-are-not-allowed-in-emails-sent-from-systeme-io
- systeme.io help, SendGrid: https://help.systeme.io/article/637-how-to-send-emails-with-your-own-sendgrid-account · external autoresponders: https://help.systeme.io/article/628-is-it-possible-to-integrate-systeme-io-with-an-external-autoresponder
- systeme.io help, footer badge: https://help.systeme.io/article/2008-how-to-remove-sent-with-systemeio-and-customize-your-email-footer · resend to non-openers: https://help.systeme.io/article/289-how-to-resend-a-newsletter-for-those-who-didn-t-open-it
- systeme.io pricing: https://systeme.io/pricing · systeme.io email page: https://systeme.io/email-marketing
- Trustpilot, systeme.io (header figures read October 8, 2026): https://www.trustpilot.com/review/systeme.io
- Trustpilot reviews and replies quoted: https://www.trustpilot.com/reviews/67dd31e65eeee1bd4d634dd8 (Mar 2025, reply Apr 2025) · https://www.trustpilot.com/reviews/699d66b98a42370760a70e96 (Feb 2026, reply Mar 2026) · https://www.trustpilot.com/reviews/676ad0581af123fe60bb52d3 (Dec 2024) · https://www.trustpilot.com/reviews/66acc3fa6a741869c6a09e20 (Aug 2024) · https://www.trustpilot.com/reviews/6ac248c6478516b285e08b13 (Oct 2026)
- First-hand review, Softailed (updated June 8, 2026): https://softailed.com/blog/systeme-io-review
- First-hand review, BlogRecode, Mia Elvasia (December 20, 2025, updated September 30, 2026; systeme.io reply September 25, 2026): https://blogrecode.com/systeme-io-review-the-budget-all-in-one-that-works/
- X, @SuperDivineUK (January 17, 2025): https://x.com/SuperDivineUK/status/1880348751958778025
- X, @AndieBibid (September 8, 2026): https://x.com/AndieBibid/status/2097331732257427735
- systeme.io help, bounce management: https://help.systeme.io/article/2924-grasping-and-navigating-bounce-management-on-systeme-io
- Reddit, r/systeme_io, thread on systeme.io's email marketing (February 2024; reply from a systeme.io affiliate): https://www.reddit.com/r/systeme_io/comments/1agkdwy/