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, Postfix uses default_transport.
Wietse-
I got this but so it's impossible to do something like that:
main.cf:
transport_maps = hash:/etc/postfix/transport, tcp:[127.0.0.1]:2527
transport:
@domain1.tld smtp:[internal.relay]
@domain2.tld smtp:[external.relay]
master.cf:
127.0.0.1:2527 inet n n n - 0 spawn
user=nobody argv=/etc/postfix/random.rb
random.rb:
#!/usr/bin/env ruby
TRANSPORTS = [ 'smtp1:', 'smtp2:', 'smtp3:' ]
while line = STDIN.readline
puts "200 #{TRANSPORTS[rand(TRANSPORTS.size)]}"
end
If I'll try to send a mail to "x...@domain1.tld" this won't use
smtp:[internal.relay] but one of 'smtp1:', 'smpt2:' or 'smtp3:'
No. x...@domain1.tld matches the first line in /etc/postfix/transport.
You seem terminally confused about how maps are used.
Each map type has specific documentation on how it is queried, but no
map determines WHEN it is queried. You define that in transport_maps.
--
J.
