Zend Mail 2.0

Ideas for Zend\Mail 2.0 that still need to be converted into decent requirements
* Zend_Mail should represent an instance of an email.
* Support verp
* Use a common class that represents a server
* "make attachments more clever" (encoding)

Protocol features:
* EHLO keyword parsing [http://www.faqs.org/rfcs/rfc1869.html]
** PIPELINING support [http://www.faqs.org/rfcs/rfc1854.html], see ticket [ZF-8528|http://zendframework.com/issues/browse/ZF-8528]
** STARTTLS support [http://www.faqs.org/rfcs/rfc2487.html], see ticket [ZF-10758|http://zendframework.com/issues/browse/ZF-10758]
** ENHANCEDSTATUSCODES support - [1|http://www.faqs.org/rfcs/rfc1893.html] [2|http://www.faqs.org/rfcs/rfc2034.html]
* Support for IMAP ACL

Analysis of Zend_Mail 1.0
* When adding recipients name and email are filtered, and headers added. Making it hard to manipulate these once added.