Flarepipe Email for Cloudflare

Flarepipe Email intercepts all outbound WordPress emails (password resets, WooCommerce receipts, form submissions) and routes them through the native Cloudflare Email API, using the Cloudflare account you already have. There is no SMTP server to configure and no separate mail service to pay for. Why use Cloudflare for Email? If your domain is already using Cloudflare for DNS, you already have access to their highly-reputable, enterprise-grade email sending infrastructure for a fraction of the cost of SendGrid or Mailgun. This plugin makes it possible to connect WordPress directly to Cloudflare's /email/sending/send endpoint. Third-Party Services This plugin relies on the Cloudflare Email Service API to function. When an email is sent via WordPress, the plugin processes the email and transmits the recipient address, sender address, subject line, and the body content payload securely over HTTPS directly to Cloudflare's servers (api.cloudflare.com/client/v4/accounts/{account_id}/email/sending/send). No data is sent to our servers. By using this plugin, you agree to Cloudflare's Terms of Service and Cloudflare's Privacy Policy. Features

• Zero Overhead: No heavy, bloated libraries. The plugin hooks directly into pre_wp_mail for instantaneous delivery.
• Email Logging: A beautiful, native WordPress interface safely logs all sent emails and any Cloudflare API connectivity errors without bloating your main options tables. The most recent 100 entries are kept by default; developers can raise, lower, or disable the limit with the flarepipe_email_log_retention_limit filter.
• Test Utility: Quickly test your Cloudflare API tokens directly from the settings page.
• 100% Native: Uses Core WordPress HTTP APIs to ensure maximum compatibility and speed.

Independence Flarepipe Email is an independent project by Six Foot 3. It is not affiliated with, endorsed by, or sponsored by Automattic Inc., the WordPress Foundation, or Cloudflare, Inc. Cloudflare is a registered trademark of Cloudflare, Inc., used here only to describe the service this plugin integrates with.

1. Upload the entire flarepipe-email folder to the /wp-content/plugins/ directory.
2. Activate the plugin through the 'Plugins' menu in WordPress.
3. Navigate to Flarepipe Email in the admin sidebar.
4. Enter your Cloudflare API Token, Account ID, and Sending Domain.
5. Send a Test Email to verify the connection is active.

(Note: Ensure your Cloudflare API Token has the "Account > Email Sending > Edit" permission enabled).

1.2.1

• New plugin icon and banner built around the Flarepipe send mark.
• Readme wording and tags now describe the plugin by what it does rather than by comparison to SMTP plugins.

1.2.0

• Everything the plugin declares now uses the flarepipe_email_ / Flarepipe_Email_ prefix: classes, functions, options, database tables, the REST namespace, settings groups, form actions and the dashboard widget. Existing installs are migrated automatically on upgrade, so settings, logs and stored credentials carry over with no reconfiguration.
• Breaking: the wp-config.php constants WPFLAREMAIL_CF_API_TOKEN, WPFLAREMAIL_API_TOKEN and WPFLAREMAIL_CF_ACCOUNT_ID are no longer read. Rename them to FLAREPIPE_CF_API_TOKEN and FLAREPIPE_CF_ACCOUNT_ID.
• Breaking: the wpflaremail_log_retention_limit filter has been removed. Use flarepipe_email_log_retention_limit.
• Fixed the Account ID field ignoring the documented FLAREPIPE_CF_ACCOUNT_ID constant, which left the field editable and let a saved value override wp-config.php.
• Fixed Export CSV emitting PHP deprecation notices into the downloaded file on PHP 8.4.

1.1.1

• Renamed the plugin to Flarepipe Email for Cloudflare.
• URLs printed into inline JavaScript are now output with wp_json_encode for context-correct escaping.
• Made the log retention limit filterable.
• Added an independence statement to the readme.

1.1.0

• Added a WordPress dashboard widget showing the most recent outbound emails.
• Added support for wp-config.php credential constants. When defined, settings fields are masked and credentials are never written to the database.
• Removed the self-update mechanism and email footer branding in preparation for WordPress.org review.
• Raised the minimum required WordPress version to 6.0.

1.0.1

• Fixed setup wizard rejecting valid credentials with "Please fill out all API Configuration fields" due to mismatched form field identifiers.

1.0.0

• Initial public release.
• Implemented core wp_remote_post integration with Cloudflare /email/routing/send.
• Added database table logging and Test Email functionalities.