<quote who="Simon Wong">
> Will postfix be better able to handle this sort of problem and cut the
> connection or is it more likely the mail server?
Using postfix to do proxying means you get the benefit of a complete MTA
with queueing and whatnot to handle problems on either end (their server or
your server).
One big disadvantage is that a postfix relay *won't* know the valid users on
your mail server, so will accept and relay everything. That's bad. If you
can suck out the valid users/domains from your 'real' server, you can use
them with relay_recipient_maps.
So, setup summary:
* Add the domain you want to relay for to relay_domains, so mails to it
will be accepted by your postfix server. In main.cf:
relay_domains = pants.org
* Add the domain and destination to your transport map. For example, in
/etc/postfix/transport you would add:
# domain to relay internal machine to relay to
pants.org smtp:[192.168.10.1]
* Ensure that postfix is using your transport map, by adding it to your
transport_maps in main.cf:
transport_maps = hash:/etc/postfix/transport
Done! relay_recipient_maps bits are up to you, but ping if you need a hand.
- Jeff
--
GVADEC 2004: Kristiansand, Norway http://2004.guadec.org/
Is Murphy's Law constitutional?
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
