Em 07-03-2004 07:14, Bernhard Schmidt escreveu:
cue...@saulo.eti.br wrote:
the $DEFAULT gives me
/var/spool/mail/domain.tld/user/Maildir, and $HOME gives me
/var/spool/mail/domain.tld/user - but i only got the $HOME and
$DEFAULT when the
user's maildir is created in the linux system.
It seems that maildrop can only get the $HOME and $DEFAULT mysql
variables only
if the maildir is created... such a strange behaviour.
It is just the normal maildrop behaviour as it seems. You have to set
HOME to /var/spool/mail and MAILDIR to domain.tld/user/Maildir
otherwise maildrop isn't able to change to user's home directory.
Maildroprc and .mailfilter is executed after being in there as far as
I know.
OK, but my $HOME and $DEFAULT maildroip variables aren't set by me or by
the linux system, but by the mysql database, am I right?
Example:
$ cat /etc/maildroprc
`echo $HOME > /tmp/maildir`
`echo $DEFAULT >> /tmp/maildir`
$
$ mail user...@domain.tld
$
$ cat /tmp/maildir
/var/spool/mail/domain.tld/user
/var/spool/mail/domain.tld/user/Maildir
$
$ mail user...@domain.tld
$
$ cat /tmp/maildir
$
Obviously, $HOME and $DEFAULT in my linux box are variables from the
linux system, and doesn't have nothing to do with maildrop/mysql/courier
environment.
My question again is: why the heck maildrop doesn't get those variables
when maildir is not created?
8 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Problems with autocre...
