Accept utf_8 as utf-8
An inspect function for Mail::Field

Before this, Mail::Fields just defaulted to .to_s, which was
both confusing to read and potentially side-effecty.
Fix 8bit decoding on jruby-1.7.4 [Fixes #570]
Merge branch 'accept_utf_8-as-utf-8' of github.com:gauteh/mail
Add ruby-1.8 support to Pull request #562
Move tasks out of lib/ to avoid namespace pollution Issue #566
Move VERSION out of lib/, [Fixes #566]
Always use an SSL context. [Fixes #548]

This reverts commit 9890b197c51f1d340fa7275aa4bc17103746657b, as latest
patch releases of 1.8.7 do accept an OpenSSL context object.

This has been broken since the refactoring d6e25e5e37e6d591f94cc04a2a52c1128fde81db,
which increased the scope of the original breakage.
Fixing #523 with a rdoc --exclude param
Added cc matcher
Merge pull request #583 from rwestgeest/master

I have added a cc matcher in has_sent_mail
Add more charsets from our internal list
Merge pull request #576 from srawlins/add-rdoc-exclude-to-gemspec

Fixing #523 with a rdoc --exclude param
Add simple header example to readme
Merge pull request #588 from ahawkins/patch-1

Add simple header example to readme
Don't pass charset from headers on to fields.

If you do then all the headers after the Content-Type: header will
inherit any encoding set on that line.

At the moment Mail::Field.new defaults to UTF-8 which is arguably the
correct value (according to RFC 5335).

We could attempt to keep headers as BINARY if we're not mutating them,
however this would require annoyingly large changes; and the practical
benefit is not clear as the mail gem seems to silently work with invalid
UTF-8 in field values (it uses rfc-2047 encoding with "ASCII-8BIT",
and while I doubt that that is a valid thing to do, it probably doesn't
matter for us).