Jonathan Tripathy a écrit : > [snip] >>> >>> Does this sound like an acceptable solution? >>> >>> >> yes. it is. >> >> for delivery, you can use virtual aliases: >> j...@example.com j...@exchange.example.com >> >> if the exchange box wants j...@example.com, you can add >> smtp_generic_maops entries to rewrite the address back: >> j...@exchange.example.com j...@example.com >> (This only works if the transport to exchange is "smtp", as the prefix >> of smtp_generic_maps suggests!). >> >> >> This approach is better than per user transports, because transport_maps >> imply performance overhead (and also: transport_maps are global inside >> a postfix instance, so you have less flexibility). >> >> > > Hi mouss, > > Thanks for that >
see also Viktor mail for more accurate information. > Can you please explain why I would need to use smtp_generic_maps? I'm > not entirely sure of the use of it in this context. > you only need that if your exchange is configured to receive mail for j...@example.com and not for j...@exchange.example.com. if you configure exchange to accept mail for j...@exchange.example.com and make it consider this the same thing as j...@example.com, then you don't need smtp_generic_maps. if on the other hand your exchange (or whatever internal server) only wants j...@example.com, then postfix gives you the opportunity to rewrite the addresses at delivery time (after virtual_alias_maps are expanded). This is an exceptionally nice feature in postfix. it means you can do rewrite at input (virtual_alias_maps) then at output (smtp_generic_maps). This somewhat resembles NAT in packet filters that allow you to do NAT at input (map destination IP address) and at output (map source IP address) for a single IP packet.
