SpeakOut! vs WP Mail SMTP by WPForms – The Most Popular SMTP and

SpeakOut! Email Petitions allows you to easily create petition forms on your site. When visitors to your site submit the petition form, a copy of your message will be sent to the email address you specified e.g. your mayor. They can also choose to have the email BCC’d to themselves (default). The petition message will be signed with the contact information provided by the form submitter. After signing the petition, visitors will have the option of sharing your petition page with their followers on Facebook or x. Signatures are stored in the WordPress database and can be easily exported to CSV format for further analysis (there is no import function). You may set a goal for the number of signatures you hope to collect and then watch as a progress bar tracks your petition’s advance toward it’s goal – the goal can even update automatically when a % of your goal is reached. Petitions may also be configured to stop accepting new signatures on a specified date. The free version includes the core features needed to run a successful petition. For those who need more, the Pro version unlocks the ability to run unlimited campaigns and provides additional tools, such as an email sharing option and expanded integration with third-party mailing services. More information about the plugin and how to upgrade to the fully featured Pro version can be found at the official SpeakOut! WordPress petition plugin website. 4.6.5.1 This is a critical security patch. Please update immediately to protect your user data. 4.6.5 Bugfix: address misc warnings. 4.6.4 Bugfix: fix anonmyous record keeping issue. Bugfix: fix nonce issue with some admin pages causing permision errors. 4.6.3 Fix bad cache. 4.6.2 Fix php warning regarding missing options. 4.6.1 Security: Added a secure AJAX endpoint with nonce and capability checks for dismissing admin notices. Improvement: Modernized admin script and style loading to improve performance and adhere to WordPress best practices. Improvement: Redesigned the the admin pages the petition settings page for a cleaner and more consistent user interface. Improvement: The GDPR (Privacy Policy) setting is now mandatory when enabled. Bug fix: Corrected an issue in an AJAX handler that could prevent petition emails from being sent correctly. Bug fix: Prevented a potential PHP warning by ensuring the petition message is always a string. Improvement: updated “tested up to” to WP version 6.8.3 4.6.0 Security: Hardened the plugin by adding comprehensive data sanitization and output escaping across all forms, AJAX handlers, and admin pages to prevent XSS and other vulnerabilities. Security: Replaced direct use of $_POST, $_GET, and $_REQUEST variables with sanitized and validated data. Security: Ensured all URLs generated by the plugin are properly escaped using esc_url. Refactor: Completely overhauled the [emailpetition] shortcode rendering. The form HTML is now loaded from a separate template file ( includes/email-petition-form-template.php), improving code organization and making customization easier. Refactor: Consolidated all mailing list integration logic (ActiveCampaign, MailChimp, etc.) into a single, cleaner function call. Refactor: Improved custom field rendering by creating a dedicated helper function to reduce code duplication. Refactor: Updated AJAX handlers to securely process and validate all incoming data. Refactor: Switched to using WordPress best practices, such as has_shortcode() for content checking and admin_url() for creating admin links. Tweak: Improved pagination logic to be more robust and prevent potential errors. 4.5.2 improvement: updated “tested up to” to WP version 6.8 4.5.1 bug fix: CSV export was throwing an error – thanks Vegard B. improvement: updates to Swedish translations – thanks Magnus improvement: updated “test to” to WordPress 6.8 4.5.0 improvement: further refined bug fixed in 4.4.0 – thanks Darius S. @ patchstack.com 4.4.3 improvement: updated old changelog link at end of current changelog 4.4.2 improvement: updated “Tested up to” to 6.7 4.4.1 bug fix: Export to CSV not working – thanks Vincent R & Shawn D 4.4.0 bug fix: fixed XSS vulnerability in specially crafted shortcode – thanks Darius S. @ patchstack.com 4.3.6 bug fix: wonky CSS setting in basic theme – thanks Jordan. 4.3.5.2 improvement: updated “tested to” to version 6.6 4.3.5.1 improvement: changed CSV max_execution_time from 180 to 300 seconds and moved it so it is only applied if script is actually run. Also reset it to system default at end of script – thanks @gideonlupine 4.3.4 improvement: updated compatibility to WordPress 6.5 4.3.3.1 bug fix: debug code removed bug fix: new social icons missing in free version bug fix: in some circumstances an error was thrown in settings page – thanks Heiko 4.3.3 bug fix: error being thrown by field that can’t be edited in free version – thanks Giuseppe bug fix: somehow above error wasn’t fixed in 4.3.2 – thanks Mayda 4.3.1 improvement: updated social icons in all style sheets 4.3.0 improvement: changed “twitter” to “X” – thanks Jos improvement: removed some superfluous code improvement: added Serbian language 4.2.6 bug fix: no error if privacy policy box not checked – thanks Mika improvement: SpeakOut! now has its own domain SpeakOutPetitions.com 4.2.3 bug fix: In certain languages if privacy was enabled to show only the first letter of the surname, it would display a ? instead – thanks Niklas bug fix: signature list wouldn’t display if petition ID was greater than one. This was implemented to limit free users, but it has unintended consequences for legacy users with multiple petitions. Thanks Jim for letting me poke around. 4.2.2 improvement: updated “tested to” to 6.3 4.2.1 bug fix: multiple email addresses in Target Email or CC Email fields would be mashed together – thanks James and someone else who reported this 4.2.0 bug fix: custom field 6 location wasn’t being saved bug fix: in admin signature list, “anonymous” icon was showing HTML instead of being superscript improvement: added several webhooks – see https://speakoutpetitions.com/webhooks. Thanks for the idea Ben & Nick improvement: added email share icon to Pro version – thanks to whoever suggested it. improvement: displaying emails in the public signature list is now optional – with a warning that it might not be a wise idea improvement: translation updates 4.1.3.1 bug fix: Somehow a stray character found its way into the code which was breaking petitions. – thanks Meagan 4.1.2 bug fix: database creation error for new installs bug fix: if message was editable, formating was lost when sent to target (Pro only) – thanks Linda bug fix: language wasn’t bein passed via URL in confirmation emails improvement: eliminated php warning “ob_end_flush(): failed to send buffer of zlib output compression” improvement: added note to when “Do not send email (only collect signatures)” is checked 4.1.1 bug fix: if the petitionmessage shortcode was used, any Markdown in the message wasn’t being displayed. Thanks Michael. bug fix: if email confirmation was enabled, the numbering in the public signature list reflected the total number of signatures, not just the confirmed signtures. Thanks Rene & Martin bug fix: if email confirmation was enabled and public signatures spanned more than one page, scrolling didn’t work as expected – thanks Rene bug fix: on one layout of the public signature list, the word anonymous wasn’t translated – thanks Myriam-Zaa bug fix: increased size of honorifics field in database – thanks Glen C. bug fix: following some actions in the admin signature list it wasn’t showing the signature count improvement: new installs will now use the utf8mb4_general_ci character set for database text fields, instead of just utf8 – down the track I will change the character set for existing installs improvement: database creation now makes fields NULL instead of NOT NULL to allow for not collecting some data – down the track I will change all fields to NULL in existing installs 4.1.0 bug fix: Confirmation emails weren’t being sent if Email From field wasn’t set up properly, which was impossible. Thanks Thomas and Rene bug fix: non-existant parameter being passed to function improvement: updated the contextual help – first time ever :o) improvement: clarified wording of “display signature count” and where it refers to. improvement: database updates so free version is ready to upgrade to Pro 4.0.10 improvement: changed a page title – thanks Debbie P bug fix: some required fields were not showing red border – thanks Debbie P bug fix: redirect after signing not working – thanks Debbie P 4.0.9 bug fix: when clicking next in signature list it was displaying html – thanks Dan @tahninial 4.0.8 bug fix: slashes added to any apostrophes in email subject or greeting bug fix: missing default value in free version 4.0.7 bug fix: missing character would cause error in certain circumstances – thanks heiko 4.0.6.1 bug fix: if WordPress was installed in a subfolder, some administrator links may not have worked. Thanks Calvin 4.0.6 bug fix: petition message kept adding slashes in editor when saved. Thanks Calvin improvement: removed %%Your Signature%% from the petition message displayed on your site. It was causing confusion. Thanks Razvan improvement: minor typo fixed improvement: Dutch language imrovements – thanks Michiel 4.0.5 bug fix: petition message losing formatting – thanks @dcbuffalo improvement: better data sanitization in signature list 4.0.4.6 bug fix: html being displayed in admin signature list bug fix: file was being included twice bug fix: reconfirming selected signatures wasn’t working 4.0.4.5 bug fix: settings not saving due to incorrect input sanitize function improvement: German language update – thanks Mario 4.0.4.4 bug fix: in some circumstances an error was thrown in settings page – thanks Heiko 4.0.4.2 Policy compliance: Version 3 of SpeakOut! included a method of upgrading that turned out to be a WordPress plugin policy breach (4 months later!) and some potential security issues (after 10+ years!). This version remedies that and introduces a more cumbersome (for users), but compliant method of upgrading. bug fix: various fixes of things found while creating V4 improvement: removed support for importing the original speakup plugin. After 10 years, it’s time. Earlier Changelog Localizations Albanian sq_AL Incomplete Arabic ar_AR Arabic ar (Faisal Kadri) Catalan ca (Alberto Canals) Czech cs_CZ (Petr Å tepán, Michal Hradecký) Danish da_DK (A. L.) Dutch nl_NL (Kris Zanders, Petronella van Leusden) Finnish fi_FI French fr_FR German de_DE (Hannes Heller, Armin Vasilico, Andreas Kumlehn, Frank Jermann) Hebrew he_IL (Oren L) Korean ko_KO (Paul Lawley-Jones) Icelandic is_IS (Hildur Sif Thorarensen) Italian it_IT (MacItaly, Davide Granti, Simone Apollo) Norwegian nb_NO (Howard Gittela) Polish pl_PL (Damian Dzieduch) Portuguese (Brazil) pt_BR (Tel Amiel) Romanian ro_RO (Web Hosting Geeks) Russian ru_RU (Teplitsa) Serbian sr_RS (Mikhailo Matovic) Slovak sk_SK (@Beata) Slovenian sl_SI (MA-SEO) Spanish es_ES Swedish sv_SE (Susanne Nyman FurugÃ¥rd @sunyfu) If you would like to request or contribute a specific translation not listed above, visit the SpeakOut! Email Petitions website and use the contact form. Emailpetition Shortcode Attributes The following attributes may be applied when using the ‘[emailpetition]’ shortcode id The ID number of your petition (required). To display a basic petition, use this format: ‘[emailpetition id=”1″]’ width This sets the width of the wrapper “ ” that surrounds the petition form. Format as you would a width rule for any standard CSS selector. Values can be denominated in px, pt, em, % etc. The units marker (px, %) must be included. To set the petition from to display at 100% of it’s container, use: ‘[emailpetition id=”1″ width=”100%”]’ A petition set to display at 500 pixels wide can be achieved using: ‘[emailpetition id=”1″ width=”500px”]’ height This sets the height of the petition message box (rather than the height of the entire form). Format as you would a height rule for any standard CSS selector. Values can be denominated in px, pt, em, % etc. The units marker (px, %) must be included. A few notes on using percentages: Using a % value only works when the “Allow messages to be edited” feature is turned off—because the petition message will be displayed in a ‘ ’. When “Allow messages to be edited” is turned on, the petition message is displayed in a ”, which cannot be styled with % heights. Use px to set the height on petitions that allow message customization. To set the message box to scale to 100% of the height of the message it contains, use any % value (setting this to 100%, 0%, 200% or any other % value has the same result). Use px if you want the box to scale to a specific height. Examples: ‘[emailpetition id=”1″ height=”500px”]’ ‘[emailpetition id=”1″ height=”100%”]’ progresswidth Sets the width of the outer progress bar. The filled area of the progress bar will automatically scale proportionally with the width of the outer prgress bar. Provide a numeric value in pixels only. Do not include the px unit marker. To display the progress bar at 300 pixels wide, use: ‘[emailpetition id=”1″ progresswidth=”300″]’ class Adds an arbitrary class name to the wrapper ‘ ’ that surrounds the petition form. Typically used to assign the alignright, alignleft or aligncenter classes to the petition in order to float the petition form to one side of its container. To assign multiple classes, separate the class names with spaces. Examples: ‘[emailpetition id=”1″ class=”alignright”]’ ‘[emailpetition id=”1″ class=”style1 style2″]’ Signaturelist Shortcode Attributes id The ID number of your petition (required). To display a basic signature list, use this format: ‘[signaturelist id=”1″]’ rows The number of signature rows to display in the table. This will override the default value provided on the Settings page. To display 10 rows, use: ‘[signaturelist id=”1″ rows=”10″]’ dateformat Format of values in the date column. Use any of the standard PHP date formating characters. Default is ‘M d, Y’. A date such as “Sunday October 14, 2012 @ 9:42 am” can be displayed using: ‘[signaturelist id=”1″ dateformat=”l F d, Y @ g:i a”]’ prevbuttontext The text that displays in the previous signatures pagination button. Default is . signaturecount Shortcode Display the number (as text) of signatures collected for a given petition: id The ID number of your petition (required). ‘[signaturecount id=”3″]’ signaturegoal Shortcode Display the number (as text) of goal for a given petition: id The ID number of your petition (required). ‘[signaturegoal id=”3″]’

