3 messages in net.sourceforge.lists.courier-users[courier-users] courier 0.47 - sqwebm...
FromSent OnAttachments
Dirk KulmseeFeb 24, 2005 2:31 am 
Stefan HornburgFeb 24, 2005 2:46 am 
Dirk KulmseeFeb 24, 2005 3:04 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:[courier-users] courier 0.47 - sqwebmail - Transport endpoint is not connectedActions...
From:Dirk Kulmsee (kulm@netgroup.de)
Date:Feb 24, 2005 2:31:23 am
List:net.sourceforge.lists.courier-users

Hi list,

I know this problem has come up earlier in this list. The answers proposed sqwebmaild had not been started. I guess this is not the problem in my case.

I run Debian/Testing and courier 0.47 with authpgsql and QUICA as an extension. 'ps ax' shows sqwebmaild and authdaemond.pgsql are running. POP3 access works fine. when i try to access http://<hostname>/cgibin/sqwebmaild i get an internal error:

"The webmail system is temporarily unavailable. An error occured in function write: Transport endpoint is not connected"

I have another system at hand with the same versions of Debian and courier. In that case sqwebmail works fine. (I compared the files sqwebmail and sqwebmaild with cmp and they are identical.) The difference between these two systems would be QUICA which introduces its own mailuser and directory tree. Could there be a problem with accessibility of these dirs through sqwebmail, probably because it is no longer suid root?

On the other hand I have a third system running Debian, Courier 0.45 with authpgsql and QUICA and everything works great.

Can anyone give a clue how i should continue to figure this out? TIA