@~ Sure, but gmail to gmail would be [encrypted from gmail user to google] (google does whatever the fuck they want) [encrypted from google to other gmail user]

@Jeremy Young, all traffic is encrypted over https. Note in gmail, opening this panel is a bit different. click on the gear, then settings -> "Accounts and Import" -> "Other Google Account Settings" https://s3.amazonaws.com/beta/settings.png

Seems to me there are three levels. 1) read docs. 2) read source. 3) write it yourself. Obviously each involves more time that could be spent doing other things; the ideal if you are using a common tool is to have good docs. But it's facile to suggest that one should just read the source when encountering a problem implementing a program, plugin, module, what have you. Am I going to read ffmpeg source when it borks in ./configure? Probably not. Will I use an un-minified jquery plugin to trace the source of an error? Almost always. Sometimes reading source is a really good idea. Other times it means you are looking in the wrong place for your solution. Ask the bear. If the bear won't answer, then read the source.