Em 09-03-2004 09:12, Bernhard Schmidt escreveu:
It has to do with maildrop and only this. I guess you've got something
like this in your maildropmysql.config:
-->%--
maildir_field maildir
homedirectory_field home
-->%--
Exactly.
So maildrop reads the values from your mysql tables and tries to cd to
$home first! If this directory doesn't exist it will normally return
something like
-->%--
relay=maildrop, delay=108, status=deferred (temporary failure. Command
output: /usr/local/bin/maildrop: Unable to change to home directory. )
-->%--
Exactly again.
and stop exactly here before any code from maildroprc gets executed.
My suggestion (the same again) is, change the home dir value to either
the home directory of your maildelivery user (vmail?) or to another
existing directory like /var/spool/mail.
OK, I changed a single user's home value in mysql to
/var/spool/mail/domain.tld (which is already created) and used Marcio
Merlone's solution (
http://sourceforge.net/mailarchive/message.php?msg_id=2446278 ). It
worked fine! Thanks!
Now just one more question: when I set $home in mysql to the user's home
dir /var/spool/mail/domain.tld/user, I was able to user .mailfilter
files for individual maildrop rules on its directory.
If I set now the mysql $home value to e.g. /var/spool/mail, will I lose
the feature of individual filtering files? Is there any workaround for this?
TIA.
8 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Problems with autocre...
