Loading
In this article, we explain why using a personal email address (such as Gmail, Yahoo, or Outlook) to send emails via systeme.io is no longer recommended. We will also outline the steps you need to take, current limitations, and best practices to ensure your messages reach your customers' inboxes.
Due to new security policies implemented by major email providers, using free "freemail" domains to send emails from third-party platforms is now heavily restricted or prohibited.
Starting in early 2024, major providers (specifically Google and Yahoo) strengthened their security policies to combat:
These new rules make using free email addresses much more restrictive when they are used to send emails through external software, such as an autoresponder.
The result:
Currently, only certain Microsoft domains remain technically "authorized" for use:
⚠️ Important: Even though these domains are currently allowed, we strongly advise against using them. Their use often leads to significant deliverability issues, meaning your emails are less likely to be seen by your customers.
The following free domains can no longer be used as your sender's address:
Gmail
As of July 16, 2024, it is no longer possible to use an @gmail.com address to send emails to your list via systeme.io.
This restriction follows Google’s 2024 policy updates since February 1, 2024, which significantly strengthen the requirements for email senders.
When you send a large number of emails (particularly more than 5,000 emails per day), Gmail considers you a bulk sender, which greatly increases the risk:
To protect the overall deliverability of our platform and your account, using a Gmail address as a sender is now prohibited.
Yahoo
Yahoo applies a strict authentication policy called DMARC. This policy prohibits emails using an @yahoo.com address from being sent through external servers. If you attempt to send an email via systeme.io using a Yahoo address:
LaPoste
The domain laposte.net is protected by a strict DMARC policy. This means that emails sent from an address on this domain via an external platform may be automatically blocked.
Zoho (ZohoMail)
The domain ZohoMail also applies a restrictive DMARC policy, preventing their addresses from being used via third-party services.
ProtonMail
ProtonMail enforces a quarantine policy for emails sent from outside its servers. Emails sent from a @protonmail.com address via an external service risk being placed directly in the spam folder.
To ensure the best possible deliverability, we strongly recommend using a professional email address associated with your custom domain name.
Example: contact@yourdomain.com
This solution allows you to:
To send emails with a professional address on systeme.io, you must authenticate your domain. This process confirms to email providers that you are authorized to send emails from that domain.
To improve the reliability of transactional emails (automated system emails) sent from our platform, we have introduced a new automatic feature.
Automatic assignment of a sender's address:
If a user does not have a valid professional sender's address, one will be automatically generated using the domain: systemeapp.com.
How it works:
Transactional emails will be sent from an address automatically generated using the following format:
useremail@transactional.systemeapp.com
Example:
If a user signs up with: example@gmail.com and does not have a custom domain configured, transactional emails will be sent from:
example=gmail.com@transactional.systemeapp.com
Reply-to management:
A "Reply-To" field is automatically added so that any replies from your customers are sent back to your original personal address (e.g., example@gmail.com).
Important details:
- This feature applies only to transactional emails
- It runs entirely in the background
- It does not appear in the user’s dashboard
Why this update is essential
Moving toward professional domain authentication allows you to:
Last updated on April 9, 2026