2012/12/20 Viktor Dukhovni <postfix-us...@dukhovni.org>:
> Instead of resolving an unmodified rfc822 address to a different
> transport:nexthop, rewrite the rfc822 address (via virtual_alias_maps)
> to a domain which is routed (via MX records or per-nexthop transport
> table entries) to that transport:nexthop.
I've test this and my ticketing system (the remote machine) is working
like a charm.
I used a tranport table entry like:
internal.example.com smtp:172.16.34.34
That, combined with:
/etc/postfix/main.cf
virtual_alias_maps = hash:/etc/postfix/virtual
/etc/postfix/virtual:
foo...@example.com foo...@internal.example.com
did the work. With a DNS server configured to resolve
internal.example.com, even the transport entry wouldn't be necessary,
but my mailhost system is using a public DNS.
Is there a way to tell postfix to use local dns server for example.com
and public dns for all other domains?
2012/12/20 Viktor Dukhovni <postfix-us...@dukhovni.org>:
> Actually you do. You can add custom LDAP attributes and populate them
> as part of your user-provisioning process. You can use the relevant
> parts of the Sendmail schema for example:
> https://www.sendmail.com/sm/open_source/docs/m4/laser.txt
I don't need this approach now, but both your advises and the link are
very worth reading, thank you so much.
