-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
keyring has broken user environment and scripts #173
Comments
@thekix I am adding this patch:
So, now any Debian user who wants to use keyring needs to menttion |
I added the patch to make keyring optional (Merge pull request #191 from WhyNotHugo/optional-keyring). Now it is working fine for you? Best Regards, |
@sudipm-mukherjee, it is fixed in a better maintained fork (and drop-in replacement) https://github.com/IMAPMirror/imapmirror |
@sudipm-mukherjee Please, try now with the latest changes. I think now this issue could be closed. |
General informations
offlineimap -V
): packaged from SHAd29a4dc459401f8a78e347cb0f8ae7670add0975
Configuration file offlineimaprc
Steps to reproduce the error
offlineimap -o
.ignore-keyring is False by default, and so offlineimap3 will check for password from keyring. So, all users will now need to modify their scripts or workflow to use offlineimap3. Since the new feature forces the users to modify their script/usage it should be considered as a regression.
Instead of ignore-keyring, there should have been an option
enable-keyring
and users who want to use keyring should have added it to their command or conf file. Since this is a new features, it is expected that users will need to modify their scripts to use it, instead of breaking all the other user's scripts.@thekix I am marking
enable-keyring
as True in Debian for now, so that it does not break user's scripts and enviroment. One of the user mailed me today about it and I can reproduce the problem.The text was updated successfully, but these errors were encountered: