Link to home
Start Free TrialLog in
Avatar of -Juddy-
-Juddy-Flag for United Kingdom of Great Britain and Northern Ireland

asked on

Exchange 2007: Messages are being sent to a deleted user.

One of our staff left (a P.A. with access rights to the M.D.'s mail) and has had their domain account and mailbox removed. The problem is that when anybody sends a meeting invite to the MD, the ex member of staff gets copied in and the sender gets a failure as they no longer have an account.  The MD still gets their meeting invite, but it's just a bit annoying.

I have checked the Delivery Options, Send As and Manage Full Access permissions and the ex member of staff does not appear in there, so why is the system trying to notify them still?

Here's a failure report:

Delivery has failed to these recipients or distribution lists:

Ex Staff Members Name

The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your system administrator.

Sent by Microsoft Exchange Server 2007

Diagnostic information for administrators:

Generating server: ourserver.our.domain.com

IMCEAEX-_O=FIRST+20ORGANIZATION_OU=First+20administrative+20group_cn=Recipients_cn=exstaffaddress.com
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

Original message headers:

Received: from ourserver.our.domain.com ([fe80::8dfa:4dc8:36a1:6809]) by
ourserver[Internal IP]) with mapi; Fri, 8 Apr 2011 16:50:33 +0100
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Anotherstaffmember<Anotherstaffmember@our-domain.com>
To: Ex staff member
      <IMCEAEX-_O=FIRST+20ORGANIZATION_OU=First+20administrative+20group_cn=Recipients_cn=exstaffaddress.com>
Date: Fri, 8 Apr 2011 16:50:33 +0100
Subject: Accepted: Meeting Request
Thread-Topic: Meeting Request
Thread-Index: Acv2BJcZv5CalacwRaeBmr+Vs5wkDgAABaKQ
Message-ID: <96B01F7459E83B46A50358B4EA02D200C517C6C@mailserver>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <96B01F7459E83B46A5035874EA02D200C517C6C@mailserver>
acceptlanguage: en-US, en-GB
MIME-Version: 1.0

Thanks in advance guys.
Avatar of Firmin Frederick
Firmin Frederick
Flag of United Kingdom of Great Britain and Northern Ireland image

is MD mail "forwarding" to user still?
SOLUTION
Avatar of -Juddy-
-Juddy-
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
MD mailbox/mail flow settings/delivery options/forwarding address
Avatar of -Juddy-

ASKER

Nothing in forwarding addresses section.
ah ok what about whether MD was in a mailing group that would have included the ex-employee?
Avatar of -Juddy-

ASKER

I have had a look through and can't find her, but this meeting request was sent direct to the MD and not a mailing group, so would this apply?
I am also wondering about aliases, and or rogue email references - you can try

1. giving another account ex-employee email address (additional SMTP) if it exists anywhere else then you will get an error message

2 . give the MD the ex-employee email address as an alias and as before if it exists anywhere you will get the same message indicating that somewhere the email address is still registered.

3. if neither of these gives an error leave ex-employee email address as alias (lazy option)
sorry I couldn't determine it was direct to the MD from the mail message:

From: Anotherstaffmember<Anotherstaffmember@our-domain.com>
To: Ex staff member
      <IMCEAEX-_O=FIRST+20ORGANIZATION_OU=First+20administrative+20group_cn=Recipients_cn=ex
if the message was direct to the MD were any resources added as required/optional/etc?  Was ex-employee responsible for any resources that may have been invited?  Just a thought.
Avatar of -Juddy-

ASKER

The HR Manager already had the ex staff members E-Mail address as an alias, in case people still try to mail her.  I'd rather not take the lazy option!!
Avatar of -Juddy-

ASKER

We have a room mail account for the Board Room which is also 'invited'.  I have gone through the permissions and manage full access (etc) permissions as well; no sign of her there either.
ok so an email is sent to your MD (meeting invite) with 1 resource added.  That email also goes (somehow) to the email address of your ex-employee which is aliased to your HR person which then gets fired back saying person does not exist.

This still points to email address linked to something included in invite otherwise there would be no NDR
if the alias is correct under the HR person alias list then even in complete fluke that the email address is linked to something there still would not be an Non Delivery Report it would just end up with HR person.
Avatar of -Juddy-

ASKER

Agreed, that's why I can't understand why this is failing!
Avatar of -Juddy-

ASKER

I suppose as a 'semi-lazy' option I could add the alias to the MD rather than the HR Managers account and test......not a fix, but could be a 'work around'. I'll do that now....
Avatar of -Juddy-

ASKER

No....fails as it's still trying to send to the ex staff member. I.s starting to think it might be easier to just re-employ her!!
Hi Juddy maybe not re-employ her...what about recreate her account with email address etc. then test to see what happens?
also, what happens if you just email the MD - no invite or resources, just a plain text email?
Avatar of -Juddy-

ASKER

E-Mail is fine, no NDR's.
"E-Mail is fine, no NDR's." - is that just a plain text message direct to MD yeah?
just noticed you put this question in MS Sharepoint as opposed to Exchange, prob why there isn't more feedback :)
Avatar of -Juddy-

ASKER

Oops...
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of -Juddy-

ASKER

Please close this as it was in the wrong section; I have re-posted.