At 5:21 PM -0600 9/30/02, Dean Brissinger wrote: > I figured it out. I also seem to have stumbled across a bug in the > process. When calling popper from inetd the first option I give it is > always ignored. When I supply an option before the -f option, it reads > my config file and works great (ignoring whatever I put before -f). So > I added '-c -f popper.conf' to fix my problem.
That's not a bug; when programs are run from a shell the path to the executable is passed as the first argument; when called from inetd you have to add this yourself. > Secondly, the error I was getting was that my POP client (Eudora, > Evolution, Netscape, Mozilla, Apple's Mail, Outlook) expected port 995 > to be speaking encryptedly. Popper was waiting for the STLS command. Qpopper can do either STLS or alternate port, you just tell it which you want. You can do both by having one instance on each port. Many of those clients can also do either STLS or alternate-port, you just have to say which it should do.
