error invalid stunnel.conf - No limit of clients
Hi, I just installed stunnel for my email programm courier. I edited the stunnel.conf as followed but am unfortunatly becoming the message from stunnel: invalid stunnel.conf No limit detected for the number of clients stunnel 4.56 on x86-pc-msvc-1500 platform Compiled/running with OpenSSL 1.0.1e-fips 11 Feb 2013 Threading:WIN32 Sockets:SELECT,IPv6 SSL:ENGINE,OCSP,FIPS Reading configuration from file stunnel.conf FIPS_mode_set: 2D07808C: error:2D07808C:FIPS routines:FIPS_module_mode_set:unsupported platform Line 11: "[POP3 T-Online]": Failed to initialize SSL Server is down my stunnel.conf is as followed: # GLOBAL OPTIONS client = yes output = stunnel-log.txt debug=4 taskbar = yes # SERVICE-LEVEL OPTIONS [POP3 T-Online] accept = 127.0.0.1:108 connect = securepop.t-online.de:995 [SMTP T-Online] accept = 127.0.0.1:107 connect = securesmtp.t-online.de:587 [POP3 web.de] accept = 127.0.0.1:106 connect = pop3.web.de:995 [SMTP web.de] accept = 127.0.0.1:105 connect = smtp.web.de:587 [POP3 STRATO] accept = 127.0.0.1:104 connect = pop3.strato.de:995 [SMTP STRATO] accept = 127.0.0.1:103 connect = smtp.strato.de:465 [POP3 GMX ] accept = 127.0.0.1:102 connect = pop.gmx.net:995 [SMTP GMX ] accept = 127.0.0.1:101 connect = mail.gmx.net:465 ___________________ Would be nice if someone could tell me what is wrong! Greetings Christian Huber
Hi, The problem is that "client = yes" is not a global option anymore. The default is "client = no" for any service unless yes is specified. So tries to load the services in server mode and fails because there are faulty parameters to set a server. You could see better the error with "debug = 7" Regards.
On 12/08/2013 04:16 AM, Javier wrote:
The problem is that "client = yes" is not a global option anymore.
The default is "client = no" for any service unless yes is specified.
Not really. If you specify a service-level option in global section, it becomes the default for all the sections. Mike
On Mon, 09 Dec 2013 09:35:49 +0100 Michal Trojnara <Michal.Trojnara@mirt.net> wrote:
On 12/08/2013 04:16 AM, Javier wrote:
The problem is that "client = yes" is not a global option anymore.
The default is "client = no" for any service unless yes is specified.
Not really. If you specify a service-level option in global section, it becomes the default for all the sections.
Mike
Oh, ok. Huge fail for me then :-S I thought that feature was removed a few versions back :-? I'm sorry for the confusion. Regards.
participants (3)
-
Christian Huber -
Javier -
Michal Trojnara