I tried to launch kmail 5.0.1 (not in the version list) after having installed and configured ibus. Pinetry would say that I could not unlock kwallet even if the correct password was provided. Since, I completely removed ibus and the files it created in my $HOME. I relaunched kmail and I had to toggle between "Work offline" and "work online" to be able to check the mail on the configured IMAP again. Now, when I create a new message, it just stays in the outbox. I tired "File->Send queued messages" and "File->Send queued messages via" the configured SMTP to no avail. I also tried completely deleting my SMTP resource and created a new one. This also did not help. If I start kmail from konsole, the only output I see when I click on Send queued message is : log_messagecomposer: Sending queued message with custom transport: -1 log_mailtransport: Fetching collection 26 log_mailtransport: Traversing 3 items. log_mailtransport: No subjobs; I am done log_mailtransport: succeeded. Reproducible: Always Steps to Reproduce: 1. Create a new message 2. Type a valid address in the "To:" field 3. Click on send button Actual Results: Message shows up as a new message in Local Folders->outbox and just stays there Expected Results: The message might show up in Local Folders->outbox, but should be sent out by the configured STMP transport almost instantly and then moved to the configured "sent" folder
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.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.