# Open Source CMS

#### Professional message delivery from your server

Open Source Content Management Systems (CMS) such as WordPress, Joomla!, or PrestaShop offer extensive configuration freedom but often face challenges with email delivery. By default, these systems use web server functions like PHP Mail. This method fails to provide the reputation or security standards required by modern mailbox providers like Gmail, WP, or Onet.

Connecting the MessageFlow SMTP server to your CMS is the simplest way to bypass the limitations of shared hosting.

### Why replace default delivery with MessageFlow?

* **Bypass the SPAM folder**: Mailbox providers often treat messages sent directly from a website server (localhost) as suspicious. Routing them through an authorized MessageFlow SMTP server with correct SPF and DKIM records drastically increases their credibility.
* **Delivery speed**: The infrastructure is optimized for the rapid delivery of transactional notifications such as order confirmations or password resets. This speed is essential for maintaining customer trust.
* **Full control**: Use the MessageFlow dashboard to track the status of every message generated by your store or website. Confirm whether a customer received the email, opened it, or clicked a link.

### How integration works

Most CMS systems allow you to configure an external SMTP server in two ways:

* **Natively**: Configure the settings directly within the system (e.g., in Joomla! or PrestaShop).
* **Via Plugin**: Install a free SMTP add-on (e.g., in WordPress / WooCommerce).

In both cases, simply enter the `smtp.messageflow.com` server details along with your login and password.

### Available instructions

Select your system to view detailed configuration steps:

<table data-view="cards"><thead><tr><th></th><th data-hidden></th><th data-hidden data-card-cover data-type="image"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><em>Global server settings configuration.</em></td><td></td><td data-object-fit="contain"><a href="/files/XcHVjhhUi66esvlQhL2v">/files/XcHVjhhUi66esvlQhL2v</a></td><td><a href="/pages/NNxi1fcdZN6Z6Q3ty9zM">/pages/NNxi1fcdZN6Z6Q3ty9zM</a></td></tr><tr><td><em>Native configuration in the store administration panel</em></td><td></td><td data-object-fit="contain"><a href="/files/vhXucNLsMq9eYsrauSUe">/files/vhXucNLsMq9eYsrauSUe</a></td><td><a href="/pages/DzvW9dM4e97UYFrR0cTU">/pages/DzvW9dM4e97UYFrR0cTU</a></td></tr><tr><td><em>Configuration using popular SMTP plugins</em></td><td></td><td data-object-fit="contain"><a href="/files/cQP6Fxot5S9hQIDe7CSe">/files/cQP6Fxot5S9hQIDe7CSe</a></td><td><a href="/pages/y9yBMcsnCkGeMMk8Aaht">/pages/y9yBMcsnCkGeMMk8Aaht</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.messageflow.com/integrations/e-commerce-and-cms/open-source-cms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.