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.
Now that's a cool feature!
However, I think I'll stick with giving the exchange server an
"internal" domain, like "exchange.local", as this is what I'm familiar
with and I have already got this setup to work. Things get messy as
Exchange needs active directory as well.
Now, all I need now is some nice "central" address book that works
across both Thunderbird (for the Linux mail server users) and Outlook..
