Bug 3654 - "Remember password permanently" option
Summary: "Remember password permanently" option
Status: REOPENED
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: UI (show other bugs)
Version: 3.14.0
Hardware: All All
: P3 enhancement
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2016-06-16 13:22 UTC by Pierre Fortin
Modified: 2016-06-16 16:20 UTC (History)
0 users

See Also:


Attachments

Description Pierre Fortin 2016-06-16 13:22:18 UTC
Unless 'Remember password for this session' is checked, every POP poll asks for the account password -- what is the reasoning for not remembering a password beyond one poll per password request?  
Few [new] users will grok that logic -- I don't...

Upon startup, users are asked for each account's password; then still need to re-enter them via "Edit accounts..." -or- Cancel poll (each account), then Edit accounts so as not to have to enter passwords twice.

Change "Remember password for this session" option to "Remember password permanently".
Comment 1 Ricardo Mones 2016-06-16 14:06:04 UTC
If you wants passwords remembered forever wrote them on account configuration, is that simple.

'Remember password for this session' is for users which doesn't want to write passwords in the accountrc file, but don't want to be asked for account password on every retrieval while Claws Mail is running.

And some users doesn't trust neither disk nor memory and want to be asked every time for the password.
Comment 2 Pierre Fortin 2016-06-16 14:21:41 UTC
(In reply to comment #1)
> If you wants passwords remembered forever wrote them on account
> configuration, is that simple.

That wasn't my point since I wrote:   re-enter them via "Edit accounts..."

> 'Remember password for this session' is for users which doesn't want to
> write passwords in the accountrc file, but don't want to be asked for
> account password on every retrieval while Claws Mail is running.

But what about the users who've been happily relying on their passwords already existing in the accountrc file; but not being transferred to the new passwordstorerc?  In fact, I was on git 141 which used passwordstorerc, yet when moving to git 153, even those were deleted...

> And some users doesn't trust neither disk nor memory and want to be asked
> every time for the password.

I'd bet quite rare user(s) v. the typical user...  :)
Comment 3 Ricardo Mones 2016-06-16 14:41:08 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > If you wants passwords remembered forever wrote them on account
> > configuration, is that simple.
> 
> That wasn't my point since I wrote:   re-enter them via "Edit accounts..."

Ok.

> > 'Remember password for this session' is for users which doesn't want to
> > write passwords in the accountrc file, but don't want to be asked for
> > account password on every retrieval while Claws Mail is running.
> 
> But what about the users who've been happily relying on their passwords
> already existing in the accountrc file; but not being transferred to the new
> passwordstorerc?  In fact, I was on git 141 which used passwordstorerc, yet
> when moving to git 153, even those were deleted...

I think that change was announced by the developer:

http://lists.claws-mail.org/pipermail/devel/2016-May/001698.html

If you follow git you're exposed to this kind of things I'm afraid.

> > And some users doesn't trust neither disk nor memory and want to be asked
> > every time for the password.
> 
> I'd bet quite rare user(s) v. the typical user...  :)

:-)
Comment 4 Pierre Fortin 2016-06-16 15:45:28 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)

> If you follow git you're exposed to this kind of things I'm afraid.

True; but doing so doesn't make the point of preserving passwords through a rework less valid.  While Andrej did add the caveat:
   Also, your currently stored passwords are invalid, as of latest commit
   (54ce0e8). Sorry. :)
surely he didn't intend for non-git users to lose all their passwords between 3.13.2 and the next release... or did he?   My goal in this enhancement request was to point out that the new password system should not lose existing passwords if entered via the password request dialog.  In my case, it meant locating my hint file to recall the FOURTEEN active and different account passwords; I should have cancelled all the POP fetches and cut my password entry to 14 instead of 28; but hey... :)   Definitely won't be fun if this happens to everyone on the next release...

Don't get me wrong...  I love being on git to help test and provide feedback. :)
Comment 5 Andrej Kacian 2016-06-16 16:20:19 UTC
No, the idea is indeed to provide a seamless move to passwordrc for users upgrading from previous version. But that will only apply for next release. It's not worth it writing a migration code between two git versions, since at that stage, we were still iterating on the format of the file (and nobody says the format is final even now :) ).

Note You need to log in before you can comment on or make changes to this bug.