Hello, I am having a problem with a distribution group that I now cannot send emails to. Originally the group worked but the clients did not want external emails to be send to this group. So I removed the Exchange attributes thinking that now only internal emails could be sent to the group but not external emails. Needless to say now no one can send emails to the group. I deleted and recreated the distribution group and added the Exchange attributes in the hope of getting the group to be at least the way it was before but I am still getting the following message (regardless of who emails the group): Your message did not reach some or all of the intended recipients. Subject: This is a Test from IT (Internal) Sent: 6/11/2009 1:04 PM The following recipient(s) cannot be reached: Joint Planning on 6/11/2009 1:04 PM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <[Our mail server] #5.1.1> In addition, the clients cannot expand the group within Outlook to send people individual emails, etc. Is there any way I can do the following: Have the group setup so that people can email to it using the original address or distribution name they were always using? Set up the group so that only people who have an account on the domain can email the group? Thank you for your time. Regards, Christopher Koeber

How long did you wait after creation of DG? AD replication and RUS may take sometime to update and stamp the email address, once it is updated OAB takes time to display in outlook which are configured with cache mode. About second question, how to setup group to stop receiving emails from external email address, in Properties -> Exchange General -> Select "From Authenticated Users only" which will block DG to receive email from external email addresses but accept email from AD users of your organization.Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Thank you so much for the reply. I did wait at least one day with the same results. Since this is a small exchange deployment within one campus there usually isnt a long delay with replication. Your advice for other groups works well as these groups produce bouncebacks once the settings were adjusted as advised for external accounts. Internal emails work fine. For this one group, however, people still cannot email at all. I have tried to disable and re-enable the mailing portion of the group via the Exchange tools to no avail. In addition, I have checked this group against other groups that have similar needs. The other groups work fine but no one can email this group (they get bouncebacks) Anything else I can do to get this group functioning again? Again, thank you for your time. Regards, Christopher Koeber

Are you able to see SMTP address in "Email Addresses" tab of group properties? If so, try by sending an email from OWA. Also in 'From' field mention the email address you checked for SMTP in "Email Addresses" tab of group properties, instead of selecting group from GAL. If nothing works then, change the SMTP address of this group to old_groupname@domain.com, create a new group and assign the original groupname@domain.com email address to SMTP address of new group and check the situation.Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

Hi Christopher, Firstly, please understand that for a distribution group to receive message, you need to have distribution group have Exchange Attributes enabled. In addition, please let me know whether you have Exchange 2003 or Exchange 2007 installed. If it is Exchange 2003, you need to have Recipient Update Service to update the Exchange attributes for the group. You can right click the Recipient Update Service in ESM and click Update Now to force the RUS to update Exchange attribute for some objects immediately. If the SMTP address is still not been set to the Distribution Group (the E-mail addresses tab is empty) after RUS update Exchange attributes and AD replication, you may need to troubleshoot RUS issue by referring to following article: How to troubleshoot the Recipient Update Service by using the Application log in Exchange 2000 Server or in Exchange Server 2003 http://support.microsoft.com/kb/822794 Mike