Sam Varshavchik wrote:
Deim Agoston writes:
Hello!
I've just upgraded to version 1.5.3 from 1.3.7 (it worked stable so
there was no reason to upgrade). Right now, I just get the EX_TEMPFAIL
message instead of EX_NOUSER. It would be OK if I didn't touch the
maildrop/main.C file and replace the static value of nouser from
EX_TEMPFAIL to EX_NOUSER - for the sake of newcommers: that's the proper
value for a non-existent user. So, I touched the files and replaced the
EX_TEMPFAIL with EX_NOUSER. Built the binaries, installed them.... and
gone mad. Why the f*@&{ maildrop can implement the correct behaviour
It is the correct behavior. If the recipient mailbox does not exist, your
mail server should reject the recipient address as nonexistent and
nondeliverable, and maildrop will never even see it.
As such, if the LDA is unable to determine the location of the recipient's
mailbox, it is interpreted as a local misconfiguration, and is deferred
accordingly.
Yes, but in some setups it might be sensible to exit with EX_NOUSER in
case of nonexistent recipient user. For example, postfix users with
mailbox_transport configured would be interested in this. It is easy to
reject mail for unknown users at the SMTP session, but the problem in
question can occur with locally originated mail or bounce messages that
are delivered to fake or mistyped local addresses.
7 messages in net.sourceforge.lists.courier-maildrop[maildropl] Re: maildrop-1.5.3 and EX...
