4 messages in net.sourceforge.lists.courier-usersRE: [courier-users] Bug in webmail/au...
FromSent OnAttachments
Eugenio RuivoJul 22, 2004 11:11 am 
Jay LeeJul 22, 2004 1:08 pm 
Eugenio RuivoJul 23, 2004 1:52 am 
Eugenio RuivoJul 23, 2004 2:09 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:RE: [courier-users] Bug in webmail/authldap..?Actions...
From:Eugenio Ruivo (euge@spel-parques.pt)
Date:Jul 23, 2004 2:09:11 am
List:net.sourceforge.lists.courier-users

Ok, "mea culpa". Point taken on the use of the term "Bug". I really didn't mean it in a way meant to alienate anyone. The objective was just to call attention to a problem that I've never seen happen with courier.

Apache's error log is only showing the following message:

Premature end of script headers: webmail, referer: http://localhost/cgi-bin/webmail

I've just tried it with Kmail and I also get an error. After checking the mail info log what seems to be happening is that somehow the check if the home directory attribute is an absolute path or a relative one isn't working.

... Imapd: chdir "/home/mail//home/mail/emruivo": No such file or directory

-----Original Message----- From: cour@lists.sourceforge.net [mailto:cour@lists.sourceforge.net] On Behalf Of Jay Lee Sent: Thursday, July 22, 2004 8:59 PM To: cour@lists.sourceforge.net Subject: Re: [courier-users] Bug in webmail/authldap..?

Eugenio Ruivo said:

Hi Sam,

I've started setting up ver. 0.45.6 and it seems like there is a problem on how sqwebmail and authldaprc interact.

http://www.catb.org/~esr/faqs/smart-questions.html#id2878006

The problem appears if in authldaprc I set LDAP_MAILROOT. In this case when logging in with sqwebmail I get an internal error from apache. Later on I'll try logging in with Outlook, KMail, Evolution, etc to see if there is also some strange behaviour.

I and many other Courier user's are happily using 0.45.6 + LDAP + LDAP_MAILROOT. Chances are quite good this is a configuration error, not a bug. Look at your /var/log/http/error_log file and find out what error Apache is reporting, that may be a good start to solving the problem.