Exchange receive connectors
We are running a program that needs to be able to send out emails to various people. I can send emails to people internally but get the error message "550.5.7.1 Unable to Relay." I have set up a receive connector and gave it a local address of the machine that the program is running on, for the remote address I put the address of the server again. Under Authentication I have Transport Layer Security (TLS) checked. Under permission groups I have only anonymous users checked. I also went into the console and type Get-ReceiveConnector "Receive Connector Name" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient" (I filled in the receive connector name) After all of this I still get the error message. I also tried restarting the microsoft edge transport service. Any ideas are welcome.
May 24th, 2010 11:55pm

"Receive Connector Name" is bound to the IP address and port the program is using, right? -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "mbh23" wrote in message news:afbcca9a-f6da-436c-b011-fdde58649c54... We are running a program that needs to be able to send out emails to various people. I can send emails to people internally but get the error message "550.5.7.1 Unable to Relay." I have set up a receive connector and gave it a local address of the machine that the program is running on, for the remote address I put the address of the server again. Under Authentication I have Transport Layer Security (TLS) checked. Under permission groups I have only anonymous users checked. I also went into the console and type Get-ReceiveConnector "Receive Connector Name" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient" (I filled in the receive connector name) After all of this I still get the error message. I also tried restarting the microsoft edge transport service. Any ideas are welcome. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
May 25th, 2010 12:07am

I am not sure what you are saying. The receiver connector is the name you set up when you are creating the connector.
May 25th, 2010 12:18am

The receive connector named "Receive Connector Name" is bound to the IP address and port the program is using, right? -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "mbh23" wrote in message news:7efbedef-f8cd-485d-b236-abc8ce42a3df... I am not sure what you are saying. The receiver connector is the name you set up when you are creating the connector. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
May 25th, 2010 12:21am

Yes it is set up for the IP of the computer that is running the program and the program is set to use port 25.
May 25th, 2010 12:33am

I don't have an answer for you. The command you ran is the way I have done it and looks like it should work. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "mbh23" wrote in message news:c4315d6d-70a6-4125-aaa8-a393150f53e7... Yes it is set up for the IP of the computer that is running the program and the program is set to use port 25. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
May 25th, 2010 1:24am

Hi mbh23, Try to enable 'Externally Secured' Authentication method and see if the issue persists: 1. Right click the receiver connector which you create to receive messages from 3rd application and choose properties. 2. Click Authentication tab, mark the checkbox 'Externally Secured (for example, with IPsec)'. More information: Allowing application servers to relay off Exchange Server 2007 http://msexchangeteam.com/archive/2006/12/28/432013.aspx
May 25th, 2010 10:36am

I have tried that as well along with basic windows authentication and then putting the admin in the program but nothing seems to work. I have had this same problem in the past trying to set a multifunction printer to email to the outside world and never got that to work either. Any other ideas?
Free Windows Admin Tool Kit Click here and download it now
May 25th, 2010 3:07pm

Try following: Get-ReceiveConnector "Receive Connector Name" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Sender" Get-ReceiveConnector "Receive Connector Name" | Add-ADPermission -User "NT AUTHORITY\Authenticated Users" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Sender" Get-ReceiveConnector "Receive Connector Name" | Add-ADPermission -User "NT AUTHORITY\Authenticated Users" -ExtendedRights "ms-Exch-SMTP-Accept-Authoritative-Domain-Sender"
May 25th, 2010 5:28pm

Still getting the same message.........Matt
Free Windows Admin Tool Kit Click here and download it now
May 25th, 2010 5:57pm

Hello mbh23, => Please Create a new Relay Connector for Application Relay à General --> Verbose Network --> IP address ---> Add IP of Application server's Permission Groups --> Exchange Server & Anonymous users Authentication --> Transport Layer security (TLS) & Externally Secured After that u can check the application relay. Still if not work then u can run command:-- Get-ReceiveConnector "Receive Connector Name" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient" => Also go through the Article : -- Allowing application servers to relay off Exchange Server 2007 http://msexchangeteam.com/archive/2006/12/28/432013.aspx This will fix the problem. MicroSoft Exchange Admin. & Connector EXCHANGE2010, MCSE, MCTS, MCSA MESSAGING, CCNA & GNIIT
June 3rd, 2010 12:48am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics