RE: hotmail troubles

"'Miller Family' [email protected] [blat]" <[email protected]>
Newsgroups gmane.mail.blat
Message-ID <C511913C4440479C953E70C4E4AFD472@LAPTOP>
Thanks all!!


 


 


[gmail-pop3]


client = yes


accept = 127.0.0.1:110


connect = pop.gmail.com:995


verify = 2


CAfile = ca-certs.pem


checkHost = pop.gmail.com


OCSPaia = yes


 


[gmail-imap]


client = yes


accept = 127.0.0.1:143


connect = imap.gmail.com:993


verify = 2


CAfile = ca-certs.pem


checkHost = imap.gmail.com


OCSPaia = yes


 


[live-smtp]


client = yes


accept = 127.0.0.1:28


connect = smtp.live.com:587


verify = 2


CAfile = ca-certs.pem


checkHost = smtp.live.com


OCSPaia = yes


sslVersion = all


options = NO_SSLv2


protocol = smtp


 


; Encrypted HTTP proxy authenticated with a client certificate


; located in the Windows certificate store


;[example-proxy]


;client = yes


;accept = 127.0.0.1:8080


;connect = example.com:8443


;engineId = capi


 


; ***************************************** Example TLS server mode services


 


;[pop3s]


;accept  = 995


;connect = 110


;cert = stunnel.pem


 


;[imaps]


;accept  = 993


;connect = 143


;cert = stunnel.pem


 


;[ssmtp]


;accept  = 465


;connect = 25


;cert = stunnel.pem


 


; TLS front-end to a web server


;[https]


;accept  = 443


;connect = 80


;cert = stunnel.pem


; "TIMEOUTclose = 0" is a workaround for a design flaw in Microsoft SChannel


; Microsoft implementations do not use TLS close-notify alert and thus they


; are vulnerable to truncation attacks


;TIMEOUTclose = 0


 


; Remote cmd.exe protected with PSK-authenticated TLS


; Create "secrets.txt" containing IDENTITY:KEY pairs


;[cmd]


;accept = 1337


;exec = c:\windows\system32\cmd.exe


;execArgs = cmd.exe


;ciphers = PSK


;PSKsecrets = secrets.txt


 


; vim:ft=dosini


 


 


 


 


 


  _____  


From: [email protected] [mailto:[email protected]] 
Sent: Monday, May 02, 2016 11:44 AM
To: [email protected]
Subject: Re: [blat] hotmail troubles


 


  


Please copy your stunnel.conf into here (no attachments) so we can view how
you have it configured.  It appears that port 28 might not be correct, so
the stunnel.conf will tell us what is the correct port number.


 


Thanks,


Chip
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.