Hi,
Noel Jones wrote:
> Lothar Braun wrote:
>> What I'm trying to do now is: Accept mails for @mydomain.tld on the new
>> server and try to deliver them to the local accounts. If that fails,
>> send it out to the old server and try to deliver it there.
>>
>> I had a look at the documentation but couldn't come up with an easy
>> solution for that. The only solution I can see so far is to create an
>> transport entry on the new server for _every_ email address that needs
>> to be delivered to the old server.
>
> Yes, that's the proper solution.
>
> If you're using SQL, just set a flag on each account indicating where
> it's to be delivered, and adjust your transport_maps query accordingly.
> You may already have the information you need in SQL.
>
> If you're using {hash, cdb, ...} indexed files, use a script to create
> your transport map. The size of the map is not a concern.
>
> An alternative is to use virtual_alias_maps to rewrite the "old" set of
> users to a different subdomain, and use transport_maps to direct the
> mail. You could then use smtp_generic_maps to rewrite the domain back
> to the original when it's transferred to the old server.
>
> Just listing everyone in transport_maps is probably easier.
Thank you for the quick answer. I think I'll go with listing all users
in transport_maps.
Best regards,
Lothar
