@thecodeassassin No I that is not what I meant.
The philosophy behind Phalcon is to create a PHP framework that is fast and can deliver its functionality immediately without any additional file scans, injections of modules etc. It is also designed in such a way whereas its components (well most of them) can be used as glue components i.e. you only use what you need. This way components don't necessarily slow each other down if used properly.
Now a mail component could very well be a good addition to the feature list, but it doesn't offer performance because it doesn't only depend on the hardware Phalcon is installed, it is also dependent on the network traffic.
So if for instance you have Zend Mail and you construct a message, that will be
- several file scans and includes
- a few lines of code on your part to construct the message
- Zend Mail constructing the mail transport class (which could be localhost or other server)
- Zend Mail sending the message
- Reporting back errors if any
If we had the same component in Phalcon, performance would be increased only in steps 1 and 2. The remaining steps would depend on network traffic, For instance #3, constructing the mail transport class, yes the creation of the class would be fast but if you are connecting to a different SMTP server and you have delays on the network layer, your component, whether it is Zend or Phalcon Mail will perform slowly. Same with #4 and #5.
It all depends on how critical the mail component is to your application. My guess would be that Zend Mail or even Swiftmail would be sufficient providing that your network is top notch :)