On Sat, 9 Nov 2013 08:54:40 +0530
tejas sarade tejas.a.sar...@gmail.com 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
Simon Effenberg:
On Sat, 9 Nov 2013 08:54:40 +0530
tejas sarade tejas.a.sar...@gmail.com 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
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.
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
On Sat, 09 Nov 2013 14:21:51 +0100
Jeroen Geilman jer...@adaptr.nl 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
On 11/09/2013 02:33 PM, Simon Effenberg wrote:
On Sat, 09 Nov 2013 14:21:51 +0100
Jeroen Geilman jer...@adaptr.nl 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
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 jer...@adaptr.nl schrieb:
On 11/09/2013 02:33 PM, Simon Effenberg wrote:
On Sat, 09 Nov 2013
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 sa...@schuldeigen.de schrieb:
Sorry the mistake was only in my example.. pardon me. The transport
file has no @
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 uses
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: map
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 head while
Hi,
my transport_maps is:
transport_maps = hash:/etc/postfix/transport,
regexp:/etc/postfix/transport.exp,
tcp:[127.0.0.1]:2527
I want to use the tcp as last resort lookup but I don't know in
which order postfix is checking everything.
It looks like it is doing:
first round:
check
Simon Effenberg:
Hi,
my transport_maps is:
transport_maps = hash:/etc/postfix/transport,
regexp:/etc/postfix/transport.exp,
tcp:[127.0.0.1]:2527
I want to use the tcp as last resort lookup but I don't know in
which order postfix is checking everything.
transport_maps are searched
wie...@porcupine.org schrieb:
transport_maps are searched in the order as specified in main.cf.
If it's not found in regexp:/etc/postfix/transport.exp, then
the tcp map is queried.
Wietse
So this means that I cannot distinguish between x...@yyy.com and yyy.com
lookups in the tcp
If lookup fails Postfix will use default transport.
On Nov 9, 2013 7:49 AM, Simon Effenberg sa...@schuldeigen.de wrote:
wie...@porcupine.org schrieb:
transport_maps are searched in the order as specified in main.cf.
If it's not found in regexp:/etc/postfix/transport.exp, then
the tcp map
15 matches
Mail list logo
