Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

No connection to the SMTP server of AWS SES possible (authentication method)

  • 4 Antworten
  • 1 hat dieses Problem
  • 1 Aufruf
  • Letzte Antwort von komandar

more options

I am currently trying to set up extra SMTP servers for additional identities in my e-mail account. I would like to use the Amazon service for this.

However, as soon as I try to send an email with the data provided by AWS, I get an error message:

"Sending of the message failed. The Outgoing server (SMTP) <ses-smtp-server-url> does not support the selected authentication method. Please change the 'Authentication method' in 'Account Settings | Outgoing Server (SMTP)'."

Changing the "Authentication method" did not work either. If I enter the same data in gmail as "Send mail as" (the equivalent to the extra identity of Thunderbird), the connection in the GUI of gmail works without any problems and I can send e-mails via it. So it can't be the data or the configuration of the SES.

I am afraid that Thunderbird does not yet support the newer protocols that SES requires. Does anyone here have any ideas?

Server: <ses-smtp-server-url> Port 587 Connection security: STARTTLS Auth. method: Encrypted password User Name: <username>

I am currently trying to set up extra SMTP servers for additional identities in my e-mail account. I would like to use the Amazon service for this. However, as soon as I try to send an email with the data provided by AWS, I get an error message: "Sending of the message failed. The Outgoing server (SMTP) <ses-smtp-server-url> does not support the selected authentication method. Please change the 'Authentication method' in 'Account Settings | Outgoing Server (SMTP)'." Changing the "Authentication method" did not work either. If I enter the same data in gmail as "Send mail as" (the equivalent to the extra identity of Thunderbird), the connection in the GUI of gmail works without any problems and I can send e-mails via it. So it can't be the data or the configuration of the SES. I am afraid that Thunderbird does not yet support the newer protocols that SES requires. Does anyone here have any ideas? Server: <ses-smtp-server-url> Port 587 Connection security: STARTTLS Auth. method: Encrypted password User Name: <username>

Ausgewählte Lösung

I had tried several variations as described above and the error message above was for trying the Encrypted Password auth method.

In the meantime I seem to have a solution for the problem. The error lies with the (Linux client of) Thunderbird. It seems that the change of an SMTP or IMAP entry is only applied if you close the application completely after the change and reopen it.

It's a bit awkward but then it works.

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (4)

more options
more options

Thanks for your reply, but unfortunately not.

I had already seen the article but had just checked the settings again as stated in the article. Unfortunately without success. There are not many variations of the SMTP settings... I first thought it might be due to the TLS protocol. But according to the AWS website they support version 1.2 and 1.3 which as far as I can see in the config:// settings Thunderbird can also use.

I also tried to establish a local connection to the SMTP server using telnet. This also worked. It must therefore probably be an error with Thunderbird.

Geändert am von komandar

more options

I just wonder where you got the idea that an encrypted password was supported. The instructions David posted are clear on the authentication method being normal password. Given the error is that the chosen authentication method is not supported, I suggest you use the supported method.

more options

Ausgewählte Lösung

I had tried several variations as described above and the error message above was for trying the Encrypted Password auth method.

In the meantime I seem to have a solution for the problem. The error lies with the (Linux client of) Thunderbird. It seems that the change of an SMTP or IMAP entry is only applied if you close the application completely after the change and reopen it.

It's a bit awkward but then it works.