[about the inconsistent EX_TEMPFAIL and logging of "Invalid user specified"]
The errorcode delivered with this error message is definitely wrong.
I just see just no reason to give back EX_TEMPFAIL instead EX_NOUSER.
Please, be so glad and explain this so we could understand.
I already provided an explanation. If a mailbox does not exist, the
should not have been accepted by the mail server and returned as
This is your point of sight. Again: Not everybody could check the address
before injecting into maildrop.
If maildrop receives a message for the recipient, but is
unable to determine the recipient's home directory, uid and gid, this is
considered a configuration error or a failure.
This is wrong. As Maildrop could be used without any other courier-
related software, this is a wrong assumption.
After a 1-minute-sight into main.C I'm saying: EX_TEMPFAIL is incorrect
in nouser(), as this is only called in following situation:
- my_pw=getpwnam(deliverymode); if (!my_pw) nouser();
If getpwnam fails, there could be just one reason:
- the user could not be retrieved (nonexistant)
After this knowledge, the only reply has to be EX_NOUSER.
The NIS server could be
down, for example. Hence, the safest course to follow is to keep the
queued up until someone notices and fixes the problem.
If the NIS is down and so get problems authenticating, this is a design
failure of the one who is using nis (no backups? no local copies?) and not
something you/maildrop has to worry about.
Back to you, Sam,
-- http://www.nextra.de - INTERNET@WORK ----- oliv...@nextra.de --
Nextra Deutschland | Oliver Blasnik Senior System Administrator
GmbH & Co KG | Lyoner Strasse 26 D-60528 Frankfurt
Engineering TA&S | tel +49-69-66441-0 fax +49-69-66441-199