Bug 356657 - Notification popups for authentication error misleading
Summary: Notification popups for authentication error misleading
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: UI (show other bugs)
Version: 5.5.2
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-14 09:26 UTC by OlafLostViking
Modified: 2023-01-27 05:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description OlafLostViking 2015-12-14 09:26:04 UTC
[This is for KMail 5.0.3, which is not selectable in the Version drop down.]

After updating to *5, KMail can no longer send out mails. I guess another configuration setting wasn't ported correctly. But the notification popup, which shows the server response on error, is a) too small to show the whole message (only the text telling me that the following - not visible - message was sent by the server is readable), b) disappears too fast/cannot be pinned to the foreground or reread in the notification area of plasma and c) cannot be logged to a file (I tried to log the notification of KMail and the SendLater agent into a logfile to be able to read the message, but no file is created at the given path).

Reproducible: Always
Comment 1 OlafLostViking 2015-12-14 10:38:39 UTC
Just to show how this can be a problem: the reason for me not being able to send an email was that the new KMail uses kwallet5 which didn't provide the correct password. But as KMail's popup told me my problem is the authtication *method* (PLAIN not supported...) and, as written above, the message from the server itself was not readable, I didn't expect any problems with my credentials. After changing the password manually sending emails works again.

Oh, and the popup is shown "anywhere" but not near or even in the notification area of Plasma. But that could also be a KWin or Plasma problem (as they both are struggeling a lot with multiple screens). I'm just mentioning it as this could lead to more people not even ever realising there was a message displayed. As this is an error message a modal dialog seems more appropriate. But that's another story ;-)
Comment 2 Denis Kurz 2017-06-23 20:17:26 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 OlafLostViking 2017-06-23 22:35:55 UTC
I am now using KMail 5.5.2 [not selectable in the version drop down].

After deliberately setting wrong passwords for receiving mails, a popup dialog is opened _in the background_ (behind Kontact). But at least it's telling me what's wrong and it won't disappear without interaction.

But setting a wrong password for the SMTP server still only triggers a notification and no dialog. And this says the server wouldn't support PLAIN (which is plain wrong ;-) ). The size of the notification is now big enough for me to read everything, though.
Comment 4 stakanov.s 2018-11-16 08:52:32 UTC
I am using Leap 15, Kmail 5.7.3 
When I did change the password of POP, as the SMTP password is not updated accordingly, the password was obviously wrong. 
However the error message you get is misleading saying: 
server error, message could not be sent. 

But it is a "Wrong Password or user, please check your settings" that would have been a sensible message. 
The user cannot therefore distinguish if the error is on the user side or server side. 

plasma 5.12.6
frameworks 5.45.0
QT 5.9.4
Comment 5 Justin Zobel 2022-12-13 02:53:59 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2022-12-28 05:26:13 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 stakanov.s 2022-12-28 09:01:22 UTC
Works for me, at least I can read the messages and it appears to have the right content now (like timeout when it is a timeout and wrong user or password when applicable. So taking this off my c/c list.
Comment 8 Bug Janitor Service 2023-01-12 05:16:03 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2023-01-27 05:08:54 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!