Exchange 2007 SP1 on Windows 2003 R2 x64 fully patched as of today. I wanted to create a new receive connector that allowed relaying from a couple of IP addresses in my office so that application servers could bounce mail out to the Internet using the new Exchange 2007 server. To do this I ran the following command as recommended from several tech docs: [PS] C:\Documents and Settings\userid>New-ReceiveConnector -Name newrelay -Usage Custom -AuthMechanism ExternalAuthoritative -PermissionGroups ExchangeServers -Bindings myexchangeserveriport -RemoteIpRanges ip_of_server_to_allow Then I ran this command: [PS] C:\Documents and Settings\userid>New-ReceiveConnector -Namenewrelay -Usage Custom -AuthMechanism ExternalAuthoritative -PermissionGroups ExchangeServers -Bindings myexchangeserveriport -RemoteIpRanges ip_of_server_to_allow Running a telnet myexchangeserver 25 from the server I had allowed above showed that this was working fine, it would allow relay from this IP. The problem came up that I wanted to add more IP addresses to this, and since I didn't know the clumsy powershell command to do this I went into the Exchange Management Console - Server Config - Hub Transport - Receive connectors - newrelay and added the IPs of the other servers to this list. Should work, right? But it doesn't. It continues to only allow the original IP mentioned in the PS command above to relay, the rest continued to get "unable to relay" messages when attempting to telnet to the exchange server from those IP addresses. I ended up creating one connector for each server to get around this. I'm sure there is a command that would allow it in powershell say -RemoteIpRanges 192.168.1.100-103 but the bug I'm seeing is that it appears that it ignores what is put into the graphical utility. I attempted disabling/enabling the connector without much luck. It just seems to ignore the rest of the IPs I put in the EMC. Thanks -Rob P.S. Setting up relays was rather simple in Exchange 2003. Please bring this back to GUI to Exchange 2007. I like powershell and think its rather powerful, but its also like be 12 again and having DOS 2.0 tell me "Syntax" error every step of the way.

Rob,It is possible to creat if via the GUI:start EMCServer ConfigurationHUB TransportIn the right menu select new receive connector and follow the wizard.Besides adding the IP's seperatly you can also add a complete IP-range, the last option I won'te recommend.Johan

Oh I know you can create it with EMC, but my point in two-fold 1) You can't set the full relay allow permissions in the EMC. 2) Once you create it with powershell, you can add more IP's in the EMC but it doesn't allow relay for them. Seems to ignore em. That looks like a bug, anyone else seeing this? Thanks _Rob