It's a unicode string. Rangeupper isn't that important. Without checking, I think you get 16,384 unicode characters, less a bit of overhead.
The number you can get is dependent on how you have them stored. For example, 192.168.1.1-192.168.1.254 takes more bytes to store than 192.168.1.0/24. So.... Probably 600 - 1,200. Depending. I would seriously question why the heck you need that many RELAY IP addresses. It seems excessive. You have that many archaic devices that cannot authenticate? From: [email protected] [mailto:[email protected]] On Behalf Of Adam Farage Sent: Sunday, December 7, 2014 4:30 PM To: [email protected] Subject: [Exchange] Maximum amount of entries in a Receive Connector (for relay)? Environment: Exchange 2010 SP3UR5, two AD sites with split roles all over the place So.. I inherited a pretty solid environment minus the Receive connector we are using for SMTP Relay. Within the Remote IP Ranges (allowed to relay) there are a TON of addresses, and yesterday we ran into an issue where we would add an address and three minutes later it would drop. Knowing the attribute has some type of rangeUpper assigned to it, I thought we hit the maximum so I consolidated the list down a bit and pow, it worked. Now, I guess the question is what is the maximum number of IP addresses that can go into the attribute ms-Exchange-Smtp-Receive-Remote-IP-Ranges? If I look at the attribute both in Production and Lab (Lab is fully up to date) it shows the same rangeUpper as 200, but I know this is impossible since we have to have at least 500+ IP addresses that relay off Exchange. I can pull a list later to confirm. Any ideas? I am stumped, as I know this is a limitation due to the rangeUpper but that value doesn't make much sense. [cid:[email protected]] Thanks! Adam F
