Comments on: How to Add Remote IP Addresses to Existing Receive Connectors

By: vadim

vadim — Wed, 02 May 2012 19:02:56 +0000

Ok, thanks. Will try. In the past I had some troubles of getting the properly formatted text file to be used with Win PowerShell for input. Maybe thats how I made it work – putting records in line by line.

By: Paul Cunningham

Paul Cunningham — Wed, 02 May 2012 10:18:41 +0000

Yes, just one IP per line will work.

By: vadim

vadim — Wed, 25 Apr 2012 23:24:52 +0000

Helpful article (and following comments). One question – talking about text file used for importing IPs, what exactly is the format of records in the file? Just type in all IPs row by row, comma delimited, one IP per line? Or else?

By: Joakim

Joakim — Thu, 23 Feb 2012 11:36:18 +0000

Thanks for replying, Yes it can ping the server normally (with hostname and ip address). For the antivirus, I’m not really sure it block the outbound SMTP because it can telnet the old exchange 2003 server as well.
I’ll enable the Protocol Logging on the RC to see if it works.

Thanks again

By: Paul Cunningham

Paul Cunningham — Thu, 23 Feb 2012 11:19:10 +0000

Can you ping the server? Not a simple routing issue?

I’ve seen firewalls (both network and client firewalls) as well as some antivirus products cause problems like that (eg preventing outbound SMTP from the server because it looks like a worm/trojan). So check for those.

What you can also do is enable Protocol Logging on the Receive Connector on the server you’re trying to telnet to, then inspect the protocol logs after trying to make the connection to see whether the traffic is hitting it or not.

By: Joakim

Joakim — Thu, 23 Feb 2012 05:57:18 +0000

Hi,

We migrated from exchange 2003 to 2010. We have many servers and application using the old server, so I had to put one by one the ip address of these application server to the new Relay connector on the new exchange 2010 so they can send email. Every thing is working fine, but only one server could not telnet this relay server. I’ve already add the IP on the list. It can telnet the exchange 2003 not the 2010.
I got the error below
Connecting To mgprelay01…Could not open connection to the host, on port 25: Connect failed

Could you help please?
Thanks

By: Josh

Josh — Fri, 20 Jan 2012 18:01:07 +0000

Excellent Post. Very helpful.
Thank you.

By: Paul Cunningham

Paul Cunningham — Tue, 15 Nov 2011 12:31:18 +0000

It is a “low effort” approach. I’ve permitted entire IP ranges in some cases before, usually for things like desktop apps that need direct SMTP relay but the pc’s are on a DHCP range without reservations (reservations might sound like a logical solution to that, but they add “yet another thing” to manage and will of course break if the user gets a new pc or logs on to a different one).

I wouldn’t do it on insecure networks, eg wireless where a guy in his car outside the building uses your server to relay spam.

And as long as they aren’t creating an open relay that can be exploited from the internet then it’s probably fine.

By: Holt Satterfield

Holt Satterfield — Tue, 15 Nov 2011 05:58:55 +0000

Hey, Paul –

We just built an Exchange 2010 and migrated all the mailboxes from the old 2003 Exchange box. My integrator says he usually adds ALL the IP addresses (and in our case, all the subnet ranges) into the Relay Connector. This is opposed to just devices that usually send mail — scanners, copiers, accounting/equitrac servers.

What say you about adding all my IP ranges into the Exchange 2010 Relay Connector?
Thanks.

By: Paul Cunningham

Paul Cunningham — Tue, 08 Nov 2011 22:38:18 +0000

Hi Aaron, try this:

http://exchangeserverpro.com/how-to-prevent-truncation-of-long-output-in-exchange-management-shell