Ed Greenberg writes:



--On Sunday, February 26, 2006 10:19 AM -0500 Sam Varshavchik <[EMAIL PROTECTED]> wrote:

Ed Greenberg writes:

Hi,

I have a new installation of courier-mta and I can no longer get any
client  software to connect to imap. It worked in previous testing, but
I seem to  have broken something.

The typical log entry for a failed connection is:
Feb 25 18:46:32 vps2 imapd: LOGIN FAILED, user=sarahf,
ip=[70.199.216.131] This is with TLS turned off.

Invalid password.

Thank you Sam, for a quick response.

I've packet captured this, and I see the correct password. :

* OK [CAPABILITY IMAP4rev1 NAMESPACE CHILDREN IDLE QUOTA SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES UIDPLUS ACL ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2005 Double Precision, Inc. See COPYING for distribution information.

A00001 CAPABILITY

* CAPABILITY IMAP4rev1 NAMESPACE CHILDREN IDLE QUOTA SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES UIDPLUS ACL ACL2=UNION STARTTLS

A00001 OK CAPABILITY completed

A00002 LOGIN jeffglass jeff123

A00002 NO Login failed.

I can log into jeffglass with password jeff123 using shell on the machine.

Does antyhing else stand out as a problem?

Nope. You should look at courier-authlib's configuration. It can be configured to check passwords from either the system's password file, an LDAP server, a MySQL database, a PostgreSQL database, and a couple of other sources. I don't remember you mentioning which authentication method you are using.

Attachment: pgpL8jl5la5U9.pgp
Description: PGP signature

Reply via email to