Title: Error sending mailing
Last modified: August 26, 2022

---

# Error sending mailing

 *  Resolved [fra83](https://wordpress.org/support/users/fra83/)
 * (@fra83)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/error-sending-mailing/)
 * Good day, from some latest updtedating, i cant send emails to users.
 * this is the error :
 * Non è stato possibile inviare l’email: SMTP Error:
    Could not connect to SMTP
   host. Connection failed. stream_socket_enable_crypto(): SSL operation failed 
   with code 1. OpenSSL Error messages: error:14090086:SSL routines:ssl3_get_server_certificate:
   certificate verify failed
 * please inform
    thank you

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Support [Dani F. a11n](https://wordpress.org/support/users/danielinhou/)
 * (@danielinhou)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/error-sending-mailing/#post-15961643)
 * Hi there [@fra83](https://wordpress.org/support/users/fra83/) 👋🏽!
 * Thank you for reaching out to MailPoet Support!
 * > Good day, from some latest updtedating, i cant send emails to users.
 * Oh, could you please let me know what MailPoet version is the site using now?
 * Cheers!
 *  Thread Starter [fra83](https://wordpress.org/support/users/fra83/)
 * (@fra83)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/error-sending-mailing/#post-15962062)
 * Hi Dani, enclose the version :
    Create and send newsletters, post notifications
   and welcome emails from your WordPress. Versione 3.95.1 | Di: MailPoet | Visualizza
   i dettagli
 * thank you
 *  Plugin Author [Bruna a11n](https://wordpress.org/support/users/bruberries/)
 * (@bruberries)
 * [3 years, 10 months ago](https://wordpress.org/support/topic/error-sending-mailing/#post-16005537)
 * Hi [@fra83](https://wordpress.org/support/users/fra83/),
 * When checking the SSL certificate for your server, it may be that the certificate
   is self-signed. As mentioned [in this doc](https://kb.mailpoet.com/article/193-tls-encryption-does-not-work),
   a self-signed certificate is disallowed by default. In this case, you can use
   a custom hook to configure the secure connection (i.e., set SSL context options)
   and disable self-signed certificates and/or authenticity verification.
 * Could you please try adding the filter [we shared here](https://kb.mailpoet.com/article/193-tls-encryption-does-not-work)
   and let me know if it works?
 * Thank you!
 *  [milos1](https://wordpress.org/support/users/milos1/)
 * (@milos1)
 * [3 years, 5 months ago](https://wordpress.org/support/topic/error-sending-mailing/#post-16493968)
 * [@bruberries](https://wordpress.org/support/users/bruberries/) [@fra83](https://wordpress.org/support/users/fra83/)
 * Hello,
 * Could you please explain exactly where to put the file [mailpoet_smtp_secure_connection_options_hook.php](https://gist.github.com/MailPoet-Staff/64364f9465eb8abe5ffa478fdea1cd85#file-mailpoet_smtp_secure_connection_options_hook-php)
   or where to integrate this piece of code ? This is described in
 * [https://kb.mailpoet.com/article/193-tls-encryption-does-not-work](https://kb.mailpoet.com/article/193-tls-encryption-does-not-work)
 * mentioned by Bruna.
 * Thanks

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Error sending mailing’ is closed to new replies.

 * ![](https://ps.w.org/mailpoet/assets/icon-256x256.png?rev=3284564)
 * [MailPoet - Newsletters, Email Marketing, and Automation](https://wordpress.org/plugins/mailpoet/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/mailpoet/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/mailpoet/)
 * [Active Topics](https://wordpress.org/support/plugin/mailpoet/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/mailpoet/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/mailpoet/reviews/)

 * 4 replies
 * 4 participants
 * Last reply from: [milos1](https://wordpress.org/support/users/milos1/)
 * Last activity: [3 years, 5 months ago](https://wordpress.org/support/topic/error-sending-mailing/#post-16493968)
 * Status: resolved