I found this to be convenient: http://techtonik.rainforce.org/2013/11/roundup-tracker-create-issues-by-email.html

And this is missing from here: http://docs.python.org/release/2.7/bugs.html#using-the-python-issue-tracker
Anf from here:
http://docs.python.org/devguide/triaging.html

Disclaimer: I didn't sign the CLA, and people keep telling me that I need it to do documentation edits. But I edit Wikipedia freely and I find it wrong that I can not edit Python documentation without signing papers. So I am not sending patches until either Wikipedia requires CLA to edit its contents, or PSF abandons its ill FUD policies in favor of creating collaborative environment.

Regarding my aforementioned blog post, feel free to copy-paste it, as an author I release this into CC0/public domain. Ask python-legal-sig if it is enough.

We cannot accept anything you produce until you sign the CLA.

Addition to bugs.html to describe submitting bugs via email

Same addition to the Python Dev Guide - seemed more appropriate on the tracker page vs. the triaging page.

I'd be just as happy to not document this.  The fact that you need an account first means that people will try to submit without an account, and get a bounce.  It also works better when people reply on the bug tracker rather than by email.  I'd not want to take the capability away, but I'd prefer to not document or encourage it.  That, however, is just my opinion.

I agree with David, I've noticed several messages recently that are mostly untrimmed replies to email so essentially have no actual content.

And I agree with David and Mark. Thanks for the attempt at a patch, Mike, but in hindsight we are going to have to turn down your contribution.