Re: Start receiving mail from outside

Have your ISP create an MX record called mail.yourdomain.com, an "A" record
that points the MX to your Cisco, and an rDNS record for
mail.yourdomain.com. Forward port 25 to the SBS.

You will most likely also want 443 and 4125 for OWA, RWW, and RDP via RWW.
Keep port 80 closed.

Gregg Hill



"Tommy Forsman" <tofors99@xxxxxxxxxxx> wrote in message
news:etUDYAt4GHA.2536@xxxxxxxxxxxxxxxxxxxxxxx
Hi Frank
yes we have a registerd public domain, and we use pop accounts today.
Our server does not have an external ip, but our Cisco Pix have. Should
the MX record point to the Cisco in which there should be a rule that lets
traffic on port 25 go to our internal ip on Exchange or do we have to have
2 external ip:s? One for Cisco and a different for Exchange?

Tomppa

"Frank McCallister SBS MVP" <anonymous> wrote in message
news:%23VXnAXs4GHA.3604@xxxxxxxxxxxxxxxxxxxxxxx
Do you have a registered Public Domain Name like company.com or are you
using email from hotmail? If you have a FQDN then you get whoever hosts
your domain to set an MX record to point to your static IP address of
your server. You will need an A record also. If you have a website hosted
elsewhere then the A record should point mail.FQDN to your Static IP so
that you won't interfere with your website.

--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC
"Tommy Forsman" <tofors99@xxxxxxxxxxx> wrote in message
news:%23o8kOIs4GHA.4888@xxxxxxxxxxxxxxxxxxxxxxx
Hi

Our SBS2003 have been up and running for a while, but we still havent
used Exchange. I have checked that Exchange mail works internally and I
can also send mail to the outside.

What has to be done to get our exchange to receive mail from outside?

1) open port 25 in our firewall from outside to the exchange
192.168.1.100 on the inside
2) have the ISP to change the MX records to point to our firewall?

Is this enough? Our domain is called "company.local"

Tomppa







.

Relevant Pages

  • Re: Local domain name not resolving for SMTP
    ... Exchange uses port 25 by default but Outlook can use whatever port the ISP ... The old server is still in place for forwarding but does not have a DNS ...
    (microsoft.public.windows.server.sbs)
  • RE: DCOM patch + Exchange
    ... Exchange needs The RPC protocol to communicate which happens to be port 135 ... same problem since some genius at my isp decided to fight the worm by ... SBC or charter communications in Madison and Chicago, ...
    (Focus-Microsoft)
  • Re: How Does Exchange Receive Email?
    ... You should get a reply from your mail server internally. ... If you have a router, port 25 must be opened and forwarding to your ... > configured to collect from the exchange and also from their previous ISP ...
    (microsoft.public.windows.server.sbs)
  • RE: DCOM patch + Exchange
    ... If I understand correctly this was an issue of exchange client ... outside your network not being able to access the server after the patch. ... Except they refered to another ISP but it does not matter what isp you have ... require access to port 135 to connect to ...
    (Focus-Microsoft)
  • Re: Setting up MX records etc
    ... need to creat in exchange itself if anything, ... We currenty use POP3 via our ISP. ... > Ensure your external IP is routed to your firewall via your ISP. ... > Open port 25 on the firewall both in and out. ...
    (microsoft.public.exchange.admin)