codecasastudios

CodeCasaStudiosLtd

Casa Mail is an end-to-end email platform for WordPress sites. It intercepts every <code>wp_mail()</code> call and delivers it through the Casa Mail gateway operated by CodeCasa Studios on the OnlineStoreNotifications infrastructure (api.onlinestorenotifications.com). On top of reliable transactional delivery it adds a full marketing platform, branded webmail mailboxes, and one-click sender-domain authentication, all driven from the WordPress admin.
If your site doesn’t send mail reliably today, Casa Mail is the simplest way to start. If you’re already paying for an SMTP plugin plus a separate marketing tool plus a separate webmail provider, Casa Mail consolidates the three so you can run customer email, broadcasts, and inbox replies from one place.
<h4>What you get</h4>
Transactional email (every plan, including Free)
<ul>
<li>Every <code>wp_mail()</code> is routed through the Casa Mail gateway with DKIM, SPF, and aligned Return-Path on <code>onlinestorenotifications.com</code> (or your own domain after one-click authentication).</li>
<li>Durable retry outbox: if the gateway is briefly unreachable, the payload is persisted and retried automatically with 30s, 2m, 10m backoff. <code>wp_mail()</code> never blocks, never loses a message, never returns false to the caller.</li>
<li>Per-tenant inbox at <code><your-site>@onlinestorenotifications.com</code>. Replies to your customer emails come back to that inbox; on the Free tier they auto-forward to your contact address. On webmail-enabled plans you can also receive replies on your own domain (e.g. <code><your-inbox>@yourdomain.com</code>).</li>
<li>Paginated send log on the Logs page with up to 30 days of history retained (hard-capped at 2,000 rows per WordPress install). The Dashboard surfaces the most recent activity at a glance.</li>
<li>Optional default-From override so every site email uses one consistent sender.</li>
</ul>
Sender domain authentication (every plan)
<ul>
<li>Add your own domain in the admin and the plugin prints three DNS records (DKIM, SPF, Return-Path).</li>
<li>One-click “Check my domain” verifier. Once verified, customer emails go from <code><your-inbox>@yourdomain.com</code> so Gmail and Outlook show your brand in the From, not “via onlinestorenotifications.com”.</li>
<li>Inline plain-English helpers for Cloudflare, GoDaddy, Namecheap, and Google Domains. Cloudflare grey-cloud guidance for replies is built in.</li>
<li>Free plan can opt out of domain authentication entirely and send from the shared <code><your-inbox>@onlinestorenotifications.com</code> address with DKIM/SPF/Return-Path already configured on the gateway.</li>
</ul>
Marketing Studio (Growth and higher)
<ul>
<li>Contacts: add manually, import from CSV, or one-click sync your WooCommerce customer base.</li>
<li>Segments: saved queries (all contacts, contacts with a specific tag) with a sample-preview before you send.</li>
<li>Campaigns: schedule a broadcast to a segment, watch send progress on a per-campaign report (sent, opens, unique-by-contact open + click rate).</li>
<li>Composer: full block-based visual editor with heading / paragraph / image / button / divider / spacer / two-columns / raw-HTML blocks, per-block and global style settings, Visual / Source HTML / Wrapper / Preview tabs, desktop + mobile preview, 50-step undo/redo, emoji picker, drag-and-drop images into the WordPress media library, per-tenant saved templates.</li>
<li>Personalization tokens: <code>[FIRST_NAME]</code>, <code>[LAST_NAME]</code>, <code>[FULL_NAME]</code>, <code>[EMAIL]</code>, <code>[UNSUBSCRIBE_URL]</code>.</li>
<li>Suppressions: paginated list with bounce / complaint / unsubscribe filters, manual add, CSV export. Bounces and FBL complaints are fanned out from the gateway automatically so you never have to clean a list by hand.</li>
</ul>
Casa Webmail mailboxes (Growth and higher)
<ul>
<li>Self-hosted branded webmail at <code>webmail.onlinestorenotifications.com</code>. Sign in with <code><your-inbox>@onlinestorenotifications.com</code> from any browser and read and reply to customer replies from a clean inbox.</li>
<li>Use your own domain too: point your domain’s MX records at <code>mx.sendemailtoday.io</code> and replies to <code><your-inbox>@yourdomain.com</code> land in the same webmail UI, signed by the platform DKIM.</li>
<li>Real Maildir storage on the Casa Mail backbone. No third-party Gmail forwarding.</li>
</ul>
Billing and plan management
<ul>
<li>One-click upgrade from Free to Starter, Growth, Business, or Agency. Stripe Checkout opens in a new tab; the plugin never sees your card details.</li>
<li>Paid plans are also available straight from the onboarding wizard, so you can start on the right tier from day one.</li>
<li>In-WordPress quota-usage display with an “approaching cap” banner so a busy month doesn’t surprise you mid-send.</li>
<li>Stripe-hosted billing portal for change-card, change-plan, view-invoices, cancel.</li>
</ul>
Built-in trust and safety
<ul>
<li>Sender-domain enforcement so a misconfigured WordPress install can never send under someone else’s domain by accident.</li>
<li>Gateway-side content review on marketing broadcasts: a separate moderation layer scans campaigns and pauses anything that looks like phishing, brand impersonation, or credential harvesting before it reaches your recipients. The gateway operator reviews flagged content and contacts you with the reason. This protects your sender reputation.</li>
</ul>
<h4>Pricing</h4>
<ul>
<li>Free: 10,000 transactional emails per month, full quota from day one (no daily ramp), 500/day soft cap. Custom-domain authentication included. No credit card required.</li>
<li>Starter (GBP 9/month): 25,000 emails per month, 2,500/day cap. Custom-domain authentication.</li>
<li>Growth (GBP 29/month): 100,000 emails per month, Marketing Studio (contacts, segments, campaigns, visual editor, suppressions), 1 branded Casa Webmail mailbox.</li>
<li>Business (GBP 79/month): 500,000 emails per month, Marketing Studio, 5 mailboxes.</li>
<li>Agency (GBP 199/month): 2,000,000 emails per month, Marketing Studio, 25 mailboxes.</li>
</ul>
Upgrades and downgrades are entirely self-serve from Settings -> Casa Mail -> Billing. Cancellation is one click from the Stripe-hosted portal; you keep service through the end of your billing cycle.
<h4>How it works (transactional path)</h4>
<ul>
<li><code>pre_wp_mail</code> is hooked at priority 1. Each call is converted to a JSON payload and POSTed to the gateway.</li>
<li>If the gateway accepts on the first POST, <code>wp_mail()</code> returns true and the message is durably enqueued upstream.</li>
<li>If the gateway is unreachable on the first POST, the payload is written to a durable outbox table (<code><prefix>casamail_outbox</code>) and a cron tick retries with 30s, 2m, 10m backoff.</li>
<li>A separate transmit log table (<code><prefix>casamail_sends</code>) records every attempt for visibility on the plugin dashboard. Rows older than 30 days are pruned automatically.</li>
</ul>
<h4>Onboarding</h4>
After activation, an in-WordPress wizard collects:
<ol>
<li>Site name, site URL, contact email address.</li>
<li>A 6-digit code emailed by the gateway to confirm the address.</li>
<li>The handle to use for your inbox (defaults to a friendly version of your site URL, e.g. <code>acmestore</code>).</li>
<li>Plan selection. Five tiers shown side-by-side (Free, Starter, Growth, Business, Agency); pick Free to get started immediately, or pick a paid tier to launch Stripe Checkout in a new tab. Either way your tenant is already provisioned so you can keep onboarding while you complete payment.</li>
<li>Where customer emails should come from: the shared Casa Mail address, or your own authenticated domain (with one-click DNS verification).</li>
</ol>
The whole onboarding is one screen with five short steps. No SMTP keys to copy, no DNS console to leave WordPress for.
<h4>Trademark note</h4>
This plugin is not affiliated with or endorsed by WooCommerce, Automattic, or any third party. The WooCommerce name appears only as a compatibility note (when WooCommerce is detected, the plugin’s admin menu attaches under it for convenience; otherwise it lands under Settings).
<h3>External services</h3>
This plugin transmits data to a third-party SMTP gateway. WordPress.org policy requires this be disclosed.
<h4>Endpoints contacted</h4>
The plugin makes HTTPS requests to:
<ul>
<li><code>https://api.onlinestorenotifications.com/v1/onboard/request</code> – during onboarding, to send your verification email.</li>
<li><code>https://api.onlinestorenotifications.com/v1/onboard/verify</code> – during onboarding, to confirm the code and provision an account.</li>
<li><code>https://api.onlinestorenotifications.com/v1/send</code> – for every <code>wp_mail()</code> call once the plugin is onboarded.</li>
<li><code>https://api.onlinestorenotifications.com/v1/email/domain</code> (GET / add / verify) – when the site administrator interacts with the Sender Domain page.</li>
<li><code>https://api.onlinestorenotifications.com/v1/billing/*</code> – checkout, billing portal, plan status. Only invoked when the site administrator interacts with the Billing page or picks a paid tier during onboarding.</li>
</ul>
The gateway is operated by CodeCasa Studios under the Casa Mail brand and runs on the OnlineStoreNotifications infrastructure. Casa Mail and OnlineStoreNotifications are sister brands of the same company; the API hostname reflects the shared backbone rather than a third-party dependency.
<h4>Data sent</h4>
During onboarding (one-time, before any send): site administrator email address, site name, site URL.
For each <code>wp_mail()</code> call once onboarded: sender email address, sender name, recipient email address(es), subject, message body, message headers (after stripping <code>From</code>/<code>To</code>/<code>Subject</code>/<code>Date</code>/<code>Message-ID</code>/<code>MIME-Version</code>/<code>Content-Type</code>/<code>Content-Transfer-Encoding</code>).
<h4>Terms and privacy</h4>
<ul>
<li>Terms of service: https://sendemailtoday.io/terms.html</li>
<li>Privacy policy: https://sendemailtoday.io/privacy.html</li>
</ul>
<h3>Privacy</h3>
When activated, this plugin transmits email content (recipient, sender, subject, body, headers) to a third-party SMTP gateway for delivery. This is the plugin’s only purpose. The data lifecycle is described above under “External services” and on the linked privacy policy.
The plugin also writes a <code>wp_add_privacy_policy_content()</code> block describing what is transmitted; this lets site administrators include the disclosure in the WordPress-managed privacy policy page (Settings -> Privacy).
Account deletion: a “Request account deletion” button on the plugin’s Settings page emails the gateway operator. Upon confirmation, the tenant record, API key(s), domain-authentication records, and recent sending history are removed from the gateway side. The plugin uninstall additionally removes the plugin’s WordPress-side options + tables.

