- vi /etc/postfix/transport & added the following two lines at the bottom of the file
intranet.com smtp:10.9.9.99
- run 'postmap' to generate the hashed transport:
- vi /etc/postfix/main.cf and commented out the global relay
- reload configuration for the running postfix. Reloading was met with some nonsense error/warnings, so I ended up with a full restart.
- tested it and it didn't work. it seemed that the transport map doesn't exist, since it looked up MX record to find SMTP servers to send mail to.
- It became obvious that main.cf doesn't have reference to use which transport hash at all. so I added the following then restarted POSTFIX. Bingo!
It still made me curious why this is not enabled by default since one needs to consciously insert rules into the transport configuration file as well as to consciously run postmap to generate the hash. This would save me the hassle to figure out it is not there, and save a service outage in production environment should custom transport becomes necessary. The only argument I can find up to now is the security, only if it takes different credentials to modify transport.db and to start use transport.db at first place.
Of course, "crazy" default behavior can be identified on other modern operating systems also. Don't get me started with that Solaris halts if it receives the POWER Fail signal sent by a resetting serial console.
No comments:
Post a Comment