Re: Installation of Blat

"[email protected] [blat]" <[email protected]> 09 Nov 2017 07:28:19 +0000
Newsgroups gmane.mail.blat
Message-ID <[email protected]>
Found out that the Web host we are using is phasing out non-encrypted SMTP, so it looks I have to look into this option now. I downloaded Stunnel and installed it on my machine.
 Next I started the exe and answered some questions about my region and organisation.
 

 Both the Documentation and the sample config file almost killed me with tons of terms I have no idea what they mean, so I am trying to find a configuration to use, with the least possible amount of data.
 

 I found the following example in thestunnel.conf file, and thought I could alter it with my data:

Here is an example I think is appropriate:

 [mypos smtp]
 accept = 25
 connect = smtp.mypos.com:26
 protocol = smtp
 

In Blat, I specified 17.0.0.1 as the mail server, 25 as the port, use the base64 encoded values for Login and Password, and sendmail.mypos.com as sender.
 

 Bad news: I still dont understand a lot of what I am doing. Good news: All is working!
 

 Thanks a lot!
 

 Now I need to find a way to install stunnel in such a way that people with much less IT knowledge than myself can install the system. I guess I can reuse my conf file. What about the certificate file? Does that need to be created locally at every installation, or can I distribute it?
 

 

 

 
 
 Outside of anything already stated by others, there is one issue not yet 
 mentioned. Blat does not directly support SSL or TLS for encrypted 
 connections, which is used by port 586 mentioned above. However, this is 
 easily supported by using stunnel from stunnel.org to provide that 
 encryption. This is what I do at home, I use stunnel to provide TLS 
 encryption to AT&T, Hotmail, and Google (gmail). Blat is then told to use 
 IP address 127.0.0.1 for its SMTP server, which uses stunnel to establish 
 the encrypted connection. The job of stunnel is only to provide encryption. 
 As such, Blat is able to then establish a connection to the intended server, 
 and use login credentials. The stunnel configuration file will tell stunnel 
 the names of all servers you intent to use, and which ports to listen on for 
 making connections to each server. There are references to stunnel in the 
 Yahoo message list, including example configuration files. The accept= 
 statements in the list below tells stunnel which ports to listen on, and 
 those dictate which servers will be connected when Blat talks on the listed 
 port numbers. Here is part of my stunnel.conf file that you can use as a 
 basis for your situation:
 
 CAfile = cert.pem
 cert = client.pem
 client = yes
 RNDfile = .rnd
 sslVersion = TLSv1
 fips = no
 
 [att yahoo smtp]
 accept = 25
 connect = outbound.att.net:465
 
 [att yahoo pop3]
 accept = 110
 connect = inbound.att.net:995
 
 [hotmail smtp]
 accept = 8002
 connect = smtp.live.com:587
 protocol = smtp
 
 [hotmail pop3]
 accept = 9002
 connect = pop3.live.com:995
 
 [gmail smtp]
 accept = 27
 connect = smtp.gmail.com:587
 protocol = smtp
 
 -- 
 Chip