atom feed14 messages in net.sourceforge.lists.courier-users[courier-users] Re: Unknown User = EX...
FromSent OnAttachments
Griffiths, JonJul 24, 2001 7:28 am 
Sam VarshavchikJul 24, 2001 2:56 pm 
Daniel RoesenJul 24, 2001 4:21 pm 
Oliver BlasnikJul 25, 2001 12:44 am 
Griffiths, JonJul 25, 2001 2:33 am 
Griffiths, JonJul 25, 2001 2:56 am 
Daniel RoesenJul 25, 2001 3:30 am 
Xavier BeaudouinJul 25, 2001 3:41 am 
Sam VarshavchikJul 25, 2001 4:46 am 
Oliver BlasnikJul 25, 2001 7:30 am 
Daniel RoesenJul 25, 2001 8:29 am 
Griffiths, JonJul 25, 2001 10:00 am 
Sam VarshavchikJul 25, 2001 2:15 pm 
Oliver BlasnikJul 25, 2001 2:58 pm 
Subject:[courier-users] Re: Unknown User = EX_TEMPFAIL??
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Jul 25, 2001 2:15:48 pm
List:net.sourceforge.lists.courier-users

Oliver Blasnik writes:

- my_pw=getpwnam(deliverymode); if (!my_pw) nouser();

If getpwnam fails, there could be just one reason: - the user could not be retrieved (nonexistant)

Or the NIS server is down.

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 mail 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.

Of course it should worry about it. Instead of bouncing all mail until the server goes back up, the mail will be nicely deferred, and redelivered when things return to normal.