Re: Exchange Server and Internet Email problem

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 08/05/04 

Date: Wed, 4 Aug 2004 22:35:39 -0400

PamelaK wrote:
> Thanks for the advice. Can anyone tell me how much time an Exchange
> 2003 implementation for 15 users might take?

You already have Exchange installed, and if the users have the Exchange
service already in their mail profiles, which they do or you couldn't get to
the public calendars, etc., it's no big deal. Make sure nobody is using a
PST file for delivery anyway...if they are, change it to the Exchange
mailbox & import data from the PST....

Then take a look at http://www.msexchange.org/tutorials/MF002.html to
understand how this all works. You will need to run the CEICW to make the
change, and you should do it over a weekend (so you can call your ISP/DNS
host on Friday eve to have them change the MX record for your domain).

Do you have a static IP? This is much easier if you do - but it isn't
mandatory. If you're dynamic, you can use a dynamic DNS host such as
www.dyndns.org - you set up an account, such as yourcompany.dnsalias.com,
and whomever hosts your public DNS should set your primary MX record to
point to yourcompany.dnsalias.com. Open up port 25 inbound in your firewall
or router, direct all traffic to your internal IP for the Exchange server.
You run a service on your server (software available for download from the
dyndns website) and set it up to update dyndns with your current dynamic
IP.

Once it's all working, the Internet Mail service in Outlook won't be
working - so remove it from the profiles.

Re AOL - they reject mail from a lot of servers in an effort to stop spam.
Some reasons for being blocked would be -

Your SMTP server has no reverse lookup records (PTR)
Your IP is considered to be on a dialup or dynamic IP [1]
Your IP or SMTP server has been blacklisted as an open relay

For the reverse lookup, check out your domain at www.dnsreport.com; ask your
ISP to create the record for you, presuming you have a static IP.

If you don't have a static IP, you can set up an SMTP connector that points
to your ISP's SMTP server & add aol.com there...also might want to do
hotmail.com as I've heard rumors they're starting to do the same thing.

>
> "Lanwench [MVP - Exchange]" wrote:
>
>> PamelaK wrote:
>>> I am running sbs 2003 standard edition but haven't implemented email
>>> on the Exchange server. I have configured the user's Outlook with
>>> Exchange in order to access a shared calendar as well as in
>>> preparation for a near future exchange email implementation. All
>>> the users are using Outlook 2003 windows xp pro and are configured
>>> for Internet email. However, while most messages seem to use the
>>> smtp for internet email on occasion some of the messages wind up in
>>> the Exchange SMTP server queue. It seems to generate a
>>> SmallBusiness SMTP connector. In a recent case one message with
>>> one recipient (at aol.com) generated two SmallBusiness SMTP
>>> connectors - one going to aol.com and the other to
>>> courtesynetwork.com. Both of these connectors are currently in a
>>> 'scheduled' state. This condition appears to setup a situation in
>>> which the message is delivered twice
>>> - once through the isp's smtp and the second time through exchange
>>> smtp. Even more troubling is that these scheduled messages can
>>> remain in the queue for months and then suddenly get sent. Last
>>> night Exchange sent out a message in the queue from June! Why is
>>> this happening and how can I prevent future occurances?
>>
>> What's the default account set to in Outlook?
>> Honestly, I'd just bite the bullet, ditch POP and set up Exchange to
>> handle all your mail. It isn't anywhere near as painful as you may
>> fear....you would resolve this and myriad other problems.

Relevant Pages

  • Re: .local or .com
    ... No, you can easily host mail for your users, one of two ways. ... Exchange, and I highly recommend using an SMTP connector in Exchange to ... You can do this without changing a thing in your Public zone as far as MX ... The other way is to make Exchange your public SMTP server with the Public ...
    (microsoft.public.windows.server.dns)
  • Re: .local or .com
    ... No, you can easily host mail for your users, one of two ways. ... Exchange, and I highly recommend using an SMTP connector in Exchange to ... You can do this without changing a thing in your Public zone as far as MX ... The other way is to make Exchange your public SMTP server with the Public MX ...
    (microsoft.public.windows.server.dns)
  • Settting Up Second (POP) Account
    ... Using Exchange 2000 and Outlook 2002... ... (We host the ... mail domain ourselves, and this address refers to an Exchange ...
    (microsoft.public.exchange.clients)
  • Re: SMTP Server
    ... Exchange 2003, The SMTP server only is used to send mails or too to ... Because, when I click on Send/Receive on Outlook, Send=SMTP ...
    (microsoft.public.exchange.admin)
  • Re: HELP Stop SBS SMTP
    ... One would be to use Exchange normally, and give the users remote access over ... RWW, Outlook RPC over HTTPS, or OWA. ... the outside SMTP Server I'll just put it in his mail box. ...
    (microsoft.public.windows.server.sbs)
Loading