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 6, 2002 6:49:39 pm
List:net.sourceforge.lists.courier-maildrop

Ben Rosengart writes:

On Wed, Nov 06, 2002 at 06:49:22PM -0500, Sam Varshavchik wrote:

Everything works fine here. With --enable-restrict-trusted=0, and maildrop installed setuid root, any UID can delivery to any other UID.

What can I give to you to help you reproduce this? Ktrace output? Autoconf's log file? Can you suggest ways to instrument maildrop to see what is going on? Giving up is not an option for me here.

For starters, look in maildrop/xconfig.h, and look for the definition of RESTRICT_TRUSTED. This symbol is what gets set by this autoconf option. It should, obviously, be 0.

Then, make sure that you have indeed compiled the code, and installed the new maildrop binary setuid root (and you are not running an old binary).

And only then provide a trace log.