You are viewing an old version of this page. View the current version.
Compare with Current |
View Page History
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
- STARTTLS support http://www.faqs.org/rfcs/rfc2487.html, see ticket ZF-10758
- ENHANCEDSTATUSCODES support - 1 2
- Support for IMAP ACL
Even more tentative:
- Signing (PGP, DKIM, ADSP)
- Templating (through Zend\View
) & batching - CSS Inlining (put all css in their respective elements) 1 2
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.
- When a returnpath is requested, the 'from' address is returned if no returnpath was specified. This is wrong. The returnpath should be set by the delivering mailserver only.
- The transports use properties rather than parameters. If only php supported threading there would be race conditions everywhere (for now, it's just unproper OOP).
Labels:
None