Casa Mail

A complete email platform for WordPress: transactional SMTP, marketing campaigns, branded mailboxes, and DKIM-aligned sending from your own domain.

Acato

Email Essentials vastly reduces the chances of your emails being marked as spam or being rejected. Originally a debugging tool, it has grown into a full-fledged email enhancement plugin.
Please note that this plugin is not a “we support any type of transport” Email plugin. For other protocols than SMTP, but rather to enhance the email sending capabilities of WordPress. 
If you need to send emails with other protocols than SMTP, this plugin is not for you. You might want to look at plugins like Post SMTP (not affiliated).
And since version 6.0.0, after more than 10 years of development and internal use, this plugin is now a FOSS plugin, meaning it is free to use, modify and distribute under the GPLv2 license.
In return, we ask you to support the development of this plugin by contributing to the codebase, reporting bugs, and helping others in the community.
Responsible disclosure: 
If you find a vulnerability, please email us at <a href="mailto:responsibledisclosure@acato.nl" rel="nofollow ugc">responsibledisclosure@acato.nl</a>.
<h3>Features</h3>
<ul>
<li>Set a good From name and email address, automatically correcting it if needed. For example, a contact form is sent from the visitors email address, resulting in an invalid Sender address. This plugin will correct it to a valid email address. This plugin automatically corrects it.</li>
<li>Correct envelope-from address; often forgotten, but important for deliverability.</li>
<li>Reformat as HTML with plain text alternative; will detect the use of HTML ensures that emails are sent as HTML with a plain text alternative.</li>
<li>Process shortcodes in your email content.</li>
<li>UTF8 recoding, to ensure that special characters are correctly encoded in the email.</li>
<li>Email Essentials allows for adding CSS, header, footer, and body template using filters, see below.</li>
<li>Convert CSS to inline styles for better support in email clients</li>
<li>SMTP configuration</li>
<li>Send emails to multiple addressees as separate emails</li>
<li>S/MIME signing, using a supplied certificate, to ensure the authenticity of the email.</li>
<li>DKIM signing, and providing all information needed to set up DKIM signing for your domain.</li>
<li>Allow redirecting emails sent to the administrator to other email addresses based on the email subject.</li>
<li>Allow redirecting emails sent to the moderators (e.g., for comments).</li>
<li>Keep a history of outgoing emails (debugging, cleared on deactivation)</li>
<li>Email receipt tracking (for investigative purposes only, see GDPR note)</li>
<li>Re-send button for failed emails</li>
<li>Allow sending emails delayed, to prevent sending too many emails at once. (Beta feature)</li>
</ul>
<h3>Important Note</h3>
This tool is for users who understand email delivery. If unsure, ask for help.
Under GDPR, storing and tracking emails is prohibited. The history feature is for investigative purposes only!
<h3>External services</h3>
Email Essentials uses one external service by default, two if you create and define your own IP services.
<ol>
<li>CloudFlare DNS over HTTPS (DoH). This is used to resolve domain names to IP addresses when (for example) checking SPF or DKIM records. In theory, it is possible to use PHPs own <code>dns_get_record</code> function, but in practice this often fails due to server DNS-resolve misconfiguration. Using CloudFlare’s DoH service ensures reliable DNS resolution. We only send the hostname (the domain part) to CloudFlare, no other data. Explicitly, we do NOT send any other information.</li>
<li>The plugin can use an IP-address relay service to accurately determine the sender’s IP address. This is required to accurately check that the sender’s IP address is authorized to send email for the domain (SPF check). To use this, you will need to set up your own service, see documentation on filter <code>acato_email_essentials_ip_services</code>. Without this service, IP detection can be inaccurate because it will use the website itself as a relay. Use of a reverse proxy, load balancer etc. can lead to incorrect IP detection.</li>
</ol>
<h3>WordPress Filters</h3>
<ul>
<li><code>acato_email_essentials_settings</code> — Filter plugin settings.</li>
<li><code>acato_email_essentials_defaults</code> — Filter default settings.</li>
<li><code>acato_email_essentials_subject</code> — Filter email subject.</li>
<li><code>acato_email_essentials_body</code> — Filter HTML body of the email.</li>
<li><code>acato_email_essentials_head</code> — Filter HEAD section of HTML email.</li>
<li><code>acato_email_essentials_css</code> — Filter CSS for the email.</li>
<li><code>acato_email_essentials_minify_css</code> — Filter CSS minification.</li>
<li><code>acato_email_essentials_mail_is_throttled</code> — Check if mail should be throttled.</li>
<li><code>acato_email_essentials_mail_throttle_time_window</code> — Set mail throttle time window.</li>
<li><code>acato_email_essentials_mail_throttle_max_count_per_time_window</code> — Set max emails per time window.</li>
<li><code>acato_email_essentials_mail_throttle_batch_size</code> — Set mail batch size.</li>
<li><code>acato_email_essentials_ip_services</code> — Define custom IP services for accurately determining the sender’s IP address.</li>
<li><code>acato_email_essentials_ip_service</code> — Filter individual IP service URLs.</li>
<li><code>acato_email_essentials_website_root_path</code> — Filter to supply the correct website root path in case of non-standard setups.</li>
<li><code>acato_email_essentials_development_tlds</code> — Filter development/local TLDs.</li>
</ul>
<h3>WordPress Filters in detail</h3>
Plugin Settings
<pre><code>acato_email_essentials_settings
</code></pre>
Parameters: 
– (array) <code>$settings</code> The current settings of the plugin.
Expected return: 
– (array) The new settings of the plugin.
<pre><code>acato_email_essentials_defaults
</code></pre>
Parameters: 
– (array) <code>$defaults</code> The current default settings of the plugin.
Expected return: 
– (array) The new default settings of the plugin.
Email Content
<pre><code>acato_email_essentials_subject
</code></pre>
Parameters: 
– (string) <code>$the_subject</code> Subject for the email. 
– (PHPMailer) <code>$mailer</code> The PHPMailer object (by reference).
Expected return: 
– (string) The (altered) Subject.
<pre><code>acato_email_essentials_body
</code></pre>
Parameters: 
– (string) <code>$should_be_html</code> A text that should be html, but might not yet be, your job to make a nice HTML body. 
– (PHPMailer) <code>$mailer</code> The PHPMailer object (by reference).
Expected return: 
– (string) A text that should be html.
<pre><code>acato_email_essentials_head
</code></pre>
Parameters: 
– (string) <code>$the_head_section</code> HTML that is the HEAD section of the HTML email. 
– (PHPMailer) <code>$mailer</code> The PHPMailer object (by reference).
Expected return: 
– (string) The altered HEAD section of the HTML email.
<pre><code>acato_email_essentials_css
</code></pre>
Parameters: 
– (string) <code>$the_css</code> CSS for the email (empty by default). 
– (PHPMailer) <code>$mailer</code> The PHPMailer object (by reference).
Expected return: 
– (string) The (altered) CSS.
<pre><code>acato_email_essentials_minify_css
</code></pre>
Parameters: 
– (string) <code>$css</code> CSS to be minified.
Expected return: 
– (string) The minified CSS.
Mail Throttling
<pre><code>acato_email_essentials_mail_is_throttled
</code></pre>
Parameters: 
– (bool) <code>$is_throttled</code> Whether the mail is currently throttled. 
– (string) <code>$ip</code> The sender’s IP address. 
– (int) <code>$mails_recently_sent</code> Number of mails recently sent from this IP.
Expected return: 
– (bool) Whether the mail should be throttled.
<pre><code>acato_email_essentials_mail_throttle_time_window
</code></pre>
Parameters: 
– (int) <code>$time_window</code> Time window in seconds for counting sent emails.
Expected return: 
– (int) The (altered) time window in seconds.
<pre><code>acato_email_essentials_mail_throttle_max_count_per_time_window
</code></pre>
Parameters: 
– (int) <code>$count</code> Maximum number of emails allowed per time window.
Expected return: 
– (int) The (altered) maximum count.
<pre><code>acato_email_essentials_mail_throttle_batch_size
</code></pre>
Parameters: 
– (int) <code>$size</code> Number of emails to send in a single batch.
Expected return: 
– (int) The (altered) batch size.
IP Detection
<pre><code>acato_email_essentials_ip_services
</code></pre>
Parameters: 
– (array) <code>$services</code> The current list of IP services used to determine the sender’s IP address.
Expected return: 
– (array) The (altered) list of IP services.
The services must be keyed with <code>ipv4</code>, <code>ipv6</code> and <code>dual-stack</code>. The values must be URLs that return the IP address in plain text. 
The dual-stack service should return an IPv6 address if available, otherwise an IPv4 address, never both.
You can set-up your own service like this;
<ul>
<li>You will need a webserver that can run PHP, and you need a DNS service that allows you to manually add records.</li>
<li>You will need three webspaces, for example; ipv4.myservice.com, ipv6.myservice.com and dual-stack.myservice.com.
<ul>
<li>You could use the same webspace for all three, but you will still need three subdomains on the service.</li>
</ul>
</li>
<li>For the ipv4 subdomain, ONLY register an A record, pointing to the webserver’s IP address.</li>
<li>For the ipv6 subdomain, ONLY register an AAAA record, pointing to the webserver’s IPv6 address.</li>
<li>For the dual-stack subdomain, register both an A and an AAAA record, pointing to the webserver’s IP addresses.</li>
<li>
Create a file called <code>index.php</code> in each of the webspaces with the following content:
<code>php 
<?php 
header('Content-Type: text/plain'); 
print $_SERVER['REMOTE_ADDR'];</code>
</li>
</ul>
That’s it. You can now use these services in the plugin settings like this;
<pre><code>`php
</code></pre>
add_filter(‘acato_email_essentials_ip_services’, ‘my_custom_ip_services’); 
function my_custom_ip_services($services) { 
 // Add your custom services here 
 $services[‘ipv4’] = ‘https://ipv4.myservice.com’; 
 $services[‘ipv6’] = ‘https://ipv6.myservice.com’; 
 $services[‘dual-stack’] = ‘https://dual-stack.myservice.com’; 
 return $services; 
} 
 `
