Email Essentials vs Really Simple Security – Simple and Performant Security (formerly Really Simple SSL)

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 [email protected]. Features 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. Correct envelope-from address; often forgotten, but important for deliverability. 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. Process shortcodes in your email content. UTF8 recoding, to ensure that special characters are correctly encoded in the email. Email Essentials allows for adding CSS, header, footer, and body template using filters, see below. Convert CSS to inline styles for better support in email clients SMTP configuration Send emails to multiple addressees as separate emails S/MIME signing, using a supplied certificate, to ensure the authenticity of the email. DKIM signing, and providing all information needed to set up DKIM signing for your domain. Allow redirecting emails sent to the administrator to other email addresses based on the email subject. Allow redirecting emails sent to the moderators (e.g., for comments). Keep a history of outgoing emails (debugging, cleared on deactivation) Email receipt tracking (for investigative purposes only, see GDPR note) Re-send button for failed emails Allow sending emails delayed, to prevent sending too many emails at once. (Beta feature) Important Note 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! External services Email Essentials uses one external service by default, two if you create and define your own IP services. 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 dns_get_record 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. 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 acato_email_essentials_ip_services. 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. WordPress Filters acato_email_essentials_settings — Filter plugin settings. acato_email_essentials_defaults — Filter default settings. acato_email_essentials_subject — Filter email subject. acato_email_essentials_body — Filter HTML body of the email. acato_email_essentials_head — Filter HEAD section of HTML email. acato_email_essentials_css — Filter CSS for the email. acato_email_essentials_minify_css — Filter CSS minification. acato_email_essentials_mail_is_throttled — Check if mail should be throttled. acato_email_essentials_mail_throttle_time_window — Set mail throttle time window. acato_email_essentials_mail_throttle_max_count_per_time_window — Set max emails per time window. acato_email_essentials_mail_throttle_batch_size — Set mail batch size. acato_email_essentials_ip_services — Define custom IP services for accurately determining the sender’s IP address. acato_email_essentials_ip_service — Filter individual IP service URLs. acato_email_essentials_website_root_path — Filter to supply the correct website root path in case of non-standard setups. acato_email_essentials_development_tlds — Filter development/local TLDs. WordPress Filters in detail Plugin Settings acato_email_essentials_settings Parameters: – (array) $settings The current settings of the plugin. Expected return: – (array) The new settings of the plugin. acato_email_essentials_defaults Parameters: – (array) $defaults The current default settings of the plugin. Expected return: – (array) The new default settings of the plugin. Email Content acato_email_essentials_subject Parameters: – (string) $the_subject Subject for the email. – (PHPMailer) $mailer The PHPMailer object (by reference). Expected return: – (string) The (altered) Subject. acato_email_essentials_body Parameters: – (string) $should_be_html A text that should be html, but might not yet be, your job to make a nice HTML body. – (PHPMailer) $mailer The PHPMailer object (by reference). Expected return: – (string) A text that should be html. acato_email_essentials_head Parameters: – (string) $the_head_section HTML that is the HEAD section of the HTML email. – (PHPMailer) $mailer The PHPMailer object (by reference). Expected return: – (string) The altered HEAD section of the HTML email. acato_email_essentials_css Parameters: – (string) $the_css CSS for the email (empty by default). – (PHPMailer) $mailer The PHPMailer object (by reference). Expected return: – (string) The (altered) CSS. acato_email_essentials_minify_css Parameters: – (string) $css CSS to be minified. Expected return: – (string) The minified CSS. Mail Throttling acato_email_essentials_mail_is_throttled Parameters: – (bool) $is_throttled Whether the mail is currently throttled. – (string) $ip The sender’s IP address. – (int) $mails_recently_sent Number of mails recently sent from this IP. Expected return: – (bool) Whether the mail should be throttled. acato_email_essentials_mail_throttle_time_window Parameters: – (int) $time_window Time window in seconds for counting sent emails. Expected return: – (int) The (altered) time window in seconds. acato_email_essentials_mail_throttle_max_count_per_time_window Parameters: – (int) $count Maximum number of emails allowed per time window. Expected return: – (int) The (altered) maximum count. acato_email_essentials_mail_throttle_batch_size Parameters: – (int) $size Number of emails to send in a single batch. Expected return: – (int) The (altered) batch size. IP Detection acato_email_essentials_ip_services Parameters: – (array) $services 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 ipv4, ipv6 and dual-stack. 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; You will need a webserver that can run PHP, and you need a DNS service that allows you to manually add records. You will need three webspaces, for example; ipv4.myservice.com, ipv6.myservice.com and dual-stack.myservice.com. You could use the same webspace for all three, but you will still need three subdomains on the service. For the ipv4 subdomain, ONLY register an A record, pointing to the webserver’s IP address. For the ipv6 subdomain, ONLY register an AAAA record, pointing to the webserver’s IPv6 address. For the dual-stack subdomain, register both an A and an AAAA record, pointing to the webserver’s IP addresses. Create a file called index.php in each of the webspaces with the following content: php <?php header('Content-Type: text/plain'); print $_SERVER['REMOTE_ADDR']; That’s it. You can now use these services in the plugin settings like this; `php 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; } ` acato_email_essentials_ip_service Parameters: – (string) $service The URL of the IP service for the given type. – (string) $type 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. acato_email_essentials_website_root_path Parameters: – (string) $path 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. acato_email_essentials_development_tlds Parameters: – (array) $tlds 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’. Scripts/styles In the public/scripts and public/styles 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 src/scripts and src/styles folders. If you feel the need to modify these files, you can change them there, and run npm install ; npm run build to create the production files. Translation files You can use npm run i18n to generate the POT file for translation, update the PO files in the languages 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. Tools In the tools 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. Arbitrary section For advanced configuration and custom IP services, see the plugin documentation or source code.

