Todd Lyons wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, Oct 09, 2006 at 06:16:49PM -0700, Mark Nienberg wrote:
/etc/maildroprc(7): Opening logfile /var/log/maildrop.log
maildrop: Unable to create log file.
You are probably using courier-authlib, and the userid/groupid defined
for the "steve" user in whatever authentication module you've configured
courier-authlib for does not match the userid/groupid the file is owned by.
Hmm, not sure what you mean. I am using maildrop as the LDA for sendmail. The
users
have real accounts on the machine.
What I did was make all LDAP mail users be part of the same group, then
make the maildrop.log file owned by that group and group writable.
CentOS44[root@smtp1 ~]# id cann...@misterball.com
uid=1008(cann...@misterball.com) gid=1000(mailusers) groups=1000(mailusers)
CentOS44[root@smtp1 ~]# vdir /var/log/maildrop.log
- -rw-rw-r-- 1 root mailusers 2277471 Oct 10 11:01 /var/log/maildrop.log
If you don't have the ability to make them all use the same group, then
I'm not sure what to do to solve that.
Yes, they are all part of the same group and the log file is writable by the
group.
The problem is that the error message is falsely claiming that the user cannot
open
the log file.
Mark
5 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] maildrop from command...
