Simon Effenberg:
> > If you want to send domain1.tld and domain2.tld to the internal
> > relay, then the correct syntax for a hash: map would be:
> >
> > domain1.tld smtp:[internal.relay]
> > domain2.tld smtp:[external.relay]
>
> yes sorry.. was only wrong in my he
On Sat, 9 Nov 2013 15:30:10 -0500 (EST)
wie...@porcupine.org (Wietse Venema) wrote:
> > transport:
> >
> > @domain1.tld smtp:[internal.relay]
> > @domain2.tld smtp:[external.relay]
>
> If you want to send domain1.tld and domain2.tld to the internal
> relay, then the correct syntax for a hash
Simon Effenberg:
> On Sat, 9 Nov 2013 07:54:30 -0500 (EST)
> wie...@porcupine.org (Wietse Venema) wrote:
>
> > transport_maps can use hash tables AND tcp tables. transport_maps
> > queries each table in the specified order, and stops when a result
> > is found. When no result is found, Postfix use
So has anybody an idea if I can get the functionallity I want? I know that I
could put all the logic from the hash table into the tcp table but that sounds
ugly..
Simon Effenberg schrieb:
>Sorry the mistake was only in my example.. pardon me. The transport
>file has no @ prefix in my configur
Sorry the mistake was only in my example.. pardon me. The transport file has no
@ prefix in my configuration. (And if I disable the tcp table the transport
file works like expected).
Jeroen Geilman schrieb:
>On 11/09/2013 02:33 PM, Simon Effenberg wrote:
>> On Sat, 09 Nov 2013 14:21:51 +0100
On 11/09/2013 02:33 PM, Simon Effenberg wrote:
On Sat, 09 Nov 2013 14:21:51 +0100
Jeroen Geilman wrote:
On 11/9/2013 2:13 PM, Simon Effenberg wrote:
On Sat, 9 Nov 2013 07:54:30 -0500 (EST)
wie...@porcupine.org (Wietse Venema) wrote:
transport_maps can use hash tables AND tcp tables. transpo
On Sat, 09 Nov 2013 14:21:51 +0100
Jeroen Geilman wrote:
> On 11/9/2013 2:13 PM, Simon Effenberg wrote:
> > On Sat, 9 Nov 2013 07:54:30 -0500 (EST)
> > wie...@porcupine.org (Wietse Venema) wrote:
> >
> >> transport_maps can use hash tables AND tcp tables. transport_maps
> >> queries each table in
On 11/9/2013 2:13 PM, Simon Effenberg wrote:
On Sat, 9 Nov 2013 07:54:30 -0500 (EST)
wie...@porcupine.org (Wietse Venema) wrote:
transport_maps can use hash tables AND tcp tables. transport_maps
queries each table in the specified order, and stops when a result
is found. When no result is found
On Sat, 9 Nov 2013 07:54:30 -0500 (EST)
wie...@porcupine.org (Wietse Venema) wrote:
> transport_maps can use hash tables AND tcp tables. transport_maps
> queries each table in the specified order, and stops when a result
> is found. When no result is found, Postfix uses default_transport.
>
>
Simon Effenberg:
> On Sat, 9 Nov 2013 08:54:40 +0530
> tejas sarade wrote:
>
> > If lookup fails Postfix will use default transport.
>
> Sure but this is only _one_ "hard-coded" transport and not one I can
> dynamically change like in the tcp_table lookup.
>
> So it looks like as if the logic t
On Sat, 9 Nov 2013 08:54:40 +0530
tejas sarade wrote:
> If lookup fails Postfix will use default transport.
Sure but this is only _one_ "hard-coded" transport and not one I can
dynamically change like in the tcp_table lookup.
So it looks like as if the logic tries to minimize the lookup queries
11 matches
Mail list logo
