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

Exchange 2010 Relay to external domain fails, mails stock in send queue.

Hi

I have made a new Relay receive connector soo my internal app. server can relay mails trough my Exchange server, this seem to work okay when I relay mail for internal Email adr. when it try to realy mail to external email adr. it leaves the app server okay, but then it stuck in my outgoing send connector on Exchange.

I have an Edge between my internal mail server and the internet and i am using a smarthost.

External mails send from Outlook client work fine. It´s only external mails relayed from app. server which is getting stock at the send connector.
0
Henrik_S_Andersen
Asked:
Henrik_S_Andersen
1 Solution
 
Alan HardistyCo-OwnerCommented:
Did you use the Exchange Management Shell to grant the Receive Connector Relay permissions:

http://technet.microsoft.com/en-us/library/bb232021.aspx

Get-ReceiveConnector "Receive_Connector"| Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"
0
 
Henrik_S_AndersenAuthor Commented:
YEs i did use EMS to grant the recive connector relay permission.

I also tried this setup:

New-ReceiveConnector -Name RelayConnector -usage Custom -Bindings ’x.x.x.x:25' -fqdn server.domain.com -RemoteIPRanges x.x.x.x -server MYEXCHANGESERVER -permissiongroups ExchangeServers -AuthMechanism ‘TLS, ExternalAuthoritative’

Recive connector works okay, i can telnet MYEXCHANGESERVER 25 from my app serveres, and the mail will be send but stock in send connector queue. See attach screendump.

But mails send from outlook clients don´t get stock in send connector queue
telnet.jpg
0
 
Henrik_S_AndersenAuthor Commented:
I get the following error on send connector 451 4.4.0 Primary Target IP address responded 421 4.2.1 unable to connect.

Againg this only happens on mail send to external through the new Relay receiver
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
atuldangiCommented:
Just disable you antivirus software and it should work.
Generally McAfee AV blocks it. You may add MS Exchange server folder found in c:\program file to exclusion list in AV software and also exclude all exchange databases from being scanned.

It will work.
0
 
suriyaehnopCommented:
0
 
PadamdeepCommented:
If messages are stuck on hub then relay connector is fine.
Do you have a specific send connector to send those messages?
If yes, what is the source server on that send connector?

Singh
0
 
Henrik_S_AndersenAuthor Commented:
Strange...

I just deleted the Relay Receiver and created it again with same powershell script restarted transport service, and now it works :)

Microsoft!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
0
 
Henrik_S_AndersenAuthor Commented:
I managed to solve the problem my self
0
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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. 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