WordPress Mail SMTP Plugin Is your WordPress site not sending emails? You’re not alone. 4+ million websites use WP Mail SMTP to send emails reliably. Our goal is to make email deliverability easy so that your emails always reach the inbox. WP Mail SMTP fixes your email deliverability issues by reconfiguring WordPress to use a proper SMTP provider when sending emails. Best of all, our easy-to-use Setup Wizard and detailed documentation guide you through the process. WP Mail SMTP is free and has everything you need to reliably send your WordPress emails! WP Mail SMTP Pro unlocks even more powerful features like email logging, advanced email reporting and stats, backup connections, email alerts, smart conditional routing, and much more. What is SMTP? SMTP (Simple Mail Transfer Protocol) is an industry-standard for sending emails. Proper SMTP configuration helps increase email deliverability by adding authentication to the emails sent from your site. Popular email clients like Gmail, Yahoo, Office 365, and Zoho are in a constant battle with email spammers, so they check whether emails are originating from a genuine sender. If the proper authentication isn’t there, emails either go in the SPAM folder or, worse, disappear. This is a problem for a lot of WordPress sites. By default, WordPress uses the PHP mail function to send emails generated by WordPress or any contact form plugin like WPForms. But most WordPress hosting companies don’t have their servers properly configured for sending PHP emails. This is why WordPress emails aren’t delivered. How does WP Mail SMTP work? WP Mail SMTP plugin easily resolves email delivery problems by changing the way your WordPress site sends email. We reconfigure the wp_mail() function to use proper SMTP host credentials or an SMTP mail provider. With our built-in SMTP mail provider integrations (recommended), emails are sent using the provider’s direct API. Even if your web host is blocking SMTP ports, your emails will still be sent successfully. This helps you fix all WordPress not sending email issues. WP Mail SMTP plugin includes many different SMTP mailers: SendLayer (#1 Recommended) SMTP.com (Recommended) Brevo (formerly Sendinblue) SMTP (Recommended) Gmail SMTP (Gmail, Google Workspace, G Suite) Elastic Email Mailgun SMTP Mailjet SMTP SendGrid SMTP Postmark SMTP SparkPost SMTP SMTP2GO Microsoft SMTP One-Click Setup (Outlook.com and Office 365) [Pro] Amazon SES SMTP [Pro] Zoho Mail SMTP [Pro] Other SMTP For most options, you can specify the “from name” and “email address” for outgoing emails too. All of these powerful features make WP Mail SMTP the best SMTP solution for WordPress. If you don’t know which mailer to choose, see our Complete Guide to WP Mail SMTP Mailers. SendLayer SendLayer is our #1 recommended transactional email service. Its affordable pricing and simple setup make it the perfect choice for sending emails from WordPress. It also has open and click tracking and email logs. SendLayer is reliable, fast, and easy to set up. You can send hundreds of emails for free when you sign up for a trial. Read our SendLayer documentation for more details. SMTP.COM SMTP.com is a recommended transactional email service. With over 22 years of email delivery expertise, SMTP.com has a reputation for being one of the most reliable senders on the internet. You can start sending emails in minutes and benefit from 50,000 free emails in your first 30 days. Read our SMTP.com documentation for more details. Brevo (formerly Sendinblue) SMTP Brevo is a recommended transactional email service. It serves 80,000+ companies worldwide. Brevo is reliable, fast, and gives you 300 free emails per day. Read our Brevo documentation for more details. WP Mail SMTP PRO In addition to native Microsoft, Amazon SES, and Zoho Mail integrations, WP Mail SMTP Pro provides access to many other powerful features. Click here to purchase WP Mail SMTP Pro now! Email Log Email logging is a powerful feature that keeps a record of all sent emails in WordPress. Email logging helps you to archive, audit, resend, or test email delivery and formatting. Our WordPress email logs also include: Email Log Details Our email logs provide a complete history of all emails sent from WordPress. View the subject, sender, recipients, content, headers, open and click rates, delivery status, source plugin, and more! Resend Emails Resend emails individually or in bulk, whether they failed or were delivered successfully. You can also forward important emails to an alternative email address. And many more Email Log Features Store all email attachments, export email logs, print emails, see delivery status, and more. Email Reports Review weekly sent and failed emails in a dashboard chart. Email reports make it easy to track deliverability and engagement. Open rates and click-through rates are grouped by subject line, making it easy to see the performance of your campaigns or notifications. Weekly Email Summary Get statistics about WordPress emails, including how many emails are being sent and which ones are being opened and clicked. The Summary also shows you deliverability statistics without the need to log in to WordPress to check them. Track Email Opens and Clicks View open and click stats for WordPress emails, grouped by subject line in your Email Report. Email Alerts If your emails stop sending, get notified instantly via Slack, Microsoft Teams, Discord, SMS/ Twilio, webhooks, or email (via secure API). In combination with our email logging and resending features, Email Alerts ensure that no important email will ever be lost. Backup Connection Configure an extra connection that kicks in if your primary connection fails. WP Mail SMTP automatically detects connection issues and automatically switches to the backup mailer. It will also automatically retry emails that failed. Smart Conditional Routing Create criteria to send different types of emails using different mailers. Filter by the contents of the email Subject or Message, From or To addresses, the plugin that generated the email, and more. This allows you to mix transactional and marketing providers to improve deliverability. Rate Limiting Control the number of emails your WordPress site sends in a specific amount of time so you stay within your SMTP provider’s rate limits. WP Mail SMTP allows you to specify the maximum number of emails that will be sent every minute, hour, day, week, or month and automatically queues emails to stay within those limits. Optimized Email Sending Are emails slowing down your site? Let WP Mail SMTP queue your emails for better performance. With optimized sending, emails are queued in the background and sent when your server has sufficient resources, avoiding bottlenecks that can slow down your site. Manage WordPress Emails and Notifications Control the default notifications WordPress sends. Use a simple switch to disable specific types of notifications if you don’t want to receive them. WordPress Multisite WordPress Multisite Network Settings For users running a multisite network, save time with a centralized location to easily configure your SMTP settings for all sites. Manage Multisite Email Logs Easily Network Admins can view and manage email logs for subsites with easy switching and dashboard views. Expert Support We provide limited support on the WordPress.org forums. World-class one-on-one email support is available to WP Mail SMTP Pro users. White Glove Setup If you’re not sure how to fix your emails, sit back and relax. We’ll set up WP Mail SMTP for you! White Glove Setup includes installation, configuration in WordPress, DNS configuration, full mailer setup, and testing. White Glove Setup is available for our recommended mailers: SendLayer, Brevo, and SMTP.com. Credits WP Mail SMTP plugin was originally created by Callum Macdonald. It is now owned and maintained by the team behind WPForms – the best drag & drop form builder for WordPress. You can try the free version of WPForms plugin to see why it’s the best in the market.