> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/faq/faq-generale/email-dans-le-spam-et-probleme-de-delivrance.md).

# Email in spam and delivery problem

### Introduction

Sending emails is a key element of communicating with your customers. However, ensuring that these emails land in the inbox and not the spam folder is crucial. In this guide, we explain the factors that influence email deliverability, how to test their quality, and what actions to take if you encounter problems.

### **Understanding email delivery**:

Email deliverability is influenced by several factors, including sender reputation, email authentication, and message content. Using Mailjet, a specialist provider, helps optimize these aspects through respectful sending practices and authentication tools like SPF and DKIM, which improve sender reputation. All emails sent by Yoplanning adhere to its technical specifications.

### **Importance of email content**:

The content of your emails has a significant impact on deliverability. Avoid using overly commercial language, suspicious links, or concealing important information, as this can trigger spam filters.

### **The most effective lever: sending from your own domain**

An email sent from `info@yoplanning.com` remains, for the filters, an email sent by a third party on behalf of your organization. By [connecting your domain name](/en/yoplanning-academy/yoplanning-parametrage/communication-client/connecter-votre-domaine-pour-lenvoi-demails.md), your emails originate from your own domain and are authenticated in the name of your domain: this action has the greatest impact on deliverability.

This option also provides access to the **Emails** tab of the **History**, which indicates whether each email was successfully delivered—allowing you to distinguish between a blocked email and one simply marked as spam. It is a paid service, charged per email sent.

### **Test your deliverability with Mail-tester.com**:

Use the online tool <https://www.mail-tester.com/> to assess the quality of your emails. This tool provides a deliverability score and recommendations for improving your emails. Make sure the score is high enough to ensure good deliverability.

### **What to do if everything is correct, but the problem persists?** :‍♂️

If, despite a high score on Mail-tester and the use of best practices, your emails are still ending up in spam, the problem may lie with the recipient sorting rules. Unfortunately, in this case, your options are limited because each email service provider has its own criteria for filtering spam.

### **Usage tips and best practices**:

* Encourage your customers to add your email address to their contact list.
* Ask them to check their spam folder and mark your emails as "not spam" if they are there.
* Inform your customers during registration or purchase that your communications may land in spam and to take the necessary steps to ensure they receive emails.

### Conclusion

Optimizing email deliverability is an ongoing process. By following best practices, regularly testing your emails, and raising awareness among your customers, you will significantly reduce the risk of your messages being filtered as spam. Over time, filtering systems adapt, and the situation can gradually improve. By applying these recommendations, you will maximize your chances of effectively reaching your audience.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.yoplanning.support/en/faq/faq-generale/email-dans-le-spam-et-probleme-de-delivrance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