Easily improve site security with WordPress Hardening, Two-Factor Authentication (2FA), Login Protection, Vulnerability Detection and SSL certificate. Really simple, Effective and Performant WordPress Security Really Simple Security is the most lightweight and easy-to-use security plugin for WordPress. It secures your WordPress website with SSL certificate generation, including proper 301 https redirection and SSL enforcement, scanning for possible vulnerabilities, Login Protection and implementing essential WordPress hardening features. We believe that security should have the absolute minimum effect on website performance, user experience and maintainability. Therefore, Really Simple Security is: Lightweight: Every security feature is developed with a modular approach and with performance in mind. Disabled features won’t load any redundant code. Easy-to-use: 1-minute configuration with short onboarding setup. Security Features Easy SSL Migration Migrates your website to HTTPS and enforces SSL in just one click. 301 redirect via PHP or .htaccess Secure cookies Let’s Encrypt: Install an SSL Certificate if your hosting provider supports manual installation. Server Health Check: Your server configuration is every bit as important for your website security. WordPress Hardening Tweak your configuration and keep WordPress fortified and safe by tackling potential weaknesses. Prevent code execution in the uploads folder Prevent login feedback and disable user enumeration Disable XML-RPC Disable directory browsing Username restrictions (block ‘admin’ and public names) and much more.. Vulnerability Detection Get notified when plugins, themes or WP core contain vulnerabilities and need appropriate action. Login Protection Allow or enforce Two-Factor Authentication (2FA) for specific user roles. Users receive a two-factor code via Email. Improve Security with Really Simple Security Pro Protect your site with all essential security features by upgrading to Really Simple Security Pro. Advanced SSL enforcement Mixed Content Scan & Fixer. Detect files that are requested over HTTP and fix them to HTTPS, both Front- and Back-end. Enable HTTP Strict Transport Security and configure your site for the HSTS Preload list. Firewall Really Simple Security Pro includes a performant and efficient WordPress firewall, to stop bots, crawlers and bad actors with IP and username blocks. 404 blocking – Blocks crawlers as they trigger unusual numbers of 404 errors. Region blocking – Only allow/block access to your site from specific regions. Automated and customisable Firewall rules. IP blocklist and allowlist. Security Headers Security headers protect your site visitors against the risk of clickjacking, cross-site-forgery attacks, stealing login credentials and malware. Independent of your Server Configuration, works on Apache, LiteSpeed, NGINX, etc. Protect your website visitors with X-XSS Protection, X-Content-Type-Options, X-Frame-Options, a Referrer Policy and CORS headers. Automatically generate your WordPress-tailored Content Security Policy. Vulnerability Measures When a vulnerability is detected in a plugin, theme or WordPress core you will get notified accordingly. With Vulnerability Measures, you can configure simple but effective measures to make sure that a critical vulnerability won’t remain unattended. Force update: An update process will be tried multiple times until it can be assumed development of a theme or plugin is abandoned. You will be notified during these steps. Quarantine: When a plugin or theme can’t be updated to solve a vulnerability, Really Simple Security can quarantine the plugin. Advanced Site Hardening Choose a custom login URL Automated File Permissions check and fixer Rename and randomize your database prefix Change the debug.log file location to a non-public folder Disable application passwords Control admin creation Disable HTTP methods, reducing HTTP requests Login Protection Secure your website’s login process and user accounts with powerful security measures. Two-Step verification (Email login) 2FA (two factor authentication) with TOTP Passwordless login with passkey login Enforce strong passwords and frequent password change Limit Login Attempts With Limit Login Attempts you can configure a threshold to temporarily or permanently block IP addresses or (non-existing) usernames. You can also throw a CAPTCHA after a failed login (hCaptcha or Google reCaptcha) Access Control Restrict access to your site for specific regions. Add specific IP addresses or IP ranges to the Blocklist or Allowlist. Useful Links Documentation Security Definitions Translate Really Simple Security Issues & pull requests Feature requests Love Really Simple Security? If you want to support the continuing development of this plugin, please consider buying Really Simple Security Pro, which includes some excellent security features and premium support. About Really Simple Plugins Our mission is to make complex WordPress requirements really easy. Really Simple Security is developed by Really Simple Plugins. For generating SSL certificates, Really Simple Security uses the le acme2 PHP Let’s Encrypt client library, thanks to ‘fbett’ for providing it. Vulnerability Detection uses WP Vulnerability, an open-source initiative by Javier Casares. Want to join as a collaborator? We’re on GitHub as well!