Hello We're running Exchange 2007 SP3....Outlook 2007 SP2. Today we have an issue with one of our DL's - someone sent an email to "Company ALL"....to which people then started replying all to, and it became a right old mess. Now, I understand that I can go to the Properties of that DL and restrict who can send to it, (which actually it was set to but someone removed it and forgot to reset), but we have hundreds of DL's like that. Does anyone know a decent method for the IT Team to be notified if emails to a certain DL are hitting a threshold (SCOM, native Exchange monitoring, NetIQ etc)? Anything new in Exchange 2010 for this?

I would setup delivery restrictions on those DL which include a high number of recipients. I would also check out the security of those users who are allowed to modify such objects. In Exch 2010 you can use Moderation for DL. So when an email is sent to a DL which is moderated, it will require approval from a designated moderator before the email is sent to that DL. - http://technet.microsoft.com/en-us/library/dd297936.aspx Use Set-Distribution to set this - http://technet.microsoft.com/en-us/library/bb124955.aspx Not sure why you want measure threshold, prevent it from happening. http://blogs.technet.com/b/exchange/archive/2004/04/08/109626.aspx Sukh

On Mon, 4 Jul 2011 15:16:08 +0000, Smith1974 wrote: > > >Hello > >We're running Exchange 2007 SP3....Outlook 2007 SP2. > >Today we have an issue with one of our DL's - someone sent an email to "Company ALL"....to which people then started replying all to, and it became a right old mess. > >Now, I understand that I can go to the Properties of that DL and restrict who can send to it, (which actually it was set to but someone removed it and forgot to reset), but we have hundreds of DL's like that. > >Does anyone know a decent method for the IT Team to be notified if emails to a certain DL are hitting a threshold (SCOM, native Exchange monitoring, NetIQ etc)? > >Anything new in Exchange 2010 for this? We usually depend on the vice-presidential alerting system. You'll hear about problems like this far quicker from vice-presidents than you will from anything that's automated. ;-) You could always make a list of the DLs you want controlled and then run Powershell in a scheduled task to verify that the DLs are stiil in the state you want them to be in. It might also be an idea to create a transport rule that rejects the message if it finds one of those "everybody" groups in the "To: or "Cc" headers. Putting the DL in the "Bcc:" header is a sure way to quash those mailstorms. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi, I have another workaround. You could set Maximum number of recipients per message to restrict such issue. Note: You could set this attribute at different levels. Organization limit: Set-TransportConfig Parameter: MaxRecipientEnvelopeLimit Connector limit: Set-ReceiveConnector Parameter: MaxRecipientsPerMessage Server limit: Set-TransportServer Parameter: PickupDirectoryMaxRecipientsPerMessage User limit: Set-MailUser Parameter: MaxRecipientsPerMessage More information: Understanding Message Size Limits Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

On Wed, 6 Jul 2011 09:05:45 +0000, Jerome Xiong wrote: >I have another workaround. > >You could set Maximum number of recipients per message to restrict such issue. Doesn't that limit apply only to the unexpanded recipients? If that's so, then the DL counts as only one recipient. If this was Exchange 2003 then it might be a useful solution, but only if the limit was appied to the user. But I think that trying to limit the number of recipients is going just going to cause more problems -- especially if you have legitimate DLs that the person can send to that exceed the limit you set. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Because user limit has the highest priority, so you could set a lower limit at organization limit, connector limit, or server limit. Specify the higher limit at user limit.

Hi Smith, Did you try my method? Do you have any update?