jona...@capi2name.de a écrit :
Hello,
I have the problem that my postfix does not work with maildrop and mysql
user tables.
I have debian sarge and recompiled it with this additional options:
--enable-maildropmysql \
--with-mysqlconfig=/etc/courier/maildropmysql.cnf \
--enable-maildrop-gid=vmail \
--enable-trusted-users="vmail postfix" \
--enable-userdb \
------------------------------------
An maildrop -v prints that out:
maildrop 1.7.0 Copyright 1998-2003 Double Precision, Inc.
GDBM extensions enabled.
Maildir quota extension enabled.
Virtual user database extension enabled.
Virtual user database via MySQL extension enabled.
This program is distributed under the terms of the GNU General Public
License. See COPYING for additional information.
---------------------------------------
My main.cf from postfix I added this:
virtual_transport = maildrop:
maildrop_destination_recipient_limit = 1
maildrop_destination_concurrency_limit = 1
In my master.cf from postfix I added this:
maildrop unix - n n - - pipe
flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient}
And also tried this: (some error see below)
maildrop unix - n n - - pipe
flags=uR user=vmail argv=/usr/bin/maildrop -d ${user} -w 90
uucp unix - n n - - pipe
My /etc/courier/maildropmysql.cnf look like this:
hostname 127.0.0.1
port 3306
#socket /var/run/mysqld/mysqld.sock
database mail_system
dbuser mail
dbpw PASWD
dbtable users
default_uidnumber 5000
default_gidnumber 5000
address_field email
uidnumber_field 5000
gidnumber_field 5000
maildir_field
CONCAT(SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/')
homedirectory_field "/home/vmail/"
But mail.log outputs this:
status=bounced (user unknown. Command output: Invalid user specified. )
What is wrong on my system?
Greets
Jonas
P.S the user vmail and group vmail extis on compile in the /etc/passwd
run maildrop manually:
maildrop -V 4 -d fo...@example.com < message.eml
both as root and as vmail.
if it works as root but not as vmail, rebuild maildrop but unset the
variable HAVE_COURIER
also run mysql with logging enabled to see whether maildrop really calls
mysql.
while this is unrelated, consider upgrading maildrop.