#4687: EmailComponent should do EHLO and try with HELO if it fails
----------------------------------------------------+-----------------------
    Reporter:  joaquin_win                          |         Owner:          
        Type:  Enhancement                          |        Status:  reopened
    Priority:  High                                 |     Milestone:  1.2.x.x 
   Component:  Components                           |       Version:  RC1     
    Severity:  Critical                             |    Resolution:          
    Keywords:  email smtp helo ehlo authentication  |   Php_version:  n/a     
Cake_version:  6949                                 |  
----------------------------------------------------+-----------------------
Comment (by kelvin):

 I'm using 7690 of email.php and HELO breaks SMTP Authentication with
 cPanel's default SMTP server, ESMTP Exim 4.69.

 It seems that version of Exim requires a "EHLO" before AUTH command, or it
 will reply that "AUTH" wasn't advertised. (should you do "HELO", then
 "HELO", it also works).

 My quick hack is to rename HELO to EHLO inside email.php, but I'm sure
 someone has a better way of doing the fix.

-- 
Ticket URL: <https://trac.cakephp.org/ticket/4687#comment:9>
CakePHP : The Rapid Development Framework for PHP <https://trac.cakephp.org/>
Cake is a rapid development framework for PHP which uses commonly known design 
patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC. 
Our primary goal is to provide a structured framework that enables PHP users at 
all levels to rapidly develop robust web applications, without any loss to 
flexibility.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"tickets 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/tickets-cakephp?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to