Version: (using Devel) Installed from: Compiled sources Forwarded from https://bugzilla.novell.com/show_bug.cgi?id=536643: Knode retrieves the article list for a newsgroup, sorts it and displays a list of articles available to read. After the user selects one, Knode uses the message ID of the article to retrieve it from the news server. In the case where an article message ID contains square brackets, these are stripped from the message Id and the now invalid message ID is requested, resulting in a 430 error being returned. As an example, a poster to the demon.service newsgroup using the identity "Wm.." uses message IDs with the right-hand side @[127.0.0.1]. These articles can't be read using Knode as Knode requests message IDs with the RHS as @127.0.0.1. In the displayed error message, the link to Google groups also strips the square brackets. Reproducible: Always Steps to Reproduce: 1. subscribe to a newsgroup where a user is using square brackets in message ID. 2. retrieve the list of articles in the group 3. select an article with the square brackets in the RHS of the message ID Actual Results: Knode displays an error with a clickable link to Google saying: An error occurred. The article you requested is not available on your news server. You could try to get it from groups.google.com. Expected Results: The article should be correctly displayed.
Created attachment 37063 [details] Test case
The issue is in the kmime component of kdepimlibs, I'm reassigning. Nevertheless, note that as a consequence of fixing bug #193550, articles are no more fetched using their messageId, so this issue will only show up when an article is fetched using the menu "Edit >> Fetch article with ID...".
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.