Lanopy
asked on
Exchange 2010, Recipient not found after creating a distribution group
A previous admin had created a mail box that forwarded to a distribution group. I did not like the implementation so removed the mailbox. I deleted the group in AD and then used power shell to delete the disconnected mailbox.
I then created a distribution group properly, and mail enabled it for external senders. I did however use the same email address for the distro that was used for the traditional mailbox that I deleted.
External senders can send to it fine. When internal senders try to send to it, they get a kick back.
I have cleared the old address references from the Outlook cache on my test machine with no luck.
The NDR is below
Help Desk
The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: ELM.domain.local
IMCEAEX-_O=BUSINESS+20NAME _OU=EXCHAN GE+20ADMIN ISTRATIVE+ 20GROUP+20 +28FYDIBOH F23SPDLT+2 9_CN=RECIP IENTS_CN=H elp+20Desk 5d0@domain .com
#550 5.1.1 RESOLVER.ADR.ExRecipNotFou nd; not found ##
Original message headers:
Received: from ELM.domain.local ([fe80::e09e:2497:475f:4e3 7]) by ELM.domain.local
([fe80::e09e:2497:475f:4e3 7%11]) with mapi id 14.03.0195.001; Fri, 21 Nov
2014 20:37:49 -0500
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Jonathan Anderson <janderson@domain.com>
To: Help Desk <helpdesk@domain.com>
Subject: TEST
Thread-Topic: TEST
Thread-Index: AdAF9OlTqCqosSopTui6Xt5yo3 4cvg==
Date: Fri, 21 Nov 2014 20:37:49 -0500
Message-ID: <206B5E939DDF2D468FAE2F57D 4CBB6C605C EE7@ELM.do main.local >
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <206B5E939DDF2D468FAE2F57D 4CBB6C605C EE7@ELM.do main.local >
MIME-Version: 1.0
X-Originating-IP: [x.x.x.x]
I then created a distribution group properly, and mail enabled it for external senders. I did however use the same email address for the distro that was used for the traditional mailbox that I deleted.
External senders can send to it fine. When internal senders try to send to it, they get a kick back.
I have cleared the old address references from the Outlook cache on my test machine with no luck.
The NDR is below
Help Desk
The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.
Diagnostic information for administrators:
Generating server: ELM.domain.local
IMCEAEX-_O=BUSINESS+20NAME
#550 5.1.1 RESOLVER.ADR.ExRecipNotFou
Original message headers:
Received: from ELM.domain.local ([fe80::e09e:2497:475f:4e3
([fe80::e09e:2497:475f:4e3
2014 20:37:49 -0500
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding:
From: Jonathan Anderson <janderson@domain.com>
To: Help Desk <helpdesk@domain.com>
Subject: TEST
Thread-Topic: TEST
Thread-Index: AdAF9OlTqCqosSopTui6Xt5yo3
Date: Fri, 21 Nov 2014 20:37:49 -0500
Message-ID: <206B5E939DDF2D468FAE2F57D
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <206B5E939DDF2D468FAE2F57D
MIME-Version: 1.0
X-Originating-IP: [x.x.x.x]
Have you actually looked at the email address tab on the distro you created? Is it possible it was not what you thought it to be? If not this has to be a cache names issues. Have you tried selecting the recipient from the address book? Specifically from an outlook client that is not in cached mode?
ASKER
I do believe this is related to caching somehow. Since the post . . . .
I was able to create a new profile on a machine, log in as administrator, and send to it just fine.
I just had a user try. They deleted the addy from the type ahead cache, then selected it from the GAL, but when they try to expand it they get an error.
Not sure where to go from here.
I was able to create a new profile on a machine, log in as administrator, and send to it just fine.
I just had a user try. They deleted the addy from the type ahead cache, then selected it from the GAL, but when they try to expand it they get an error.
Not sure where to go from here.
ASKER
Further update . . . . .
I had a user uncheck cached mode and it works. Its not really reasonable to go to all the machines on the network and disable cached mode.
Any workarounds for this?
I had a user uncheck cached mode and it works. Its not really reasonable to go to all the machines on the network and disable cached mode.
Any workarounds for this?
Communicate the change to everyone and ask them to select from the address book. It is the easiest way.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.