Dear Celejar, Celejar <cele...@gmail.com> writes:
> On Tue, 26 Apr 2022 09:42:38 +0900 > 황병희 <soyeo...@doraji.xyz> wrote: > >> Dear Greg, >> >> Greg Wooledge <g...@wooledge.org> writes: >> >> > (... thanks ...) >> > unicorn:~$ apt-cache show ssmtp >> > [...] >> > Description-en: extremely simple MTA to get mail off the system to >> > a mail hub >> > A secure, effective and simple way of getting mail off a system to your >> > mail hub. It contains no suid-binaries or other dangerous things - no mail >> > spool to poke around in, and no daemons running in the background. Mail is >> > simply forwarded to the configured mailhost. Extremely easy configuration. >> > >> > The entire point of this package is that it's meant to be used on a >> > "dumb client" which does not wish to have its own outgoing mail queue. >> > Instead, it forwards all of your mail to your "smart host" -- the MTA >> > that has been set up for your organization's dumb clients to use. >> > >> > So, the single piece of information you need in order to use ssmtp is >> > the hostname of your smart host. Also known as your mail relay. Or many >> > other names. It's where you want your outgoing mail to be handled. >> > >> >> Thanks for your time and your life! >> >> Really i love sSMTP so much!!! > > FWIW, there's an outstanding ten year old bug against sSMTP pointing > out that it doesn't bother to validate server TLS certificates. You'll > have to decide whether this bothers you or not: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662960 That seems some technical issue. However i have no skills to repair that C level program. Actually i have no trouble with current sSMTP. Both Gmail and yw-1204 does not break about this matter (verify certificate). So for a while i'll keep this state. It means that i will continue to use the sSMTP. Sorry and thanks ^^^ Sincerely, Linux fan Byung-Hee -- ^고맙습니다 _布德天下_ 감사합니다_^))//
