Bug 43145

Summary: KMail stops trying to download new messages after first fail
Product: [Unmaintained] kmail Reporter: kvr
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: wishlist    
Priority: NOR    
Version: 1.4.1   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description kvr 2002-05-27 19:00:51 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kmail
Version:           1.4.1 (using KDE 3.0.1 )
Severity:          wishlist
Installed from:    Unspecified Linux
Compiler:          gcc version 2.95.4 20011002 (Debian prerelease)
OS:                Linux
OS/Compiler notes: Not Specified

In KDE2 KMail didn't report any failure when downloading mails. Now (KDE3) it shows dialog with user and password but when it shows it it stops to connect to any receive-accounts until user fills the dialog. Usually the download fails because of server overload and next try is successful. So... I think it's good to show the error but when user doesn't fill the dialog (he's sleeping etc ;) ) it simply should to retry on the background and if successful it should remove that dialog.


(Submitted via bugs.kde.org)
(Called from KBugReport dialog. Fields Application KDE Version OS Compiler manually changed)
Comment 1 Michael H 2002-05-27 19:17:50 UTC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 27 May 2002 21:00 kvr@centrum.cz wrote:
>
> In KDE2 KMail didn't report any failure when downloading mails. Now (KDE3)
> it shows dialog with user and password but when it shows it it stops to

The password dialog is not an error dialog.

If KMail doesn't know your password it obviously can't connect to your 
server. You can tell KMail to store that in its config file if you don't want 
to reenter it always.

> connect to any receive-accounts until user fills the dialog. Usually the
> download fails because of server overload and next try is successful.
> So... I think it's good to show the error but when user doesn't fill the
> dialog (he's sleeping etc ;) ) it simply should to retry on the background
> and if successful it should remove that dialog.

I don't fully understand what you want sorry.

Regards
Michael Häckel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE88oZge9KEPyN2R8URAo2eAJ9clZROLt5Cafbvl7HQ1Euj4Geg+gCfQPLT
OiFGJJ4BEdIvGYbjezQGLkc=
=xE34
-----END PGP SIGNATURE-----
Comment 2 Zbynek Vyskovsky 2002-05-27 20:38:43 UTC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 27 May 2002 21:17 Michael Häckel wrote:
> On Monday 27 May 2002 21:00 kvr@centrum.cz wrote:
> > In KDE2 KMail didn't report any failure when downloading mails. Now
> > (KDE3) it shows dialog with user and password but when it shows it it
> > stops to
>
> The password dialog is not an error dialog.
>
> If KMail doesn't know your password it obviously can't connect to your
> server. You can tell KMail to store that in its config file if you don't
> want to reenter it always.

 I typed it already so KMail does know the password the problem is that it 
shows the password dialog when the (pop3 for example) fails. Try the 
following:
Run KMail create pop3 account (set Check interval to one minute) and click 
on "Check Mail In" and type the password.
Then confuse KMail with incompatible protocol for example redirect it to 
ftp-port:
iptables -t nat -I OUTPUT -p tcp --dport pop3 -j REDIRECT --to-ports 21
On next check it fails and shows the password dialog although it was already 
typed. And stops receiving e-mails until user types the password again.

 As you said there is possibility to tell KMail to store it in config file 
it works then but first problem is security and another problem - user 
isn't informed if receive (connect auth ...) fails.

> > connect to any receive-accounts until user fills the dialog. Usually the
> > download fails because of server overload and next try is successful.
> > So... I think it's good to show the error but when user doesn't fill the
> > dialog (he's sleeping etc ;) ) it simply should to retry on the
> > background and if successful it should remove that dialog.
>
> I don't fully understand what you want sorry.

 I hope now it's better. As I was trying with password in config file I found 
out the problem above. So I think good solution would be: when receive 
fails don't show password dialog but error dialog and continue to connect 
and receive mails on the background. If the next one is successful hide that 
error dialog.

- -- 
Zbynek Vyskovsky
rat@atrey.karlin.mff.cuni.czhttp://atrey.karlin.mff.cuni.cz/~rat/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE88plXkEjKs0GDlxERAiJoAJwOgWcyWaHdCvIkOsJklfqTrtZMfACdH8nL
Fv/JB1ZB28822nMOqYqj0yE=
=WEK7
-----END PGP SIGNATURE-----
Comment 3 Michael H 2002-05-28 05:59:32 UTC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 27 May 2002 22:38 Zbynek Vyskovsky wrote:
>
>  I typed it already so KMail does know the password the problem is that
> it shows the password dialog when the (pop3 for example) fails. Try the
> following:
> Run KMail create pop3 account (set Check interval to one minute) and
> click on "Check Mail In" and type the password.
> Then confuse KMail with incompatible protocol for example redirect it to

This is intended behaviour.

The problem is that the POP3 protocol doesn't allow the mail client to 
distinguish if the password was wrong or the login failed for some other 
reason.

In KDE 2.x there was the problem that if the user entered the password wrong 
he did have to restart KMail in order to type the correct one.

If the password is stored in the configuration KMail assumes that the 
password is most likely correct but the problem is elsewhere. If the password 
is entered every time KMail assumes that the password is wrong.

However maybe not asking again if the login was successful at least once 
could slightly improve the situation.

Regards
Michael Häckel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE88xzHe9KEPyN2R8URAg1hAJ0eyNykdrhq36B2GTGXUTvT0Dx5GQCeNBjs
7umLf+MHKxOxCuEKDnclUBI=
=yJqt
-----END PGP SIGNATURE-----
Comment 4 Thomas McGuire 2007-06-25 13:00:25 UTC

*** This bug has been marked as a duplicate of 39097 ***