FlashCoders is just plain and simply not the place for sitechecks. If you need to post a sitecheck you may want to look into Flasher-L
Make your thread title short and descriptive. Remember it often gets truncated, so get your message across in the first few words. Don't: “Help! problem with Flash”. Do “Failed method inheritance with onEnterFrame”.
Clearly state what the problem is, when it happens and how to reproduce it. Also inform of any failed fixes you have already tried. Describing the results you were expecting to see can be helpful.
Explain what caused the problem. Explain how to fix/work around it.
Share the solution with the list. Reply to the thread appending [SOLUTION] to the question. Explain and exemplify the solution.
Always test your code before posting. Don't waste helpful people's time with typos, syntax errors and omissions. Leave your code in native AS format and use helpful comments.
Each email is a request for the time of other people… they have to spend at least some time with it, even if it's just to delete your message unread. If you post too much, without offering corresponding value for the reading, then you risk diminishing the community, and risk getting yourself killfiled in the process.
You can learn a lot of things by solving someone's problem, but try not to hurt more than you can help. Test your solutions before proffering them and you will discover as much as the person you are assisting.
Turn off “request read/delete” receipts in your email client.
We really don't need to know you're having problems with your email. Show a little consideration and send your test message to yourself or to a friend - don't send it to 2000+ very busy people.
Try to reduce the message you quote to the necessary minimum, at least remove the default footer.