[Skip to content](#main)

[→](/)

[![Avunu](/brand/avunu-logo.svg)![Avunu](/brand/avunu-logo-light.svg)](/)[Services](/services/)[Consulting](/services/consulting/)[ERP](/services/erp/)[Odoo](/services/erp/odoo/)[ERPNext](/services/erp/erpnext/)[Custom software](/services/custom-software/)[Devices & IoT](/services/devices-iot/)[Websites](/services/websites/)[Infrastructure](/services/infrastructure/)[Partners](/partners/)

[Work](/work/)[Open source](/open-source/)[Knowledge base](/kb/)[About](/about/)

[About Avunu](/about/)[Team](/about/team/)[Insights](/insights/)[Contact](/contact/)

[Client portal](https://erp.avunu.net/projects)[Start a project](/start/)

- [Services](/services/)[Consulting](/services/consulting/)
- [ERP](/services/erp/)
- [Odoo](/services/erp/odoo/)
- [ERPNext](/services/erp/erpnext/)
- [Custom software](/services/custom-software/)
- [Devices & IoT](/services/devices-iot/)
- [Websites](/services/websites/)
- [Infrastructure](/services/infrastructure/)
- [Partners](/partners/)

[Work](/work/)[Open source](/open-source/)[Knowledge base](/kb/)[About](/about/)

- [About Avunu](/about/)
- [Team](/about/team/)
- [Insights](/insights/)
- [Contact](/contact/)

[Client portal](https://erp.avunu.net/projects)[Start a project](/start/)

[Knowledge base](/kb/)[Email](/kb/email/)Send WordPress email through Cloudflare Email Sending

Search the knowledge basePress/

ESC

Jump to

[Browse the knowledge base](/kb/)[Frappe](/kb/frappe/)[ERPNext](/kb/erpnext/)[Odoo](/kb/odoo/)[WordPress](/kb/wordpress/)[NixOS](/kb/nixos/)[Email](/kb/email/)[Linux](/kb/linux/)[Databases](/kb/databases/)[Containers](/kb/containers/)[Proxmox](/kb/proxmox/)[Git & Dev Tools](/kb/git-and-dev-tools/)

↵select↑↓navigateescclose

Search the knowledge base

[Skip to the article](#kb-article)[Email](/kb/email/)6 articles

- [Overview](/kb/email/)
- [Deploy the cloudflare-email-relay Worker](/kb/email/deploying-cloudflare-email-relay/)
- [Email without SMTP for business systems](/kb/email/email-without-smtp-for-business-systems/)
- [Send and receive Frappe and ERPNext email through Cloudflare](/kb/email/cloudflare-email-for-frappe-and-erpnext/)
- [Send and receive Odoo email through Cloudflare](/kb/email/cloudflare-email-for-odoo/)
- [Send WordPress email through Cloudflare Email Sending](/kb/email/cloudflare-email-for-wordpress/)
- [Troubleshooting Cloudflare email delivery](/kb/email/troubleshooting-cloudflare-email/)

Other sections[Frappe](/kb/frappe/)[ERPNext](/kb/erpnext/)[Odoo](/kb/odoo/)[WordPress](/kb/wordpress/)[NixOS](/kb/nixos/)[Linux](/kb/linux/)[Databases](/kb/databases/)[Containers](/kb/containers/)[Proxmox](/kb/proxmox/)[Git & Dev Tools](/kb/git-and-dev-tools/)

In Email: 6 articles

[Overview](/kb/email/)[Deploy the cloudflare-email-relay Worker](/kb/email/deploying-cloudflare-email-relay/)[Email without SMTP for business systems](/kb/email/email-without-smtp-for-business-systems/)[Send and receive Frappe and ERPNext email through Cloudflare](/kb/email/cloudflare-email-for-frappe-and-erpnext/)[Send and receive Odoo email through Cloudflare](/kb/email/cloudflare-email-for-odoo/)[Send WordPress email through Cloudflare Email Sending](/kb/email/cloudflare-email-for-wordpress/)[Troubleshooting Cloudflare email delivery](/kb/email/troubleshooting-cloudflare-email/)

Other sections[Frappe](/kb/frappe/)[ERPNext](/kb/erpnext/)[Odoo](/kb/odoo/)[WordPress](/kb/wordpress/)[NixOS](/kb/nixos/)[Linux](/kb/linux/)[Databases](/kb/databases/)[Containers](/kb/containers/)[Proxmox](/kb/proxmox/)[Git & Dev Tools](/kb/git-and-dev-tools/)

EmailSend WordPress email through Cloudflare Email Sending

Install the Cloudflare Email plugin to route every wp_mail() message through Cloudflare Email Sending, then use its log viewer, WP-CLI checks and updates.

UpdatedOct 5, 2026

Applies toCloudflare Email plugin 0.1.4WordPress 7.0PHP 8.4

Tagsemailcloudflarewordpresswp-mail

Reading time9 min

On this page[How it works](#how-it-works)[Requirements](#requirements)[Install the plugin](#install-the-plugin)[Configure wp-config.php](#configure-wp-configphp)[When the constants are missing](#when-the-constants-are-missing)[Adjust the outgoing payload](#adjust-the-outgoing-payload)[Verify the setup](#verify-the-setup)[Use the log viewer](#use-the-log-viewer)[What a resend can and cannot restore](#what-a-resend-can-and-cannot-restore)[Retention](#retention)[Limits and behavior to know about](#limits-and-behavior-to-know-about)[Updates](#updates)[Troubleshooting](#troubleshooting)[Mail still goes out the old way](#mail-still-goes-out-the-old-way)[A send is logged as failed](#a-send-is-logged-as-failed)[Plugin error about missing dependencies](#plugin-error-about-missing-dependencies)[The log viewer shows an error about missing assets](#the-log-viewer-shows-an-error-about-missing-assets)[Entries disappear sooner than expected](#entries-disappear-sooner-than-expected)[Successful sends are missing from the log](#successful-sends-are-missing-from-the-log)[Related documents](#related-documents)

Cloudflare Email is an Avunu plugin that sends every message WordPress produces through the Cloudflare Email Sending API instead of the server's own mail transport, and keeps a searchable log of what was sent. Use it when you want WordPress mail to leave from a verified domain without running an SMTP relay. For how it fits with the Odoo and Frappe integrations, see [Email Without SMTP for Business Systems](/kb/email/email-without-smtp-for-business-systems/).

The plugin has no settings screen. You configure it with constants in `wp-config.php`, and the only screen it adds is the log viewer.

## How it works

The plugin does not replace `wp_mail()`. When WordPress is about to send a message, the plugin swaps the global PHPMailer object for a subclass of WordPress's own bundled PHPMailer. Core then parses the recipients, headers, subject, body and attachments as it always does. When core calls `send()`, the plugin posts the message to Cloudflare over the WordPress HTTP API instead of using SMTP or `mail()`.

Because core does the parsing, every plugin and theme that sends mail is routed automatically. Cc, Bcc, Reply-To, custom headers and inline images are preserved. The `wp_mail_succeeded` and `wp_mail_failed` actions still fire.

There is no fallback. If Cloudflare rejects a message, the send is logged as failed and `wp_mail()` returns `false`.

## Requirements

WordPress 7.0 or later and PHP 8.4 or later. These are the values in the plugin header, which WordPress enforces when you activate the plugin.

A Cloudflare account with Email Sending enabled for your sending domain. Onboarding the domain and its deliverability records (SPF, DKIM, DMARC) happens in Cloudflare. Follow [Cloudflare's Email Service documentation](https://developers.cloudflare.com/email-service/) for that part. The plugin only sends.

A Cloudflare API token with the **Email Sending: Edit** permission, plus your Cloudflare account ID. In the dashboard, open any domain's *Overview* page and find the account ID under *API*.

Optional: [WP-CLI](https://wp-cli.org/) for the verification commands below.

## Install the plugin

The plugin is distributed as a zip attached to each [GitHub release](https://github.com/Avunu/wordpress-cloudflare-email/releases). The zip bundles its PHP dependencies and the compiled log viewer, so you do not need Composer or Node on the server.

Download `cloudflare-email.zip` from the latest release.

In wp-admin, go to **Plugins**, then **Add New Plugin**, then **Upload Plugin**, and upload the zip. Alternatively, extract it into `wp-content/plugins/` so the folder is `wp-content/plugins/cloudflare-email/`.

Activate the plugin.

You can also install from the command line. Run this in the WordPress root:

```
<span style="--shiki-dark:#FFA657;--shiki-light:#953800">wp</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">plugin</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">install</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">https://github.com/Avunu/wordpress-cloudflare-email/releases/latest/download/cloudflare-email.zip</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">--activate</span>
```

Activation creates the log table and schedules a daily cleanup job. The plugin also creates the table on its own if it is missing, which covers in-place updates and databases imported from another environment.

Warning

Do not install from a source checkout or GitHub's "Source code" archive. Those do not contain `vendor/` or `build/`. Without `vendor/` the plugin shows an admin error asking you to run `composer install` or use the release zip, and does nothing else.

## Configure wp-config.php

Add the constants to `wp-config.php`, above the line that tells you to stop editing. [wp-config Reference](/kb/wordpress/wp-config-reference/) lists the other constants we set most often.

```
<span style="--shiki-dark:#8B949E;--shiki-light:#6E7781">// Required</span>
<span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">define</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">(</span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">'CLOUDFLARE_EMAIL_ACCOUNT_ID'</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">, </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">'<CLOUDFLARE_ACCOUNT_ID>'</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">);</span>
<span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">define</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">(</span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">'CLOUDFLARE_EMAIL_API_TOKEN'</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">, </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">'<CLOUDFLARE_API_TOKEN>'</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">);</span>

<span style="--shiki-dark:#8B949E;--shiki-light:#6E7781">// Recommended: the From domain must be onboarded to Cloudflare Email Sending</span>
<span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">define</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">(</span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">'CLOUDFLARE_EMAIL_FROM'</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">, </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">'no-reply@example.com'</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">);</span>
<span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">define</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">(</span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">'CLOUDFLARE_EMAIL_FROM_NAME'</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">, </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">'Example Site'</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">);</span>

<span style="--shiki-dark:#8B949E;--shiki-light:#6E7781">// Optional</span>
<span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">define</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">(</span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">'CLOUDFLARE_EMAIL_LOG'</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">, </span><span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">false</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">);</span>
<span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">define</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">(</span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">'CLOUDFLARE_EMAIL_LOG_RETENTION_DAYS'</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">, </span><span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">30</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">);</span>
```

| Constant                              | Required    | Behavior                                                                                     |
| ------------------------------------- | ----------- | -------------------------------------------------------------------------------------------- |
| `CLOUDFLARE_EMAIL_ACCOUNT_ID`         | yes         | Your Cloudflare account ID.                                                                  |
| `CLOUDFLARE_EMAIL_API_TOKEN`          | yes         | The API token used to send.                                                                  |
| `CLOUDFLARE_EMAIL_FROM`               | recommended | Forces the From address through the `wp_mail_from` filter.                                   |
| `CLOUDFLARE_EMAIL_FROM_NAME`          | recommended | Forces the From name through the `wp_mail_from_name` filter.                                 |
| `CLOUDFLARE_EMAIL_LOG`                | no          | Set to `false` to stop logging successful sends. Defaults to on. Failures are always logged. |
| `CLOUDFLARE_EMAIL_LOG_RETENTION_DAYS` | no          | Days to keep log rows. Defaults to 30. `0` keeps them forever.                               |

Set the From address explicitly. If you do not, WordPress defaults to `wordpress@` plus your site's domain, which is usually not onboarded to Cloudflare, so Cloudflare is likely to reject the message.

Tip

Keep the token out of version control. Because `wp-config.php` is plain PHP, you can pass the value in from the server environment, for example `define('CLOUDFLARE_EMAIL_API_TOKEN', getenv('CLOUDFLARE_API_TOKEN'));`. The plugin trims whitespace and treats an empty value as not configured.

### When the constants are missing

If the account ID or token is absent, the plugin does not intercept anything and WordPress mail continues through its normal transport. In production (`WP_ENVIRONMENT_TYPE` set to `production`, or not set at all, since that is WordPress's default), administrators with `manage_options` see a warning notice in wp-admin saying the plugin is not configured. In any other environment type the plugin stays quiet, because a development machine catching mail locally or a staging site with no Cloudflare account is the expected state.

The log viewer stays available even when the credentials are removed, so you can still review past sends.

### Adjust the outgoing payload

Cloudflare can reject a message for reasons the plugin cannot predict, such as a custom header it does not allow. The `cloudflare_email_payload` filter gives you the final payload, and the mailer object, just before it is sent:

```
<span style="--shiki-dark:#D2A8FF;--shiki-light:#8250DF">add_filter</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">(</span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">'cloudflare_email_payload'</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">, </span><span style="--shiki-dark:#FF7B72;--shiki-light:#CF222E">function</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> (</span><span style="--shiki-dark:#FF7B72;--shiki-light:#CF222E">array</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> $payload) {</span>
<span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">    </span><span style="--shiki-dark:#79C0FF;--shiki-light:#0550AE">unset</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">($payload[</span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">'headers'</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">][</span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">'X-Some-Header'</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">]);</span>
<span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">    </span><span style="--shiki-dark:#FF7B72;--shiki-light:#CF222E">return</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> $payload;</span>
<span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328">});</span>
```

## Verify the setup

With WP-CLI, run these from the WordPress root (the [WP-CLI Cookbook](/kb/wordpress/wp-cli-cookbook/) has more day-to-day commands):

```
<span style="--shiki-dark:#FFA657;--shiki-light:#953800">wp</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">cloudflare-email</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">verify</span>
<span style="--shiki-dark:#FFA657;--shiki-light:#953800">wp</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">cloudflare-email</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">send-test</span><span style="--shiki-dark:#E6EDF3;--shiki-light:#1F2328"> </span><span style="--shiki-dark:#A5D6FF;--shiki-light:#0A3069">jane@example.com</span>
```

`verify` prints the configured account ID and From address, then asks Cloudflare whether the token is active. It checks the token only. It does not prove that your From domain is onboarded, so a passing `verify` can still be followed by a rejected send.

`send-test` sends a small HTML message through the normal `wp_mail()` path, so it also exercises the From filters and the log. It requires a valid email address. After it runs, open **Tools**, then **Cloudflare Email** in wp-admin to see the entry.

## Use the log viewer

The log viewer is at **Tools**, then **Cloudflare Email**. It is visible to users with the `manage_options` capability, which means administrators on a standard install.

The table shows date, status, From and To, titled by subject. You can search across From, To and Subject, filter by status (`sent` or `failed`), sort by date, status, From or Subject, and page through the results. Each row has three actions:

**View** opens the full record: status, resend count, recipients, Cc, Bcc, Reply-To, attachment names and the body. HTML bodies render in a sandboxed frame. A failed entry shows the error Cloudflare returned.

**Resend** sends the logged message again through `wp_mail()`. The original row is updated with the new status and its resend count goes up. No duplicate row is created.

**Delete** removes one entry, or several at once when you select multiple rows. It asks for confirmation and cannot be undone.

Note

The log stores the full message body, so treat it as sensitive. Password-reset and similar emails are stored like any other. Lower `CLOUDFLARE_EMAIL_LOG_RETENTION_DAYS`, or set `CLOUDFLARE_EMAIL_LOG` to `false` if that is a concern. Failures are logged regardless of the second setting.

### What a resend can and cannot restore

The log keeps attachment file paths, not file contents. A resend re-attaches a file only if it is still readable at that path. If it is gone, the message is resent without it. Attachments created from in-memory strings have no path and are not restored.

A resend rebuilds the headers from what was logged: From, content type, Cc, Bcc, Reply-To and custom headers.

### Retention

Rows older than the retention window are deleted by a daily WP-Cron job named `cloudflare_email_prune`, which activation schedules. Cleanup depends on WP-Cron actually running. See [WordPress Cron](/kb/wordpress/wordpress-cron/) if your site disables it in favor of a system cron.

## Limits and behavior to know about

A message needs at least one To recipient.

To, Cc and Bcc together are limited to 50 recipients per message. The plugin refuses larger sends with an error before calling Cloudflare.

Only the first Reply-To address is sent.

HTML messages are sent as HTML, with the plain-text alternative included when WordPress provides one. Other messages are sent as text.

An attachment that cannot be read, or is empty, is skipped rather than failing the send.

Inline images keep their `cid:` references.

The API call has a 30 second timeout.

## Updates

The plugin updates itself from GitHub releases using the [plugin-update-checker](https://github.com/YahnisElsts/plugin-update-checker) library. New versions show up in the normal WordPress update screens, and the update downloads the `cloudflare-email.zip` asset from the release rather than GitHub's source archive. That asset is the one with the dependencies and the built log viewer inside.

Releases are cut from the repository's `main` branch through Release Please, which tags the version and attaches the zip. You do not need to do anything on the site beyond updating when WordPress offers it.

## Troubleshooting

For errors that span platforms, such as sender domains, token errors and Cloudflare limits, see [Troubleshooting Cloudflare Email](/kb/email/troubleshooting-cloudflare-email/).

### Mail still goes out the old way

The plugin only intercepts mail when both required constants are non-empty. Run `wp cloudflare-email verify`. If it says the plugin is not configured, check that the constants are in `wp-config.php` and spelled exactly as shown.

### A send is logged as failed

Open the entry with **View** and read the error. It is Cloudflare's own message, prefixed with `Cloudflare API error` and the HTTP status. The most common causes are:

The From domain is not onboarded to Email Sending. Set `CLOUDFLARE_EMAIL_FROM` to an address on a domain you have onboarded.

The token is invalid or lacks permission. Run `wp cloudflare-email verify`.

A custom header was rejected. Remove it with the `cloudflare_email_payload` filter.

Network errors, such as a blocked outbound HTTPS connection, appear in the log as the underlying WordPress HTTP error message.

### Plugin error about missing dependencies

You installed from source or a repository archive. Reinstall from the release zip.

### The log viewer shows an error about missing assets

The built viewer files in `build/` are missing. Reinstall from the release zip. In a development checkout you would run `npm run build` instead.

### Entries disappear sooner than expected

The default retention is 30 days. Set `CLOUDFLARE_EMAIL_LOG_RETENTION_DAYS` to a larger number, or `0` to keep entries forever.

### Successful sends are missing from the log

Check whether `CLOUDFLARE_EMAIL_LOG` is set to `false`. Only failures are recorded in that mode.

## Related documents

[Email Without SMTP for Business Systems](/kb/email/email-without-smtp-for-business-systems/): the architecture and its limits.

[Cloudflare Email for Odoo](/kb/email/cloudflare-email-for-odoo/) and [Cloudflare Email for Frappe and ERPNext](/kb/email/cloudflare-email-for-frappe-and-erpnext/): the inbound and outbound integrations for the two ERPs.

[Troubleshooting Cloudflare Email](/kb/email/troubleshooting-cloudflare-email/): symptom-first checks across all three platforms.

Sources

- [github.com/Avunu/wordpress-cloudflare-email](https://github.com/Avunu/wordpress-cloudflare-email)
- [developers.cloudflare.com/email-service](https://developers.cloudflare.com/email-service/)
- [developers.cloudflare.com/api/resources/email_sending/methods/send](https://developers.cloudflare.com/api/resources/email_sending/methods/send)
- [github.com/YahnisElsts/plugin-update-checker](https://github.com/YahnisElsts/plugin-update-checker)

Need help with business email?

Our notes can take you a long way, but sometimes you'd rather have someone who's done it before.

[Managed infrastructure](/services/infrastructure/)

[← PreviousSend and receive Odoo email through Cloudflare](/kb/email/cloudflare-email-for-odoo/)[Next →Troubleshooting Cloudflare email delivery](/kb/email/troubleshooting-cloudflare-email/)

CC0This article is in the public domain ([CC0 1.0](https://creativecommons.org/publicdomain/zero/1.0/)), code samples included. Use it however helps you.

On this page

- [How it works](#how-it-works)
- [Requirements](#requirements)
- [Install the plugin](#install-the-plugin)
- [Configure wp-config.php](#configure-wp-configphp)
- [When the constants are missing](#when-the-constants-are-missing)
- [Adjust the outgoing payload](#adjust-the-outgoing-payload)
- [Verify the setup](#verify-the-setup)
- [Use the log viewer](#use-the-log-viewer)
- [What a resend can and cannot restore](#what-a-resend-can-and-cannot-restore)
- [Retention](#retention)
- [Limits and behavior to know about](#limits-and-behavior-to-know-about)
- [Updates](#updates)
- [Troubleshooting](#troubleshooting)
- [Mail still goes out the old way](#mail-still-goes-out-the-old-way)
- [A send is logged as failed](#a-send-is-logged-as-failed)
- [Plugin error about missing dependencies](#plugin-error-about-missing-dependencies)
- [The log viewer shows an error about missing assets](#the-log-viewer-shows-an-error-about-missing-assets)
- [Entries disappear sooner than expected](#entries-disappear-sooner-than-expected)
- [Successful sends are missing from the log](#successful-sends-are-missing-from-the-log)
- [Related documents](#related-documents)

[Back to top↑](#top)

Services

- [ERP implementation](/services/erp/)
- [Odoo](/services/erp/odoo/)
- [ERPNext](/services/erp/erpnext/)
- [Custom software](/services/custom-software/)
- [Devices & IoT](/services/devices-iot/)
- [Websites](/services/websites/)
- [Infrastructure](/services/infrastructure/)

Resources

- [Our work](/work/)
- [Open source](/open-source/)
- [Knowledge base](/kb/)
- [Insights](/insights/)

Company

- [About](/about/)
- [Team](/about/team/)
- [Partners](/partners/)
- [Contact](/contact/)

Clients

- [Project portal](https://erp.avunu.net/projects)
- [Invoices](https://erp.avunu.net/)
- [Support](https://erp.avunu.net/)

[![Avunu](/brand/avunu-logo-light.svg)](/)[\<av-icon data-jx-static>\<svg viewBox="0 0 24 24" width="20" height="20" fill="currentColor" stroke="none" stroke-width="1.6" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true" focusable="false">\<path d="M20.400 20.500h-3.600v-5.600c0-1.300 0-3-1.800-3s-2.100 1.400-2.100 2.900v5.700H9.400V9h3.400v1.600c.5-.9 1.600-1.900 3.400-1.900 3.600 0 4.300 2.400 4.300 5.500v6.300zM5.300 7.400a2.100 2.100 0 1 1 0-4.100 2.100 2.100 0 0 1 0 4.100zm1.800 13.100H3.600V9h3.500v11.500zM22.200 0H1.800C.8 0 0 .8 0 1.700v20.600c0 .9.800 1.700 1.800 1.700h20.400c1 0 1.800-.8 1.800-1.700V1.700C24 .8 23.200 0 22.200 0z">\</path>\</svg>\</av-icon>](https://www.linkedin.com/company/avunu)[\<av-icon data-jx-static>\<svg viewBox="0 0 24 24" width="20" height="20" fill="currentColor" stroke="none" stroke-width="1.6" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true" focusable="false">\<path d="M12 .3a12 12 0 0 0-3.8 23.4c.6.1.8-.3.8-.6v-2c-3.3.7-4-1.6-4-1.6-.6-1.4-1.4-1.8-1.4-1.8-1-.7.1-.7.1-.7 1.2.1 1.8 1.2 1.8 1.2 1 1.8 2.8 1.3 3.5 1 .1-.8.4-1.3.7-1.6-2.7-.3-5.5-1.3-5.5-5.9 0-1.3.5-2.4 1.2-3.2-.1-.3-.5-1.5.1-3.2 0 0 1-.3 3.3 1.2a11.500 11.500 0 0 1 6 0c2.300-1.500 3.300-1.200 3.300-1.200.6 1.700.2 2.900.1 3.200.8.8 1.200 1.900 1.200 3.200 0 4.600-2.800 5.600-5.500 5.900.4.400.8 1.100.8 2.200v3.300c0 .3.2.7.8.6A12 12 0 0 0 12 .3">\</path>\</svg>\</av-icon>](https://github.com/Avunu)[Client portal](https://erp.avunu.net/projects)[Start a project](/start/)

Avunu LLC · 948 East Philadelphia Street, York, PA 17403 · (717) 814-8540Knowledge base articles are in the public domain[Privacy](/privacy/)[Terms](/terms/)
