Todd Lyons writes:
On Wed, Oct 11, 2006 at 06:27:16PM -0400, Sam Varshavchik wrote:
Again, explain how you've configured Courier to use maildrop for local mail
delivery.
Ah, you must have missed my original email where I said I was using
sendmail with maildrop. I have to run and catch the train to get home.
I'll post my entire configs tomorrow. On this smtp machine, only
authdaemond is running, with authldap configured as the auth mechanism.
From your original message:
# CentOS44[root@smtp1 ~]# rpm -qa courier*
# courier-authlib-devel-0.58-1
# courier-maildrop-0.53.2-1
# courier-authlib-ldap-0.58-1
# courier-0.53.2-1
# courier-maildrop-wrapper-0.53.2-1
# courier-pop3d-0.53.2-1
# courier-authlib-0.58-1
# courier-imapd-0.53.2-1
"courier-maildrop" is the Courier maildrop subpackage. The key word here is
"subpackage".
This is a Courier-only version of maildrop, that only works, properly, with
Courier. maildrop expects Courier to set up the environment before invoking
maildrop. "courier-maildrop" is a subpackage, and requires the main courier
package to be installed. The courier RPM should be listed as a prerequisite
of the courier-maildrop RPM (if whoever did the CentOS rpms based it on
Courier's Red Hat/Fedora rpms), and that's not an accident.
Courier is responsible for reading account data from the authentication
source -- in your case it's LDAP -- and passing it to maildrop via the
environment variables. Obviously, sendmail doesn't know anything about
this.
You can probably get this to work by using the "maildrop" package, not
"courier-maildrop", if you can find it. This is the version of maildrop
without the Courier-specific hooks (it builds from the same source, but with
some behind-the-scenes configuration changes), and it should work for you.