Project

General

Profile

Actions

Bug #96878

open

smtp transport port problem and ssl-protocol

Added by Sabine Deeken about 2 years ago. Updated about 2 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2022-02-14
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
7.4
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Hi,
We have a smtp mail problem since december, it makes me mad..
in V9.5 and even V10, at the beginning, we sent mails via smtp and port 587, via starttls as I presume.
'transport_smtp_encrypt' => 'tls',//later we tried false, also not working;
error:

Failed to find an authenticator supported by the SMTP server

we switched back to sendmail. but we want smtp.
we try again:
I found out that during the outlook-Problems end 202 security on the outlook-Server had been improved,
the mail-host and the webspace host are both sure they support TLSv1.2, but the webspace hoster told me to switch to port 465 on which they would normaly deliver TLSv1.2 and not STARTTLS like on port 587. (->failed to find authenticator..)

So I tried port 465, but then we get the other error:

Connection could not be established with host "ssl://exchange.mydomain.de:465": stream_socket_client(): unable to connect to ssl://exchange.mydomain.de:465 (Connection timed out)

'transport_smtp_encrypt' true or false doesn't matter, it's always ssl.
and there is the problem: our exchange-server doesn't support ssl. https or smtp or some others would work..
is there a chance to configure the protocol?
with the best regards,
Sabine

Actions #1

Updated by Stefan Bürk about 2 years ago

Just some toughts.

MS has added OAUTH2 for there services to there products and rolled them out. So at least for MS OFFCICE365 and so on the already enforces the OAUTH2 authentication for new customers etc. And I read a blog post that they wanted to enforce this for SMTP also.
I'm not a exchange admin oder user, but maybe the authenticator things changed ? As this is wat the first message is telling you. The server connection is etablished, but the "AUTH " lines recieved from the server do not contain a valid Authenticate the mail library has.
Maybe check there with your exchange admin first ?

Beside's this, there has been a fix in v10 for the flag transport_smtp_encrypt ... and a ne feature for v12/main regarding mail settings, encryptions and SSL verificatins .. but all not for the v9 which is in ELTS anyway.

Actions

Also available in: Atom PDF