<pre><code>acato_email_essentials_ip_service
</code></pre>
Parameters: 
– (string) <code>$service</code> The URL of the IP service for the given type. 
– (string) <code>$type</code> The type of IP service (‘ipv4’, ‘ipv6’, or ‘dual-stack’).
Expected return: 
– (string) The (altered) IP service URL.
Filter to modify individual IP service URLs based on type.
<pre><code>acato_email_essentials_website_root_path
</code></pre>
Parameters: 
– (string) <code>$path</code> The current website root path.
Expected return: 
– (string) The (possibly altered) website root path.
Filter to supply the correct website root path in case of non-standard setups.
<pre><code>acato_email_essentials_development_tlds
</code></pre>
Parameters: 
– (array) <code>$tlds</code> Array of top-level domains considered as development environments.
Expected return: 
– (array) The (altered) array of development TLDs.
Filter to modify which TLDs are treated as development/local environments. Default values are ‘local’ and ‘test’.
<h3>Scripts/styles</h3>
In the <code>public/scripts</code> and <code>public/styles</code> folder you find the JS and CSS files used in the plugin admin area. 
These files are processed with Webpack, just so it works in all recent browsers. Script is nearly identical to the source.
You can find the source files in the <code>src/scripts</code> and <code>src/styles</code> folders.
If you feel the need to modify these files, you can change them there, and run <code>npm install ; npm run build</code> to create the production files.
<h3>Translation files</h3>
You can use <code>npm run i18n</code> to generate the POT file for translation, update the PO files in the <code>languages</code> folder, and compile to MO/php files. 
This is a one-task-does-all; run it, change the translations, run it again. Done. 
See package.json for more details or individual commands.
<h3>Tools</h3>
In the <code>tools</code> folder you will find a script to generate DKIM keys, should you want to use DKIM signing. 
rename to remove the .txt extension and run it in a shell.
Tools are provided as-is, without support. Use at your own risk. Read the scripts before using them.
You DO NOT HAVE TO USE these scripts, you can generate DKIM keys with any tool you like.
<h3>Arbitrary section</h3>
For advanced configuration and custom IP services, see the plugin documentation or source code.

Email Essentials

A plugin to make WordPress outgoing emails better and less likely to be marked as spam.

Casa Mail vs Email Essentials