Managing IMAP

What Do You Get with UW IMAP?

After building the UW IMAP server, you will find the following programs in the source tree:

mtest

The C-Client test bed program. This is a fairly simple command-line testing program for IMAP servers. We’ll get into the specifics of using this utility in the UW system administration chapter. mtest is largely useful to developers using the C-Client library who want to test new mailbox drivers, system administrators troubleshooting an IMAP client/server issue who want an IMAP-specific protocol analyzer, or anyone who simply wants to learn more about what happens “on the wire” between an IMAP client and server.

ipop2d and ipop3d

These are Post Office Protocol servers (Versions 2 and 3, respectively) that you can run on your mail server to provide POP access to any IMAP server. If a given INBOX is accessed by the POP daemon before IMAP, then IMAP will access it in read-only mode. If IMAP gets to it first, POP access will fail with an access error.

imapd

The IMAP4rev1 daemon. The likely reason why you’re mucking about with all this stuff in the first place. A perfectly acceptable course of action for many folks with nothing-out-of-the-ordinary Unix boxes is to build the software, throw a reference to it in /etc/inetd.conf, and be up and running.

The C-Client library (c-client.a)

The heart of the IMAP package. All the other software in this package uses the C-Client library, and it’s the API this library provides that gives UW IMAP its mailbox flexibility ...