Bug 416942

Summary:	Typo and unclear TLS settings
Product:	[Applications] trojita	Reporter:	Damian Poddebniak <93s4m32gd2ab8ax6>
Component:	Desktop GUI	Assignee:	Trojita default assignee <trojita-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	aacid, lueck
Priority:	NOR
Version First Reported In:	0.7
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Damian Poddebniak 2020-01-30 12:39:38 UTC

Hello,

There seems to be a typo in the german translation of the IMAP and SMTP configuration.

The *english translation* is as follows:

SMTP
* No encryption
* Use encryption (STARTTLS)
* Force encryption (TLS)

IMAP
* No encryption
* Use encryption (STARTTLS)
* Force encryption (TLS)

The *german translation* is:

SMTP
* Keine Verschlüsselung
* Verschlüsselung verwenden (STARTTLS) // "verwenden" translates to "use"
* Verschlüsselung erzwingen (TLS) // "erzwingen" translates to "force"

IMAP
* Keine Verschlüsselung
* Verschlüsselung verwenden (STARTTLS)
* Verschlüsselung erzwingen (*STARTTLS*) // typo here


Can you also clarify what those options mean? Given that we have "use" and "force", it seems that the encryption over STARTTLS is optional?

Precisely, if Trojita is configured with "Use encryption (STARTTLS)", is it supposed to proceed in plaintext when the server does not advertise STARTTLS?

Thunderbird and other MUAs do it differently: they let you specify the method (STARTTL or TLS), but will enforce transition to STARTTLS.

Comment 1 Unknown 2020-02-14 07:46:19 UTC

SVN commit 1562256 by lueck:

fix german translation (STARTTLS -> TLS) reported by Damian Poddebniak, thanks

 M  +3 -3      trojita_common.po  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1562256

Comment 2 Albert Astals Cid 2021-10-18 20:39:31 UTC

Burkhard should this be marked as closed then?

Comment 3 Burkhard Lück 2021-10-19 06:19:29 UTC

From a translation point of view yes

Comment 4 Albert Astals Cid 2021-10-19 19:47:52 UTC

Damian i'm going to close this.

You made the mistake of reporting two issues in the same bug, which makes things un-trackable.

Since one of them is closed and the other one seems to not be, i encourage you to post a new bug with the new issue.