I am experiencing some unexpected behaviour in maildrop when the authlib returns a default value for maildir. This behaviour is also incompatible with the way Courier IMAP handles the default.

I have compiled maildrop with authlib support and authlib uses and LDAP backend to retrieve information about home and mail directory. In my setup there are no configuration files for maildrop, no global one and none for the individual users, so maildrop perfoms its default action when called. The users in LDAP have a homedirectory but do not have a maildir attribute. The default behaviour for Courier IMAP and Authlib is to revert to the default maildir "Maildir/", however maildrop seems to default to "../user@domain".

An example: The user with the email address te...@example.com has as home directory "/var/mail/example.com/test" and no maildir, and no configuration files. The expected behaviour would be for the mail to be delivered to "/var/mail/example.com/test/Maildir/" however maildrop delivers it to the mbox file "/var/mail/te...@example.com". See this run:

$ maildrop -d "te...@example.com" -V 9 < testfile maildrop: authlib: groupid=500 maildrop: authlib: userid=500 maildrop: authlib: logname=te...@example.com, home=/var/mail/example.com/test, mail=(default) maildrop: Changing to /var/mail/example.com/test Message start at 0 bytes, envelope sender=te...@example.com maildrop: Attempting .mailfilter maildrop: Delivering to /var/mail/te...@example.com maildrop: Flock()ing /var/mail/te...@example.com. maildrop: Appending to /var/mail/te...@example.com. maildrop: Delivery complete.

I am wondering whether this behaviour is intended or a bug, and how to fix this _without_ creating a config file to hardcode the mail directory.