Irritating NDRs with non-existent users: Exchange 2003
- From: Trix <trixtah@xxxxxxxxx>
- Date: Tue, 27 Nov 2007 22:42:52 -0800 (PST)
Actually NDRs for a non-existent user is a good thing, but it's not
the usual kind of issue. It's when a user has left the organisation,
and their account is deleted. For quite some time afterwards,
individuals who send mail to a distribution list which formerly
contained the user, or who try to send a meeting request to a mailbox
to which the user was a delegate will get the following form of NDR:
There was a SMTP communication problem with the recipient's email
server. Please contact your system administrator.
<servername #5.5.0 smtp;550 <IMCEAex-_O=ourdomainOU=FIRST
+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=HARRISON
+5FDG@xxxxxxxxxxxxx>: Recipient address rejected: User unknown>
For the life of me, I cannot find where these entries are coming from.
I've dumped the entire Domain Users container in the AD to see if
there are any old entries in something like publicDelegates and so on,
and can't find anything with the correct username. Since the user
account no longer exists, there's nowhere for the LegacyDN to be
lurking.
If someone could explain two things, I'd be grateful:
a) where the entries are hiding so I can delete them
b) how to stop this problem recurring in the future. Regarding this,
we have some rather hacked-together scripts to remove users from the
domain (which I don't control), so if there's something about the
account deletion process we might be omitting, it'd be good to know
what it is
Thanks.
.
- Follow-Ups:
- Re: Irritating NDRs with non-existent users: Exchange 2003
- From: Alexander Zammit [MVP]
- Re: Irritating NDRs with non-existent users: Exchange 2003
- Prev by Date: Charset modified by transport rule
- Next by Date: Re: Recipient Filtering....Exchange Server 2003 SP2
- Previous by thread: Charset modified by transport rule
- Next by thread: Re: Irritating NDRs with non-existent users: Exchange 2003
- Index(es):
Relevant Pages
|
