At 12:48 PM -0500 9/26/05, Jerry K wrote:
This is my configure string that I use for my solaris 9 systems. I
came up with this based on other hints that I have read on this
list, plus reading the docs. The enable-temp-drop-dir works well
for me as I use user quotas.
I am using the same version of gcc that you are.
Hope this helps,
Jerry Kemp
./configure --disable-apop \
--enable-specialauth \
--enable-uw-kludge \
--disable-check-pwmax \
--enable-log-login \
--without-pam \
--enable-temp-drop-dir=/var/tmp
It may be the "--without-pam" that is the key. The ./configure
script tries to figure out by itself if if '--enable-specialauth' is
needed, so normally you don't need to set it. If you run into a case
where ./configure does the wrong thing, let's try and fix it.
Doug Wellington wrote:
I'm not able to login to Qpopper 4.0.8 running on a Solaris 9 server. I
keep getting the error:
-ERR [AUTH] Password supplied for "ddw" is incorrect
I can telnet and ftp to the server, but qpopper won't let me in. I looked
in the FAQ and did a google search, but the only thing I've found so far is
to use --enable-specialauth. I have done a make realclean and configured
both with and without --enable-specialauth and the binary ends up being
exactly the same. Is there an issue with which version of gcc I compile
with? (I'm using 3.4.2...)
I'd suggest enabling debug logging and see what gets logged. That
should give a hint as to what is wrong.
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.
Also, 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'.
