Created attachment 308679 [details, diff] Patch adding TLSKey option. The current versions of sSMTP require the client key and certificate in a single file (`TLSCert`) if you're authenticating your client using TLS. Often, keys (secret) and certificates (public) are stored in separate files. The ability to use separate files was listed as one of the TODO options in the `TLS` readme. I wanted the functionality, so I've implemented it via a new `TLSKey` option. This is a duplicate of Debian bug report 662958 [1], but since upstream sSMTP seems pretty much dead, I thought I'd see if I could at least get this patch included in the Portage tree. I've attached the patch from the Debian bug report. [1]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662958
Patch is innocent enough but still I am going to close this bug as UPSTREAM. You might want to try some other mta (msmtp or similar) if seperate key/cert files are critical for your setup. Sorry.