You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Modern PHP versions, if you're creating a TLS connection the certificate needs to be valid, and will fail with an uninformative error if the certificate is incorrect
This bit me because the cerificate on our SMTP host is valid, but for development we refer to it as 'intmail' (10.x.x.x) not 'mail' (203.x.x.x). The certificate is only valid for 'mail'.
Because of this, I've explicitly disabled TLS, but, because the server still offers STARTTLS, the AutoTLS flag means that phpMailer tries to convert it to TLS, the certificate errors, and the connection is dropped.
The text was updated successfully, but these errors were encountered:
xrobau
added a commit
to xrobau/UserFrosting-1
that referenced
this issue
May 30, 2019
I can't find the other issue, but there was this idea to have a setting to send all mail to some sort of log file in development. It would help all sort of issue with mail in development mode. For example, right now, we can't create users in development mode without email support. It also mean you can spam your user when testing something in development mode with a copy of the production db 😱.
On Modern PHP versions, if you're creating a TLS connection the certificate needs to be valid, and will fail with an uninformative error if the certificate is incorrect
https://github.com/PHPMailer/PHPMailer/blob/master/src/PHPMailer.php#L282
This bit me because the cerificate on our SMTP host is valid, but for development we refer to it as 'intmail' (10.x.x.x) not 'mail' (203.x.x.x). The certificate is only valid for 'mail'.
Because of this, I've explicitly disabled TLS, but, because the server still offers STARTTLS, the AutoTLS flag means that phpMailer tries to convert it to TLS, the certificate errors, and the connection is dropped.
The text was updated successfully, but these errors were encountered: