On Wed, Sep 24, 2008 at 06:42:11PM -0400, Sahil Tandon wrote:
> To avoid this situation, use a transport map to temporarily defer mail
> *just* for those recipients. Once you're ready to "go live" on the new
> server, remove the "defer:" transport map for example.com (make sure you
> postmap if it's a hash), and flush the queue. If mail destined for
> example.com should instead be directed to smtp:[some.where.else], then
> instead of removing the transport map entirely, you would obviously
> update it (replacing the "defer:" portion) as necessary and then flush
> the queue. See transport(5).
Note, Postfix has no "defer" transport, but Postfix 2.4 and later has a
"retry" transport that defers all mail. Do NOT confuse the "defer"
service in master.cf (using to update defer logs) with a delivery agent
(aka transport).
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:[EMAIL PROTECTED]>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
