[Tim]

Hi webelous,

I’ve also experienced this too. It only seems to happen to a very small and somewhat random subsection of WooCommerce emails – is that right? From what you’ve said, it sounds like the same problem – very difficult to track down as some work fine (like test mails) and some just fail completely.

I have flagged this to the Post SMTP developer/creator, Yehuda, who will look as soon as he is able. He is super busy, so we appreciate your patience.

If you do come across any more useful debugging information, please feel free to post it on this topic – as it may well be helpful in getting a bug fix for this.

Thanks!

Kind Regards,
Tim

[Tim]

Hi Alberto,

Have you checked the API permissions for your Azure app?

Kind Regards,
Tim

[Tim]

Hi Martine,

Can I ask you to create another topic here, so we don’t lose track of your problem? It seems slightly different, but I’m keen that we look into it though.

Thank you!

Kind Regards,
Tim

[Tim]

Hi Karen,

Any further thoughts/updates on this from you?

Kind Regards,
Tim

[Tim]

Hi David,

That’s unusual. Are you sending from @jitterbyte.com? Normally this would sound like an SPF issue, but I checked yours and it’s set up completely correctly.

Does the issue affect mail sent only to your internal Office 365 accounts, or all Office 365 accounts, including ones not in your tenancy.

Thanks.

Kind Regards,
Tim

[Tim]

Hi Test Download,

This is certainly not normal behaviour. Please could you paste your Post SMTP diagnostics log here? If you want to keep your information private and hidden from the public and forum users, just check the ‘Set as private reply’ box on the reply.

Thanks!

Kind Regards,
Tim

[Tim]

Hi Alberto,

Try adding a trailing slash after your redirect URI.

Kind Regards,
Tim

[Tim]

Hi Andrew,

Okay, could you paste a copy of your Post SMTP diagnostics log? If you want to keep your site info private, please mark the reply as “private” using the relevant checkbox below. Your reply will then only be visible to you, me, and the plugin creator – Yehuda.

Thanks.

Kind Regards,
Tim

[Tim]

Hi Andrew,

Are you able to update your WP core?

Kind Regards,
Tim

[Tim]

Hi Andrew,

Thanks for posting. What version of Post SMTP and the extension are you running?

Kind Regards,
Tim

[Tim]

Thanks for feeding back Ray, that’s helpful!

Kind Regards,
Tim

[Tim]

Hi Ray,

Thanks for confirming this issue is resolved. Could I ask what you did to fix the problem? Any information you provide could be massively valuable and helpful to others in the future too.

Site is looking good already, thanks for sharing! 🙂

Kind Regards,
Tim

[Tim]

This might be helpful too: https://shouts.dev/php-curl-error-code-60-ssl-certificate-problem-solved

[Tim]

Hi Ray,

I had this with a user the other week. I actually asked the developer Yehuda about it, as he is more clued up on that than me.

The specific error that you got, looking at the docs relates to:
The remote server's SSL certificate or SSH md5 fingerprint was deemed not OK. This error code has been unified with CURLE_SSL_CACERT since 7.62.0. Its previous value was 51.

This is a different certificate than your public HTTPS certificate from CertifyTheWeb.

In some cases, it may be that you are missing a CA certificate installed on your server – so installing/re-installing that might help.

If you could also share your site’s URL with us that’d be great. If you want to keep this private, you can mark the reply as ‘private’ and it is only visible to myself, you, and the developer/creator Yehuda.

Thanks.

Kind Regards,
Tim

[Tim]

Hi Ray,

There is a problem with your hosting server, please contact your provider and ask them to check the servers certificate. cURL is making a certificate check and failing.

Kind Regards,
Tim

[Author]

Posts