Wierd stunnel behaviour

I've been trying to wrap pop3 via stunnel thru xinetd, following the many virtually identical howtos out there for this. It's not workin', though, because, well, as far as I can tell, stunnel is being stupid.

The /etc/xinetd.d/pop3s file is:

------
service pop3s
{
disable = no
socket_type = stream
wait = no
user = root
server = /usr/sbin/stunnel
server_args = -T -p /etc/stunnel/stunnel.pem -l /usr/sbin/vm-pop3d -- vmpop3d -i -u 99
}
--------

This is on a CentOS/DirectAdmin box.

Anyway, when I try to connect remotely, after opening port 995 in the firewall, it fails unexpectedly. Connecting locally produces a more useful error:

2005.02.11 16:24:46 LOG3[18697:3076436096]: -T: No such file or directory (2)

Removing the -T from server_args produces a similar error message, only for "-p". In other words, as far as I can tell, the stupid thing is, for some reason, not parsing the arguments correctly. I've done a strace, and it really is trying to open "-T", and failing (-3).

Any suggestions? OpenSSL and Stunnel are up-to-date, SSL pages via Apache work just fine... it's just that, well, stunnel seems to be misbehavin'. I've done the same thing on other servers, and it's worked just fine, but for some reason this one isn't.

 

 

 

 

Top