|
Home > Archive > microsoft.public.exchange2000.admin > October 2002 > outbound msg not relayed - fqdn resolution brain-teaser
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 |
outbound msg not relayed - fqdn resolution brain-teaser
|
|
|
| [I hope this doesn't make me a candidate for the Darwin Awards. Any
insight will be greatly appreciated.]
scenario:
server - e2k server in ad domain corp.wileyecoyote.com, ip 10.0.0.1
public dns registration - wileyecoyote.com resolves to 66.xxx.xxx.xxx
(hosted at an outside domain hosting company, i.e. hostingcom.com)
mail sent by you (outside) to anyone@wileyecoyote.com (i.e. any
recipient) - resolved by mx records on the nameservers at
hostingcom.com, happily routed to the pop3 server at hostingcom.com
where it awaits pickup by outlook clients inside
corp.wileyecoyote.com... or by pop3 mail clients outside of
corp.wileyecoyote.com
mail sent by an insider to someoneinside@wileyecoy
ote.com (with ad
users/computers email address set to type smtp and address
someone@wileyecoyote.com) - message never leaves the building,
intercepted by e2k and routed directly to the mailbox store
mail sent by insider to someoneoutside@wileyeco
yote.com (with no ad
user account whatsoever) - message never leaves the building, but it's
bounced back to the sender's inbox inside of a system administrator's
undeliverable mail notification message
finally, the big question:
"Can e2k be configured to resolve addresses so mail messages
originating from within ad corp.wileyecoyote.com destined for
someoneinside@wileyecoy
ote.com (inside) and
someoneoutside@wileyeco
yote.com (outside) will be routed successfully,
OR will I have to resort to pointing all mail originating from within
ad corp.wileyecoyote.com to a non-e2k smtp server elsewhere on the
LAN?"
TIA,
Boris
| |
| Bryan Nyce 2002-10-05, 8:23 pm |
| Boris wrote:
> "Can e2k be configured to resolve addresses so mail messages
> originating from within ad corp.wileyecoyote.com destined for
> someoneinside@wileyecoy
ote.com (inside) and
> someoneoutside@wileyeco
yote.com (outside) will be routed successfully,
> OR will I have to resort to pointing all mail originating from within
> ad corp.wileyecoyote.com to a non-e2k smtp server elsewhere on the
> LAN?"
>
> TIA,
>
> Boris
You cannot do this. You are telling Exchange it is responsible for inbound
delivery for wileyecoyote.com. Whenever they send a message to
anyone@wileyecoyote.com Exchange will place that into its local domain
queue, and not try to send it out of the organization. As you saw, if the
user does not exist in the organization, and NDR is generated. This is by
design.
Bryan Nyce
|
|
|
|
|