Within exchange 2003, is there any easy way to: identify to what extent these daft chain/joke emails are in operation? identify any sensitive data such as attachments being sent externally, such as to personal yahoo/hotmail accounts?

Within exchange 2003, is there any easy way to: identify to what extent these daft chain/joke emails are in operation? identify any sensitive data such as attachments being sent externally, such as to personal yahoo/hotmail accounts? Nobody on an exchange forum full of exchange experts knows how to do this?

Within exchange 2003, is there any easy way to: identify to what extent these daft chain/joke emails are in operation? identify any sensitive data such as attachments being sent externally, such as to personal yahoo/hotmail accounts? identify to what extent these daft chain/joke emails are in operation? You may consider netmon. identify any sensitive data such as attachments being sent externally, such as to personal yahoo/hotmail accounts? the Message tracking may indicate the message size (total size including message text and the attachment), however, it could not tell if a message includs an attachment. 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.

Within exchange 2003, is there any easy way to: identify to what extent these daft chain/joke emails are in operation? identify any sensitive data such as attachments being sent externally, such as to personal yahoo/hotmail accounts? Nobody on an exchange forum full of exchange experts knows how to do this? 1. By Using Exch 2003 alone you can't meet your first bullet point. All I can think of is thatyou can use message tracking to see where the joke email originate from (internal/external). If it's internal then you can have a "word" with your users, create a policy, highlight to management etc...If it's external, then maye you can block those senders from ESM under the Sender filtering tab. 2. With Exch 2003 you can't do this. This is lacking the features of exch 2007/2010 whereby you can use transport rules to detect such sensitive data. If data is sensitive, then I would maybe upgrade to Exch 2010 or use Windows RMS to protect your data, i.e allow what a user can do with a documents for e.g restrict forward to external recipients, attaching documents to emails etc.. Sukh