Installing BincIMAP

11 Mar 2004 09:35 qmail

Configuring BincIMAP

Another of my requirements is that my email should be accessible using IMAP. I’ve had a quick look at Courier IMAP, and (IMO) it’s a bit oversized for my needs. So, I’m going to install BincIMAP instead. I grabbed the 1.2.7beta5 tarball and unpacked it in /usr/local/src.

Compiling it is easy:

# cd /usr/local/src/bincimap-1.2.7beta5
# ./configure
# make

I think I should have got hold of a faster test box. It was a little slow (the C++ compiler uses a lot of memory, which causes paging on a box with only 64Mb of memory).

# make install
# ln -s /var/opt/bincimap/service/* /service

And it’s running.

Configuring BincIMAP to use vchkpw

Nothing particularly exciting here. Just some changes to the startup scripts. This is /var/opt/bincimap/service/imap/run:

exec 2>&1

exec    tcpserver -c 100 -u 0 -g 0              \
    -l $(hostname) -HDRP                        \
    0 143                                       \
    /opt/bincimap/bin/bincimap-up                       \
    --logtype=multilog                          \
    --conf=/etc/opt/bincimap/bincimap.conf --   \
    /home/vpopmail/bin/vchkpw                   \

…and the corresponding change to the imaps/run script. To make it easier to start and stop BincIMAP, I’ve added the relevant stuff to the qmailctl script, originally from LWQ.

Testing it

To test it, I used Outlook Express:

Display Name: Roger Lipscombe
Email Address: roger@beerology.test
POP3 Server: flimsy.beerology.test
IMAP Server: flimsy.beerology.test
User ID: roger@beerology.test
Password: password

Unfortunately, it doesn’t work initially – the server responds with:

LOGIN failed: Plain text password authentication is disallowed.
Please try enabling SSL or TLS in your mail client.

For now, I’m going to configure BincIMAP to allow plain text authentication, and then I’ll look at tightening it up later.

BincIMAP keeps its configuration file in /etc/opt/bincimap/bincimap.conf. The setting we need to change is called “allow plain auth in non ssl” and it’s set to “no” by default. I’ll change it to “yes”

This time, Outlook Express successfully connects and displays the Inbox. If I send an email to this account from somewhere else, it turns up correctly, too. Which is cool.

Using IMAPdir

By default, BincIMAP is configured for Maildir++ support, which is the simplest, but only allows folders to be created inside INBOX.

I’d like to be able to create folders at the same level as INBOX. To do this, I need to change BincIMAP to use “IMAPdir” mode. The change to BincIMAP is simple. In /etc/opt/bincimap/bincimap.conf:

Mailbox {
    depot = "IMAPdir",                           /* Use Maildir++ style
                                                    * depot. */

    type = "Maildir",                              /* only Maildir
                                                    * support */

    path = "IMAPdir",                              /* default path */

Looking at the BincIMAP FAQ shows that the IMAPdir mode requires some extra directories:

# cd /home/vpopmail/domains/beerology.test/roger
# mkdir IMAPdir
# chown vpopmail.vchkpw IMAPdir
# chmod 2700 IMAPdir
# cd IMAPdir
# ln -s ../Maildir INBOX

At this point, it’s possible to create IMAP folders at the same level as INBOX. This is a little irritating. This needs to be done on every account created. A good fix for this would be to change vadduser so that it did this for us. First, we rename vadduser to vadduser.real, and then create a script to replace it:


/home/vpopmail/bin/vadduser.real $1 $2
VDIR=`/home/vpopmail/bin/vuserinfo -d $1`

mkdir -p $VDIR/IMAPdir
chown vpopmail.vchkpw $VDIR/IMAPdir
chmod 2700 $VDIR/IMAPdir
ln -s ../Maildir $VDIR/IMAPdir/INBOX

This script doesn’t correctly handle switches passed to it. This is left as an exercise for the reader. If anyone fancies writing one, send it to me and I’ll put it here.