Marc Silver: > Hi guys, > > I have two (probably) very simple questions for you Postfix gurus. > > Firstly, I was wondering if there's a Postfix equivalent of the 'exim -bt > <address>' command in Exim?
Postfix mail delivery daemons can report the result of one attempt to deliver mail (without actually delivering mail) with "sendmail -bv". See http://www.postfix.org/ADDRESS_REWRITING_README.html for an example at the bottom. However, this does not give information about *why* Postfix is trying to deliver mail to that particular machine, or what other systems it would try when a particular machine is not available. > This command shows the specific route that > the MTA would use to deliver the message for the given recipient. An > example of the output can be seen below: > > [EMAIL PROTECTED] exim]# exim -bt [EMAIL PROTECTED] > [EMAIL PROTECTED] > router = dnslookup, transport = remote_smtp > host smtp3.google.com [64.233.183.25] MX=10 > host smtp4.google.com [72.14.221.25] MX=10 > host smtp2.google.com [64.233.167.25] MX=10 > host smtp1.google.com [209.85.237.25] MX=10 The SMTP client could be modified to append MX expansion information to the "sendmail -bv" report. Right now, MX hosts are logged to the maillog file until delivery succeeds. There currently is no other mechanism to get information from a Postfix daemon process besides "sendmail -v", "sendmail -bv", logfile records, or invasive debugging. > [EMAIL PROTECTED] exim]# exim -bt [EMAIL PROTECTED] > [EMAIL PROTECTED] > router = forcepath, transport = remote_smtp > host 172.24.125.11 [172.24.125.11] The queue manager could be modified to append (transport, nexthop) information to the "sendmail -bv" report. Right now, such information is logged only in case of errors. There currently is no other mechanism to get information from a Postfix daemon process besides the ones mentioned earlier. > Secondly, is there a way to specify multiple hosts in a transport_map? > Ie, can I have mail send to one host and/or balance/failover to another if > the primary host is unavailable? No. Postfix concurrency scheduling is based on the nexthop destination name, so the nexthop must not specify multiple destinations. However, the Postfix SMTP client supports a smtp_fallback_relay which solves the most common problem. Postfix without concurrency scheduling would overwhelm remote hosts by making up to 100 simultaneous connections to them. Wietse
