On Thu, Jan 10, 2002 at 02:53:49PM -0500, Daniel Senie wrote: > At 02:29 PM 1/10/02, you wrote: > >Mmmm, the private KEY is in the CERTIFICATE. And i didnŽt have any problems > >with that. > > No, it doesn't work that way. You must have the following TWO lines in your > config: > > set tls-server-cert-file=<cert file> > set tls-private-key-file=<private key file> > > >Can anybody tell me how to tell QPOPPER to bind to port 995. IŽm running it > >in STAND ALONE mode. So NO INETD or XINETD available. But if INETD is the > >ONLY solution well, iŽll recompile and use it that WAY. > > Someone else should be able to answer this. I personally run qpopper from > xinetd for a variety of reasons.
I'll recommend the same - in fact we installed xinetd to our main machine specifically for qpopper, because it gives the ability to rate-limit based on load. Qpopper does have the ability to hammer the hell out of your disk system if you get many sudden POP connections for users with large mailspools. If you start refusing all POP connections when your CPU load hits 100 (or some number appropriate for the stability of your OS) your machine will stay up; if you don't have *some* limit, it's possible for it to be pushed until it becomes completely unresponsive, or possibly until it crashes if you're running something less bulletproof than a stable release of a BSD-type UNIX. -- Clifton Royston -- LavaNet Systems Architect -- [EMAIL PROTECTED] WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
