Since your comments go out to so many people, please refrain from flames and critiques of someone else's post. Abuse can result in being dropped from the list.

• Don't use this list or the membership of this list to solicit your product. If I see evidence of this, you will be dropped. It has happened once already.
• All material sent to this list is considered copyrighted by the author of the email. Don't forward a message from this list without first receiving permission from the author. This has happened many times already, and I will start dropping violators. Microsoft employees are *not* exempt from this rule in order to pass feedback to product teams. If the author explicitly indicates that they are giving feedback for Microsoft (or the post is part of a thread started by a MS employee asking for feedback) then, of course, the content can be passed along within MS. Bottom line: please ask the author for permission before forwarding.
• If your subscribed address starts to bounce messages, I'll unsubscribe it after a couple days. I try to send an email to the subscribed address about this.
• Don't send attachments. Put your attachment on a webserver and reference the URL. A large number of the list members block attachments (and the list owners will hear from every one of their servers when you ignore this rule--making us grumpy at you).

Suggestions:

• While there are several Microsoft representatives on the list, you should not expect them to give you PSS level support. They participate to be helpful, while looking to hear constructive feedback. Which leads to the next suggestion ...
• I know I'm as guilty as the next person of getting upset at Microsoft. When you find yourself writing a remark along these lines, try to channel your emotions into constructive suggestions that someone at MS could realistically take action on. Your consideration will ultimately help our community get more responsiveness from MS.
• If you have a specific problem you are looking to solve, you can suggest that others with suggestions contact you directly. Once you find a solution or have what you feel is a quorum of suggestions, you can follow-up with a summary post to the list. Of course, this type of approach has limitations--only suggest it when you feel it would help limit list traffic and not impact potential collaboration. A good example of when this approach would be appropriate are for surveys.

Other notes:

• Don't hesitate to contact Brian Arkills, Ross Wilper, or Brad Judy on list issues. We are all list owners.