I can send mail out of SBS exchange but can not receive

Posted on 2008-11-03
Medium Priority
Last Modified: 2012-05-05
After resetting our SBC netopia router and not making ANY other changes to exchange or any other piece of infrastucture I am able to send email (internally and externally)l out of my SBS Exchange server but, am not able to receive any incoming external mail from any domain.

All the port forwarding on the "firewall" has remained unchanged.

Here is output from checkdns.com:
  Domain farmerinsurance.com has only one mail-server
  Checking mail server (PRI=10) mail.global.frontbridge.com []
  Mail server mail.global.frontbridge.com[] answers on port 25
  <<< 220 mail94-wa4.bigfish.com ESMTP Postfix EGGS and Butter
  >>> HELO www.checkdns.net
  <<< 250 mail94-wa4.bigfish.com
  >>> MAIL FROM: <dnscheck@uniplace.com>
  <<< 250 Ok
  >>> RCPT TO: <postmaster@farmerinsurance.com>
  <<< 250 Ok
  >>> QUIT
  Mail server mail.global.frontbridge.com [] accepts mail for farmerinsurance.com
  All MX are configured properly  

mail.farmerinsurance.com resolves to which is the netopia.

I know that mail is forwarded to a 3rd party frontbridge spam filter... I'm assuming that mail is forwarded to

I'm sure that it's something super simple...

Alil help please...
Question by:fortress11
  • 2

Accepted Solution

mickinoz2005 earned 400 total points
ID: 22872748
I would suggest logging into your frontbridge accoutn and check that your correct WAN IP is in the frontbridge domain setup.

Then I would also assume that you have blocks on your firewall to only alllow Port 25 traffic to come from the Frontbridge servers, i would turn this off for the the period of testing and then telnet to your external IP on port 25 and see do you get a connection if you do then send a test mail via command prompt.  http://www.yuki-onna.co.uk/email/smtp.html

Your problem is either at frontbridge / your firewall / SMTP server. Also your frontbridge logs will indicate if frontbridge is recieving mail and not able to send it to you or if they are nto recievning mail at all if that is the case ring their support line.


Author Comment

ID: 22873512

We're actually moving away from the frontbridge spam filter altogether. I went ahead and changed the MX record with NS to point to mail.farmerinsurance.com vs. mail.global.frontbridge.com several hours ago so I'm hoping for an early propagation at this time. We only had read access to the front bridge account so there were no configuration changes that were visible.

Right now the port forwarding is being done on a NetGear wireless router with SMTP, HTTP, HTTPS, and RDP. The  SBS server runs on a single NIC and everything is forwarded to it's address.

I can not telnet to port 25 to mail.farmerinsurance.com externally either by hostname or by IP.
I can telnet to port 25 on the inside.

Bad Netgear??? I'm going to change it out in the morning.

Is there a best practice solution to get mail in the interim?

Thanks ahead of time.

Assisted Solution

by:Jerry Solomon
Jerry Solomon earned 100 total points
ID: 22873872
I would definitely suspect the Netgear, especially if it is one of the home-models.  Their prosafe series holds up pretty well in front of an Exchange server, but any router under $100 generally crashes, sputters, and dies under the load. The higher-end "firewalls" are better, the Sonicwall TZ170 or Watchguard x10e/x25e  are pretty popular selections for this kind of use.

As for the interim, you're already planning to put in another router in the morning, so that should float you until you get a better one, assuming that is your problem.

good luck.

Author Comment

ID: 22874024
New MX propgated. Everything tricking in. Accepting from "all" domains. Thanks for all the help.

Featured Post

2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Among the most obnoxious of Exchange errors is error 1216 – Attached Database Mismatch error of the Jet Database Engine. When faced with this error, users may have to suffer from mailbox inaccessibility and in worst situations, permanent data loss.
Let us take a look at the scenario, you have a database that is corrupt and you run the ESEUTIL command only to find you are unable to repair it. How do you now get the data back?
This video discusses moving either the default database or any database to a new volume.
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses

601 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question