smtps problem on Fedora Core 4

Hi, I am trying to get the smtps solution described on http://www.linuxquestions.org/questions/answers.php?action=viewarticle&artid... working on my server. Basically I want my users on Windows XP boxes to get their mail from 127.0.0.1:100 and send their mail to 127.0.0.1:25 I have gotten as far as having the users able to get mails. That is I have stunnel on a windows box, with a configuration file like this: client = yes debug = debug cert = pemfile.pem [pop3s] accept = localhost:110 connect = my.domain.com:995 [smtps] accept = localhost:25 connect = my.domain.com:465 And a telnet to port 110 on the lookback interface gives me access to the pop server. Så I am guessing that the certificates etc. are working correctly. As for the smtps I am using xinetd, and have tried with various configurations. Here is one of the one's that didn't work: service smtps { disable = no socket_type = stream wait = no user = root server = /usr/sbin/stunnel server_args = -v3 -rlocalhost:25 log_on_success += HOST DURATION log_on_failure += HOST ATTEMPT } Any ideas as to how to setup my xinetd file (or is there a better solution?) # stunnel -version stunnel 4.08 on i386-redhat-linux-gnu PTHREAD+POLL+IPv4+LIBWRAP with OpenSSL 0.9.7f 22 Mar 2005 Global options cert = /etc/stunnel/stunnel.pem ciphers = ALL:!ADH:+RC4:@STRENGTH debug = 5 key = /etc/stunnel/stunnel.pem pid = /var/run/stunnel.pid RNDbytes = 64 RNDfile = /dev/urandom RNDoverwrite = yes session = 300 seconds verify = none Service-level options TIMEOUTbusy = 300 seconds TIMEOUTclose = 60 seconds TIMEOUTconnect = 10 seconds TIMEOUTidle = 43200 seconds Kind regards, Anders

"Anders Gjerløv" <anders@gjerlov.dk> wrote:
Here is one of the one's that didn't work: service smtps { disable = no socket_type = stream wait = no user = root server = /usr/sbin/stunnel server_args = -v3 -rlocalhost:25 log_on_success += HOST DURATION log_on_failure += HOST ATTEMPT }
You're using stunnel 4.x. You need server_args = /etc/stunnel.conf and a valid stunnel.conf file. See the manual for syntax. BTW: It's usually a bad idea to start stunnel with xinetd. Setup stunnel as a daemon (just like you did on your Windows box). Best regards, Mike
participants (2)
-
Anders Gjerløv
-
Michal Trojnara