This is so similar in detail to my problem i just had to respond. I just was waiting until I had all my facts straight before I reported it. In my situation I only am allowing encrypted protocols, so pop3s and imaps. My setup is just about the same as yours altho sqwebmail instead of Horde IMP (RH7.2+qmail+courier+sqwebmail+daemon/ucspi blah blah..)
pop3s is working w/ close to no noticeable errors; however IMAPs especially via sqwebmail over SSL is having troubles authing; In my case, restarting authdaemond fixed things != restarting courier itself, and I am currently restarting autdaemonond every three hours via cron and nobody notices anything. So, I'll try to answer your question while asking another of Mr Sam... "download the latest courier-imapd CVS snapshot, especially if you're having problems w/ SSL" Sam, is it sane for me to have sqwebmail authing against the same authdaemon socket that serves my imapds/pop3s services? Is that 'correct'? Also, how can I go about getting better debug information out of authdaemon before I ask question on this list. thanks, brian On Tue, Mar 26, 2002 at 03:27:00PM -0500, webmaster wrote: > OS - RedHat 7.2 > Mail - Qmail + vpopmail + autoresponder + ezmlm + qmailadmin + > daemontools + ucspi-tcp + courier-imap > Webserver - Apache 1.3.24 + php4.1.2 compiled with imap + xml + gettext > I am using Horde 2.0 and IMP 3.0 for webmail, everything works great > except for one thing. I am always having to restart courier so I can log > in. Once I restart courier I can log in fine but after I log out and try > to log back in I have to restart courier for me to be able to log back _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
