Apologies for resurrecting an old thread.
I’m currently deploying a Passbolt server internally and sending email via an internal smarthost server (Postfix). Which has a certificate signed by our internal CA. (All corporate CA’s are self-signed, if you will).
So if there a way to add a root CA to the trust store that Passbolt uses so that TLS can be used for sending email? We’d like to use TLS also for internal email transport.
This even older post alludes to pointing to a root ca for email TLS verification. Passbolt SMTP TLS Problems - #9 by Gerold
But there are several files which reference
user@host:~$ sudo grep EmailTransport /etc/ -R grep: /etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service: No such file or directory grep: /etc/systemd/system/dbus-org.freedesktop.timesync1.service: No such file or directory grep: /etc/alternatives/php-fpm.sock: No such device or address /etc/passbolt/passbolt.default.php: 'EmailTransport' => [ /etc/passbolt/app.default.php: 'EmailTransport' => [ /etc/passbolt/bootstrap.php:Configure::write('EmailTransport.default.className', SmtpTransport::class); /etc/passbolt/bootstrap.php:Configure::write('EmailTransport.Debug.className', DebugTransport::class); /etc/passbolt/bootstrap.php:TransportFactory::setConfig(Configure::consume('EmailTransport')); /etc/passbolt/app.php: 'EmailTransport' => [
So which one to change, would these edits survive Passbolt updates? Wouldn’t it be nice to expose this option in the GUI?