bring along computed charset while setting content type for unicode bodies
comment
no need to support py2.5 anymore, so simplify tests, making them pass on 3.X
- response.MIMEPart now correctly sets the charset of the email payload if it's
  one of the content_type parameters of the Message or Attachment.

- Add a functest that emulates what happens when you call send_to_queue.
make the correct assertions
- Allow charset header to be set in content-type passed to Attachment
  constructor.

- Don't permit a text body to be set when creating a non-text attachment.

- Add an attach_binary method to a response.

- Encode the body properly on Python 2 in the various attach_* methods in a
  response.

- Encode the body properly within the to_message method of a response.

- Transfer-encode the body properly within the extract_payload method of a
  response.

- About to lose my shit.
accept other spellings for quopri, raise an exception for an unknown encoding
nope, must be that spelling
simplify transfer_encode_string
conditionalize setting charset on whether it has a valid value
centralize the straddling code madness
throw encodingerror instead of invalidmessage in appropriate places
import encodingerror from its canonical location
coverage
79 chars
comment
79 chars
use newer import form
comments
coverage for the mailer module