2
1
Stunnel running as service on Windows Server 2008 R2 but Stunnel All Users shortcut on the desktop reports that it server is down?
by Alex Birchall 16 May '18
by Alex Birchall 16 May '18
16 May '18
Hello,
I have Stunnel running as a service on a Windows Server 2008 R2. But the shortcut on the desktop "Stunnel All Users", when launched, informs me that the server is down due to an "invalid configuration file".
In the config file, if Stunnel is being run as a service, should it be "client = no" or "server = yes"?
Many thanks.
Best regards,
Alex
2
2
Hi List,
I have just joined the stunnel community.
I am in the process of migrating our mailserver's public facing ports to
stunnel for PCI compliance reasons.
So far i have managed to get working:
- imap (143/tcp) with starttls
- imaps (993/tcp)
- pop3 (110/tcp) with starttls
- pop3s (995/tcp)
My trouble is with smtp(25/tcp,587/tcp) with starttls.
I have now tried a couple different mail clients and everyone of them tells
me that the server does not support the authentication protocols.
I have installed stunnel 5.44. Tee relevant parts in my config:
[mail2-imap]
protocol = imap
accept = 143
connect = <mail-fqdn>:143
[mail2-imaps]
accept = 993
connect = <mail-fqdn>:143
[mail2-pop3]
protocol = pop3
accept = 110
connect = <mail-fqdn>:110
[mail2-pop3s]
accept = 995
connect = <mail-fqdn>:110
[mail2-smtp]
protocol = smtp
accept = 25
connect = <mail-fqdn>:25
[mail2-smtps]
accept = 465
connect = <mail-fqdn>:465
[mail2-smtps-submission]
debug = 7
protocol = smtp
accept = 587
connect = <mail-fqdn>:587
In the logfile I have the following entries upon connecting
2018.04.30 09:20:50 LOG7[5]: Service [mail2-smtps-submission] started
2018.04.30 09:20:50 LOG7[5]: Option TCP_NODELAY set on local socket
2018.04.30 09:20:50 LOG5[5]: Service [mail2-smtps-submission] accepted
connection from 41.13.8.49:56890
2018.04.30 09:20:50 LOG6[5]: s_connect: connecting 10.10.11.2:587
2018.04.30 09:20:50 LOG7[5]: s_connect: s_poll_wait 10.10.11.2:587: waiting
10 seconds
2018.04.30 09:20:50 LOG5[5]: s_connect: connected 10.10.11.2:587
2018.04.30 09:20:50 LOG5[5]: Service [mail2-smtps-submission] connected
remote server from 10.10.11.11:42466
2018.04.30 09:20:50 LOG7[5]: Option TCP_NODELAY set on remote socket
2018.04.30 09:20:50 LOG7[5]: Remote descriptor (FD=23) initialized
2018.04.30 09:20:50 LOG7[5]: RFC 2487 detected
2018.04.30 09:20:50 LOG7[5]: <- 220 <mail-fqdn> ESMTP Postfix
2018.04.30 09:20:50 LOG7[5]: -> 220 <mail-fqdn> stunnel for ESMTP Postfix
2018.04.30 09:20:51 LOG7[5]: <- EHLO [100.125.153.220]
2018.04.30 09:20:51 LOG7[5]: -> 250-<mail-fqdn>
2018.04.30 09:20:51 LOG7[5]: -> 250 STARTTLS
2018.04.30 09:20:51 LOG7[5]: <- STARTTLS
2018.04.30 09:20:51 LOG7[5]: -> 220 Go ahead
2018.04.30 09:20:51 LOG6[5]: Peer certificate not required
2018.04.30 09:20:51 LOG7[5]: TLS state (accept): before/accept
initialization
2018.04.30 09:20:51 LOG7[5]: SNI: no virtual services defined
2018.04.30 09:20:51 LOG7[5]: TLS state (accept): SSLv3 read client hello A
2018.04.30 09:20:51 LOG7[5]: TLS state (accept): SSLv3 write server hello A
2018.04.30 09:20:51 LOG7[5]: TLS state (accept): SSLv3 write certificate A
2018.04.30 09:20:51 LOG7[5]: TLS state (accept): SSLv3 write key exchange A
2018.04.30 09:20:51 LOG7[5]: TLS state (accept): SSLv3 write server done A
2018.04.30 09:20:51 LOG7[5]: TLS state (accept): SSLv3 flush data
2018.04.30 09:20:51 LOG7[5]: TLS state (accept): SSLv3 read client
certificate A
2018.04.30 09:20:52 LOG7[5]: TLS state (accept): SSLv3 read client key
exchange A
2018.04.30 09:20:52 LOG7[5]: TLS state (accept): SSLv3 read certificate
verify A
2018.04.30 09:20:52 LOG7[5]: TLS state (accept): SSLv3 read finished A
2018.04.30 09:20:52 LOG7[5]: TLS state (accept): SSLv3 write change cipher
spec A
2018.04.30 09:20:52 LOG7[5]: TLS state (accept): SSLv3 write finished A
2018.04.30 09:20:52 LOG7[5]: TLS state (accept): SSLv3 flush data
2018.04.30 09:20:52 LOG7[5]: New session callback
2018.04.30 09:20:52 LOG7[5]: 2 server accept(s) requested
2018.04.30 09:20:52 LOG7[5]: 2 server accept(s) succeeded
2018.04.30 09:20:52 LOG7[5]: 0 server renegotiation(s) requested
2018.04.30 09:20:52 LOG7[5]: 0 session reuse(s)
2018.04.30 09:20:52 LOG7[5]: 2 internal session cache item(s)
2018.04.30 09:20:52 LOG7[5]: 0 internal session cache fill-up(s)
2018.04.30 09:20:52 LOG7[5]: 0 internal session cache miss(es)
2018.04.30 09:20:52 LOG7[5]: 0 external session cache hit(s)
2018.04.30 09:20:52 LOG7[5]: 0 expired session(s) retrieved
2018.04.30 09:20:52 LOG6[5]: TLS accepted: new session negotiated
2018.04.30 09:20:52 LOG6[5]: No peer certificate received
2018.04.30 09:20:52 LOG6[5]: Negotiated TLSv1.2 ciphersuite
ECDHE-RSA-AES128-GCM-SHA256 (128-bit encryption)
2018.04.30 09:20:52 LOG7[5]: Compression: null, expansion: null
2018.04.30 09:20:52 LOG6[5]: Read socket closed (read hangup)
2018.04.30 09:20:52 LOG7[5]: Sending close_notify alert
2018.04.30 09:20:52 LOG7[5]: TLS alert (write): warning: close notify
2018.04.30 09:20:52 LOG6[5]: SSL_shutdown successfully sent close_notify
alert
2018.04.30 09:20:52 LOG6[5]: TLS fd: Connection reset by peer (104)
2018.04.30 09:20:52 LOG6[5]: TLS socket closed (SSL_read)
2018.04.30 09:20:52 LOG7[5]: Sent socket write shutdown
2018.04.30 09:20:52 LOG5[5]: Connection closed: 156 byte(s) sent to TLS, 30
byte(s) sent to socket
2018.04.30 09:20:52 LOG7[5]: Remote descriptor (FD=23) closed
2018.04.30 09:20:52 LOG7[5]: Local descriptor (FD=22) closed
2018.04.30 09:20:52 LOG7[5]: Service [mail2-smtps-submission] finished (4
left)
This is the error I am getting from K9-Mail
The google mail app just tells me:
Alpine (linux commandline smtp client)
Any advise from the gurus?
Kind regards
Ian
1
1
Hi
I am using lastest stunnel version.
When i try to send an email, i get:
"error permanente de SMTP: 503 Bad sequence of commands".
This is the trace generated when I try to send an email.
2018.05.14 12:59:08 LOG5[main]: Reading configuration from file stunnel.conf
2018.05.14 12:59:08 LOG5[main]: UTF-8 byte order mark not detected
2018.05.14 12:59:08 LOG5[main]: FIPS mode disabled
2018.05.14 12:59:08 LOG5[main]: Configuration successful
2018.05.14 12:59:08 LOG7[main]: Binding service [pseudo-ssmtp]
2018.05.14 12:59:08 LOG7[main]: Listening file descriptor created (FD=568)
2018.05.14 12:59:08 LOG7[main]: Option SO_EXCLUSIVEADDRUSE set on accept socket
2018.05.14 12:59:08 LOG7[main]: Service [pseudo-ssmtp] (FD=568) bound to 172.31.41.84:116
2018.05.14 12:59:08 LOG7[main]: Signal pipe is empty
2018.05.14 12:59:22 LOG7[main]: Found 1 ready file descriptor(s)
2018.05.14 12:59:22 LOG7[main]: FD=324 ifds=r-x ofds=r--
2018.05.14 12:59:22 LOG7[main]: Dispatching signals from the signal pipe
2018.05.14 12:59:22 LOG7[main]: Processing SIGNAL_RELOAD_CONFIG
2018.05.14 12:59:22 LOG7[main]: Running on Windows 6.1
2018.05.14 12:59:22 LOG5[main]: Reading configuration from file stunnel.conf
2018.05.14 12:59:22 LOG5[main]: UTF-8 byte order mark not detected
2018.05.14 12:59:22 LOG5[main]: FIPS mode disabled
2018.05.14 12:59:22 LOG7[main]: Compression disabled
2018.05.14 12:59:22 LOG7[main]: Snagged 64 random bytes from C:/.rnd
2018.05.14 12:59:22 LOG7[main]: Wrote 1024 new random bytes to C:/.rnd
2018.05.14 12:59:22 LOG7[main]: PRNG seeded successfully
2018.05.14 12:59:22 LOG6[main]: Initializing service [pseudo-ssmtp]
2018.05.14 12:59:22 LOG7[main]: Ciphers: HIGH:!DH:!aNULL:!SSLv2
2018.05.14 12:59:22 LOG7[main]: TLS options: 0x03000004 (+0x03000000, 0x00000000)
2018.05.14 12:59:22 LOG6[main]: Loading certificate from file: stunnel.pem
2018.05.14 12:59:22 LOG6[main]: Certificate loaded from file: stunnel.pem
2018.05.14 12:59:22 LOG6[main]: Loading private key from file: stunnel.pem
2018.05.14 12:59:22 LOG6[main]: Private key loaded from file: stunnel.pem
2018.05.14 12:59:22 LOG7[main]: Private key check succeeded
2018.05.14 12:59:22 LOG5[main]: Configuration successful
2018.05.14 12:59:22 LOG7[main]: Unbinding service [pseudo-ssmtp]
2018.05.14 12:59:22 LOG7[main]: Service [pseudo-ssmtp] closed (FD=568)
2018.05.14 12:59:22 LOG7[main]: Service [pseudo-ssmtp] closed
2018.05.14 12:59:22 LOG7[main]: Binding service [pseudo-ssmtp]
2018.05.14 12:59:22 LOG7[main]: Listening file descriptor created (FD=568)
2018.05.14 12:59:22 LOG7[main]: Option SO_EXCLUSIVEADDRUSE set on accept socket
2018.05.14 12:59:22 LOG7[main]: Service [pseudo-ssmtp] (FD=568) bound to 172.31.41.84:116
2018.05.14 12:59:22 LOG7[main]: Signal pipe is empty
2018.05.14 12:59:34 LOG7[main]: Found 1 ready file descriptor(s)
2018.05.14 12:59:34 LOG7[main]: FD=324 ifds=r-x ofds=---
2018.05.14 12:59:34 LOG7[main]: Service [pseudo-ssmtp] accepted (FD=584) from 172.31.41.84:53557
2018.05.14 12:59:34 LOG7[main]: Creating a new thread
2018.05.14 12:59:34 LOG7[main]: New thread created
2018.05.14 12:59:34 LOG7[37]: Service [pseudo-ssmtp] started
2018.05.14 12:59:34 LOG7[37]: Option TCP_NODELAY set on local socket
2018.05.14 12:59:34 LOG5[37]: Service [pseudo-ssmtp] accepted connection from 172.31.41.84:53557
2018.05.14 12:59:34 LOG6[37]: failover: round-robin, starting at entry #1
2018.05.14 12:59:34 LOG6[37]: s_connect: connecting 212.227.15.158:465
2018.05.14 12:59:34 LOG7[37]: s_connect: s_poll_wait 212.227.15.158:465: waiting 10 seconds
2018.05.14 12:59:34 LOG5[37]: s_connect: connected 212.227.15.158:465
2018.05.14 12:59:34 LOG5[37]: Service [pseudo-ssmtp] connected remote server from 172.31.41.84:53558
2018.05.14 12:59:34 LOG7[37]: Option TCP_NODELAY set on remote socket
2018.05.14 12:59:34 LOG7[37]: Remote descriptor (FD=552) initialized
2018.05.14 12:59:34 LOG6[37]: SNI: sending servername: smtp.1and1.es
2018.05.14 12:59:34 LOG6[37]: Peer certificate required
2018.05.14 12:59:34 LOG7[37]: TLS state (connect): before/connect initialization
2018.05.14 12:59:34 LOG7[37]: TLS state (connect): SSLv2/v3 write client hello A
2018.05.14 12:59:34 LOG7[37]: TLS state (connect): SSLv3 read server hello A
2018.05.14 12:59:34 LOG7[37]: Verification started at depth=2: C=US, O="thawte, Inc.", OU=Certification Services Division, OU="(c) 2006 thawte, Inc. - For authorized use only", CN=thawte Primary Root CA
2018.05.14 12:59:34 LOG7[37]: CERT: Pre-verification succeeded
2018.05.14 12:59:34 LOG7[37]: OCSP: Ignoring root certificate
2018.05.14 12:59:34 LOG6[37]: Certificate accepted at depth=2: C=US, O="thawte, Inc.", OU=Certification Services Division, OU="(c) 2006 thawte, Inc. - For authorized use only", CN=thawte Primary Root CA
2018.05.14 12:59:34 LOG7[37]: Verification started at depth=1: C=US, O="thawte, Inc.", CN=thawte SSL CA - G2
2018.05.14 12:59:34 LOG7[37]: CERT: Pre-verification succeeded
2018.05.14 12:59:34 LOG5[37]: OCSP: Connecting the AIA responder "http://t2.symcb.com"
2018.05.14 12:59:34 LOG6[37]: s_connect: connecting 23.5.251.27:80
2018.05.14 12:59:34 LOG7[37]: s_connect: s_poll_wait 23.5.251.27:80: waiting 10 seconds
2018.05.14 12:59:34 LOG5[37]: s_connect: connected 23.5.251.27:80
2018.05.14 12:59:34 LOG7[37]: OCSP: Connected t2.symcb.com:80
2018.05.14 12:59:34 LOG7[37]: OCSP: Response received
2018.05.14 12:59:34 LOG6[37]: OCSP: Status: good
2018.05.14 12:59:34 LOG6[37]: OCSP: This update: May 13 18:15:02 2018 GMT
2018.05.14 12:59:34 LOG6[37]: OCSP: Next update: May 20 18:15:02 2018 GMT
2018.05.14 12:59:34 LOG5[37]: OCSP: Certificate accepted
2018.05.14 12:59:34 LOG6[37]: Certificate accepted at depth=1: C=US, O="thawte, Inc.", CN=thawte SSL CA - G2
2018.05.14 12:59:34 LOG7[37]: Verification started at depth=0: C=DE, ST=Rheinland-Pfalz, L=Montabaur, O=1&1 Internet SE, CN=smtp.1and1.es
2018.05.14 12:59:34 LOG7[37]: CERT: Pre-verification succeeded
2018.05.14 12:59:34 LOG6[37]: CERT: Host name "smtp.1and1.es" matched with "smtp.1and1.es"
2018.05.14 12:59:34 LOG5[37]: OCSP: Connecting the AIA responder "http://tj.symcd.com"
2018.05.14 12:59:34 LOG6[37]: s_connect: connecting 23.5.251.27:80
2018.05.14 12:59:34 LOG7[37]: s_connect: s_poll_wait 23.5.251.27:80: waiting 10 seconds
2018.05.14 12:59:35 LOG5[37]: s_connect: connected 23.5.251.27:80
2018.05.14 12:59:35 LOG7[37]: OCSP: Connected tj.symcd.com:80
2018.05.14 12:59:35 LOG7[37]: OCSP: Response received
2018.05.14 12:59:35 LOG6[37]: OCSP: Status: good
2018.05.14 12:59:35 LOG6[37]: OCSP: This update: May 14 01:38:59 2018 GMT
2018.05.14 12:59:35 LOG6[37]: OCSP: Next update: May 21 01:38:59 2018 GMT
2018.05.14 12:59:35 LOG5[37]: OCSP: Certificate accepted
2018.05.14 12:59:35 LOG5[37]: Certificate accepted at depth=0: C=DE, ST=Rheinland-Pfalz, L=Montabaur, O=1&1 Internet SE, CN=smtp.1and1.es
2018.05.14 12:59:35 LOG7[37]: TLS state (connect): SSLv3 read server certificate A
2018.05.14 12:59:35 LOG7[37]: TLS state (connect): SSLv3 read server key exchange A
2018.05.14 12:59:35 LOG6[37]: Client certificate not requested
2018.05.14 12:59:35 LOG7[37]: TLS state (connect): SSLv3 read server done A
2018.05.14 12:59:35 LOG7[37]: TLS state (connect): SSLv3 write client key exchange A
2018.05.14 12:59:35 LOG7[37]: TLS state (connect): SSLv3 write change cipher spec A
2018.05.14 12:59:35 LOG7[37]: TLS state (connect): SSLv3 write finished A
2018.05.14 12:59:35 LOG7[37]: TLS state (connect): SSLv3 flush data
2018.05.14 12:59:35 LOG7[37]: TLS state (connect): SSLv3 read finished A
2018.05.14 12:59:35 LOG7[37]: 1 client connect(s) requested
2018.05.14 12:59:35 LOG7[37]: 1 client connect(s) succeeded
2018.05.14 12:59:35 LOG7[37]: 0 client renegotiation(s) requested
2018.05.14 12:59:35 LOG7[37]: 0 session reuse(s)
2018.05.14 12:59:35 LOG6[37]: TLS connected: new session negotiated
2018.05.14 12:59:35 LOG7[37]: Peer certificate was cached (5543 bytes)
2018.05.14 12:59:35 LOG6[37]: Negotiated TLSv1.2 ciphersuite ECDHE-RSA-AES256-GCM-SHA384 (256-bit encryption)
2018.05.14 12:59:35 LOG7[37]: Compression: null, expansion: null
2018.05.14 12:59:53 LOG3[36]: transfer: s_poll_wait: TIMEOUTclose exceeded: closing
2018.05.14 12:59:53 LOG5[36]: Connection closed: 15 byte(s) sent to TLS, 166 byte(s) sent to socket
I can't find the error.
Thanks in advance for your help.
Best regards,
Alix
2
5
stunnel-5.44 fails cross compile due to wrong include path in Gentoo....fix available
by Joe Harvell 14 May '18
by Joe Harvell 14 May '18
14 May '18
The src/Makefile.am hardcodes -I/usr/kerberos/include. When cross
compiling it should be including -I$(SYSROOT)//usr/kerberos/include.
I patched configure.ac and Makefile.am, taking advantage of the existing
--with-sysroot configure option.
The Gentoo bug report: https://bugs.gentoo.org/654374
The patch to configure.ac and Makefile.am:
https://654374.bugs.gentoo.org/attachment.cgi?id=528968
I was unable to find a bug reporting system for stunnel. So I guess this
is it. Please source this fix.
---
Joe Harvell
1
1
Hi,
We are running stunnel 5.44 on Solaris. Our b2b legacy system is using TLS 1.0. We have a supplier who recently switched to TLS 1.2 and we can no longer connect to the site from our b2b. How can I configure stunnel to connect to the supplier site using TLS 1.2? TIA.
Dan T
This message and any attachment are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person. If you have received this transmission in error, please notify the sender immediately and delete the message and any attachment from your system. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept liability for any omissions or errors in this message which may arise as a result of E-Mail-transmission or for damages resulting from any unauthorized changes of the content of this message and any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not guarantee that this message is free of viruses and does not accept liability for any damages caused by any virus transmitted therewith.
Click http://www.emdgroup.com/emd/imprint/mail_disclaimer.html to access the German, French, Spanish and Portuguese versions of this disclaimer.
1
0
Hello,
I have Stunnel installed on Windows Server 2008 R2, running as a service. I have it installed as a client on a Windows POS 2009 device.
This setup is working, in that the client is operating correctly and using Stunnel.
But how can I tell if communications between the Stunnel client and the Stunnel server are being encrypted, rather than Stunnel just doing port forwarding?
I did read the client needs to have access to the server's certificate, but at the moment it does not.
Alex
2
1
I am trying to get a device on my network to send pop email notifications to my outlook account but can't seem to get it to work. I have enabled the outlook account to accept pop and enabled the client to send them. I'm not sure if I'm missing something or what, any help would be greatly appreciated.
Here is my config:
debug = info
output = stunnel.log
[outlook-pop3]
client = yes
accept = 110
connect = pop-mail.outlook.com:995
[outlook-imap]
client = yes
accept = 143
connect = imap-mail.outlook.com:993
[outlook-smtp]
protocol = smtp
client = yes
accept = 25
connect = smtp-mail.outlook.com:587
Here is the log as well:
2018.05.08 15:15:03 LOG5[main]: stunnel 5.44 on x86-pc-msvc-1500 platform
2018.05.08 15:15:03 LOG5[main]: Compiled/running with OpenSSL 1.0.2m-fips 2 Nov 2017
2018.05.08 15:15:03 LOG5[main]: Threading:WIN32 Sockets:SELECT,IPv6 TLS:ENGINE,FIPS,OCSP,PSK,SNI
2018.05.08 15:15:03 LOG5[main]: Reading configuration from file stunnel.conf
2018.05.08 15:15:03 LOG5[main]: UTF-8 byte order mark detected
2018.05.08 15:15:03 LOG5[main]: FIPS mode disabled
2018.05.08 15:15:03 LOG6[main]: Initializing service [outlook-pop3]
2018.05.08 15:15:03 LOG4[main]: Service [outlook-pop3] needs authentication to prevent MITM attacks
2018.05.08 15:15:03 LOG6[main]: Initializing service [outlook-imap]
2018.05.08 15:15:03 LOG4[main]: Service [outlook-imap] needs authentication to prevent MITM attacks
2018.05.08 15:15:03 LOG6[main]: Initializing service [outlook-smtp]
2018.05.08 15:15:03 LOG4[main]: Service [outlook-smtp] needs authentication to prevent MITM attacks
2018.05.08 15:15:03 LOG5[main]: Configuration successful
2018.05.08 15:15:03 LOG5[main]: Logging to C:\Users\dps_engineer\AppData\Local\stunnel.log
2018.05.08 15:15:53 LOG5[0]: Service [outlook-pop3] accepted connection from 126.10.230.254:52629
2018.05.08 15:15:53 LOG6[0]: failover: round-robin, starting at entry #1
2018.05.08 15:15:53 LOG6[0]: s_connect: connecting 40.97.135.130:995
2018.05.08 15:15:53 LOG5[0]: s_connect: connected 40.97.135.130:995
2018.05.08 15:15:53 LOG5[0]: Service [outlook-pop3] connected remote server from 126.10.218.222:60145
2018.05.08 15:15:53 LOG6[0]: SNI: sending servername: pop-mail.outlook.com
2018.05.08 15:15:53 LOG6[0]: Peer certificate not required
2018.05.08 15:15:54 LOG6[0]: Certificate verification disabled
2018.05.08 15:15:54 LOG6[0]: Certificate verification disabled
2018.05.08 15:15:54 LOG6[0]: Client certificate not requested
2018.05.08 15:15:54 LOG6[0]: TLS connected: new session negotiated
2018.05.08 15:15:54 LOG6[0]: Negotiated TLSv1.2 ciphersuite ECDHE-RSA-AES256-GCM-SHA384 (256-bit encryption)
2018.05.08 15:15:55 LOG6[0]: Read socket closed (readsocket)
2018.05.08 15:15:55 LOG6[0]: SSL_shutdown successfully sent close_notify alert
2018.05.08 15:15:55 LOG6[0]: TLS socket closed (SSL_read)
2018.05.08 15:15:55 LOG5[0]: Connection closed: 58 byte(s) sent to TLS, 253 byte(s) sent to socket
2018.05.08 15:15:55 LOG5[1]: Service [outlook-smtp] accepted connection from 126.10.230.254:52639
2018.05.08 15:15:55 LOG6[1]: failover: round-robin, starting at entry #2
2018.05.08 15:15:55 LOG6[1]: s_connect: connecting 40.97.162.162:587
2018.05.08 15:15:55 LOG5[1]: s_connect: connected 40.97.162.162:587
2018.05.08 15:15:55 LOG5[1]: Service [outlook-smtp] connected remote server from 126.10.218.222:60147
2018.05.08 15:15:55 LOG6[1]: SNI: sending servername: smtp-mail.outlook.com
2018.05.08 15:15:55 LOG6[1]: Peer certificate not required
2018.05.08 15:15:55 LOG6[1]: Certificate verification disabled
2018.05.08 15:15:55 LOG6[1]: Certificate verification disabled
2018.05.08 15:15:55 LOG6[1]: Empty client CA list
2018.05.08 15:15:55 LOG6[1]: TLS connected: new session negotiated
2018.05.08 15:15:55 LOG6[1]: Negotiated TLSv1.2 ciphersuite ECDHE-RSA-AES256-GCM-SHA384 (256-bit encryption)
2018.05.08 15:16:00 LOG6[1]: TLS socket closed (SSL_read)
2018.05.08 15:16:00 LOG5[1]: Connection closed: 50 byte(s) sent to TLS, 194 byte(s) sent to socket
2018.05.08 15:16:00 LOG5[2]: Service [outlook-pop3] accepted connection from 126.10.230.254:52644
2018.05.08 15:16:00 LOG6[2]: failover: round-robin, starting at entry #2
2018.05.08 15:16:00 LOG6[2]: s_connect: connecting 40.97.161.50:995
2018.05.08 15:16:00 LOG5[2]: s_connect: connected 40.97.161.50:995
2018.05.08 15:16:00 LOG5[2]: Service [outlook-pop3] connected remote server from 126.10.218.222:60149
2018.05.08 15:16:00 LOG6[2]: SNI: sending servername: pop-mail.outlook.com
2018.05.08 15:16:00 LOG6[2]: Peer certificate not required
2018.05.08 15:16:00 LOG6[2]: Certificate verification disabled
2018.05.08 15:16:00 LOG6[2]: Certificate verification disabled
2018.05.08 15:16:00 LOG6[2]: Client certificate not requested
2018.05.08 15:16:00 LOG6[2]: TLS connected: new session negotiated
2018.05.08 15:16:00 LOG6[2]: Negotiated TLSv1.2 ciphersuite ECDHE-RSA-AES256-GCM-SHA384 (256-bit encryption)
2018.05.08 15:16:01 LOG6[2]: TLS socket closed (SSL_read)
2018.05.08 15:16:01 LOG5[2]: Connection closed: 58 byte(s) sent to TLS, 253 byte(s) sent to socket
2018.05.08 15:16:01 LOG5[3]: Service [outlook-smtp] accepted connection from 126.10.230.254:52647
2018.05.08 15:16:01 LOG6[3]: failover: round-robin, starting at entry #3
2018.05.08 15:16:01 LOG6[3]: s_connect: connecting 40.97.162.146:587
2018.05.08 15:16:01 LOG5[3]: s_connect: connected 40.97.162.146:587
2018.05.08 15:16:01 LOG5[3]: Service [outlook-smtp] connected remote server from 126.10.218.222:60150
2018.05.08 15:16:01 LOG6[3]: SNI: sending servername: smtp-mail.outlook.com
2018.05.08 15:16:01 LOG6[3]: Peer certificate not required
2018.05.08 15:16:01 LOG6[3]: Certificate verification disabled
2018.05.08 15:16:01 LOG6[3]: Certificate verification disabled
2018.05.08 15:16:01 LOG6[3]: Empty client CA list
2018.05.08 15:16:01 LOG6[3]: TLS connected: new session negotiated
2018.05.08 15:16:01 LOG6[3]: Negotiated TLSv1.2 ciphersuite ECDHE-RSA-AES256-GCM-SHA384 (256-bit encryption)
2018.05.08 15:16:03 LOG6[cron]: Executing cron jobs
2018.05.08 15:16:03 LOG6[cron]: Cron jobs completed in 0 seconds
2018.05.08 15:16:06 LOG6[3]: TLS socket closed (SSL_read)
2018.05.08 15:16:06 LOG5[3]: Connection closed: 50 byte(s) sent to TLS, 194 byte(s) sent to socket
2018.05.08 15:16:06 LOG5[4]: Service [outlook-pop3] accepted connection from 126.10.230.254:52653
2018.05.08 15:16:06 LOG6[4]: failover: round-robin, starting at entry #3
2018.05.08 15:16:06 LOG6[4]: s_connect: connecting 40.97.134.18:995
2018.05.08 15:16:06 LOG5[4]: s_connect: connected 40.97.134.18:995
2018.05.08 15:16:06 LOG5[4]: Service [outlook-pop3] connected remote server from 126.10.218.222:60153
2018.05.08 15:16:06 LOG6[4]: SNI: sending servername: pop-mail.outlook.com
2018.05.08 15:16:06 LOG6[4]: Peer certificate not required
2018.05.08 15:16:06 LOG6[4]: Certificate verification disabled
2018.05.08 15:16:06 LOG6[4]: Certificate verification disabled
2018.05.08 15:16:06 LOG6[4]: Client certificate not requested
2018.05.08 15:16:06 LOG6[4]: TLS connected: new session negotiated
2018.05.08 15:16:06 LOG6[4]: Negotiated TLSv1.2 ciphersuite ECDHE-RSA-AES256-GCM-SHA384 (256-bit encryption)
2018.05.08 15:16:07 LOG6[4]: Read socket closed (readsocket)
2018.05.08 15:16:07 LOG6[4]: SSL_shutdown successfully sent close_notify alert
2018.05.08 15:16:07 LOG6[4]: TLS socket closed (SSL_read)
2018.05.08 15:16:07 LOG5[4]: Connection closed: 58 byte(s) sent to TLS, 253 byte(s) sent to socket
2018.05.08 15:16:07 LOG5[5]: Service [outlook-smtp] accepted connection from 126.10.230.254:52656
2018.05.08 15:16:07 LOG6[5]: failover: round-robin, starting at entry #4
2018.05.08 15:16:07 LOG6[5]: s_connect: connecting 2603:1036:101::2:587
2018.05.08 15:16:07 LOG3[5]: s_connect: connect 2603:1036:101::2:587: Network is unreachable (WSAENETUNREACH) (10051)
2018.05.08 15:16:07 LOG6[5]: s_connect: connecting 2603:1036:102:108::2:587
2018.05.08 15:16:07 LOG3[5]: s_connect: connect 2603:1036:102:108::2:587: Network is unreachable (WSAENETUNREACH) (10051)
2018.05.08 15:16:07 LOG6[5]: s_connect: connecting 2603:1036:102:cc::2:587
2018.05.08 15:16:07 LOG3[5]: s_connect: connect 2603:1036:102:cc::2:587: Network is unreachable (WSAENETUNREACH) (10051)
2018.05.08 15:16:07 LOG6[5]: s_connect: connecting 2603:1036:102:8f::2:587
2018.05.08 15:16:07 LOG3[5]: s_connect: connect 2603:1036:102:8f::2:587: Network is unreachable (WSAENETUNREACH) (10051)
2018.05.08 15:16:07 LOG6[5]: s_connect: connecting 40.97.161.50:587
2018.05.08 15:16:08 LOG5[5]: s_connect: connected 40.97.161.50:587
2018.05.08 15:16:08 LOG5[5]: Service [outlook-smtp] connected remote server from 126.10.218.222:60158
2018.05.08 15:16:08 LOG6[5]: SNI: sending servername: smtp-mail.outlook.com
2018.05.08 15:16:08 LOG6[5]: Peer certificate not required
2018.05.08 15:16:08 LOG6[5]: Certificate verification disabled
2018.05.08 15:16:08 LOG6[5]: Certificate verification disabled
2018.05.08 15:16:08 LOG6[5]: Empty client CA list
2018.05.08 15:16:08 LOG6[5]: TLS connected: new session negotiated
2018.05.08 15:16:08 LOG6[5]: Negotiated TLSv1.2 ciphersuite ECDHE-RSA-AES256-GCM-SHA384 (256-bit encryption)
2018.05.08 15:16:13 LOG6[5]: TLS socket closed (SSL_read)
2018.05.08 15:16:13 LOG5[5]: Connection closed: 50 byte(s) sent to TLS, 194 byte(s) sent to socket
Sent from Outlook<http://aka.ms/weboutlook>
2
1
HI All,
We recently moved our email server from an in-house server to Office 365.
We are now in the process of replacing all our XP boxes with Windows 10.
One of the boxes are running the email service which collects emails from
Office 365, that we have just recently upgraded. This process works on the
XP but times out on windows 10.
Attached, is the time out the log file.
Below is the code I am using: Basic program code
* variables
ChannelNo = 0
Pop3Server =
'outlook.office365.com'
Pop3User = UserName
Pop3Pass = Password
Pop3Port = '995'
ProxYServer =
'127.0.0.1'
ProxyPort = '110'
ProxyDir =
'C:\see4OI\SSL\'
ProxyExe =
'stunnel.exe'
ProxyCert =
'stunnel.pem'
* retreives mail in MIME format
Gosub GET_EMAILS
return Mail_Rec
*
----------------------------------------------------------------------------
-------------
GET_EMAILS:
* close previous session If it wasnt closed properly
Code = seeClose(ChannelNo)
Code = seeRelease()
* attach key code
Code = seeAttach(1, KeyCode)
if Code < 0 then
RetFlag = 1
return
end
* start stunnel
Code = seeSetProxySSL(0, 1, ProxyDir, ProxyCert, ProxyExe)
If Code < 0 Then
RETURN
end
* connect to email server
Code = seePop3ConnectSSL(ChannelNo, ProxyPort, Pop3Port,
Pop3Server, Pop3User, Pop3Pass, ProxyServer)
If Code < 0 Then
RETURN
End
Your assistance in this regard will be highly appreciated.
Thank you.
Kind Regards,
Logicore
SEDICK CLOETE
IT Business Consultant
Cell: 083 228 7058
Fax: 086 515 9695
email: sedick(a)logicore.co.za
If you are not the intended recipient of this communication, please notify
the sender immediately. The information and/or attachment contained in this
email is confidential and may contain proprietary and/or personal
information. It is meant solely for the intended recipient. Access to this
email by anyone else is unauthorised. If you are not the intended recipient,
any processing of the email or the information contained therein (including
disclosure, copying, distribution, storage) or any action taken or omitted
in reliance on this, is prohibited and may be unlawful.
2
1
I've successfully set up stunnel for Windows and Linux clients. Now to set up
for Mac. I've gone to the website http://macappstore.org/stunnel/ and followed
the instructions there which are:
1. Press Command+Space and type Terminal and press enter/return key.
2. Run in Terminal app:
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" < /dev/null 2> /dev/null
and press enter/return key.
3. Run:
brew install stunnel
And then it says, "Done! You can now use stunnel."
Well, not exactly. Where do I put my stunnel.conf and certificate.pem? How do I
make stunnel run automatically at boot time?
The web instructions aren't very complete. Need additional assistance.
THX --Mark
1
1