Environment: Exchange 2007 Windows Server 2008 64 bit 2 mailbox servers, 2 hub transport servers. (all 2k8x64) We have a very odd issue with one of our dynamic distribution lists. If a meeting invite is sent to group it it automatically sends to another distribution group as well. Emails sent to the group do not exhibit this behavior, only meeting invites. Any ideas on this one?

Another odd behavior is that if I run the following 2 commands I don't get just the members of the dynamic distribution list, but rather all members and groups. $group = Get-DynamicDistributionGroup –identity “groupname” Get-Recipient –RecipientPreviewFilter $group.RecipientFilter

I see the correct membership if I view them in the EMC.

Update. There was one user in the group whom was the cause. The user was removed from the group and the forward to the other group stopped. Is it possible for a user to cause email sent to a group he is a member of to forward to another group?

It could have been by rule, but the message would have indicated that it was forwarded.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "FuriouS76" wrote in message news:9e8cd14f-0688-467e-9213-0487a843aa3b...Update.There was one user in the group whom was the cause. The user was removed from the group and the forward to the other group stopped.Is it possible for a user to cause email sent to a group he is a member of to forward to another group? Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

That is exactly what we thought. We researched all rules on the account and in the end the fix was to remove the user that the meeting shows as "received on behalf of" in the meeting invite. If this user was put back into the distribution list the meeting was forwarded to another distribution group, but the odd part is it was forwarded as the original sender. We deleted and re-created the user account that was causing this, and now everything functions normally. This is one of the oddest behaviors I have ever seen from exchange and the fix was to recreate the account.