SMTP relay part 2 - Thanks chad
First off - thanks for help on the first part of my problem goes to Chad.
The second part of my problem is that as well as accepting email from the friendly IP's I also want to set-up iMS to accept mail for another domain.
This is because we act as a third line backup server for that domain (3rd MX record in domain). So I wish to set-up iMS to receive only email for our own domain or the domain we backup (where we have no local knowledge of their email accounts, we simply would queue it up for them and when their servers came back on line iMS could then forward it on), but to also allow clients from the IP addresses we define as friendly to send email to anyone.
Thanks in advance.
Kind Regards - Steve Harris
[757 byte] By [
709028] at [2007-11-25 7:09:38]
Your welcome, gald I could help.
As for your second question, this also is straight forward, okay for those that have been with this MTA for almost 10 years. ;-)
Here's what you need to do create a new channel, say tcp_relay. Something like
tcp_relay smtp mx single_sys remotehost inner switchchannel identnonelimited \
subdirs 20 maxjobs 7 pool SMTP_POOL
tcp-relay
Then in the rewrite rule section you need to add rewrite rules to direct mail for this domain to this new channel you created. For example you are going to relay mail for sun.com and eng.sun.com. Here's the rewrite rules you would need to add
sun.com$U%$D@tcp-relay
eng.sun.com$U%$D@tcp-relay
or if you wanted to handle all domains under sun.com you'd do
.sun.com$U%$H$D@tcp-relay
The anti-relay rules use the orig_send_access mapping, which basically says coming in channel tcp_local and going out channel tcp_local is relaying and not allowed, unless coming from an address listed in INTERNAL_IP mapping.
By creating this new channel and puting the rewrite rules in place you've changed the channels and made it arriving via tcp_local and leaving via tcp_relay and thus not stopped by orig_send_access mapping.
708686 at 2007-6-29 17:41:22 >
