• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 731
  • Last Modified:

What is "My Internet ReceiveConnector" named?

Exchange 2007, Two Servers:

1 on domain running Mailbox, Hub Transport, Client Access, Unified Messaging

1 not on domain running Edge

I'm trying to prevent spoof emails from my own domain.

I can't get the following command to accept:

Get-ReceiveConnector “My Internet ReceiveConnector” | Get-ADPermission -user “NT AUTHORITY\Anonymous Logon” | where {$_.ExtendedRights -like “ms-exch-smtp-accept-authoritative-domain-sender”} | Remove-ADPermission

It keeps telling me:
Get-ReceiveConnector : The operation could not be performed because object 'My Internet ReceiveConnector' could not be found on domain controller 'localhost'.

Should I be typing "My Internet ReceiveConnector" or should that be replaced with a computer or domain name? I've tried replacing it but can't get anything to accept.

I tried this from both servers' Shells, assuming it should be done on Edge.

Let's say my computer name is abc-edge (full computer name: abc-edge.abc.org)
1 Solution
“My Internet ReceiveConnector” looks like a placeholder in whatever article you read. Just type Get-ReceiveConnector on its own to see the names of your connectors.
MikeAlbertsAuthor Commented:

Get-ReceiveConnector game me the "Identity" which I replaced in the "My Internet ReceiveConnector" placeholder.

Mine was actually:
"abc-edge\Default internal receive connector ABC-EDGE"
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now