02-04-2015 11:03 PM
Hi All,
I am abit of a greenthumb when it comes to our Ironport appliances, but I have been assigned a task that I am stuck on.
Basically we use Google Apps for our mail, with Ironport being the gateway into our old legacy environment.
I need to get Ironport to redirect any email it receives for a specific recipient (a@example.com) to a specific host (n.example.com) on Port 25000 specifically.
The host is listening on that port for the incoming connection rather than port 25.
I have created an SMTP route on our Ironport appliance for n.example.com with its IP and also specified port 25000.
I have also added the domain example.com to the RAT on our appliance.
Basically the mail gets to the Ironport appliance, but then its queued for delivery until it eventually expires. I am not sure what else I can try to get this working so any advice is appreciated.
Sorry for the trouble
Ash
Solved! Go to Solution.
02-05-2015 09:58 PM
Hi matt
Default interface is indeed set to Auto. I do know that the appliance delivers mail perfectly fine for the other domains we have hosted on it.
Telnet failed too, timed out with an "Unable to connect to remote host" message.
So I should take that info to the network team and also the guys administering the target server to recheck their app is definitely awake on port 25000?
Ash
02-05-2015 09:59 PM
Yep that is the plan i would suggest.
Check with network guys and see if there is availability to connect to the host and also check the destination host itself and see if it's listening on the port and allowing
02-05-2015 10:01 PM
Will do, and I will update the case when I hear back from them.
Thanks very much for the excellent support and advice, I really appreciate it.
Ash
02-05-2015 10:03 PM
Happy to help :)
Keep us updated if possible.
02-08-2015 06:57 PM
Hi Matt
Looks like there are indeed connectivity issues for the appliances other interface IP's at the firewall.
Getting them resolved and then hopefully will work. will update again when I the rules are in place.
Ash
02-08-2015 06:59 PM
Hope it does get resolved for you ash :)
02-11-2015 05:37 PM
All working now thanks Matt & Jens!
The 2 missing firewall rules did the trick. Thanks very much again!
Ash
02-11-2015 05:38 PM
That is awesome ! :D
Good stuff, happy to hear it's working for you Ash.
Have a good day.
- matty
02-12-2015 05:52 PM
Hi Matt
Was wondering if I could run another routing scenario past you? Is this the place to do that or should I start a new one?
Ash
02-12-2015 06:01 PM
Happy to answer here.
02-12-2015 06:04 PM
:D thanks
Ok so we are in the process of migrating a bunch of servers to a new DC.
I have been asked to route mail differently for this set group of servers while during the migration.
Basically they only want the servers to be able to send to our domain only, or even a single specified address (whichever is simpler).
Once they are migrated they will revert that so they relay to anyone as normal.
Short of me creating a content filter for every server IP, I thought their must be a more efficient solution? Maybe another relay policy? Its above my (low) skill level.
Any ideas?
Ash
02-12-2015 06:44 PM
Hey Ash
Sorry for the delay in response, a bit occupied with some things here on my end.
Um for this requirement this is my assumption from what i've read.
Your IronPort needs to allow only a certain set of IPs to allow to be relayed through it, and to only be able to send to an individual domain/sender as welel.
So this set of IPs is very restricted to sending emails through the IronPort only to 1 address/domain
Keep in mind, if you set them to "RELAY" action then they will ignore recipient validation (RAT table) and be treated as outbound email, if this is fine just simply make a new sendergroup and make it use the RELAY mail flow policy, else if you want it to be treated as inbound, use the ACCEPT policy
For this setup i recommend (for easiest setup) use of Sendergroup + 1 message filter.
Create a new sendergroup
Name it a meaningful name, for this example i'll call it "Allowed_IP"
order it '1' or the top or so
Add the set of IPs that will match this sendergroup (rather than others).
Submit this sendergroup.
Commit changes.
Then go to CLI and create a message filter.,
CLI > filters > new
Filter syntax, you can copy and paste or re-type.
Allowed_IP_Restrict:
if (sendergroup =="Allowed_IP") AND (rcpt-to !="@domain.com")
{
drop();
}
.
Then press enter twice and commit changes.
What this does is, the restricted IPs will match this Allow_IP sendergroup
This message filter will take action where if the IPs match this sendergroup but is not sending to this allowed domain, it will be dropped.
If it is the allowed domain, it'll ignore this filter.
02-12-2015 09:08 PM
Worked perfectly thanks Matt!
Saved me a horribly inefficient solution and taught me something very useful. Thanks very much for your help and time.
Ash
02-12-2015 09:10 PM
:D
Happy to help!
Glad to hear my solution worked to your requirements.
It's all good, here to help and also we're all here to learn as well -- i myself am learning off other users here.
Don't hesitate to start up new threads with any questions (hopefully some i can answer as well :))
03-19-2015 05:01 PM
Hello again Matt :D
Just a quick question related to your previous advice and help.
I need to make changes to the filter you wrote for me, but also to another one, but I am not sure how to edit an existing filter through the CLI. Can you tell me how to do that?
Basically what I want to achieve is that the filter you gave me needs to drop all email that is not addressed to a domain or a specific email address. I wasnt sure on the format.
This is what we started with from you(which works perfectly for the domain):
Allowed_IP_Restrict:
if (sendergroup =="Allowed_IP") AND (rcpt-to !="@domain.com")
{
drop();
}
Would this work for the new requirement?
Allowed_IP_Restrict:
if (sendergroup =="Allowed_IP") AND (rcpt-to !=("@domain.com" OR "the_email@gmail.com")
{
drop();
}
The second thing I am looking at doing is modifying the following filter:
if rcpt-to == "address@example\\.com"
{
skip-filters();
Instead I want to specify one or more IP's instead. I wasnt sure if a sender group was the right way to go?
Thanks in advance again for any advice on the above!
Ash
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide