'transport_maps' getting ignored?

11 msg	(noob-newbie here) Configuring postfix to be us...
5 msg	(No Subject)
3 msg	When is 'for <recipient>'present in header?
2 msg	client does not detect mail
11 msg	Empty MAIL FROM
3 msg	Change format of emails in active directory
3 msg	Logging a message from within a restriction list
4 msg	mailbox_transport_maps lookup key
10 msg	mailbox_transport_maps problem
5 msg	Default value of unknown_address_reject_code
9 msg	Issue with using LDAP for transport maps
4 msg	limit max. used bandwith?
2 msg	maximum number of smtpd_restriction_classes

'transport_maps' getting ignored?
\ Daniel Maher (13 Apr 2007)
. \ Noel Jones (13 Apr 2007)
. . \ Daniel Maher (13 Apr 2007)
. . . \ (Wietse Venema) (13 Apr 2007)
. \ mouss (13 Apr 2007)

3 msg	Server configuration problem
6 msg	smtpd_sasl_auth_enable is true, but SASL suppor...
3 msg	Mail to local domains
2 msg	nonexistent virtual account received
13 msg	How to make postfix use one IP for receiving an...
3 msg	ldap search fails

Subject:	'transport_maps' getting ignored?
Group:	Postfix-users
From:	Daniel Maher
Date:	13 Apr 2007

Hello,

I am using Postfix 2.0.x (yes, I know) on a border mail server, which is configured to relay mail to an internal Exchange server. Normally, incoming mail is tested against the hash defined by relay_domains, as well as the hash defined by relay_recipient_maps, before being sent to the host defined by relayhost.

Now that the Postfix primer is done (heh), the problem: one of the domains that my border mail server accepts mail for would like to use their own mail server (i.e. not the one defined by relayhost). My first instinct was simple: set up a transport hash. In my 2.2.x (yes, I know) test environment, I did the following:

"/etc/postfix/main.cf"
...
transport_maps = hash:/etc/postfix/transport
...

"/etc/postfix/transport"
other.domain.com relay:[987.65.43.21]
# I realise the brackets may not be necessary...

I postmap'd the transport file, then restarted postfix (note that the domain already exists in relay_domains, so no changes were made there). I sent a couple of emails through the test environment, and the transport function worked flawlessly.

Unfortunately, when I replicated these exact steps on my 2.0.x production servers, the behaviour did not replicate as well. Instead, mail destined for "other.domain.com" continued to be sent to the relayhost, instead of the one defined in the transport file.

It would, at first glance, appear as though the transport table is being ignored entirely. I'm not sure what direction to take in terms of further diagnosis, so any insight that the list might be able to provide would be more than welcome. I am happy to post any sort of (sanitised) postconf outputs, and the like, upon request.

Thank you.

--
_
°v° Daniel Maher
/(_)\ Administrateur Système Unix
^ ^ Unix System Administrator

"How can a man choose between Fresh and Fly? And believe me, there IS a difference." - Crack Stuntman, 2007.