Marcus:
> Wietse:
> >> Marcus:
> >> What are the benefits of socketmap (postfix 2.10+) vs tcp_table?
> >
> > tcp_table is Postfix-only. socketmap also works with Sendmail,
> > and is a better protocol.
>
> Out of curiosity... when you say "better", are you talking about
> performance and/or reliab
Wietse:
>> Marcus:
>> What are the benefits of socketmap (postfix 2.10+) vs tcp_table?
>
> tcp_table is Postfix-only. socketmap also works with Sendmail,
> and is a better protocol.
Out of curiosity... when you say "better", are you talking about
performance and/or reliability,
or do you mean it's
Marcus:
> What are the benefits of socketmap (postfix 2.10+) vs tcp_table?
tcp_table is Postfix-only. socketmap also works with Sendmail,
and is a better protocol.
> And can I use socketmap with sender_dependent_default_transport_maps ?
You can use any Postfix table-driven feature with socketmap
What are the benefits of socketmap (postfix 2.10+) vs tcp_table?
And can I use socketmap with sender_dependent_default_transport_maps ?
i.e. sender_dependent_default_transport_maps = socketmap:inet:127.0.0.1:
I'm struggling to understand the what the documentation of socketmap
refers to "name"