I'll be the first to admit that I can be a total nub at times - which is why when I recently migrated a network and introduced a new exchange server I ran into a small problem.
On the previous server, clients were able to send email from their bespoke software directly to the server but they couldn't do this anymore.
I checked all the settings on the receive connectors and everything seemed fine - eventually I tracked the problem down to a power-shell command that needs to be run on the receive connector in question (thank you http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/managing-relay-connectors-exchange-server-2007-2010-part2.html)
Get-ReceiveConnector <RelayName> | Add-ADPermission –User “NT Authority\Anonymous Logon” –ExtendedRights ms-Exch-SMTP-Accept-Any-Recipient,ms-exch-bypass-anti-spam
As a heads up, if you try and copy and paste the command off the website mentioned above there's a typo in it which will throw an error (look closely and there is a space between smtp- accept- which needs removing)
Back on track - I should now be able to send a mail.. but no, still coming up with unable to relay.
Eventually I read the most useful advice that I've EVER read when dealing with receive connectors..
Change the FQDN that the receive connector provides in response to HELO commands
Why so useful? Well, you can instantly see which connector you are connecting to and find out where the problem lies. Immediately, I could see that I was connecting to a default connector which has no purpose. So I disabled it and tried again - BOOM
And that is why i'm a nub.. it's so obvious and so brilliant!
PS. don't forget to restart the transport service when you make changes :)
On the previous server, clients were able to send email from their bespoke software directly to the server but they couldn't do this anymore.
I checked all the settings on the receive connectors and everything seemed fine - eventually I tracked the problem down to a power-shell command that needs to be run on the receive connector in question (thank you http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/managing-relay-connectors-exchange-server-2007-2010-part2.html)
Get-ReceiveConnector <RelayName> | Add-ADPermission –User “NT Authority\Anonymous Logon” –ExtendedRights ms-Exch-SMTP-Accept-Any-Recipient,ms-exch-bypass-anti-spam
As a heads up, if you try and copy and paste the command off the website mentioned above there's a typo in it which will throw an error (look closely and there is a space between smtp- accept- which needs removing)
Back on track - I should now be able to send a mail.. but no, still coming up with unable to relay.
Eventually I read the most useful advice that I've EVER read when dealing with receive connectors..
Change the FQDN that the receive connector provides in response to HELO commands
Why so useful? Well, you can instantly see which connector you are connecting to and find out where the problem lies. Immediately, I could see that I was connecting to a default connector which has no purpose. So I disabled it and tried again - BOOM
And that is why i'm a nub.. it's so obvious and so brilliant!
PS. don't forget to restart the transport service when you make changes :)
No comments:
Post a Comment