https://bugs.kde.org/show_bug.cgi?id=364021
Thomas Lübking <thomas.luebk...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Summary|Sending mails hangs at 50 % |qwwsmtp prefers AUTH PLAIN,
| |gmx announces PLAIN but
| |actually only supports
| |LOGIN. BOING.
Ever confirmed|0 |1
Status|NEEDSINFO |CONFIRMED
--- Comment #4 from Thomas Lübking <thomas.luebk...@gmail.com> ---
smtps is more robust than starttls (at least in the gmx.net case, because if
anything goes wrong they fell back to the unencrypted variant which was oc.
blocked ... ;-)
465 is smtps, so starttls will naturally fail.
That said, it fails. The server will timeout and afterwards you'll get:
SMTP <<< 334 421 gmx.com Service closing transmission channel - command timeout
SMTP <<< [authentication data]
Nuking AuthPlain in qwwsmtpclient.cpp (ie. enforcing LOGIN) works like a charm.
PLAIN authentication on gmail works like a charm.
=> gmx broke PLAIN authentication and it's unfortunately preferred by qwwsmtp.
Since LOGIN is announced first, kmail will likely just use that (for the order)
Seems to have been a problem on kmail around 2005 as well:
https://bugs.kde.org/show_bug.cgi?id=67797#c70
=> I guess it would be required to either allow config of the preferred
authentication or prefer the announced order (what could be just as much
troublesome) or walk them on each timeout (what's oc. outmost crap, sending a
mail could easily last 10 minutes - every time!)
--
You are receiving this mail because:
You are watching all bug changes.
