I'm going to assume you're just having a bad day, bite my tongue, and
follow along. Among the myriad other things I have to do, I'm also
attempting to co-configure a couple of pieces of software new to my
experience in a method that is likewise new to my experience. It has
proven more difficult than I originally anticipated. I really apologize
if my request for clarification upsets you.
Seeing as how the ultimate recipient of the message DOES NOT HAVE A
LOCAL UID/GID (as I've clearly stated a few times prior), I assumed that
the software would use a global UID/GID presumably of a non-privileged
user (courier, in my case, seems appropriate). I configured the call to
Maildrop in that way, where the UID/GID matches the user "Courier" with
the home directory configured in userdb matching that user "Courier".
Now then, that said, I still get the same behavior ("user not found").
Nothing is thrown in the configured log file indicating exactly what the
error is, so I'm now groping blind, hoping that someone who knows more
than me can assist (presumably the intent of this mailing list).
The documentation available on courier-mta.org (specifically the maildrop and makeuserdb pages) seem much more focussed on local users (those with UNIX accounts on the machine), hence my requests.
Every user has to have a UID/GID. Even if they're not local, they still need one. What normally happens is the admin creates a user in whatever authentication system they use and keep assigning the same UID and GID to all the virtual users. The 'master' virtual user has no privileges to log on or anything, and is only used for mail things.
The maildirs are then created under this shared UID and everything works nicely. There's no 'default' UID or GID - they must be specified.
-- Phillip Hutchings [EMAIL PROTECTED] http://www.sitharus.com/
smime.p7s
Description: S/MIME cryptographic signature
