You could try to use a virtual user table, although I use sendmail, I
presume postfix also supports this. With a virtual user table it is
possible, to have a default mailbox where all mails get deliverd to,
which don't fit into your aliases.
That way, you don't even have to use 2 servers.
Op 22-mei-2006, om 11:55 heeft Bert Slagter het volgende geschreven:
Hello all,
We want to migrate a customer (with 50 domains and 600 mailboxes)
to DBMail. This is a good opportunity to cleanup their mailbox
mess, so we won't import existing mailboxes but start with a fresh
new DBMail. To allow them to take the time they need to think about
aliases, mailboxes, etc we would like to create a setup like this:
1. New Server (Postfix + DBMail)
2. Old Server (Postfix + MySQL + Maildir)
We would like this setup to behave like this:
1. The new server receives the e-mail, tries to deliver it to
DBMail, if it fails (because no aliases exist for this message yet)
2. The old server tries to deliver the e-mail.
I've tried to:
1. Setup the new server as primary MX and the old server as
secondary MX, but that didn't work (the new server bounces the mail
if DBMail can't find an alias/user).
2. Setup the old server as fallback_transport in postfix main.cf.
Doesn't work, a bounce message is sent anyway.
Questions:
* Is there a way to stop DBMail from bouncing a message if it
cannot be delivered, but reject it instead? Maybe a rejected
message will be given to the fallback_transport?
* Do you know other solutions?
Thanks!
Bert Slagter
Procurios Webdevelopment
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
