Hi Steve!
I was woundering if its possible to use catchall addy's with maildrop
Im using postfix 2.0 and maildrop 5.0
Postfix and MailDrop both get there address's and info from a mysql
table...
Just say if i was to send an email to ste...@xxx.com maildrop looks up the
table and see's ste...@xxx.com is there so it dilvers it..
But if i send an email to bl...@drifthost.com MailDrop looks up the table
and
cant see bl...@drifthost.com and comes back with this error
Jan 2 17:03:10 xxx postfix/pipe[14744]: 14439271EC: to=bl...@xxx.com,
relay=maildrop, delay=1, status=deferred (temporary failure. Command
output:
/usr/local/bin/maildrop: Invalid user specified. )
But in my mysql tables i have a user called mas...@xxx.com that has a
catch-all addy of @xxx.com
Is there anyway to make postfix or maildrop see that its a catch-all addy?
Did you try to deliver to that catch-all address only with postfix? Like
using virtual or such. I think this catch-all thing is done by Postfix by a
lookup @xxx.com in the mysql table.
Maildrop doesn't seem to do such a lookup in the tables. Perhaps, you could
alternatively work with making Maildrop use the delivered-to: line to
examine which user to pass the mail to, as Postfix would write the final
recipient (the existing one) down here.
Talking about Maildrop and Postfix. I'm also trying to get this running. How
did you compile Maildrop to support Mysql? I used these for configure:
--enable-maildirquota # quotas are also in mysql
--enable-userdb # Am I right with using virtual users here?
--enable-maildropmysql # this should enable mysql support
--with-mysqlconfig=/usr/local/etc/maildrop_mysql.conf
Should be fine, but make is only looking for mysql config file in /etc. No
further actions about mysql are done by make.
The final program has only GDBM enabled. Nothing about any other settings.
Philon