Hi, and thanks in advance for any help anyone can share with me; We are trying to create an opt-out feature for our clients that will allow them to add their internet email addresses to a 'do not mail' list -for newsletters, but they must still be able to receive their monthly statements (these come from two different and unique addresses. We are running a Windows 2003 functionality AD domain and an Exchange 2007 MB & CA server with an E2K3 Bridge Head. Our initial thoughts are; the opt-out email addresses will be entered by the client on a webpage. This will create an LDAP (AD) contact object in an 'OPT-OUT' OU. We were then going to create a dynamic group based on this OU membership that was restricted from receiving any email except email from the address we use for their monthly statements. **This solution (as we tested it) failed because the group members were only restricted if the dynamic group was sent to directly, they were not individually blocked from receiving email. Now our thought is: If there is a way to apply a 'send to' restriction directly to the 'OPT-OUT' OU that would be inherited by the contacts -LDAP objects, that web development will programmatically create, we could just restrict any member of this OPT-OUT OU from receiving any email from our domain (with the exception of whatever address we choose). **Is there a way to restrict OU members from receiving email from our domain members as an inherited security restriction? Thanks again for any help.

Are you suggesting having two contacts, one an opt-out contact, with the same SMTP address? You can't have an SMTP contact on more than one AD object. Well, actually you can if you put it on outside the Exchange tools, but Exchange will complain a lot and your mail many not route properly. Why don't you use an extension attribute for the opt-out feature, and create a dynamic distribution list for contacts that don't have the opt-out set for sending to the non-opt-out contacts?Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Why not just move the "newsletter" group out to a service that can manage that for you? Loads of options, and if the numbers are quite low then it can be done for free. Look at mailchimp for example - there are others. A dedicated service will also be more efficient for sending the mass email. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

I don't really need two groups created just an attruibute that would apply directly to the contacts that don't want to receive any (except their statements) email from anyone at our company (besides the account used to send statments). Is there a way to apply an attribute to an OU that would inherit to the external contacts in the OU; that exchange would read and restrict all email to this external account? -If member of 'optout' OU then do not allow email to be sent to account (or block at internet connector, etc). I understand this may be intensive for exchange to check every piece of Internet bound email to see if it is restricted but this is the current idea we need to try to make work. As far as using an outside service this is not an option because we need to integrate this email restriction and apply it to everyone at our company also. There are homebuilt programs that sales people use to email information and contact clients -& prospective clients, and we don't want to take the chance of them email anyone on the optout list. Maybe I'm thinking about this the wrong way but this is the only way I can think of, short of a manual black list, to ensure we conform 100% with CanSpam.