On Sat, Apr 05, 2003 at 10:54:52AM -0500, Gary MacKay wrote: > Thanks Mike! Yup, tried all that. I even changed the DEBUG setting in the > imapd and pop3d config files to 5 but nothing new is added to the log > files. I restarted it also. No difference. Very hard to debug something > with no help from the logs.
For the record, my approach to debugging authentication issues is as follows: change /etc/courier/authdaemonrc so daemons=1 restart courier so that the authdaemon is restarted, and there is only one child. Then run strace, ptrace, or ktrace (whichever your platform supports) on the child process. Use the option that will show longer strings. For strace the option I use is "-s 1024". Its likely that you should be using -o /tmp/authdaemon.trace. On the other end, run ethereal, or tcpdump, or something that gives you a packet trace that you can extract with a protocol analysis tool like ethereal. Now, after you've made your failure happen, you can figure out: 1) What data was entered by the user 2) What data was passed by the client to the server 3) What data the server got. 4) What data the authdaemon got. -Peter -- The 5 year plan: In five years we'll make up another plan. Or just re-use this one. ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
