Any user with a Litech account can receive mail at the address "<user>@litech.org" and can send mail messages using marduk as an SMTP relay server. Mail can be read either locally with Pine on marduk, or using a standard IMAP4rev1 client such as Netscape Communicator or Microsoft Outlook Express. Soon a web-based method of reading and sending mail will be available as well. We allow server-side mail filtering too.
This document describes how to configure and use several IMAP clients for use with Litech mail servers. If you need further information or your client is behaving oddly, you'll probably want to visit the Courier IMAP site and particularly the IMAP compatibility and configuration guide.
If you're not interested in how mail is stored and the security requirements of the server, you can skip this section.
All mail files are stored in Maildir format, which stores one message per file. Each user keeps their mail in the Maildir folder in their home directory, and Exim delivers new mail directly into the Maildir/new folder. The IMAP daemon will look for new messages in this folder and will move them into the Maildir/cur directory before notifying the user that new mail has arrived. The program /usr/local/bin/cknewmail tests whether you have new mail waiting. It gets run on login, which is what prints the "You have new mail" message after the MOTD.
Access to use the SMTP server for sending mail must be authenticated using SMTP "PLAIN" authentication. This is supported by most mail clients. Use your Litech account username and password to authenticate.
Since both the IMAP and SMTP protocols send the authentication information in cleartext, you must encrypt your connection using SSL. This is also supported by most mail clients. Unfortunately, there are two different ways that clients have implemented SSL. The old way, still in use by Microsoft Outlook and some others, is to have an SSL-capable server running on a special port that initiates the SSL protocol immediately on connect. The new way, not yet officially recognized but in use by Netscape Communicator, is to integrate the SSL and non-SSL services on the same port and then only to start SSL when the client issues the STARTTLS command. We support both methods for both IMAP and SMTP.
Service | SSL method | Port number |
---|---|---|
IMAP | on-connect | 993 |
IMAP | STARTTLS | 143 |
SMTP | on-connect | 465 |
SMTP | STARTTLS | 25 |
In order to enforce the use of SSL for authenticated connections, you will not be able to log in with either SMTP or IMAP unless you are using SSL. Without SSL, the IMAP server will advertise the "LOGINDISABLED" capability and the SMTP server will not advertise the "AUTH" capability.
Our SSL certificate (for mail.litech.org) is self-signed and will cause most clients to complain. Check the Litech SSL information page for details.
Pine on marduk has been configured system-wide to access mail by executing the IMAP daemon locally and using IMAP to manipulate your mailbox. Fortunately, an SSH connection is used with host-based authentication, so you don't need to enter your password again when you run Pine.
If you want to use Pine on a different server to access your Litech mailbox, you're on your own. Take a look at the system-wide configuration on marduk (/etc/pine.conf) and copy the relevant parts to your ~/.pinerc file. Looking at the Courier IMAP site (linked at the top of the page) will probably also help.
Netscape Communicator has supported IMAP4rev1 in its Messenger mail client since Communicator v4.0. However, we recommend that you use Communicator v4.5 or later because of bugs in the IMAP implementation in earlier versions.
You will probably want to read the Litech SSL information page before proceeding.
Netscape Messenger has worked really well so far with the IMAP server. However, it lists all of your folders as sub-folders of your INBOX. I'm not sure why (since it supports the IMAP NAMESPACE extension), but it's not that hard to deal with.
You will probably want to read the Litech SSL information page before proceeding.