Can't Send or receive external emails in exchange 07
i have just configured a new exchange 07 server i made the neccsary changes to the firewall to allow emails but it wont let me receive them i have pointed my mx record to this new server and i have tried setting up the accepted domains with many differant setting non have workedso iset back to my default domain
September 6th, 2006 3:55pm
What types of errors or NDRs are you getting?
September 14th, 2006 11:54am
Hi Doctorw, In a single-server Exchange 2007 setup you'll need to allow annonymous connections on your default receive connector. By defaultExchange 2007 servers not running the Edge Transport rolewill only accept inbound smtp connections from Exchange Users (clients), Exchange Servers (other Exchange 2007 servers)and Exchange Legacy Servers (legacy Exchange 2003 & below servers). To allow annonymous smtp connections for your server, run the following management shell command: Set-ReceiveConnector -Identity "Default <ServerName>" -PermissionsGroup "AnonymousUsers" As for not being able to send external email, have you configured a Send Connector? This is done through Organizational Configuration->Hub Transport->Send Connectors, or by using the management shell command New-SendConnector. Hope this helps, Rob Costello
September 15th, 2006 8:27am
Thank you so much for the information. This solved my problem. Now my question would be this. At this point in time I have no edge transport server which is why this information helped. In the next couple of days i will be getting a machine setup to function as the edge transport server. So if i want to remove the allow anonymous user so that the edge transport server can function properly how would i go about doing this? Thanks again for the valuable information.
October 27th, 2006 10:27am
Marc & Rob, Thanks for your help. I had the same issue. I installed Windows 2003 R2 and installed Exchange 2007 beta. I could not receive or send any email to outside world. After giving permissions to anonymous users, I can receive emails from external world but looks like I can not still send out emails. I will appreciate your help.
December 25th, 2006 10:25am
You should add a send connector to your Exchange server. In the Exchange Management Console, go to Organization Configuration -> Hub Transport. In the Action Panel choose: "New Send Connector" Go through the Wizard. In the Address Space you have to choose "*" if you want to send email to every domain. Hope this one help
January 18th, 2007 11:48am
I was reading the above as I too am having the same problem. Although when I run the shell cmd I get double arrows and a flashing cusor. Now what???? I am sorry but I am really new to this. any help would be great. Thanks.
February 6th, 2007 2:17pm
Thanks a lot, This was the solution! The external clients are unable to send email to us, they received the following errors like: The mail email@example.com: host 22.214.171.124[126.96.36.199] said: 530 5.7.1 Client was not authenticated (in reply to MAIL FROM command) Once we had anonymouse-fixed, everything went smootly.
April 1st, 2007 2:57pm
Since you have this set to AnonymousUsers, will people be able to use your Exchange server as a pass through (relay) for SPAM? or does this prevent relays from happening.Rick
April 10th, 2007 10:51am
if you did not get it figured out try this: the double arrows indicate the command is not compete as far as I can tell and is awaiting further input [MSH] C:\>Set-ReceiveConnector -Identity "<name of receive connector>" -PermissionGroups AnonymousUsers you can get the name of the receive connector from the properties of it from the gui hope this helps, there is a good example if you use the help fil-- search for set-receiveconnector
April 16th, 2007 8:42pm
fyi this is the onlysyntax that worked for me... Set-ReceiveConnector -Identity main\default* -PermissionGroups "AnonymousUsers"
April 17th, 2007 11:59pm
I've got some issues with this approach. I've done what is mentioned here, and I'm now relaying mail for someone. I did the anonyomous on the receive connector first, and I noticed my queues were filling up. So I did the send connector and the mail out left. I disabled the send connector and again the queue starts filling up. All the relayed mail is from user <> in the queue. At abuse.net the script didn't get through the first 5 tests, but the 6th was a maybe. Someone is defianlty using this test server to relay through. What could I be missing? We've kept the send connector disabled and just delete the emails because we know that they are not ours.
April 19th, 2007 1:00pm
Thanks solved my problem
June 7th, 2007 9:51am
I agree if you set it to anonymous, your server will become a relay agent. I tested this using telnet and my exchange 2007 server accepted the mail from: adddress from any email address i put in there. Does anyone know a soulution to this??
July 5th, 2007 4:23pm
Does anyone know the answer to this? I am very interested in the response to see if there is any way once changing this setting can you STOP the open relay. That would kind of defeat the purpose dont you think? Any helpful reply to this would be greatly appreciated. Cheers Ross
November 6th, 2007 3:20pm
Hello, I don't have your response but i think that you can usethis workaround : Active the Antispam agent, on this one you can configure : The Recipient filtering with the "Block messages sent to recipients not listed inthe GAL" => it's good but it's send a NDR message to sender. You can use the senders filtering too : "Block messages from the following senders" in fact, it's impossible too receive an email from internet that have your dns domain. And "Block the messages from blank senders too" And you can use the Content filtering too, and configure the rate of SCL that you want to use, i preconize you to test this level with the quarantaine mailbox to adjust like you want and limit the falsepositve mails. I hope that it help you, Cordialy,
November 22nd, 2007 10:47am
Accepting email from any address doesn't make you a spam relay. However, letting people send to any email address via your server does. That's why you have to restrict what domains your server accepts mail for in Organization Configuration -> Hub Transport -> Accepted Domains.IceColdEuro
November 25th, 2007 8:21am
My situation is different, yet same error...cannot send to outside world. Using an external SMTP server andEdge Server. I send email out to the edge server and then out to the smtp server. I want connections and access secured all the way to the SMTP server sinceit is internal. How do I setup? I followed Microsoft'sinstructions...doesn't work.
November 25th, 2007 10:51am
Good day Naugtyboy119,Thanks for your help...Just follow your advice...and walla....I can receive and send email...to and from the internet...Thanks again...
March 10th, 2008 4:22am
Great posts and advice.. This fixed my issue! Rock on
April 4th, 2008 11:00am
you can restrict the receive connector by IP address. default is all IP's. Incidentally, I've added anonymous, but still get 5.7.1 client was not authenticated
July 9th, 2008 9:25am
Hi everyone. Thanks for all this great information, it has been very helpful. Whenever I try to implement the command "Set-ReceiveConnector -Identity "Default <ServerName> -PermissionGroups "AnonymousUsers"" I get the default object does not exist. I tried to use the command "New-ReceiveConnector -Name Default" to create a new receive connector with default bindings (0.0.0.0:25) and ip address range (0.0.0.0-255.255.255.255). I am not sure why this is occuring, as I believe I am following all the directions above correctly. If anyone has any suggestiongs, they are appreciated.
July 28th, 2008 4:23pm
In your recieve connectors, check the port for the connectors. By Default, mst has port 587. You can change that to Port 110 which is the typcial default ports for email recieving.--Chad
August 21st, 2008 2:55pm
Uh....no. You receive (and send) email on port 25 if one is running a mail server (as opposed to a mail client, which *might* receive mail on port 110) Instead of messing with the default receive connector, just createa new one, and allow anonymous,use port 25. (This doesn't mean that Exchange will be an open relay, as it will acept mail only for "accepted domains", set elsewhere)
October 14th, 2008 8:36pm
Hi Doctorw, In a single-server Exchange 2007 setup you'll need to allow annonymous connections on your default receive connector. By default Exchange 2007 servers not running the Edge Transport role will only accept inbound smtp connections from Exchange Users (clients), Exchange Servers (other Exchange 2007 servers) and Exchange Legacy Servers (legacy Exchange 2003 & below servers). To allow annonymous smtp connections for your server, run the following management shell command: Set-ReceiveConnector -Identity "Default <ServerName>" -PermissionsGroup "AnonymousUsers" As for not being able to send external email, have you configured a Send Connector? This is done through Organizational Configuration->Hub Transport->Send Connectors, or by using the management shell command New-SendConnector. Hope this helps, Rob Costello
May 15th, 2010 12:15pm
Rob, you have a small syntax error: The command should read: Set-ReceiveConnector -Identity "Default <ServerName>" -PermissionGroups "AnonymousUsers" ( PermissionsGroup --> PermissionGroups ) Marc
May 15th, 2010 12:15pm
Hi All, Thanks for the above info, tried the above but my exchange server 2007 in server 2003 sp2 isnt allowing me to send or receive emails to the external world, i can only send an receive emails locally. Recently our company has changed the domain hosting company from yahoo to another, this problem arrived then. Can you please help me out with this? azmath
January 11th, 2012 8:42am