But you can't have ipop3d handling pop3s on *two different ports* at the same time; either 995 is SSL, -or- another port is SSL. I'm in the middle of changing my pop3 config to use stunnel, that was the only way I can see to get this working short term.
ipop3d ought to have a "force SSL" switch to support the xinetd crowd. :( ----- Original Message ----- From: "Brad Arlt" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, July 09, 2004 12:02 PM Subject: Re: Force ipop3d to use TLS/SSL when running on odd port > On Fri, Jul 09, 2004 at 10:26:26AM -0400, Erik Kangas wrote: > > I think, that short of modifying the source for ipop3d, you could > > accomplish this task my using "stunnel" on the server to listen to > > the desired port for SSL connections and "forward" these to the > > pop3s port locally. This will ensure that you can have an SSL-only > > POP connection on an alternate port and will solve the ipop3d port > > issue. See "stunnel.org". > > This seems rather extreme given the source code changes are changing > "995" to another number (src/c-client/pop3.c line 35 of imap-2004 > release). And it appears that you might be able to get away with > simply changing the pop3s line in /etc/services. > > Neither is it overly complicated. Certainly less hassle than stunnel > was (I have used it for imap over SSL before uw-imap supported SSL - > builtin support is *so* much better).
