Tag: courier

courier-authlib, userdb: entry not found

If you get error messages like this

Oct 18 15:38:47 server authdaemond: userdb: opened /etc/authlib/userdb.dat
Oct 18 15:38:47 server authdaemond: userdb: looking up 'user'
Oct 18 15:38:47 server authdaemond: userdb: entry not found

You should check that your user entry is really seperated from the the rest of the line with a tab – and not with spaces.

Migrating from courier imap to exchange 2007 using imapsync

The following blogpost describes my experience when migrating from courier imap to an exchange 2007 server with the help of imapsync. The intend is not to provide a complete howto but rather reflect my thought and experiences during the migration phase.

Continue reading “Migrating from courier imap to exchange 2007 using imapsync”

Superuser / administrators group in courier imap

One not obvious feature in courier imap is the superuser account. The feature is a bit hidden in documentation for courier-authlib (see man auth_generic). It is based on the IMAP group functionality of courier.

You can assign a user account to different groups independently from other (system) groups the belongs to. The group assignement is implemented with the option field in courier-authlib, see man auth_generic.

There is a special group name “administrators”. If you assign one account to that group you have automatically full access to all other users mailboxes and folders over the #shared namespace. This is especially usefull when doing e.g. email migration over IMAP from one server to another.

If you use courier-authlib-ldap there is neither a explicit option field nor a groups field in couriers LDAP scheme. But you can assign arbitrary text attributes to group setting with the LDAP_AUXOPTIONS variable. As I don’t use the sharedgroup attribute I simply misused it for the group setting by adding the following to /etc/authlib/authldaprc:

LDAP_AUXOPTIONS disableimap=disableimap,disablepop3=disablepop3,disablewebmail=disablewebmail,sharedgroup=group

Courier mail server and SSL error SSL3_GET_RECORD:wrong version number

Just realized that some of the incoming mails where bouncing, meaning that the other mailserver wasn’t able to connect at all.

This concerned all all mailservers starting a STARTTLS SMPT connection. In the logs the “SSL routines:SSL3_GET_RECORD:wrong version number” occured.

It turned out to be a configuration problem of courier. In the default install TLS_PROTOCOL is set to TLS1. The problem dissapears when setting it to SSL23 instead.