Problem since last update (Could not open socket)

@polina92

Hi Alina,

Hope you are doing good.

Can you share the Diangtioc test report and send the test mail report here?

Also, share the Post SMTP setting page screenshot.

Thanks

Hi There,

As I wrote I switched back to former version, which works perfect, while former one failed.

In this context, this is the result of the email test which failed:
Test SMTP de Postman (polinacouture.com)
Could not open socket
Your hosting is blocking the connection, contact their support

This is diagnotic test

Mailer: postsmtp
HostName: polinacouture.com
cURL Version: 7.52.1
OpenSSL Version: OpenSSL/1.0.2u
OS: Linux 477426.cloudwaysapps.com 4.9.0-14-amd64 #1 SMP Debian 4.9.246-2 (2020-12-17) x86_64
PHP: Linux 7.4.28 C
PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=No, zlib_encode=Yes
WordPress: 5.9.3 fr_FR UTF-8
WordPress Theme: Woodmart
WordPress Plugins: WPML Multilingual CMS, Blackhole for Bad Bots, Block Visibility, Breeze, Classic Widgets, Code Snippets, Contact Form 7, Copyright Proof, Disable Bloat for WordPress & WooCommerce, GTM4WP, Lightbox for Gallery & Image Block, GenerateBlocks, WPBakery Page Builder, LuckyWP Table of Contents, Maintenance, MalCare WordPress Security Plugin - Malware Scanner, Cleaner, Security Firewall, Meow Gallery, Mollie Payments for WooCommerce, Post SMTP, Safe SVG, Rank Math SEO, Advanced Shipment Tracking for WooCommerce, WooCommerce Multilingual & Multicurrency, WooCommerce PDF Invoices & Packing Slips, WooCommerce Table Rate Shipping, WooCommerce, Woodmart Core, Wordfence Security, WP Cerber Security, Anti-spam & Malware Scan, WP Rollback, WPML Media, WPML String Translation
WordPress wp_mail Owner: /home/477426.cloudwaysapps.com/yvumxfxbcu/public_html/wp-content/plugins/post-smtp/Postman/PostmanWpMailBinder.php
WordPress wp_mail Filter(s): wp_staticize_emoji_for_email, WPO\WC\PDF_Invoices\Main->set_phpmailer_validator, PostsmtpMailer->get_mail_args
WordPress wp_mail_from Filter(s): wordfence::fixWPMailFromAddress
WordPress phpmailer_init Action(s): wpcf7_phpmailer_init, PostsmtpMailer->phpmailer_smtp_init
Postman: 2.0.26
Postman Sender Domain (Envelope|Message): polinacouture.com | polinacouture.com
Postman Prevent Message Sender Override (Email|Name): No | No
Postman Active Transport: SMTP (smtps:plain://secure.emailsrvr.com:465)
Postman Active Transport Status (Ready|Connected): Yes | Yes
Postman Deliveries (Success|Fail): 5908 | 54
Postman Stealth Mode: Yes

About Post SMTP settings, as I see it (I am a dummie) there are different tabs. Which one(s) do you need?

Kind regards
Alina

@polina92

You have to contact your hosting support seems like your hosting is blocking ports or sockets, talk to them and they will guide you, if still issue is there then let us know.

Thanks

Hi,
Weird answer, where you seem to be willing to shoot the ball in another field. Or seem to have read just the last sentence, while bypassing the rest.
Could you please explain then why it’s perfectly OK with your former version (2.0.26) and failing with last update (2.0.27)? I mean what would explain that my host would be blocking 2.0.27 and not 2.0.26? Give me the technical reason, and then I will be able to talk to them with a fact, rather than a belief or guess
Kind regards

@polina92

let me discuss it with my senior technical team but in the meantime can you download the Beta version and test it on your staging site?

you can download beta from here, scroll down that page and select Beta 2.1.

Thanks

Hi there,
As I wrote, 2.0.26 works fine, the problem is 2.0.27, ie your last update.
Therefore, I don’t need a beta.
Question is why 2.0.27 does not work
Kind regards

@polina92

Can you update the plugin to 2.1.1.1 and then test it? there are a lot of reasons, we have upgraded the security features of our plugin so may ports are blocking, or sometimes because of SSL, there are some issues.

Please update the plugin and then let me know.

Thanks

We haven’t heard from you so we’re going to mark this thread as resolved. Feel free to open a new one if you need it.