Inboxili for WordPress — Coming Soon

WordPress sends email with PHP's mail() unless something replaces it. On many hosts that means password resets and order emails that arrive late, land in spam, or never arrive. The Inboxili plugin is being built to replace that path with the Inboxili transactional API, from your own verified domain.

Status

| | | |---|---| | Release status | Coming soon | | Where | Not yet on WordPress.org | | Tested on a live WordPress site | Not yet | | Logic covered by automated tests | Yes, 18 unit tests |

What it is designed to do

• Take over wp_mail(). Anything that sends mail the standard way is sent through Inboxili: password resets, WooCommerce order emails, contact form notifications, membership plugins.
• Make setup short. Paste an API key, enter a From address on your verified domain, click Verify connection, then send a test email to yourself.
• Store the key carefully. Encrypted in the database, or kept out of it entirely with a constant in wp-config.php.
• Say what happened. A short log of recent emails with the result, and the standard wp_mail_failed action when a send fails.

What it cannot do

The Inboxili API sends one recipient per request and has no attachment or Reply-To field. The plugin handles these openly:

| WordPress feature | Plugin behaviour | |---|---| | Attachments | Hand the email back to WordPress (default), send without the attachment, or fail | | Reply-To | Print the address at the top of the email (default), hand back, or ignore | | Several recipients, Cc, Bcc | One separate email per address | | A From address you have not verified | Not possible. The configured verified address is used |

There is also no SMTP mode, and it cannot send from a domain you have not verified in Inboxili.

What to do before it is released

Fixing WordPress email is mostly about the domain, whichever tool sends it:

1. Read why WordPress emails do not send and work through the checks.
2. Verify your sending domain and publish SPF, DKIM and DMARC. The free SPF, DKIM and DMARC checkers show what is missing.
3. Create an Inboxili account so your domain and API key are ready on release day.

If you are a developer and cannot wait, the API is a single request, so a few lines of custom code can send from WordPress today:

<?php
// Example only: send one email from WordPress code through the Inboxili API.
$response = wp_remote_post( 'https://api.inboxili.com/api/v1/transactional/send', array(
	'timeout' => 10,
	'headers' => array(
		'Authorization' => 'Bearer ' . INBOXILI_API_KEY, // defined in wp-config.php
		'Content-Type'  => 'application/json',
	),
	'body'    => wp_json_encode( array(
		'to'         => 'ada@example.com',
		'from_email' => 'hello@yourdomain.com',
		'subject'    => 'Hello from WordPress',
		'html_body'  => '<p>Sent through the Inboxili API.</p>',
	) ),
) );

if ( is_wp_error( $response ) || 200 !== wp_remote_retrieve_response_code( $response ) ) {
	error_log( 'Inboxili send failed: ' . wp_remote_retrieve_body( $response ) );
}

Follow the release

Subscribe to product updates and you will hear when the plugin is available:

The newsletter covers all Inboxili product updates, not only WordPress.