I hope I understand you right ... You will need two daemons. One for waiting on port 110 for normal SSL conection and one waiting on port 995 for (old style) alternate-port connections. Independent from this it should be possible to set the clear-text-password option for both daemons. I don't know whether you have to use "ssl" or "tsl" (for the clear-text-password option). I suppose that you shouldn't use "tsl" for the alternate port, cause the corresponding clients can't control this.
- oliver Nachricht vom Dienstag 23 Oktober 2001 17:15: > > I would use the clear-text-password option with "ssl" or "tsl". > > (described on page 31 of the QPopper User-Guide) > > Hmm... I like that idea better. However, since I have tls-support set to > alternate-port, that means I'll still have a port open on 110 that can't > do anything. > > If I set the main port to 995, change tls-support to stls, and set the > clear-text-password to ssl, would that work? Or would the negotiation > process for SSL that normally takes place on port 110 break other > SSL-aware pop clients when they hit port 995 looking for a non-negotiable > pop3s connection? I guess I could just try it, but I won't be in front of > the box until tonight. > > What's really needed here is a "alternate-port-only" value for the > tls-support option. -- Oliver Egginger FH Giessen-Friedberg DV-Zentrum Wiesenstrasse 14 35390 Giessen Tel. +49 641 309-1283 Fax +49 641 309-2908 Mail: [EMAIL PROTECTED] **************************************************** Sprechzeiten des DV-Zentrums fuer E-Mail-Angelegenheiten: Mo 11:30 - 15:30 Uhr Di 13:15 - 15:30 Uhr Do 9:30 - 16:00 Uhr Fr 9:45 - 11:45 Uhr ****************************************************
