-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lack of having the option to not verifying mail server (tls_skip_verify) #498
Comments
Hey @erfantkerfan, we are already tracking this task in our internal system (PB-26156). We'll let you know once we have any update. |
I think we have the same issue. Our mailrelay allows STARTTLS, and plain mail to be send, and sending a test mail from Passbolt works like a charm. All other mails get a TLS error. Setting This is the backtrace I can see when sending a mail fails:
Edit: We use our own CA, and the CA Certificate is present in |
Hey @oyxnaut, we will be releasing the support for self-signed certificate for SMTP server with upcoming release (v4.7.0). Also, as a Passbolt Pro user you can reach out to [email protected] for further support. |
…f-signed cert on my mail server (GITHUB #498)
…to-use-TLS-with-a-self-signed-cert-on-my-mail-server-GITHUB-498' into 'common' PB-26156 As administrator, I can configure SMTP to use TLS with a self-signed cert on my mail server (GITHUB #498) See merge request passbolt/passbolt-pro-api!1535
We have released support this with v4.7 release. The documentation is under progress, but here's what you can do to tell passbolt to use your custom root CA file:
Or, you can also use environment variables:
If you want to skip verification (not recommended) then you can set |
I saw the release, but this is great support for your FOSS project, replying me in person. |
The lack of this feature is causing a lot of problems for us,
Would it be possible to add the option to skip TLS verification of the (SMTP) mail server?
Thanks a lot
https://community.passbolt.com/t/feature-tls-skip-verify-for-self-signed-smtp-email/8640/1
The text was updated successfully, but these errors were encountered: