(>> = Cassandra)
(> = Brian)
Although apt-get kept reporting sqwebmail was not available, I was
finally able to locate it on the Debian FTP server.
Ah, well that might explain the problems. If sqwebmail doesn't
come from exactly the same package repository that you used for
everything else, then it's quite likely that it won't talk to
your authentication daemon; it may expect the socket to be in
a different directory, for instance.
Indeed very correct. I have SqWebMail running on Debian. And I too initially
had problems getting the login to work on SqWebMail. What solved it for me
was to download the newest source for both SqWebMail and courier-authlib,
and compile and install it. Almost everyting on that server is installed
with apt-get, (or actually aptitude) but to make SqWebMail work I gave up
using the .deb packages and did it the old fashion way. The trouble doing it
this way is of cource that now I will need to keep an eye out for updates to
these packages, and install them manually myself, while everything else on
the server can be upgraded by a simple "apt-get upgrade"-command.
I have to say I'm
learning to despise Debian.
Thats your right, feel free to despise. It's a bit sad though, that you
should start your meeting with Debian with this problem. (Debian and
SqWebMail might not be the biggest of lovers). I have happily been running
Debian on several production servers for many years. Very stable. Very
secure. I love it!
15 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] Invalid userid or pas...
