Sam Varshavchik wrote:
Mark Nienberg writes:
In order to troubleshoot a delivery problem I tried this as root
[root@tesla ~]# maildrop -d steve -V 7 < msg.txt
maildrop: Changing to /home/steve
Message start at 0 bytes, envelope sender=steve
/etc/maildroprc(5): SHELL="/bin/bash"
/etc/maildroprc(6): SENDMAIL="/usr/sbin/sendmail -oi -t"
/etc/maildroprc(7): Opening logfile /var/log/maildrop.log
maildrop: Unable to create log file.
The error message about creating the log file appears to be bogus
because the user "steve" does have write access to the log file and
receives other messages without any problem. In fact, I can su to the
user "steve" and run the command again and the message will be delivered.
Any ideas appreciated,
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.
Mark
5 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] maildrop from command...
