Link to home
Start Free TrialLog in
Avatar of topprops
toppropsFlag for United States of America

asked on

Setting up exchange 2010 on sbs 2011

I have setup sbs 2011. and Dell pro help has confirmed that it is setup correctly.  server software found an error by running check network wizard and fixed it.  Port mapping for sending email hadn't been setup.  I don't know why that is or how to check for that.

I have static ip address and have setup a record pointing to the ip address of my router and port forwarded port 25 to local ip address.  I have had at&t create reverse ip address for the public ip address of my router.

My server name is exchange.  the domain is samuelscompany.com.  The local domain is samuelscompany.local.  

The work stations connect to the exchange server.  Email goes and comes from the server.  I haven't changed the mx record yet, still letting old hosted exchange server function.

But I thought that I should be able to send email out.  I have tried, but the email never gets to its destination.

Are there any clues here as to what I have done wrong.

Or do I have to wait until I change the mx record?

thanks
SOLUTION
Avatar of Elmar Koschka
Elmar Koschka
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of topprops

ASKER

yes ran connet internet without errors
is there some where to look on server for error messages about outgoing email.  or a way to test smtp sending.
via telnet:

telnet mailserver 25

HowTo: http://support.microsoft.com/kb/153119
I can telnet into server from local computer.

I have used mxtoolbox.com to test server.  I get the following response.

220 remote.samuelscompany.local Microsoft ESMTP MAIL Service ready at Thu, 15 Mar 2012 09:20:14 -0700
 OK - 76.209.185.251 resolves to exchange.samuelscompany.com
 Warning - Reverse DNS does not match SMTP Banner
 Supports TLS.
 0 seconds - Good on Connection time
 Not an open relay.
 5.304 seconds - Warning on Transaction time

this is a test on my public ip address since I haven't changed mx record yet


but I get connect failed if I telnet from my home computer  could not open connection to the host on port 25
telnet 76.209.185.251 25
If you have your MX records set to talk to Hosted Exchange, there's a good chance that the email from your server is getting blocked by reverse DNS spam filters. One common spam filtering technique is to run a reverse DNS lookup on the email address domain and see if the sending server matches that domain. If it doesn't, the mail is often dropped.
I set up reverse dns with at&t.  but the banner doesn't match what ever that means.  see response from mxtoolbox above
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
yes send connector set to use dns.  

mail is still not getting to recipient.

and I setup exchange.samuelscompany.com in receive connector

I can telnet in from computers outside office.  just not my home computer.
I'm trying to send email to my home computer but my mail server is in england somewhere
I think it is a dns problem.  but I can get to websites so I dns must be working just not for email sending
I still get warning about reverse lookup smtp banner not matching
I think it's your reverse DNS.   Many organizations will not accept email from you if it is not set up properly.

Try setting up a SmartHost using an account on your ISP.   This will fix the reverse DNS issue.


You'll do it from the same Window where you're telling the computer to use DNS.
If your server isn't authorized to send mail and/or doesn't have an MX record defined, the receiving mail server (whoever runs that) may have decided to ignore your message/treat it as spam since it appears to be coming from a fake source.  Create an MX record for your server with a higher priority (with MX records, the lowest number is the "primary" server) and adjust your SPF record if you have one (and if you don't look into creating one).  And try sending to other accounts on different mail systems - example, if you've been testing with your gmail account, ask a neighbor (business) with their own server if you can send them a message.  Try Yahoo, Hotmail, or another provider.  They don't ALL use the same rules... but as it is, messages you're sending from the server probably look suspicious until you completely configure it to be your mail server.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
because I solved problem with help of Dell pro support rather than the advice here.  though the advice here was also helpful.