Re: Exchange setup when not a public mail server
- From: "Frank McCallister SBS MVP" <anonymous>
- Date: Mon, 8 Aug 2005 13:18:37 -0500
The Smarthost is send only and you will receive as you have been. This is
configured in CEICW Email configuration.
--
Frank McCallister SBS MVP
COMPUMAC
"Scott Frazier" <ScottFrazier@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:22242EEB-00B4-4EEA-8BFB-BC8E1623D119@xxxxxxxxxxxxxxxx
> Thank you Frank. We fall under number two - since we have no static IP
> and
> no DNS records to add to. The Smart host option in the CIECW wizard - is
> that the part where you can pull mail from a POP3 server?
>
> Correct me also if I am wrong, I need to get information and permission
> from
> my ISP (Hurricane Electric) to do the Smart Host thing?
>
> How are the clients configured then in the Smart Host environment? Do
> they
> have an Exchange account and a POP3 account (pointing to our ISP mail
> boxes)?
> Or just an Exchange account?
>
> "Frank McCallister SBS MVP" wrote:
>
>> Hi Scott
>>
>> This is primarily governed by your ISP and in the case of some ISPs the
>> class of service you have. I will assume that you have a Static IP and
>> that
>> you are currently sending by DNS and not by Smarthost hence your AOL
>> issues.
>> There are three possible solutions to your issue using Exchange.
>>
>> 1. Using DNS arrange with your ISP for a proper PTR record for your
>> domain
>> so the a reverse DNS lookup will be correct and AOL messages will not
>> fail.
>>
>> 2. If ISP allows it on your service switch to Smarthost by running CEICW
>>
>> 3. If ISP won't do either 1 or 2 the arrange for third party Smarthost. I
>> use Dyndns.org Mailhop Outbound.
>> http://www.dyndns.com/services/mailhop/outbound.html which is inexpensive
>> and gets around Bellsouth Draconion policies and I have never had an AOL
>> or
>> other domain message bounce for any reason.
>>
>> --
>> Frank McCallister SBS MVP
>> COMPUMAC
>> "Scott Frazier" <Scott Frazier@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message
>> news:4C5652A2-6C8B-4B8B-B0D6-110FB38CF130@xxxxxxxxxxxxxxxx
>> >I see bits and peices amongst all of these threads, but I need a little
>> >more
>> > than that. Can someone just summarize the set up for an SBS exchange
>> > server
>> > and the Outlook 2003 clients, behind the standard SBS firewall, when
>> > the
>> > exchange server is NOT a public exchange server. This is to solve,
>> > once
>> > and
>> > for all, the AOL reverse DNS issue. What is the specific set up on the
>> > server, what is the specific set up on the Outlook 2003 clients also?
>> > I
>> > want
>> > to be able to use the shared public folders, calendars, and mail store
>> > of
>> > the
>> > exchange server but I do not want it to send mail that gets rejected by
>> > the
>> > reverse DNS thing.
>>
>>
>>
.
- Follow-Ups:
- Re: Exchange setup when not a public mail server
- From: Jeff Teel
- Re: Exchange setup when not a public mail server
- References:
- Exchange setup when not a public mail server
- From: Scott Frazier
- Re: Exchange setup when not a public mail server
- From: Frank McCallister SBS MVP
- Re: Exchange setup when not a public mail server
- From: Scott Frazier
- Exchange setup when not a public mail server
- Prev by Date: Re: Exchange monitoring.
- Next by Date: Re: SBS2k3 to SBS2k3
- Previous by thread: Re: Exchange setup when not a public mail server
- Next by thread: Re: Exchange setup when not a public mail server
- Index(es):
Relevant Pages
|