Is it possible to use a private email address to send emails from systeme.io ?

In this article, we explain whether you can use a personal email address (such as Gmail, Yahoo, Outlook, etc.) to send emails through systeme.io. We will also detail the steps you need to take, the current limitations, and best practices to ensure your messages reach your contacts' inboxes.

Due to new security policies implemented by major email providers, the use of personal "freemail" domains for sending emails from third-party platforms is now heavily restricted or prohibited.

Why are personal email addresses being restricted?

Starting in early 2024, major providers (specifically Google and Yahoo) strengthened their security policies to combat:

• Spam
• Identity spoofing
• Fraudulent emails

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:

• Emails may be blocked.
• Emails may be flagged as spam.
• In some cases, emails may be outright rejected by the recipient’s server.

Authorized domains (but not recommended)

Currently, only certain Microsoft domains remain technically "authorized" for use:

• Outlook.com / Outlook.fr
• Hotmail.com / Hotmail.fr
• Live.com / Live.fr

Prohibited free domains

The following free domains can no longer be used as your sender address:

Gmail

As of July 16, 2024, it is no longer possible to use a @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:

• Email rejection
• Spam filtering

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 a @yahoo.com address from being sent through external servers. If you attempt to send an email via systeme.io using a Yahoo address:

• The receiving servers will reject the email.
• The email will never reach its destination.

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.

The recommended solution: use a professional email address

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:

• Improve your brand credibility.
• Increase your email deliverability.
• Comply with current industry standards set by email providers.

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.

Automatic transactional email address

To improve the reliability of transactional emails (automated system emails) sent from our platform, we have introduced a new automatic functionality.

Automatic assignment of a sender address::

If a user does not have a valid professional sender address, an address 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).

Why this update is essential

Moving toward professional domain authentication allows you to:

• Stay compliant with industry standards.
• Improve your sending reputation.
• Avoid blocks from unauthenticated senders.
• Ensure reliable communication with your audience.