I apologize in advance to those who are subscribed to both courier-users and courier-maildrop; I have duped this post to both lists. I didn't realize at first that there was a courier-maildrop list.

We are running a Debian sarge system. I've installed the latest courier-imap, courier-authdaemon, and courier-maildrop from APT but found to my dismay that Debian's maildrop package is not linked against authlib, and thus cannot perform authdaemond lookups. Odd, but hey that's binary packages for ya.

So we decided to compile maildrop from source. Unfortunately, the Debian packages don't install the requird authlib development files for maildrop to compile against.

So we installed courier-authlib-0.55.20050320 from source, to /opt/courier. Then we set about the task of compiling courier-maildrop-1.8.0 against it. This has proven to be a formidable task. Here are the problems we found:

I can get it to compile and build if I:

- set COURIERAUTHCONFIG=/opt/courier/bin/courierauthconfig - manually set, in maildrop/main.C: #include "/opt/courier/include/courierauth.h"

but when I run the maildrop binary with -d as a test, I get:

ERR: authdaemon: s_connect() failed: No such file or directory Invalid user specified.

The reason I had to set a hardcoded path on that #include is because if I run (as ./configure does also) /opt/courier/bin/courierauthconfig --cppflags, I get no output. --ldflags gives correct output.

I have also tried setting AUTHINCLUDE=-I/opt/courier/include and AUTHLDADD=-L/opt/courier/lib/courier-authlib and manually setting AUTHLIB=1 in 'configure', to no avail.

This really shouldn't be that difficult, but somehow it's managing to drive us up the wall.

Any help would be greatly appreciated.

Thanks!

-Brian