> On Jun 25, 2018, at 9:39 AM, Olaf313 wrote:
>
> for a period of time we need to route ~ 2.000 mail addresses to our old
> system.
> I would add those addresses into the transport file like
>
> na...@domain.com smtp:system.fqdn.com
>
> name2...@domain.com smtp:system.fqdn.com
>
> Will
On 25 June 2018 at 09:42, Matus UHLAR - fantomas wrote:
>
> depends on how do you configure it. hash: should not have noticeable
> performance impact.
>
a linear search through 2000 addresses should not have a noticeable
performance impact either, compared to, say, network round-trip times...
-
The problem is that all mails for domain.com will go to O365 now but there
are some mailboxes not yet migrated so they still reside on our on-premise
system.
That's why we can't define the whole domain.
But yes, the transport file is hash'ed :)
--
Sent from: http://postfix.1071664.n5.nabble.co
On 25.06.18 06:39, Olaf313 wrote:
for a period of time we need to route ~ 2.000 mail addresses to our old
system.
I would add those addresses into the transport file like
na...@domain.com smtp:system.fqdn.com
name2...@domain.com smtp:system.fqdn.com
Will the larger transport file now affec
Hi,
for a period of time we need to route ~ 2.000 mail addresses to our old
system.
I would add those addresses into the transport file like
na...@domain.com smtp:system.fqdn.com
name2...@domain.com smtp:system.fqdn.com
Will the larger transport file now affect the performance of the Postfi