On 01/19/2018 12:48 PM, Alan McKinnon wrote:
I'm also wondering why you need 2 bits. Earlier in the thread you mentioned that you send perhaps a few messages a week and never more than one connection at a time.
Grant E. has indicated elsewhere in the thread that his /usr/bin/sendmail script is speaking something custom to the destination mail server.
Read: /usr/bin/sendmail script is NOT speaking SMTP.
Why do you need anything more complex than ssmtp? where are the messages coming from? localhost? the lan? somewhere on the internet?
Do you know what protocol(s) that Grant E.'s /usr/bin/sendmail script is speaking? Do you know if ssmtp (et al) support it?
I feel like Grant E. has not revealed enough information to know if other things can speak what ever custom communications is possible between the SMTP server and the destination mail server. He has only revealed enough to know that it is custom, and that his /usr/bin/sendmail interface script must be used.
Grant, you should explain your requirements in detail, and not describe what you currently have (broken, as you say). Otherwise I'm going to give you boilerplate advice:
Arguably Grant E. has described his requirements. - That being said, questioning the motivation behind the requirements is worth exploring far enough to see if it's pertinent.
Grant E. has also, revealed that the broken bit is more the lack of functional encryption support, not lack of overall functionality. Thus I feel like "currently have (broken, as you say)" is inaccurate.
Use ssmtp, unless the mail isn't coming from localhost and you need simple (use postfix); otherwise if your setup is tricky use exim.
I don't think there is enough information to know that ssmtp / postfix / exim / sendmail / et al are capable of speaking the protocols that Grant E. needs or wants.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
