15 messages in net.sourceforge.lists.courier-sqwebmailRe: [sqwebmail] Invalid userid or pas...
FromSent OnAttachments
CassandraDec 20, 2006 2:38 pm 
Sam VarshavchikDec 20, 2006 3:13 pm 
Brian CandlerDec 22, 2006 1:25 am 
CassandraDec 22, 2006 12:49 pm 
CassandraDec 22, 2006 1:32 pm 
Sam VarshavchikDec 22, 2006 3:14 pm 
CassandraDec 22, 2006 4:34 pm 
Sam VarshavchikDec 22, 2006 6:53 pm 
CassandraDec 25, 2006 11:37 pm 
Sam VarshavchikDec 26, 2006 3:15 am 
Brian CandlerDec 29, 2006 12:39 pm 
timDec 29, 2006 12:54 pm 
CassandraDec 29, 2006 2:37 pm 
Brian CandlerDec 30, 2006 1:37 pm 
Lars Olav TveitoDec 30, 2006 5:29 pm 
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: [sqwebmail] Invalid userid or passwordActions...
From:Cassandra (deb@homenetnw.net)
Date:Dec 22, 2006 4:34:50 pm
List:net.sourceforge.lists.courier-sqwebmail

Re: Invalid userid or password (New) From: Sam Varshavchik <mrsam@co...> - 2006-12-22 15:14 Cassandra writes:

Follow the instructions at http://www.courier-mta.org/authlib/README.authdebug.html to debug this problem.

Done. Courier-authlib seems to be working fine. I can log in using an email client, and everything works fine.

Define "email client". The fact that you can supposedly log in with some mysterious email client, which uses some unknown protocol to access the same mailboxes on your server, doesn't really mean much.

My apologies. By "email client," I meant an email program, such as Outlook or
Outlook Express.

You can take sqwebmail out of the equation entirely by using authtest <username> <password> at the command line.

I tried this and got "ERR: authdaemon: s_connect() failed: Connection refused Authentication FAILED: Illegal seek."

That proves that courier-authlib is not "working fine". You probably just forgot to start courier-authlib: "authdaemond start".>

OK. I checked and thought courier-authlib was running, but perhaps it is not.
My apologies again. My users are able to authenticate to receive their email (I
can see the login and logouts in the mail.log file), and perhaps naively thought
if they could authenticate, the would be doing it via the authlib authentication
files. Maybe I just need some sleep.

However, I can authenticate with an email client

See above.

and also by telnetting to the various ports.

sqwebmail does not telnet to random ports in order to log in.

Again, my apologies for my naivete and lack of clarity. I realize sqwebmail
does not telnet to random ports in order to log in. The ports to which I was
referring were those suggested in the debug instructions the other poster
referred me to.

Yes, these are correct and working fine, I assume--since everyone can log in using their email clients.

Nope. There is no email client anywhere that uses courier-authlib directly, so this means absolutely nothing.

Thank you. I hadn't realized that. Since the email clients my customers use
(Mail, Outlook, Outlook Express, Incredimail) can access their email and these
clients do not use courier-authlib directly, then perhaps this is the problem.