5 messages in net.sourceforge.lists.courier-maildrop[maildropl] revisited: maildrop + use...
FromSent OnAttachments
Matthias AndreeApr 13, 2002 9:08 am 
Sam VarshavchikApr 13, 2002 5:32 pm 
Matthias AndreeApr 14, 2002 3:44 am 
Devin RubiaApr 15, 2002 6:10 am 
Matthias AndreeApr 23, 2002 8:18 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[maildropl] revisited: maildrop + userdb: invalid recipient messages not coming back?Actions...
From:Matthias Andree (matt@stud.uni-dortmund.de)
Date:Apr 13, 2002 9:08:49 am
List:net.sourceforge.lists.courier-maildrop

Hello,

I'm revisiting the old "long time to bounce for invalid users" (with userdb) issue that plagued some users.

Sam replied that running maildrop like this should help, but one should consult the documentation of the mailsystem:

maildrop || exit 77

However, looking at maildrop/main.C (1.3.8), I find:

static void nouser() { errexit=EX_TEMPFAIL; throw "Invalid user specified."; }

Two issues:

1. What should the mail system do about this other than defer the mail and bounce it only when it expires (after a week)? Why is mail for nonexistant users deferred in the first place -- hardcoding this seems like the wrong thing to do. A configure-time option would be fine, similarly with an additional command-line switch.

2. Wouldn't it be much more reasonable to set EX_NOUSER here? Of course, that's not sufficient because of the trap handler that overrides this to EX_TEMPFAIL, but still?