On Thu, Jun 12, 2008 at 1:31 PM, Gwoo <[EMAIL PROTECTED]> wrote: > But since we have the component in the core, it's > not going anywhere, and we are not going to include 3rd party > libraries, can we do something to match those features without > bloating Cake. My goal is for the Email component to solve the > majority of the needs. For example, not everyone needs to send 10,000 > emails per second. So, maybe this thread is more about an edge case > and I should just move on :)
I agree that the Email component should solve the majority of the needs and I think based on certain server configurations, it does. It can send out emails using PHP's mail implementation or using SMTP with certain server configurations. I do think the Email component needs to be more robust on how it handles EHLO, HELO, especially for AUTH handling. Beyond that, support for SIZE would be nice. PIPELINING is a special case, in my opinion, that can wait or be left for third party components to solve (which is what SwiftMailer likely uses). I can set up enhancement tickets for these requests. -Jonathan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
