|
Home > Archive > microsoft.public.exchange2000.admin > October 2002 > Contacts in Acitve Directory cant send email to
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Contacts in Acitve Directory cant send email to
|
|
|
| I have an Exchange default domain name as e.g.
toughone.com, this is
also the same name as our Windows 2000 domain name. I am
in the
process of bringing the e-mail service in house from our
ISP. I am
doing on a user-by-user basis by using a 3rd party POP3
retriever.
For Exchange enabled users to send mail to those not yet
Exchange
enabled, I have configured it to fire out all unresolved e-
mail
address (i.e. where there is no Exchange mailbox) to our
ISP. This
means that exchange@toughone.com can send mail to
isp@toughone.com
even though the domain name is the same and the accounts
are in
different realms altogether.
This works fine except for one small detail - the Global
Address List.
I want all users to appear in the address book even
though not all of
them will connect to the Exchange service - some will
continue to
connect to the ISP until their client PC's are upgraded.
For users to appear in the GAL they have to be Exchange
enabled -
either with a mailbox or as a contact with an e-mail
address. I cannot
mail enable a user who I don't want to upgrade yet because
the mail
will never get to the ISP - it will stay in the database.
I have tried
to make a Contact with an e-mail address, like a 5.5
custom recipient,
and so thought that when sending a mail to the contact
there would be
no mailbox for that person and the mail would get fired
out to the
ISP. The problem is that that doesn't happen what happens
is that I
get an immediate bounce back message:
Subject "Undeliverable: Delivery Status Notification
(Failure)"
Body "A configuration error in the e-mail system caused
the message to
bounce between two servers or to be forwarded between two
recipients.
Contact your administrator".
| |
| David Sengupta [MVP] 2002-10-05, 8:39 pm |
| See my response in m.p.e.adintegration ... pls don't multipost.
--
David Sengupta M.T.S., B.Sc., MVP, MCSE, MCSE 2000, CCA Ottawa, Canada
Exchange Diagnostics: Quest Spotlight on Exchange
http://www.quest.com/spotlight_exchange
Exchange Management: http://www.microsoft.com/mom
Exchange FAQ - http://www.swinc.com/resource/exch_faq.htm
"John" <jleoniak@hotmail.com> wrote in message
news:e3a201c255e3$dc6bbaa0$9ee
62ecf@tkmsftngxa05...
> I have an Exchange default domain name as e.g.
> toughone.com, this is
>
> also the same name as our Windows 2000 domain name. I am
> in the
>
> process of bringing the e-mail service in house from our
> ISP. I am
>
> doing on a user-by-user basis by using a 3rd party POP3
> retriever.
>
> For Exchange enabled users to send mail to those not yet
> Exchange
>
> enabled, I have configured it to fire out all unresolved e-
> mail
>
> address (i.e. where there is no Exchange mailbox) to our
> ISP. This
>
> means that exchange@toughone.com can send mail to
> isp@toughone.com
>
> even though the domain name is the same and the accounts
> are in
>
> different realms altogether.
>
>
>
> This works fine except for one small detail - the Global
> Address List.
>
> I want all users to appear in the address book even
> though not all of
>
> them will connect to the Exchange service - some will
> continue to
>
> connect to the ISP until their client PC's are upgraded.
>
>
>
> For users to appear in the GAL they have to be Exchange
> enabled -
>
> either with a mailbox or as a contact with an e-mail
> address. I cannot
>
> mail enable a user who I don't want to upgrade yet because
> the mail
>
> will never get to the ISP - it will stay in the database.
> I have tried
>
> to make a Contact with an e-mail address, like a 5.5
> custom recipient,
>
> and so thought that when sending a mail to the contact
> there would be
>
> no mailbox for that person and the mail would get fired
> out to the
>
> ISP. The problem is that that doesn't happen what happens
> is that I
>
> get an immediate bounce back message:
>
>
>
> Subject "Undeliverable: Delivery Status Notification
> (Failure)"
>
> Body "A configuration error in the e-mail system caused
> the message to
>
> bounce between two servers or to be forwarded between two
> recipients.
>
> Contact your administrator".
>
|
|
|
|
|