Another "thank you" to Flurdy for the great guide. Your time and effort is greatly appreciated.
I've followed the guide and learned a LOT about postfix and courier (coming from a sendmail/cyrus background, and wanting to learn something different). Mail seems to be arriving where it ought to, which is a good thing.
One problem I have however is I can't log into the Courier-IMAP server from mutt. I don't know if this is a mutt problem, an SASL problem, or something else.
I open mutt, tell it to connect (press "c") and feed it imap://user:pass@servername . It finds the TLS certificitate fine, tells me it's authenticating via CRAM-MD5, and then gives me a "SASL Authentication Failed" error.
My logfiles look like this:
Code:
Jul 25 10:19:46 localhost imaplogin: Connection, ip=[::ffff:127.0.0.1]
Jul 25 10:19:46 localhost imaplogin: LOGIN: DEBUG: ip=[::ffff:127.0.0.1], command=CAPABILITY
Jul 25 10:19:46 localhost imaplogin: LOGIN: DEBUG: ip=[::ffff:127.0.0.1], command=STARTTLS
Jul 25 10:19:47 localhost imaplogin: LOGIN: DEBUG: ip=[::ffff:127.0.0.1], command=CAPABILITY
Jul 25 10:19:48 localhost imaplogin: LOGIN: DEBUG: ip=[::ffff:127.0.0.1], command=AUTHENTICATE
Jul 25 10:19:51 localhost imaplogin: authdaemon: starting client module
Jul 25 10:19:51 localhost imaplogin: authdaemon: REJECT
Jul 25 10:19:56 localhost imaplogin: LOGIN FAILED, ip=[::ffff:127.0.0.1]
Jul 25 10:19:58 localhost imaplogin: LOGIN: DEBUG: ip=[::ffff:127.0.0.1], command=LOGOUT
Now if I telnet it instead, I get the following:
Code:
# telnet localhost 143
Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc. See COPYING for distribution information.
imap login user@servername pass
imap OK LOGIN Ok.
imap logout
* BYE Courier-IMAP server shutting down
imap OK LOGOUT completed
Connection closed by foreign host.
And the logs:
Code:
Jul 25 12:53:29 localhost imaplogin: Connection, ip=[::ffff:127.0.0.1]
Jul 25 12:53:47 localhost imaplogin: LOGIN: DEBUG: ip=[::ffff:127.0.0.1], command=LOGIN
Jul 25 12:53:47 localhost imaplogin: LOGIN: DEBUG: ip=[::ffff:127.0.0.1], username=user@servername
Jul 25 12:53:47 localhost imaplogin: LOGIN: DEBUG: ip=[::ffff:127.0.0.1], password=pass
Jul 25 12:53:47 localhost imaplogin: authdaemon: starting client module
Jul 25 12:53:47 localhost imaplogin: authdaemon: ACCEPT, username user@servername
Jul 25 12:53:47 localhost imaplogin: LOGIN, user=user@servername, ip=[::ffff:127.0.0.1], protocol=IMAP
Jul 25 12:56:34 localhost imaplogin: LOGOUT, user=user@servername, ip=[::ffff:127.0.0.1], headers=0, body=0, time=167
Is someone able to shed some light on this? The box is in another location, so I'm unable to test it locally with a GUI client like mozilla-thunderbird, etc. I will try to get near it eventually and test with other clients. Is mutt the problem? Or did I break something?
[edit]
World's quickest edit! The username is "user@servername". When using mutt and telling it to connect to imap://user:pass@servername, the username is only "user".
Instead, I now tell mutt to connect to "imap://servername". It prompts me for a username, which I enter as "user@servername" (ie: the complete entry from "id" column from the "users" table) and the correct password, and I am in.
Sometimes you just need to talk out your problem, and the solution becomes clear.
And once again, thanks heaps to Flurdy for the clear and concise guide. Great software is nothing without people who take the time to explain/howto it.
Bookmarks