https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #14 from Jan Kundrát ---
Git commit 0993c644234391625bda12ad3fac85e8e97aa875 by Jan Kundrát.
Committed on 10/03/2019 at 13:08.
Pushed by gerrit into branch 'master'.
Improve port number warnings
The SSL/TLS/STARTTLS distinction appears to
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #13 from Jan Kundrát ---
FYI, a patch series which attempts to clear some of these warnings:
https://gerrit.vesnicky.cesnet.cz/r/#/q/topic:bug-404211
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=404211
Jan Kundrát changed:
What|Removed |Added
Resolution|UPSTREAM|NOT A BUG
--- Comment #12 from Jan Kundrát ---
(
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #11 from Filipe Azevedo ---
Fine, will test that with 5.13 at time.
Thanks for the support !
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #10 from Thomas Lübking ---
The config is probably misleading, but I'm pretty sure gmail won't do STARTTLS
on 465 (you can wireshark what's going on)
I assume the issue at hand to be Qt w/o 1.3 support running into an 1.3
supporting openssl
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #9 from Filipe Azevedo ---
The Trojita GUI does not specify SSL at all, it has:
- Use encryption (STARTTLS)
- Force encryption (TLS)
Hence I selected the expected port 587 from the support page for gmail.
My distribution is using Qt 5.12.1
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #8 from Thomas Lübking ---
465 *is* SSL, you'll not use STARTTLS on it (no idea about the trojitá config
GUI suggesting something different?)
So this is a TLS version conflict (and 1.3 mess), can one see your distros
downstream patches to Qt
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #7 from Filipe Azevedo ---
Ah, just tested TLS port 465 for smtp and it worked fine !
Which is weird, google support page say 465 if for ssl.
See https://support.google.com/mail/answer/7126229?hl=en
So I guess my configuration was not wrong
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #6 from Filipe Azevedo ---
I do use those imap/smtp configurations:
* imap: TLS on imap.gmail.com:993
* smtp: TLS on smtp.gmail.com:587
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #5 from Thomas Lübking ---
Looks like TLS/1.3 but Qt 5.12 should not even support that…
Do you use smtp on port 465 or port 587?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #4 from Filipe Azevedo ---
I did a full uninstall/resintall/restart of the package, the full output log
clearly state it initiate ssl upon connection opening and correctly handle
initial sychronization, only message sending fails.
Could it b
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #3 from Filipe Azevedo ---
I did test again, and the error still occurs.
Still i can read / load content being hosted on secure servers (ie, loading
https images by examples).
Here is the output log:
17:15:44.765 Submission STATE_INIT
17:1
https://bugs.kde.org/show_bug.cgi?id=404211
--- Comment #2 from Filipe Azevedo ---
Hm, the problem is ... only Trojita is having ssl issues.
No other Qt apps nor KDE apps do have ssl issues.
I can by example use KMail with the same gmail account, browse sftp / ssh
remotes machines without issues
https://bugs.kde.org/show_bug.cgi?id=404211
Jan Kundrát changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
14 matches
Mail list logo
