--- /etc/postfix/readme/MAILDROP_README	2003-06-12 13:52:57.000000000 +0200
+++ /etc/postfix/readme/MAILDROP_README.tonni	2004-02-01 11:21:36.492862680 +0100
@@ -37,3 +37,37 @@
 userdb lookup). The ${extension} and the other address components
 are available to maildrop rules as $1, $2, $3, ...  and can be
 omitted from master.cf or ignored by maildrop when not needed.
+
+===========================================================================
+
+Date: Sat, 31 Jan 2004 16:00:00 +1:00 (CET)
+Tonni Earnshaw <>
+addition for MAILDROP_README.
+
+LDAP and maildrop.
+
+maildrop can be compiled with LDAP support by including "--enable-maildropldap"
+in the configure parameters.
+
+maildrop's LDAP support, combined with Courier IMAP's authldap.schema, give 3
+new objectclasses over and above standard object classes. These enable LDAP-
+based quotas, virtual aliases and virtual mailboxes, as well as maintaining 
+regular $HOME/Maildir based mail directories, where these are applicable.
+
+By using the standard combination of master.cf/transport as given above,
+NO standard Postfix LDAP lookups are done before passing the message to the
+Postfix transport. This in itself takes care of immediate delivery; however, it's
+most likely that LDAP lookups have to be done - for example on system and other
+aliases - before enabling delivery to users' mailboxes.
+
+With Postfix 2.1.0 (perhaps before that too), it is possible to circumvent the
+master.cf/transport pair by giving maildrop as the mailbox_command in main.cf
+and omitting the master.cf/transport combination. Choosing this alternative
+enables all LDAP lookups before passing the message to the transport. For LDAP
+deliveries, the file /etc/maildropldap.config has to be configured correctly
+before this will work.
+
+Example (note the upper-case "USER"):
+
+mailbox_command = /usr/local/bin/maildrop -d ${USER}
+