Version of Kmail now: 4.14.1 Version of KDE now: 4.14.2 I need help after doing an upgrade from Debian Wheezy to Debien Jessie. Upgrade went through without showing problems. After starting Kmail for the first time I was asking for passwords to all of my accounts. Opps. Ok, I went through this. All ok. Really? No. One password of an very old mailaccount by GMX wasn't accepted (but I was receiving mails daily from this account, so it was working). I tried it several times, but I can't connected to my account. I think, I saved not the last password in my files. My fault. :-( I looked around to find a file in my saved files before upgrading, which contains the passwords. The only file I found was mailtransports. In this file (for the SMTP) are all my passwords, but not to read, because encrypted. The part in this file for my GMX-Account contains it too, but not in the migrated file. The new file contains no area for the passwords. I have no chance to rebuild a new passwort by GMX, because this account is old and I have to pay money to GMX while I am calling then with a paid-telefonnumber. So I asking for a helping hand how I am able to decrypt my password from the file mailtransport. My searches in internet have had results, but all this results were old than 3 years. Nothing of the tipps and scripts give the right answers to my problem. How can I handle this? How can I decrypt my password? BTW: Sorry for my bad English. I hope you are able to understand my problem. Reproducible: Didn't try
Created attachment 101153 [details] screener from saved file mailtransports with password area
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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!
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!