At 10:48 PM -0600 2/2/03, Steven J. Hill wrote:

 Yes, that is what I already did. And this still shows up in the
 system logs:

    Feb  2 22:52:42 real /usr/sbin/in.qpopper[5657]: (null) at
    207-191-210-241.cpe.ats.mcleodusa.net (207.191.210.241): -ERR Unknown
    command: "\200f^A^C". [pop_get_command.c:152]
Try enabling debug tracing. Let's see if Qpopper is processing the configuration file, and if not, why, and if so, why TLS/SSL doesn't seem to be working as you want.

You did set TLS to alternate-port, I assume?


To enable tracing in Qpopper:

1. Do a 'make clean'
2. Re-run ./configure, adding '--enable-debugging'.
3. Edit the inetd.conf line for Qpopper, adding '-d' or '-t <tracefile-path>'.
4. Send inetd (or xinetd) a HUP signal.

(Steps 3 and 4 are only needed if you use inetd (or xinetd). In standalone mode, you can add '-d' or '-t <tracefile-path>' to the command line directly.)

(In either standalone or inetd mode, if you use a configuration file you can add 'set debug' or 'set tracefile = <tracefile>' to either a global or user-specific configuration file instead of steps 3 and 4.)

This causes detailed tracing to be written to the syslog or to the file specified as 'tracefile'.

Reply via email to