16 messages in net.sourceforge.lists.courier-maildrop[maildropl] Re: maildrop 1.5.0 not fi...
FromSent OnAttachments
Ben RosengartNov 1, 2002 4:27 pm 
Ben RosengartNov 4, 2002 12:25 pm 
Sam VarshavchikNov 4, 2002 2:53 pm 
Ben RosengartNov 4, 2002 3:42 pm 
Sam VarshavchikNov 4, 2002 3:59 pm 
Ben RosengartNov 5, 2002 4:22 pm 
Sam VarshavchikNov 5, 2002 7:41 pm 
Ben RosengartNov 5, 2002 8:09 pm 
Ben RosengartNov 6, 2002 2:31 pm 
Luc BrouardNov 6, 2002 2:38 pm 
Ben RosengartNov 6, 2002 3:20 pm 
Ben RosengartNov 6, 2002 5:52 pm 
Sam VarshavchikNov 6, 2002 6:49 pm 
Ben RosengartNov 6, 2002 7:09 pm 
Sam VarshavchikNov 6, 2002 7:40 pm 
Ben RosengartNov 6, 2002 8:19 pm.userdb
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] Re: maildrop 1.5.0 not finding users in userdbActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Nov 4, 2002 3:59:44 pm
List:net.sourceforge.lists.courier-maildrop

Ben Rosengart writes:

On Mon, Nov 04, 2002 at 05:53:31PM -0500, Sam Varshavchik wrote:

Ben Rosengart writes:

This behavior seems to vary with the setting of "--enable-restrict-trusted" for some reason. If it is set to 1, then the userdb is consulted, but delivery to users with UIDs other than the trusted one is impossible. If it is set to 0, then the below-described behavior occurs. Please advise.

What exactly is unclear about the following description from INSTALL:

When I compile with --enable-restrict-trusted=0, all deliveries fail with "Invalid user specified", and the userdb is not consulted. Why?

By the way, I did remember to set the setuid bit on the maildrop binary.

Try --disable-restrict-trusted. It might be something changed in autoconf2.5x's parser. Investigating...