Re: Blat and stunnel: SSL_accept: Peer suddenly disconnected

"Frank Cazabon [email protected] [blat]" <[email protected]>
Newsgroups gmane.mail.blat
Organization Samaan Systems Ltd.
Message-ID <[email protected]>
It turns out I was misled by not reading the full error messages when I 
first got the problem.

The blat log said:

 >>>putline>>> AUTH PLAIN  *****
<<<getline<<< 535 Authentication failed
*** Warning ***  The SMTP server did not accept Auth PLAIN value.
*** Warning ***  Are your login userid and password correct?

I stopped reading at the first warning and assumed it meant I couldn't 
send the password as a plain text value, so it had to be sent using 
SSL.  This was confused by their Outlook setup having the SSL checkbox 
checked too.

I got them to re-enter their password and took stunnel out of the 
equation and it al worked.

Thanks for all the help.



On 11/05/2015 07:44 PM, Frank Cazabon wrote:
> OK, thanks. As you can see I know nothing about this kind of stuff. 
> The error I got from blat when I tried it without stunnel made me 
> think I needed SSL. I didn't know specific ports were for specific types.
>
> I'll try it again without s tunnel and come back here with the error I 
> get.
>
> On 11 May 2015 19:18:17 GMT-04:00, "'Mike Mattos' [email protected] 
> [blat]" <[email protected]> wrote:
>
>     No, because port 25 is used for unsecured email, and rarely used
>     any more. SMTP using SSL is typically on port 465
>
>     Stunnel is a wrapper that handles SSL , you give stunnel a local
>     ip and port , usually 127.0.0.1 plus a high port not in use, like
>     127.0.0.1:2025
>
>     And point it to smtp.my_service_provider.com:465
>
>     Blat in installed as blat 127.0.0.1:2025 which means blat connects
>     to stunnel, and stunnel relays using SSL. But you do have to
>     provide the user and password info for my_service_provider
>
>     Mike
>
>     From: [email protected] [mailto:[email protected]]
>     Sent: May-11-15 18:31
>     To: [email protected]
>     Subject: RE: [blat] Blat and stunnel: SSL_accept: Peer suddenly
>     disconnected
>
>     Because it requires SSL, so don't I need to use stunnel for that?
>
>     On 11 May 2015 17:13:50 GMT-04:00, "'Mike Mattos'
>     [email protected] [blat]" <[email protected]> wrote:
>
>     If 25, why bother with stunnel?
>
>     Mike Mattos
>
>     “Confidence is what you have before you understand the problem.”
>
>     Woody Allen <http://www.goodreads.com/author/show/10356.Woody_Allen>
>
>     From: [email protected] [mailto:[email protected]]
>     Sent: May-11-15 14:18
>     To: [email protected]
>     Subject: Re: [blat] Blat and stunnel: SSL_accept: Peer suddenly
>     disconnected
>
>     On 11/05/2015 10:35 AM, 'Skand Bhargava' [email protected]
>     [blat] wrote:
>
>     I think it is listening on port 587, not 25..
>
>     Do you mean their smtp server is listening on 587?
>
>     They are pretty sure that it is 25. That is how they have their
>     Outlook set up.
>
>     -----Original Message-----
>     From: [email protected] [mailto:[email protected]]
>     Sent: Monday, May 11, 2015 5:27 PM
>     To: [email protected]
>     Subject: Re: [blat] Blat and stunnel: SSL_accept: Peer suddenly
>     disconnected
>
>     I'm now trying this at my client site and getting this displayed:
>
>     2015.05.11 09:35:37 LOG6[main]: Initializing service [smtp]
>     2015.05.11 09:35:37 LOG5[main]: Configuration successful
>     2015.05.11 09:35:59 LOG5[3]: Service [smtp] accepted connection
>     from 127.0.0.1:2852
>     2015.05.11 09:35:59 LOG6[3]: Failover strategy: round-robin
>     2015.05.11 09:35:59 LOG6[3]: s_connect: connecting 172.16.9.6:25
>     2015.05.11 09:35:59 LOG5[3]: s_connect: connected 172.16.9.6:25
>     2015.05.11 09:35:59 LOG5[3]: Service [smtp] connected remote
>     server from 10.187.11.65:2853
>     2015.05.11 09:35:59 LOG6[3]: SNI: sending servername:
>     axigen.republictt.com
>     2015.05.11 09:35:59 LOG3[3]: SSL_connect: 140770FC:
>     error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
>     2015.05.11 09:35:59 LOG5[3]: Connection reset: 0 byte(s) sent to
>     SSL, 0 byte(s) sent to socket
>
>     This is the stunnel.conf file:
>
>     debug = info
>     output = stunnel.log
>
>     RNDfile = .rnd
>     sslVersion = all
>     fips = no
>
>     [smtp]
>     client = yes
>     accept = 127.0.0.1:27
>     connect = axigen.********.com:25
>     ;verify = 2
>     ;CAfile = ca-certs.pem
>     ;checkHost = smtp.gmail.com
>
>     Can anyone tell me what to do to fix this?
>
>     On 11/05/2015 07:25 AM, Frank Cazabon wrote:
>
>     Thanks Chip.
>
>     Once I used your settings but removed the CAfile and cert entries,
>     it worked!
>
>     Now I need to see if I can get this working at a client site with
>     their own secured smtp server.
>
>     On 10/05/2015 08:55 PM, 'Chip' [email protected] [blat] wrote:
>
>     > Frank,
>     >
>     > Take a look at the example page, http://www.blat.net/examples/,
>     at the
>     > bottom is Chip’s configuration file. It may have some clues that
>     will
>     > help.
>     >
>     > Cheers,
>     >
>     > Doug
>
>     Frank,
>
>     Here is my stunnel.conf file that works with Gmail. Please take
>     note of the
>     first section, and the last section.
>
>     Chip
>
>     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
>
>
> -- 
> Frank Cazabon
>
> Sent from my phone. Please excuse my brevity. 


-- 

Frank.

Frank Cazabon
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.