Lucio Crusca writes:
Hello,I've just installed a new Courier instance in a new Debian GNU/Linux 9 amd64 server from distro packages.This Courier should act as smart relay for another server and nothing else.So far I've enabled courier-mta and courier-msa systemd services, changed the ports they listed on and created a real system account for mail relay (authpam). I've also letTLS_VERIFYPEER=NONE in /etc/courier/courierd.Then I tested the smarthost from Thunderbird, by configuring it as outgoing server. It does not work. When TB tries to send a message, it connects to the non-default MSA port, it starts talking to the server (STARTTLS) for a few seconds, then it fails for "unknown reason". Server-side, in the logs, I get:Jul 19 04:48:17 mrelay courieresmtpd: started,ip=[::ffff:80.180.158.103]Jul 19 04:48:18 mrelay courieresmtpd: courieresmtpd: STARTTLS failed: Certificate is badI don't know what to try next.
Check the server's certificate, esmtpd.pem. That's the only certificate in play here. The file is probably corrupted.
pgp4Q8tPJRZML.pgp
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users