Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Wed, 30 Mar 2005 00:29:04 -0800,    group: microsoft.public.exchange2000.transport        back       


Getting NDR reports on removed domain   
I run Exchange 2000 on a Win 2000 server. This server had two email domain 
configured: comp1.com and comp2.com. I then moved some users over to a new 
server, outside the network, and they took with them comp2.com. I then 
deleted the reference/connector for comp2.com form the server. If some people 
tries to send email to someone in comp2.com, they get a NDR 5.1.1 with the 
text: The e-mail account does not exist at the organization the message was 
sent to.

If I do a message tracking, I see the following information:

SMTP: Store Driver: Message Submitted from Store
SMTP: Message Submitted to Advanced Queuing
SMTP: Started Message Submission to Advanced Queue
SMTP: Message Submitted to Categorizer
SMTP: Non-Delivered Report (NDR) Generated

Where should I look or what sould I do, to figure out how to remove the 
comp2.com completely, so that it works like all other email domains in the 
rest of the world? Email to all others works totally fine, and other people 
can send to com2.com on their new site totally fine.


Kind regards,

Rune
date: Wed, 30 Mar 2005 00:29:04 -0800   author:   Broboman

RE: Getting NDR reports on removed domain   
I have found the solution. The comp2.com domain was still included as a 
receipient email domain in the default recipient policy, and the checkbox for 
that this exchange server is responsible, was crossed. Removed this, and now 
it works...

Rune
date: Wed, 30 Mar 2005 05:37:05 -0800   author:   Broboman

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us