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.
I am trying to use maildrop 1.5.0 in delivery mode. However, I find
that it opens the userdb:
11377 maildrop NAMI "/etc/userdb.dat"
11377 maildrop RET open 3
11377 maildrop CALL fcntl(0x3,0x2,0x1)
11377 maildrop RET fcntl 0
reads a few bytes:
11377 maildrop CALL read(0x3,0x8077000,0x104)
11377 maildrop GIO fd 3 read 260 bytes
[...]
and closes it:
11377 maildrop RET read 260/0x104
after which it looks at its own credentials:
11377 maildrop CALL getuid
11377 maildrop RET getuid 1012/0x3f4
11377 maildrop CALL getgid
11377 maildrop RET getgid 1012/0x3f4
11377 maildrop CALL getegid
11377 maildrop RET getegid 1012/0x3f4
and then calls getpwent(). Since the user is in usedb, not the
passwd file, getpwent fails, and maildrop prints "Invalid user
specified." and exits with a failure.
What is going on here?
Kids, the seven basic food groups are GUM, PUFF PASTRY, PIZZA,
PESTICIDES, ANTIBIOTICS, NUTRA-SWEET and MILK DUDS!!
Kids, the seven basic food groups are GUM, PUFF PASTRY, PIZZA,
PESTICIDES, ANTIBIOTICS, NUTRA-SWEET and MILK DUDS!!
16 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] maildrop 1.5.0 not fi...
.userdb
