Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Finding domain within Send Connectors

Posted on 2011-03-08
4
Medium Priority
?
247 Views
Last Modified: 2012-05-11
Running Exchange 2007 SP2.

We have multiple Send Connectors to partner companies or those we have merged with, about twenty Send Connectors in all.

I know how to view the Properties of a Send Connector (SC) and see which domains it is configured for, but is there a way to find out which Send Connector is being used for a specific domain? For example. say I wanted to find out which SC was used for partner1.com, is there a way apart from going through each SC until I saw partner1.com listed within its Address Space?
0
Comment
Question by:bruce_77
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 12

Expert Comment

by:Nenadic
ID: 35074360
Something like should produce results:
Get-SendConnector -list | where {$_.addressspace "partner1.com"}
0
 
LVL 12

Expert Comment

by:Nenadic
ID: 35074373
Apologies, missed an argument:
Get-SendConnector -list | where {$_.addressspace -match "partner1.com"}
0
 
LVL 2

Author Comment

by:bruce_77
ID: 35074529
Hi

Thanks for that!

My apologies, but I should have clarified the question better.

I'm actually looking for the Send Connector that routes mail to emea.partner1.com

I guess I could use Get-SendConnector -list | where {$_.addressspace -match "partner1.com"} if EMEA.PARTNER1.COM was explicitly listed, but what if there was a Send Connector for the *.partner1.com namespace? Apart from trying:

Get-SendConnector -list | where {$_.addressspace -match "emea.partner1.com"}

checking to see for results, and if not running what?
0
 
LVL 12

Accepted Solution

by:
Nenadic earned 2000 total points
ID: 35074598
-match "partner1.com" should match partner1.com,, emea.partner1.com and *.partner1.com. I'm not near an Exchange Server to double-check the argument, though, so it may require correction tomorrow morning, unless you can try it in the meantime.

Basically, the matching process is the same as for the selection of the connector when there are multiple connectors that could be used.  It starts from right and matches characters.  The one with most matched characters would be used.

E.g.:
- Conn1: *.partner1.com
- Conn2: *
- Conn3: emea.partner1.com

If you're sending an email to user@emea.partner1.com, all three are valid, but Conn3 would be used as it matches the most characters to the address.
(I apologies if this is a bit off topic, perhaps, or if this is something you already know)
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
how to add IIS SMTP to handle application/Scanner relays into office 365.

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question