[kmail2] [Bug 350555] Unable to handle quotation marks in »To« field.
https://bugs.kde.org/show_bug.cgi?id=350555 Bernhard Scheirle changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Version|5.5.2 |5.21.2 --- Comment #8 from Bernhard Scheirle --- Reproduced with kmail2 5.21.2 (22.08.2) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 350555] Unable to handle quotation marks in »To« field.
https://bugs.kde.org/show_bug.cgi?id=350555 Justin Zobel changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #7 from Justin Zobel --- Thank you for reporting this issue 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! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 350555] Unable to handle quotation marks in »To« field.
https://bugs.kde.org/show_bug.cgi?id=350555 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED Version|4.14.2 |5.5.2 --- Comment #6 from Christoph Feck --- Thanks for the update; reopening. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 350555] Unable to handle quotation marks in »To« field.
https://bugs.kde.org/show_bug.cgi?id=350555 --- Comment #5 from Bernhard Scheirle --- Still reproduce able in kmail2 5.5.2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 350555] Unable to handle quotation marks in »To« field.
https://bugs.kde.org/show_bug.cgi?id=350555 Denis Kurz changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Denis Kurz --- This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.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 oportunity 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. -- You are receiving this mail because: You are watching all bug changes.
