At 7:43 PM -0700 6/24/02, T. Shaw wrote: > Hello all, > I built Sendmail 8.12.4 on Solaris 2.7 and qpopper 4.0.4 to provide SSL pop > access to virtual domains. Now I didn't build Sendmail for SSL > because I wanted > users accessing mail via pop3 to only have that "feature". But I'm > finding when > I turn on "tsl" or "ssl" under the parameter "set > clear-text-password" and "set > tls-support" set to STLS, it's either 1) not starting at all.. ( > have debugging > enabled and tracefile set in config file) , no clue as to why its > not starting, > or 2)some internal error ( cryptic). > > I'm wondering if SASL should be compiled into Sendmail as well? I thought it > would work without it.. > > Any suggestions?
It seems to me that you're discussing two separate issues: sendmail and qpopper. I think you're saying that when you set clear-text-password in qpopper to 'tls' and also set tls-support to 'stls', that qpopper fails to start. If so, there should be an error message written to the log, and also send to the remote end. If the error message isn't clear, try enabling debug tracing, which should provide much more detail. 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'. --
