After updating osclass 3.6.1 to 3.7.3 no validation mail is sent by the website

[rakesh kumar]

After upgrading from Osclass 3.6.1 to Osclass 3.7.3 the problem was arose that mail was not sent by the system after registering the user and anyone is unable to recover the forget password by mail.

[Aficionado]

After upgrading from Osclass 3.6.1 to Osclass 3.7.3 the problem was arose that mail was not sent by the system after registering the user and anyone is unable to recover the forget password by mail.

Do you have SSL enabled site ?

[BritWeb]

After upgrading from Osclass 3.6.1 to Osclass 3.7.3 the problem was arose that mail was not sent by the system after registering the user and anyone is unable to recover the forget password by mail.

I had the same issue after upgrading to 3.7.3 and my site is SSL’ed. I had my site’s email address in the field ‘Mail from’ in ‘Mail Settings’ and once I removed it everything worked fine. See the pic attached that shows my current settings and try this.

Don’t shoot in the dark. SSL has nothing to do with this.

[uve]

I have similar problem with SSL in my site after update to 3.7.3 .

When I trying to send email to owner of ad, I get this error:

Warning: stream_socket_enable_crypto(): SSL operation failed with code 1. OpenSSL Error messages: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed in /home/gielda/domains/gieldarowerowa.net/public_html/oc-includes/phpmailer/class.smtp.php on line 367

Warning: Cannot modify header information - headers already sent by (output started at /home/gielda/domains/gieldarowerowa.net/public_html/oc-includes/osclass/utils.php:1738) in /home/gielda/domains/gieldarowerowa.net/public_html/oc-includes/osclass/utils.php on line 1743

[dev101]

This is simply related to your hosting and email server config @ Osclass admin, but it falls outside Osclass scope, because it is impossible to know all parameters. You need to work with your hosting support to resolve it. What works for BritWeb above, will not work for everyone.

[_CONEJO]

Here's the thing. In the last version we also updated PHPMailer (due to a vulnerability). This version of PHPMailer verify the validity of the certificate (it's the correct domain, it's not expired,...) of your email server by default. This is how things have to be, if you use a certificate but it's expired or issue to the wrong domain, it shouldn't work. You could disable this check (in the code) but we do not recommend it.

So, what is happening? Well, some hosting are using the wrong certificate when their clients connect to their mail servers. Your  hosting company probably has something like "mailserver3.hostingcompany.tld" and you could probably connect to the same server with your domain in a nicer way with "mail.yourdomain.tld". The problem is that your hosting company (probably) only issued a certificate for mailserver3.hostingcompany.tld, so when you are connecting through mail.yourdomain.tld, the certificate belongs to a different domain (but same server). and thus failing to connect and send any email.

There several ways to fix this, the first is to ask your hosting company to do things properly and use the correct certificate (they are free!), you could use directly "mailserver3.hostingcompany.tld" as your email server, so the certificate is correct, or you could modify Osclass to disable the verification (which we do not recommend). The modifications are explained here : https://forums.osclass.org/3-7-x/update-to-3-7-3-my-findings/msg149561/#msg149561

The problem might be different, but this seems to be a probable cause