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.
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. Thanks for the response though! On Mon, 2002-09-30 at 15:01, Andi Reisenhofer wrote: > Hallo Dean, > > > Hello, > > > > I just built qpopper on Solaris 9. I installed the OpenSSL and GCC > > packages from sunfreeware.com. Then used: > > > > > > ./configure --with-openssl=/usr/local/ssl --with-specialauth > > --enable-debugging > > Try first without ssl support. > > > I then followed the instructions in the GUIDE.pdf file for setting up > > SSL/TLS and created a test certificate according to the method on the > > web site FAQ. In inetd.conf I launch qpopper with (wraps in e-mail): > > > > pop3s stream tcp nowait root /usr/local/sbin/popper -d -f \ > > /etc/mail/pop/popper.conf > > How does your popper.conf look like? > You could try -t parameter to write the debugging information to an extra > file. > > > The conf file is the same as the GUIDE.pdf recommends. When my client > > connects, I get this message in the logs: > > > > > > mail -d[12295]: [ID 702911 local0.notice] (null) at binks: -ERR Unknown > > command: "\200f^A^C^A". [pop_get_command.c:152] > > I looks like your client is sending a command which is not a valid pop > command. > Which client are you using for testing and how is your client configured? > > hth, > reg, > Andreas > > >
