SmtpMailer: add support for AUTH PLAIN#31
Conversation
|
I wonder how did you manage accidentally set the executable flag on the file 😄 |
|
https://tools.ietf.org/html/rfc2595#section-2.3 may be related. |
| $this->write(base64_encode($this->password), 235, 'password'); | ||
| $authMechanisms = []; | ||
| foreach (preg_split("~\r?\n~", $ehloResponse) as $line) { | ||
| if (strpos($line, '250-AUTH ') === 0) { |
There was a problem hiding this comment.
shouldn't this be 250 AUTH? EDIT: https://tools.ietf.org/html/rfc4954#section-4.1 uses both so I don't really know
|
... some Windows magic I guess, I don't usually push code on this computer so it got a bit clumsy :D I will try to fix it ... How should the STARTTLS be related? If it is required and for some reason it fails to activate then the execution stops - the credentials are never sent. The space after return code is used to indicate the last line of the response. The link you posted is a good example of that. |
|
Thanks for pointing out the space vs dash issue - I updated the implementation to count with both of them (because the AUTH can also be the last line of the response). And btw the +x flag was set by PhpStorm on Windows ... I don't know why but it happened again. Weird. |
| $authMechanisms = explode(' ', trim($matches[1])); | ||
| } | ||
|
|
||
| if (array_search('PLAIN', $authMechanisms, true) !== false) { |
There was a problem hiding this comment.
can be simplified with in_array
Also now it uses PLAIN auth whenever possible, shouldn't we prefer LOGIN auth when both plain and login auth are allowed?
There was a problem hiding this comment.
Alright, I will change it to in_array.
I also though about it and I don't think that there is a reason to prefer LOGIN mechanism over PLAIN. They both offer same security. The PLAIN mechanism will be just a bit faster ... correct me if I'm wrong.
|
Thanks |
3 participants
It's strange that there are some SMTP servers not supporting the LOGIN mechanism but I stumbled upon one ... so here is the fix :)