Getting Exchange 2007 to work with SBC Yahoo DSL
Update: Beginning yesterday, November 14, 2008, the smtpauth.sbcglobal.net email relay servers began NDRing emails sent from AT&T customers. Again, this information was not passed on to its customers.
I've updated the instructions below to use the smtp.att.yahoo.com servers, which are now accepting authenticated connections.
First, let me say that SBC Yahoo is less than helpful on any assistance with configuring Exchange (any version) to work with their SMTP gateways. Really, I can't blame them too much because of the potential to hammering of their systems with large quantities of email from businesses using a "home"level of service.
In any event, here's how to configure Exchange 2007 with Edge services to send email through SBC Yahoo's email servers.
Configure the outbound Send Connector
- Logon to the server hosting the Hub Transport role
- Open the Exchange Management Console (EMC)
- Expand Microsoft Exchange\Organization Configuration\Hub Transport
- Click the Send Connectors tab
- Double-click your outbound SMTP connector to open its properties. Mine is named "EdgeSync - expta to the Internet"
- Click the Network tab
- Select "Route email through the following smart hosts" and click the Add button
- Select "Fully qualified domain name (FQDN)" and enter smtp.att.yahoo.com as the smart host. Click OK
- Select Basic Authentication (do not check Basic Authentication over TLS)
- Enter your SBC username (i.e., username@pacbell.net) and SBC password. Click OK
Configure the Edge server to use port 587
- Yes, yes, I know that SBC's documentation says SSL port 469, but trust me, it's 587...
- On the Hub Transport server, open the Exchange Management Shell (EMS)
- Type Get-SendConnectors and make note of the name of the send connector you just configured. Again, mine is "EdgeSync - expta to the Internet"
- Type Set-SendConnector "EdgeSync - expta to the Internet" -port 587 to change the port. Obviously, change the name in quotes to the name of your Send Connector.
- Type Start-EdgeSynchronization to force a sync with the Edge server
Force the Send Connetor to Retry
- Open EMC on the Edge server and click Toolbox
- Double-click Queue Viewer
- On the Queues tab, select the outbound SMTP queue and click the Retry action
Notes: TLS is not the same thing as SSL. TLS creates a secure connection between servers, while SSL creates a secure connection between a client and a server. TLS is capable of reverting back to SSL 3.0 if TLS doesn't work, but this is not an RFC requirement. At the time of this writing, Microsoft's implementation of TLS does not revert to TLS.
You should also register your external email address with SBC Yahoo's email system. This will ensure that email from your external account won't be NDR'd back to you when you send it. See http://help.yahoo.com/l/us/yahoo/mail/original/manage/sendfrom-07.html
Labels: Edge, Microsoft Exchange 2007, s, tip, troubleshooting
Subscribe to my feed
posted by Jeff @ 2:48 PM
9 Comments
Links to this post
9 Comments:
You solved my problem. Thanks and great post!
This has been brilliantly helpful. I'm on ATT Connecticut, and this info enabled me to work around the new problem. It's much appreciated!!!
This ATT thing is a load of crap!!! What are all the people of the SBS 2003 community suppose to do with their smarthosts until SBS 2008 is released??? Carriers such as TDS, Charter, or Comcast are not making this mandatory yet.
If I Have Exchange 2007 setup on a single server (not recommended I know) would any of these steps change? For example, I do not have the edge transport role installed.
Thanks again for the very informative post. It applies directly to what I am attempting to accomplish which is connect an exchange07 server to the internet and send mail with it.
These instructions should work fine even if you don't have an Edge server. BTW, it is totally supported to have all roles installed on the same server.
Thanks very much for this post! Your solution works perfectly, and I can finally send mail through this god-forbidden service provider.
Thanks for this post! I've been using smtpauth.sbcglobal.net as my smarthost for awhile and I haven't seen any NDRs come through. So far, e-mail is being delivered without any trouble. I do have 2 questions about your settings. 1)We don't use an edge server, so when i try to change the port to 587, EMS doesn't recognize the Get-SendConnectors command. 2)Would i have to verify each e-mail address with yahoo or just the one your a logging in with?
Steven, keep an eye out for NDRs. When mine started, about half my email went through, then none. It all happened on one day.
You don't need to use 587 if port 25 works fine for you. Port 25 is used for server-to-server SMTP transport and port 587 is used for client-to-server.
You only need to use one email account to use for authentication, as long as it's valid.
Hi Jeff, thanks for getting back to me. I tried changing our settings to smtp.att.yahoo.com, but every email bounced with a "address not verified" error message. I've verified our email account, but i was still getting that error so i moved back to smtpauth.sbcglobal.net. Hopefully I won't get the NDRs anytime soon. :)
Post a Comment
Thank you for posting a comment! It is my hope that you find the information here useful. Let me know (and others) if this post helped you out or if you have a comment or further information.
Links to this post:
Create a Link
<< Home