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?
and
1. New Server (Postfix + DBMail)
2. Old Server (Postfix + MySQL + Maildir)
Answer:
Not much is known about your configuration to go into any detail but it is
no less true that DBMail (lmtpd? or smtp?) should not be bouncing messages.
If the system has no such user Postfix should be rejecting early in the
chain of events -- in fact there should be no chain ;o)
Postfix is the MTA and should be configured to query the database directly
to learn if the alias/account exists. If not, reject early. The earlier this
done the better off you are in terms of system expense. A good read of the
Postfix documentation will show you many ways of configuring your system and
in what order events should occur. There are may choices
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).
That's a little mystifying. How are you doing this? Sounds like a
misconception, but how are you passing mail from mx2 to mx1's database
dbmail-lmtd??
best...
Mike
----- Original Message -----
From: "Bert Slagter" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, May 22, 2006 5:55 AM
Subject: [Dbmail] Migration: if dbmail cannot deliver,fallback to old
mailserver
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
