From removed-gdpr at example.com Sat Dec 1 09:51:42 2018 From: removed-gdpr at example.com (Removed after GDPR request) Date: Sat, 1 Dec 2018 10:51:42 +0200 Subject: [Users] Replies appear as unread in ignored thread In-Reply-To: <20181127185620.56f0ac79@localhost> References: <20181127185620.56f0ac79@localhost> Message-ID: <20181201105142.3c873cd1@localhost> It keeps happening (attached screenshot). Can anyone comment please? -- George -------------- next part -------------- A non-text attachment was scrubbed... Name: 2018-12-01-10-50-30-screenshot.png Type: image/png Size: 28623 bytes Desc: not available URL: From noreply at thewildbeast.co.uk Sat Dec 1 22:03:07 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sat, 01 Dec 2018 21:03:07 +0000 Subject: [Users] [Bug 4130] New: Please reconsider merging the patch syntax highlight Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4130 Bug ID: 4130 Summary: Please reconsider merging the patch syntax highlight Classification: Unclassified Product: Claws Mail Version: other Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P3 Component: UI/Message View Assignee: users at lists.claws-mail.org Reporter: kubakici at wp.pl Three years back I submitted a patch to highlight git --diff syntax in-line inside email bodies. It was rejected due to fear of false positives. I've used it since and never had a false positive. I have also found that other people have very similar patches on GitHub, which makes me thinks its a popular feature. I have had a quite a few of my coworkers start using my fork of Claws just to get the patch coloring, and subsequently go back to Thunderbird because of the extra hassle of having to compile from source and rebase. I think it would be a really good thing for the project if the feature got merged. Patches are available here: https://github.com/kuba-moo/claws-mail/commit/ed5adc67276e7ee0e50c031daccfddcc92488e30 https://github.com/kuba-moo/claws-mail/commit/36300a476c2dc401dd78e3396a6b19848041c08f Please let me know if I can improve them somehow. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sat Dec 1 22:57:38 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sat, 01 Dec 2018 21:57:38 +0000 Subject: [Users] [Bug 4130] Please reconsider merging the patch syntax highlight In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4130 --- Comment #1 from Paul --- Can you attach the patches here, please? -- You are receiving this mail because: You are the assignee for the bug. From bdm at fenrir.org.uk Sun Dec 2 01:00:27 2018 From: bdm at fenrir.org.uk (Brian Morrison) Date: Sun, 2 Dec 2018 00:00:27 +0000 Subject: [Users] Replies appear as unread in ignored thread In-Reply-To: <20181201105142.3c873cd1@localhost> References: <20181127185620.56f0ac79@localhost> <20181201105142.3c873cd1@localhost> Message-ID: <20181202000027.00006925@prost.fenrir.org.uk> On Sat, 1 Dec 2018 10:51:42 +0200 Removed after GDPR request wrote: > It keeps happening (attached screenshot). > Can anyone comment please? > Are you seeing this happen in only this folder? Could there be something unusual about the headers for messages in the list? I don't know how the thread ignore function works, but it clearly has to re-assess the state of the messages as the folder is opened after a thread has a new message added to it. If that process happens in the wrong order then it won't work, but if it is only this folder and/or list mail that causes it I would be looking for something different in the headers. HTH -- Brian From noreply at thewildbeast.co.uk Sun Dec 2 01:59:42 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 00:59:42 +0000 Subject: [Users] [Bug 4130] Please reconsider merging the patch syntax highlight In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4130 --- Comment #2 from Jakub Kiciński --- Created attachment 1939 --> https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=1939&action=edit small fix for diff detection from git -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 02:00:22 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 01:00:22 +0000 Subject: [Users] [Bug 4130] Please reconsider merging the patch syntax highlight In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4130 --- Comment #3 from Jakub Kiciński --- Created attachment 1940 --> https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=1940&action=edit the actual feature -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 10:17:42 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 09:17:42 +0000 Subject: [Users] [Bug 4130] Please reconsider merging the patch syntax highlight In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4130 --- Comment #4 from wwp --- Interesting, I'm currently running CM w/ this patch applied, will see if I get false positives or negatives. BTW, some changes in 3.16.0-191-g0c28ce4 may indicate that it would be better to match all known signatures instead of checking for "-- \n" only. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 11:34:10 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 10:34:10 +0000 Subject: [Users] [Bug 4131] New: Per feed proxy preference Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4131 Bug ID: 4131 Summary: Per feed proxy preference Classification: Unclassified Product: Claws Mail Version: GIT Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P3 Component: Plugins/RSSyl Assignee: users at lists.claws-mail.org Reporter: removed-gdpr at example.com Currently RSSyl does not have a setting for using proxy or not. As discussed in the mailing list to use Tor (local running service) one has to set: export http_proxy=socks5://127.0.0.1:9050 export https_proxy=socks5://127.0.0.1:9050 and then run Claws Mail. However certail RSS feeds don't work with Tor (sites using Cloudflare recaptcha etc). It would be good to have an option to control the default (global) RSSyl proxy setting as well as individual setting for each feed (i.e. to use proxy or not). -- You are receiving this mail because: You are the assignee for the bug. From removed-gdpr at example.com Sun Dec 2 11:41:23 2018 From: removed-gdpr at example.com (Removed after GDPR request) Date: Sun, 2 Dec 2018 12:41:23 +0200 Subject: [Users] Replies appear as unread in ignored thread In-Reply-To: <20181202000027.00006925@prost.fenrir.org.uk> References: <20181127185620.56f0ac79@localhost> <20181201105142.3c873cd1@localhost> <20181202000027.00006925@prost.fenrir.org.uk> Message-ID: <20181202124123.584ae97e@localhost> On Sun, 2 Dec 2018 00:00:27 +0000 Brian Morrison wrote: > Are you seeing this happen in only this folder? Yes. > Could there be something unusual about the headers > for messages in the list? Like what? > I don't know how the thread ignore function works, > but it clearly has to re-assess the state of the > messages as the folder is opened after a thread has > a new message added to it. I have noticed that ignore thread works without having to open a folder. So my understanding is that it does not evaluate upon opening a particular one. But just like you I don't know the inner workings of it. > looking for something different in the headers. For the messages from the last screenshot: Message #1 (marked as "ignore thread"): Message-ID: Message #2 (reply to #1, not marked as "ignore thread"): References: In-Reply-To: Date: Fri, 30 Nov 2018 11:38:32 -0800 Message-ID: Message #3 (reply to #2, also not marked as "ignore thread"): References: In-Reply-To: Date: Fri, 30 Nov 2018 11:51:07 -0800 X-Gmail-Original-Message-ID: Message-ID: -- George From noreply at thewildbeast.co.uk Sun Dec 2 11:50:00 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 10:50:00 +0000 Subject: [Users] [Bug 4132] New: "Mark all as (un)read" dialog appears when acting on 1 message only Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4132 Bug ID: 4132 Summary: "Mark all as (un)read" dialog appears when acting on 1 message only Classification: Unclassified Product: Claws Mail Version: GIT Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P3 Component: Folders Assignee: users at lists.claws-mail.org Reporter: removed-gdpr at example.com version 3.17.0git188 STR: 1. Open a folder (mail or RSSyl) containing only 1 message 2. Click to select the message 3. Message->Mark->Mark as read (or as unread) EXPECTED: The message should be marked as read (or as unread, respectively) because it is already selected and the action is performed on it only. ACTUAL: The "Mark all as (un)read" dialog box appears asking "Do you really want to mark all mails in this folder as read?" -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 12:01:28 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 11:01:28 +0000 Subject: [Users] [Bug 4132] "Mark all as (un)read" dialog appears when acting on 1 message only In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4132 Paul changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|PC |All OS|Windows NT |All -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 12:13:08 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 11:13:08 +0000 Subject: [Users] [Bug 4132] "Mark all as (un)read" dialog appears when acting on 1 message only In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4132 wwp changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|All |PC OS|All |Windows NT --- Comment #1 from wwp --- What you describe is a bit wrong or fuzzy. Your scenario mentions, at step 3: Message->Mark->Mark as read. But the "Mark all as read" dialog you're dealing with is bound to the feature Message->Mark->Mark ALL as read (see the ALL) (and the recursive one). Note that this "Mark all as read", whatever called from the Message menu or a folder's context menu, will show the confirmation dialog whatever "all" implies 1 or 2 or 3 or.. any amount of messages in folder, selected or not. It's about marking all messages in folder, not all *selected* messages. And you'll get the dialog until you uncheck "Show this message next time" in it (or uncheck "Confirm when marking all messages as read or unread" in the preferences Display->Summaries->Message list. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 12:15:15 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 11:15:15 +0000 Subject: [Users] [Bug 4132] "Mark all as (un)read" dialog appears when acting on 1 message only In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4132 wwp changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|PC |All OS|Windows NT |All -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 12:17:35 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 11:17:35 +0000 Subject: [Users] [Bug 4132] "Mark all as (un)read" dialog appears when acting on 1 message only In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4132 wwp changed: What |Removed |Added ---------------------------------------------------------------------------- Version|GIT |3.17.0 --- Comment #2 from users at lists.claws-mail.org --- Changes related to this bug have been committed. Please check latest Git and update the bug accordingly. You can also get the patch from: http://git.claws-mail.org/ ++ ChangeLog 2018-12-02 12:16:06.992698541 +0100 http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=f21dc9270747cba5f1a99051984f04d71455ae1d Author: Paul Date: Sun Dec 2 11:15:11 2018 +0000 fix bug 4132, '"Mark all as (un)read" dialog appears when acting on 1 message only' -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 12:40:40 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 11:40:40 +0000 Subject: [Users] [Bug 4132] "Mark all as (un)read" dialog appears when acting on 1 message only In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4132 Paul changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 12:41:53 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 11:41:53 +0000 Subject: [Users] [Bug 4132] "Mark all as (un)read" dialog appears when acting on 1 message only In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4132 --- Comment #3 from wwp --- Sorry George, I miserably failed in seeing that corner case, by not believing your: when a folder contains only one message, there's always a selection (that's what I didn't expect) and the selection is equal "all messages" (obviously). This condition raises the dialog, it should not. Paul fixed the case, thanks for reporting! -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 12:56:07 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 11:56:07 +0000 Subject: [Users] [Bug 4132] "Mark all as (un)read" dialog appears when acting on 1 message only In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4132 Removed after GDPR request changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #4 from Removed after GDPR request --- No problem wwp, it happens. I have rebuild CM (using version 3.17.0git193 now) and I notice that "Mark as read" works fine now. However "Mark as unread" still works the old (wrong) way (i.e. like "Mark all as unread"). Would you guys please consider fixing that one too? Thanks. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 13:15:44 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 12:15:44 +0000 Subject: [Users] [Bug 4132] "Mark all as (un)read" dialog appears when acting on 1 message only In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4132 Paul changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #5 from users at lists.claws-mail.org --- Changes related to this bug have been committed. Please check latest Git and update the bug accordingly. You can also get the patch from: http://git.claws-mail.org/ ++ ChangeLog 2018-12-02 13:14:02.758381853 +0100 http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=7d856421906969bedfae33f12d930fb91446ac24 Author: Paul Date: Sun Dec 2 12:13:45 2018 +0000 complete fix for bug 4132 -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 13:30:11 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 12:30:11 +0000 Subject: [Users] [Bug 4130] Please reconsider merging the patch syntax highlight In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4130 --- Comment #5 from Olivier Brunel --- For what it's worth, I've been running claws with those patches for years now without (noticing) any issues. Great addition IMO. Also for reference, original bug is: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3035 -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 13:35:57 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 12:35:57 +0000 Subject: [Users] [Bug 3035] Enhance diff coloring to git patches In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3035 Paul changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Paul --- *** This bug has been marked as a duplicate of bug 4130 *** -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 13:35:57 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 12:35:57 +0000 Subject: [Users] [Bug 4130] Please reconsider merging the patch syntax highlight In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4130 --- Comment #6 from Paul --- *** Bug 3035 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 2 16:20:28 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 02 Dec 2018 15:20:28 +0000 Subject: [Users] [Bug 4132] "Mark all as (un)read" dialog appears when acting on 1 message only In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4132 --- Comment #6 from Removed after GDPR request --- Excellent. Thanks Paul! -- You are receiving this mail because: You are the assignee for the bug. From ricardo at mones.org Sun Dec 2 18:16:39 2018 From: ricardo at mones.org (Ricardo Mones) Date: Sun, 2 Dec 2018 18:16:39 +0100 Subject: [Users] Clawsker 1.3.0 released Message-ID: <20181202181639.0705b021@busgosu> Hi all, Clawsker, the Claws Mail hidden preferences editor and tweaker has been released again. This version requires Perl bindings to GTK+3 and a non-core module to finding the claws-mail binary in a more portable way. Check the Dependencies section in README file for required versions. Changes shamelessly copied from the NEWS file: 1.3.0: - Migrated to GTK+3 perl bindings - Migrated UI layouts to new GtkGrid widget - Reimplemented about dialogue using GTK+3 AboutDialog - Hotkey background stripes now use theme colours - Fixed bug detecting unapplied changes - Fixed window height to fit common resolutions (4128) - Translations: • New: Portuguese • Updated: Turkish, Dutch, Swedish, French, Spanish and Danish - Late translations: • New: Traditional Chinese (for 1.2.0) • Updated: Brazilian Portuguese (for 1.2.0) More details, updated screenshots and download links on homepage: http://www.claws-mail.org/clawsker.php -- Ricardo Mones ~ I'm sorry, my responses are limited. You must ask the right questions. A hologram -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: Firma digital OpenPGP URL: From myetto at gmail.com Sun Dec 2 19:07:50 2018 From: myetto at gmail.com (Michael A. Yetto) Date: Sun, 2 Dec 2018 13:07:50 -0500 Subject: [Users] Replies appear as unread in ignored thread In-Reply-To: <20181202124123.584ae97e@localhost> References: <20181127185620.56f0ac79@localhost> <20181201105142.3c873cd1@localhost> <20181202000027.00006925@prost.fenrir.org.uk> <20181202124123.584ae97e@localhost> Message-ID: <20181202130750.4e20a48e@braetac.lighthouse.yetnet> On Sun, 2 Dec 2018 12:41:23 +0200 Removed after GDPR request writes, and having writ moves on: >For the messages from the last screenshot: > > >Message #1 (marked as "ignore thread"): > >Message-ID: > > > >Message #2 (reply to #1, not marked as "ignore >thread"): > >References: > > >In-Reply-To: > >Date: Fri, 30 Nov 2018 11:38:32 -0800 Message-ID: > > > >Message #3 (reply to #2, also not marked as "ignore thread"): > >References: > > > >In-Reply-To: > >Date: Fri, 30 Nov 2018 11:51:07 -0800 X-Gmail-Original-Message-ID: > >Message-ID: > > It looks like you are missing a message between #1 and #2 above. Where is the message with MID: ? If the threading goes by the In-Reply-To: header or the last id in the References: header there is a break in your thread. Mike Yetto -- "It is morally as bad not to care whether a thing is true or not, so long as it makes you feel good, as it is not to care how you got your money as long as you have got it" - Edmund Way Teale -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From subscript at free.fr Sun Dec 2 22:22:30 2018 From: subscript at free.fr (wwp) Date: Sun, 2 Dec 2018 22:22:30 +0100 Subject: [Users] Clawsker 1.3.0 released In-Reply-To: <20181202181639.0705b021@busgosu> References: <20181202181639.0705b021@busgosu> Message-ID: <20181202222230.7222c42b@ladybug> Hello Ricardo, On Sun, 2 Dec 2018 18:16:39 +0100 Ricardo Mones wrote: > Hi all, > > Clawsker, the Claws Mail hidden preferences editor and tweaker has been > released again. > > This version requires Perl bindings to GTK+3 and a non-core module to > finding the claws-mail binary in a more portable way. Check the > Dependencies section in README file for required versions. > > Changes shamelessly copied from the NEWS file: > > 1.3.0: > - Migrated to GTK+3 perl bindings > - Migrated UI layouts to new GtkGrid widget > - Reimplemented about dialogue using GTK+3 AboutDialog > - Hotkey background stripes now use theme colours > - Fixed bug detecting unapplied changes > - Fixed window height to fit common resolutions (4128) > - Translations: > • New: Portuguese > • Updated: Turkish, Dutch, Swedish, French, Spanish and Danish > - Late translations: > • New: Traditional Chinese (for 1.2.0) > • Updated: Brazilian Portuguese (for 1.2.0) > > More details, updated screenshots and download links on homepage: > http://www.claws-mail.org/clawsker.php Thanks for this update! Regards, -- wwp -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: From removed-gdpr at example.com Mon Dec 3 05:48:11 2018 From: removed-gdpr at example.com (Removed after GDPR request) Date: Mon, 3 Dec 2018 06:48:11 +0200 Subject: [Users] Replies appear as unread in ignored thread In-Reply-To: <20181202130750.4e20a48e@braetac.lighthouse.yetnet> References: <20181127185620.56f0ac79@localhost> <20181201105142.3c873cd1@localhost> <20181202000027.00006925@prost.fenrir.org.uk> <20181202124123.584ae97e@localhost> <20181202130750.4e20a48e@braetac.lighthouse.yetnet> Message-ID: <20181203064811.655833e0@localhost> On Sun, 2 Dec 2018 13:07:50 -0500 Michael A. Yetto wrote: > It looks like you are missing a message between #1 > and #2 above. Where is the message with MID: > ? I don't know. > If the threading goes by the In-Reply-To: header or > the last id in the References: header there is a > break in your thread. If the thread was started before I subscribed to that list - why should that matter? CM obviously recognizes that this is a thread (and displays it as a thread), so logically - if the first message in it has been marked as "ignore thread", why aren't the follow ups ignored too? -- George From msuchanek at suse.de Mon Dec 3 15:28:04 2018 From: msuchanek at suse.de (Michal =?UTF-8?B?U3VjaMOhbmVr?=) Date: Mon, 3 Dec 2018 15:28:04 +0100 Subject: [Users] [Bug 4104] SMTP doesn't work over VPN In-Reply-To: <20181128214423.7fc08476@kitsune.suse.cz> References: <20181027000337.27dd4081@naga.suse.cz> <20181027074139.68a11ccc@localhost> <20181028185447.562e5800@naga.suse.cz> <20181028195553.6bed5355@penny> <20181128130710.2db4d532@naga.suse.cz> <20181128124951.0df0ffb9@localhost> <20181128135649.4d40a2e4@naga.suse.cz> <20181128130058.2fdef8b9@localhost> <20181128142707.7923fb85@naga.suse.cz> <20181128145735.3ac9edbb@riri.DEF.witbe.net> <20181128171753.3c7704e0@kitsune.suse.cz> <20181128175108.09427888@sleipner.datanom.net> <20181128181036.2b03b854@kitsune.suse.cz> <20181128212411.6a13c71e@penny> <20181128214423.7fc08476@kitsune.suse.cz> Message-ID: <20181203152804.6be2ab44@kitsune.suse.cz> On Wed, 28 Nov 2018 21:44:23 +0100 Michal Suchánek wrote: > On Wed, 28 Nov 2018 21:24:11 +0100 > Andrej Kacian wrote: > > > On Wed, 28 Nov 2018 18:10:36 +0100 > > Michal Suchánek wrote: > > > > > According to top it is claws using memory. It's the top offender. Also > > > when I run claws it takes about 700M virtual/60M resident. When I > > > open a small folder this does not change much. When I open inbox this > > > grows to like 2G VSS/ 1G RSS, and when I open small folder again it > > > does not get down. Opening inbox does not seem any faster the second > > > time. So to me it looks like claws is hoarding large amounts of > > > memory for no good reason (other than freeing it properly sounds like > > > work). > > > > If only it was that simple. :) Besides Claws Mail data, VSS/RSS also > > include any data and code objects from shared libraries (libc, glibc, > > gtk+, ...). Those are loaded only when first needed, and not merely on > > the application startup. That's why e.g. opening of a first folder > > makes the memory footprint grow considerably more than opening of a > > second folder, regardless of size of either, because for the second > > opening operation, most of what's needed is already loaded in memory. > > And that's not the problem here. I specifically open a small folder > first for comparison. After opening a big folder the occupied memory > grows significantly and never drops. > > > > > > Worse, fork() > > > has to replicate the page tables for the process and it may run out of > > > memory for said tables which depend solely on VSS size. > > > > The way I understand it, page tables themselves are not very big, > > perhaps 1-2MB of kernel space > > ("grep VmPTE /proc/$(pidof claws-mail)/status" for exact number at a > > given moment). Content of those memory pages is another matter, but > > that is not duplicated at the time of fork(). The memory pages are > > duplicated and allocated for the child process only when parent of > > child writes to them later (copy-on-write). > > > > That's why I find it incredible that on any today's decent desktop > > system, things could go as far as fork() reporting ENOMEM. > > Processes grow until they occupy all available memory. Plus this is on > a laptop which is more a thin client than a decent machine. I suppose I > could run claws on a remote machine to save memory at the expense of > network bandwidth. > > > > > There could also be leaks which are triggered over and over again. Just > > a few months ago, we fixed a leak which IIRC leaked a few hundreds > > of bytes on every POP3 mail fetch, along with a dozen or so other, > > smaller leaks. What can I say, C is hard, and we make mistakes. :) > > > > There are probably other uncaught leaks in the code, perhaps some > > triggered only in conditions which I, or whoever bothers running Claws > > Mail through valgrind or similar tool, do not happen to have, so they > > go undetected, and after weeks of uptime, they inevitably add up. > > They add up by opening inbox for me. It should be quite easy to run > through valgrind then I suppose. > The inbox has around 400k messages in an IMAP folder. valgrind does not find anything amiss (in claws itself, it did not trace the workers). So it looks like there is something allocated by claws on opening a folder that is properly freed on exit but not on closing the folder. Thanks Michal -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From noreply at thewildbeast.co.uk Mon Dec 3 16:27:53 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Mon, 03 Dec 2018 15:27:53 +0000 Subject: [Users] [Bug 4117] migrate clawsker to Perl-Gtk3 In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4117 Ricardo Mones changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Ricardo Mones --- Fixed in 1.3.0 release. -- You are receiving this mail because: You are the assignee for the bug. From myetto at gmail.com Mon Dec 3 19:43:32 2018 From: myetto at gmail.com (Michael A. Yetto) Date: Mon, 3 Dec 2018 13:43:32 -0500 Subject: [Users] Replies appear as unread in ignored thread In-Reply-To: <20181203064811.655833e0@localhost> References: <20181127185620.56f0ac79@localhost> <20181201105142.3c873cd1@localhost> <20181202000027.00006925@prost.fenrir.org.uk> <20181202124123.584ae97e@localhost> <20181202130750.4e20a48e@braetac.lighthouse.yetnet> <20181203064811.655833e0@localhost> Message-ID: <20181203134332.06f85cc7@braetac.lighthouse.yetnet> On Mon, 3 Dec 2018 06:48:11 +0200 Removed after GDPR request writes, and having writ moves on: >On Sun, 2 Dec 2018 13:07:50 -0500 Michael A. Yetto >wrote: > >> It looks like you are missing a message between #1 >> and #2 above. Where is the message with MID: >> ? > >I don't know. > >> If the threading goes by the In-Reply-To: header or >> the last id in the References: header there is a >> break in your thread. > >If the thread was started before I subscribed to that >list - why should that matter? CM obviously recognizes >that this is a thread (and displays it as a thread), >so logically - if the first message in it has been >marked as "ignore thread", why aren't the follow ups >ignored too? > Yes it is threaded. No, it is not treated as an ignored message and marked as read. No, the message between your #1 and #2 is not there. Yes, message #2 is in reply to the missing message. I can easily imagine that this is an avenue to explore, but if you think it is an obvious red herring you should look elsewhere. Mike Yetto -- "When kids look up to great scientists the way they do to great musicians and actors, civilization will jump to the next level." - Brian Greene -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From lbickley at bickleywest.com Mon Dec 3 20:42:26 2018 From: lbickley at bickleywest.com (Lyle Bickley) Date: Mon, 3 Dec 2018 11:42:26 -0800 Subject: [Users] Dillo 3.1 upgrade... Message-ID: <20181203114226.513110b6@asrock> Over the weekend I discovered that Dillo 3.1-dev is available for testing (it is not yet a "released" version). "This release is mainly intended for developers and advanced users." I tried it with Claws - and it has worked perfectly for me with the current "Dillo" plugin. (Note: I'm running Claws version 3.17.0git160). What is great - Dillo now seems to handle TLS properly (enable it with: ./configure --enable-ssl). It also uses version 1.3.x of the FLTK GUI toolkit (http://fltk.org). If you want to experiment, here's where to get the Dillo 3.1-dev version: https://github.com/orsenthil/dillo Cheers, Lyle -- 73 NM6Y Bickley Consulting West Inc. http://bickleywest.com "Black holes are where God is dividing by zero" From ticho at claws-mail.org Mon Dec 3 21:03:45 2018 From: ticho at claws-mail.org (Andrej Kacian) Date: Mon, 3 Dec 2018 21:03:45 +0100 Subject: [Users] Replies appear as unread in ignored thread In-Reply-To: <20181202124123.584ae97e@localhost> References: <20181127185620.56f0ac79@localhost> <20181201105142.3c873cd1@localhost> <20181202000027.00006925@prost.fenrir.org.uk> <20181202124123.584ae97e@localhost> Message-ID: <20181203210345.6d1ab874@penny> On Sun, 2 Dec 2018 12:41:23 +0200 George wrote: > For the messages from the last screenshot: > > > Message #1 (marked as "ignore thread"): > > Message-ID: > > > Message #2 (reply to #1, not marked as "ignore > thread"): > > References: > > In-Reply-To: > Date: Fri, 30 Nov 2018 11:38:32 -0800 > Message-ID: > > > Message #3 (reply to #2, also not marked as "ignore thread"): > > References: > > > In-Reply-To: > Date: Fri, 30 Nov 2018 11:51:07 -0800 > X-Gmail-Original-Message-ID: > Message-ID: Do you have the "Thread using subject in addition to standard headers" option enabled in preferences? Messages are only considered as "belonging to thread" if they are connected by their In-Reply-To and/or References headers. There is a special case handled if the above mentioned option is enabled and the message can be matched to a thread using its subject, but only if the message has no In-Reply-To header, nor References header (folder.c, around line 2450). I'd guess that is why these messages do not have "ignored thread" flag set to them. I'm not sure if that's correct, but it does make certain sense - a message which has those two headers can be considered belonging to a different thread, so we do not want to have the "ignored thread" flag spread to this thread from the original thread. Regards, -- Andrej From codeblue at inbox.lv Tue Dec 4 11:52:35 2018 From: codeblue at inbox.lv (John Long) Date: Tue, 4 Dec 2018 10:52:35 +0000 Subject: [Users] Some questions from new/old claws user Message-ID: <20181204105235.1e367027@inbox.lv> Hi, Running 3.16.0 on Fedora 28. I have my message list sorted from oldest to newest (newest on bottom). When I delete any email in the list, the last email (newest) gets focus next. The desired behavior is to focus on the email immediately after the one I just deleted. It seems like this used to work. Can anyone help? Also in the message view Tags: header is always showing. Is there a way to suppress it? Thanks, /jl From claws at thewildbeast.co.uk Tue Dec 4 12:01:40 2018 From: claws at thewildbeast.co.uk (Paul) Date: Tue, 4 Dec 2018 11:01:40 -0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204105235.1e367027@inbox.lv> References: <20181204105235.1e367027@inbox.lv> Message-ID: <20181204110140.33751aa8@localhost> On Tue, 4 Dec 2018 10:52:35 +0000 John Long wrote: > When I delete any email in the list, the last email (newest) gets > focus next. The desired behavior is to focus on the email > immediately after the one I just deleted. It seems like this used > to work. Can anyone help? There's a hidden preference, 'next_on_delete'. Quit claws-mail, open ~/claws-mail/clawsrc, locate the option, change it to 1. (Or use clawsker.) > Also in the message view Tags: header is always showing. Is there a > way to suppress it? No. with regards Paul From codeblue at inbox.lv Tue Dec 4 18:34:46 2018 From: codeblue at inbox.lv (John Long) Date: Tue, 4 Dec 2018 17:34:46 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204110140.33751aa8@localhost> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> Message-ID: <20181204173446.7080c18e@inbox.lv> On Tue, 4 Dec 2018 11:01:40 -0000 Paul wrote: > On Tue, 4 Dec 2018 10:52:35 +0000 > John Long wrote: > > > When I delete any email in the list, the last email (newest) gets > > focus next. The desired behavior is to focus on the email > > immediately after the one I just deleted. It seems like this used > > to work. Can anyone help? > > There's a hidden preference, 'next_on_delete'. Quit claws-mail, open > ~/claws-mail/clawsrc, locate the option, change it to 1. (Or use > clawsker.) Thanks, this restores the desired behavior. > > Also in the message view Tags: header is always showing. Is there a > > way to suppress it? > > No. Would you consider adding it to prefs? It's really unsightly and I don't use gmail and also don't typically correspond with people who use gmail, it's rather a sore thumb in the UI. Thanks, /jl From ticho at claws-mail.org Tue Dec 4 18:56:53 2018 From: ticho at claws-mail.org (Andrej Kacian) Date: Tue, 4 Dec 2018 18:56:53 +0100 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204173446.7080c18e@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> Message-ID: <20181204185653.4b4919b7@penny> On Tue, 4 Dec 2018 17:34:46 +0000 John Long wrote: > > > Also in the message view Tags: header is always showing. Is there a > > > way to suppress it? > > > > No. > > Would you consider adding it to prefs? It's really unsightly and I > don't use gmail and also don't typically correspond with people who use > gmail, it's rather a sore thumb in the UI. This has nothing to do with gmail tags. :) Still, I only see the Tags: line in messages which actually have some tags assigned to them. For messages without any tags the line is not there. -- Andrej From codeblue at inbox.lv Tue Dec 4 19:08:50 2018 From: codeblue at inbox.lv (John Long) Date: Tue, 4 Dec 2018 18:08:50 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204185653.4b4919b7@penny> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> Message-ID: <20181204180850.07c0d1b2@inbox.lv> On Tue, 4 Dec 2018 18:56:53 +0100 Andrej Kacian wrote: > On Tue, 4 Dec 2018 17:34:46 +0000 > John Long wrote: > > > > > Also in the message view Tags: header is always showing. Is > > > > there a way to suppress it? > > > > > > No. > > > > Would you consider adding it to prefs? It's really unsightly and I > > don't use gmail and also don't typically correspond with people who > > use gmail, it's rather a sore thumb in the UI. > > This has nothing to do with gmail tags. :) Even better! But I still hope for its permanent disappearance :) > Still, I only see the Tags: line in messages which actually have some > tags assigned to them. For messages without any tags the line is not > there. I see Tags: $an in almost every message or maybe even every message. Your email shows one. I thought it was coming only from the client. Maybe I misunderstood and something else is involved. From lfiskgr at gmail.com Tue Dec 4 19:50:35 2018 From: lfiskgr at gmail.com (Leon Fisk) Date: Tue, 4 Dec 2018 14:50:35 -0400 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204180850.07c0d1b2@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> Message-ID: <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> On Tue, 4 Dec 2018 18:08:50 +0000 John Long wrote: >I see Tags: $an in almost every message or maybe even every message. >Your email shows one. I thought it was coming only from the client. >Maybe I misunderstood and something else is involved. Maybe you have a bad filter setup? What do you see at Configuration->Tags... ? -- Leon Claws 3.16.0, Ubuntu Lucid From codeblue at inbox.lv Tue Dec 4 20:14:06 2018 From: codeblue at inbox.lv (John Long) Date: Tue, 4 Dec 2018 19:14:06 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> Message-ID: <20181204191406.616913ff@inbox.lv> On Tue, 4 Dec 2018 14:50:35 -0400 Leon Fisk wrote: > On Tue, 4 Dec 2018 18:08:50 +0000 > John Long wrote: > > > >I see Tags: $an in almost every message or maybe even every message. > >Your email shows one. I thought it was coming only from the client. > >Maybe I misunderstood and something else is involved. > > Maybe you have a bad filter setup? What do you see at > Configuration->Tags... ? This seems to be per message, correct? For your message, it shows $an $ay $has cal $encrypted and it allows me to delete those from a specific message or add new tags to it. I may have not typed those exactly correct, I can't see the popup and reply at the same time. Thanks, /jl From claws at thewildbeast.co.uk Tue Dec 4 20:27:54 2018 From: claws at thewildbeast.co.uk (Paul) Date: Tue, 4 Dec 2018 19:27:54 -0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204191406.616913ff@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> Message-ID: <20181204192754.0c2d29f6@localhost> On Tue, 4 Dec 2018 19:14:06 +0000 John Long wrote: > For your message, it shows If you have not added them yourself then perhaps gmail is adding them? By default Claws Mail has no tags configured at all. with regards Paul From claws at thewildbeast.co.uk Tue Dec 4 20:33:31 2018 From: claws at thewildbeast.co.uk (Paul) Date: Tue, 4 Dec 2018 19:33:31 -0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204192754.0c2d29f6@localhost> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> Message-ID: <20181204193331.7f62bdab@localhost> On Tue, 4 Dec 2018 19:27:54 -0000 Paul wrote: > If you have not added them yourself then perhaps gmail is adding > them? Quite clearly you said you don't use gmail. Then instead of gmail, the server you use seems to be adding them. with regards Paul From lfiskgr at gmail.com Tue Dec 4 20:47:05 2018 From: lfiskgr at gmail.com (Leon Fisk) Date: Tue, 4 Dec 2018 15:47:05 -0400 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204191406.616913ff@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> Message-ID: <5c06d9ba.1c69fb81.de54.e152@mx.google.com> On Tue, 4 Dec 2018 19:14:06 +0000 John Long wrote: >This seems to be per message, correct? > >For your message, it shows > >$an >$ay >$has cal >$encrypted > >and it allows me to delete those from a specific message or add new >tags to it. > >I may have not typed those exactly correct, I can't see the popup and >reply at the same time. I suspect you may have an amuck filter or folder processing action with "set_tag" in it that isn't working correctly. Quick and dirty is to try searching "~/.claws-mail/matcherrc" file for "set_tag". Be very careful it you try editing that file directly. I don't recommend it. If you find some entries for that term in there make sure they do what you want via the normal configuration tools. Otherwise Paul's answer is probably correct, they're being added en-route somehow... -- Leon Claws 3.16.0, Ubuntu Lucid From codeblue at inbox.lv Tue Dec 4 20:59:33 2018 From: codeblue at inbox.lv (John Long) Date: Tue, 4 Dec 2018 19:59:33 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204193331.7f62bdab@localhost> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> Message-ID: <20181204195933.0bd9f538@inbox.lv> On Tue, 4 Dec 2018 19:33:31 -0000 Paul wrote: > On Tue, 4 Dec 2018 19:27:54 -0000 > Paul wrote: > > > If you have not added them yourself then perhaps gmail is adding > > them? > > Quite clearly you said you don't use gmail. Then instead of gmail, > the server you use seems to be adding them. It seems quite unlikely; I've got about a dozen email accounts configured right now in claws and every message I've checked from every provider has the $an tag set. I'm using Fedora 28, could it be a local patch? How can I find the source of the problem? Thanks, /jl From codeblue at inbox.lv Tue Dec 4 21:03:01 2018 From: codeblue at inbox.lv (John Long) Date: Tue, 4 Dec 2018 20:03:01 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <5c06d9ba.1c69fb81.de54.e152@mx.google.com> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <5c06d9ba.1c69fb81.de54.e152@mx.google.com> Message-ID: <20181204200301.0d2e60b4@inbox.lv> On Tue, 4 Dec 2018 15:47:05 -0400 Leon Fisk wrote: > On Tue, 4 Dec 2018 19:14:06 +0000 > John Long wrote: > > > >This seems to be per message, correct? > > > >For your message, it shows > > > >$an > >$ay > >$has cal > >$encrypted > > > >and it allows me to delete those from a specific message or add new > >tags to it. > > > >I may have not typed those exactly correct, I can't see the popup and > >reply at the same time. > > I suspect you may have an amuck filter or folder processing action > with "set_tag" in it that isn't working correctly. Quick and dirty is > to try searching "~/.claws-mail/matcherrc" file for "set_tag". Be > very careful it you try editing that file directly. I don't recommend > it. If you find some entries for that term in there make sure they do > what you want via the normal configuration tools. All I've got in there is [preglobal] [postglobal] [filtering] And I have filtering unchecked on every email account. This is a brand-new setup with only a few plugins, not including any filtering or spam goodies. > > Otherwise Paul's answer is probably correct, they're being added > en-route somehow... I can't find a common denominator except for the distro I'n running! About a dozen email accounts on as many providers and all messages I've checked appear the same way! Thank you, /jl From avrunin at math.umass.edu Tue Dec 4 21:19:07 2018 From: avrunin at math.umass.edu (George Avrunin) Date: Tue, 4 Dec 2018 15:19:07 -0500 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204195933.0bd9f538@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> Message-ID: <20181204151907.6216316d.avrunin@math.umass.edu> On Tue, 4 Dec 2018 19:59:33 +0000, John Long wrote: > It seems quite unlikely; I've got about a dozen email accounts > configured right now in claws and every message I've checked from every > provider has the $an tag set. > > I'm using Fedora 28, could it be a local patch? How can I find the > source of the problem? > > Thanks, > > /jl I don't think it's a Fedora patch. I'm now on Fedora 29, but I don't see this now and didn't have it with Fedora 28. No "$an" tag of any kind anywhere. George -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From ticho at claws-mail.org Tue Dec 4 21:48:32 2018 From: ticho at claws-mail.org (Andrej Kacian) Date: Tue, 4 Dec 2018 21:48:32 +0100 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204200301.0d2e60b4@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <5c06d9ba.1c69fb81.de54.e152@mx.google.com> <20181204200301.0d2e60b4@inbox.lv> Message-ID: <20181204214832.6a4d792a@penny> On Tue, 4 Dec 2018 20:03:01 +0000 John Long wrote: > > > > Otherwise Paul's answer is probably correct, they're being added > > en-route somehow... > > I can't find a common denominator except for the distro I'n running! > About a dozen email accounts on as many providers and all messages I've > checked appear the same way! You could try enabling filtering log (See Other->Logging in preferences) and reviewing it after getting some new messages. Is this in an IMAP mailbox, or in a local (MH) mailbox and messages being fetched via POP3? If it's IMAP, the tags could be getting added through server-side filtering (e.g. sieve or procmail rules). Regards, -- Andrej From codeblue at inbox.lv Tue Dec 4 21:49:33 2018 From: codeblue at inbox.lv (John Long) Date: Tue, 4 Dec 2018 20:49:33 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204151907.6216316d.avrunin@math.umass.edu> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> Message-ID: <20181204204933.288a9704@inbox.lv> On Tue, 4 Dec 2018 15:19:07 -0500 George Avrunin wrote: > On Tue, 4 Dec 2018 19:59:33 +0000, John Long > wrote: > > > It seems quite unlikely; I've got about a dozen email accounts > > configured right now in claws and every message I've checked from > > every provider has the $an tag set. > > > > I'm using Fedora 28, could it be a local patch? How can I find the > > source of the problem? > > > > Thanks, > > > > /jl > > I don't think it's a Fedora patch. I'm now on Fedora 29, but I don't > see this now and didn't have it with Fedora 28. No "$an" tag of any > kind anywhere. Thank you. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From codeblue at inbox.lv Tue Dec 4 22:29:07 2018 From: codeblue at inbox.lv (John Long) Date: Tue, 4 Dec 2018 21:29:07 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204214832.6a4d792a@penny> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <5c06d9ba.1c69fb81.de54.e152@mx.google.com> <20181204200301.0d2e60b4@inbox.lv> <20181204214832.6a4d792a@penny> Message-ID: <20181204212907.043953da@inbox.lv> On Tue, 4 Dec 2018 21:48:32 +0100 Andrej Kacian wrote: > On Tue, 4 Dec 2018 20:03:01 +0000 > John Long wrote: > > > > > > Otherwise Paul's answer is probably correct, they're being added > > > en-route somehow... > > > > I can't find a common denominator except for the distro I'n running! > > About a dozen email accounts on as many providers and all messages > > I've checked appear the same way! > > You could try enabling filtering log (See Other->Logging in > preferences) and reviewing it after getting some new messages. Filtering is disabled on all accounts, so there is no filtering log. > > Is this in an IMAP mailbox, or in a local (MH) mailbox and messages > being fetched via POP3? If it's IMAP, the tags could be getting added > through server-side filtering (e.g. sieve or procmail rules). All of the accounts but one are IMAP. I don't have any email from the pop account to be able to check. It's used infrequently. Thanks, /jl From ticho at claws-mail.org Tue Dec 4 23:53:13 2018 From: ticho at claws-mail.org (Andrej Kacian) Date: Tue, 4 Dec 2018 23:53:13 +0100 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204212907.043953da@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <5c06d9ba.1c69fb81.de54.e152@mx.google.com> <20181204200301.0d2e60b4@inbox.lv> <20181204214832.6a4d792a@penny> <20181204212907.043953da@inbox.lv> Message-ID: <20181204235313.34187af2@penny> On Tue, 4 Dec 2018 21:29:07 +0000 John Long wrote: > > > > Is this in an IMAP mailbox, or in a local (MH) mailbox and messages > > being fetched via POP3? If it's IMAP, the tags could be getting added > > through server-side filtering (e.g. sieve or procmail rules). > > All of the accounts but one are IMAP. I don't have any email from the > pop account to be able to check. It's used infrequently. Must be your IMAP server(s) adding those tags, then. Claws Mail by itself does not apply any tags, unless you have filtering or processing rules set to do so. Regards, -- Andrej From avrunin at math.umass.edu Wed Dec 5 01:39:44 2018 From: avrunin at math.umass.edu (George Avrunin) Date: Tue, 4 Dec 2018 19:39:44 -0500 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204204933.288a9704@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> Message-ID: <20181204193944.6e634f82@g.localdomain> Maybe try setting up a fresh user and configuring claws-mail from scratch with one of the accounts that gets the strange tag? (Without touching any other configuration.) See if that user also gets these funny tags. George -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From noreply at thewildbeast.co.uk Thu Dec 6 20:45:46 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Thu, 06 Dec 2018 19:45:46 +0000 Subject: [Users] [Bug 4061] 'make uninistall' leaves empty directories In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4061 Andrej Kacian changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Andrej Kacian --- "make uninstall" is not supposed to remove empty directories, just files. As its own documentation states, the "uninstall" target is not meant to be a replacement for package management, see https://www.gnu.org/software/automake/manual/automake.html#index-installdirs The only bug here is that the "sylpheed-claws" symlink is not removed, we will be fixing that soon. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Thu Dec 6 23:02:30 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Thu, 06 Dec 2018 22:02:30 +0000 Subject: [Users] [Bug 4038] Make enum RecvProtocol (prefs_account.h) extensible In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4038 --- Comment #1 from Andrej Kacian --- Created attachment 1941 --> https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=1941&action=edit Rework recvtype in wizard.c Attached patch makes "recvtype" store combobox index of desired default option, and the actual protocol number is pulled from the relevant row's data pointer in the combobox. That way we do not care whether the actual wanted default protocol has number 0 or not. This is probably the simplest solution to this problem. A more proper solution (one that would ultimately likely simplify a lot more than just this) would be to modify our pref system to use GValue type for the default value in the PrefParam struct, but that's a rather complex change. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Thu Dec 6 23:07:11 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Thu, 06 Dec 2018 22:07:11 +0000 Subject: [Users] [Bug 4054] Scroll preferences have no effect In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4054 --- Comment #2 from Andrej Kacian --- FWIW, the half-page scrolling has been fixed for a while, with commit https://git.claws-mail.org/?p=claws.git;a=commitdiff;h=5b0e5014b -- You are receiving this mail because: You are the assignee for the bug. From claws_mail_list at zeithaben.de Fri Dec 7 07:34:37 2018 From: claws_mail_list at zeithaben.de (KJD) Date: Fri, 7 Dec 2018 07:34:37 +0100 Subject: [Users] Search Function Message-ID: <20181207073437.242d576c@zeithaben.de> How do I search to all Folders in all Boxes in several accounts? I only found search function to search in one folder. Thanks for help! Regards From buhtz at posteo.de Fri Dec 7 07:52:08 2018 From: buhtz at posteo.de (buhtz at posteo.de) Date: Fri, 7 Dec 2018 07:52:08 +0100 Subject: [Users] Lost my address book and alias accounts Message-ID: <43B36x16r5z9rxV@submission02.posteo.de> I am using Claws for years - currently on Debian stable. I am not sure about it but maybe there was an update in the last two days. But I havened check if Claws was a part of it. The current version her is 3.14.1. Opening Claws I got the messing "addressbook index missing". The adressbook is empty. Also my two alias accounts are lost. The mailbox in claws and the folders on the hard disc are still present. My configuration is so old and long ago that I even don't know how to configure alias accounts. :D Is there regular way for aliases in Claws or do I have to create a full account for each alias just all of them using the same mbox-folder? But the biggest question: Does anyone have an idea what was going on here? Why do I lost the accounts and addressbook? I think the mails themselfs are still here. From frapox at yahoo.it Fri Dec 7 18:56:53 2018 From: frapox at yahoo.it (Francesco) Date: Fri, 7 Dec 2018 18:56:53 +0100 Subject: [Users] Sub-thread sort order missing? Message-ID: <20181207185653.14b043da@siddino> Hi, I'm using Claws mail for a while until now, and I've searched extensively before posting here. I was looking for a feature to sort sub (or child) threads of a discussion by an opposite criteria to the global one. Since I use to order mails by Date/descending , I'd like to get all child threads ordered by Date/ascending. If found that with this way of ordering is much it's much more easy to understand the "thread of discussion", since older informations and references are displayed first (higher in the summary). This time I have to choose global ascending ordering because there's not a dedicate setting for child threads. I've also used others mail clients (such as Thunderbird, Evolution or Kmail) and they all have the chance to reverse the "sub-thread" ordering from the "global" list ordering. So am I missing something or currently this feature is not present? Will it be in the future? (and should I ask for it somewhere else?). Ty in advance Ps. I've also searched for related plugins but found nothing. And I'm using Claws version 3.17.1 from Debian sid repos. -- fp From claws at thewildbeast.co.uk Fri Dec 7 19:56:41 2018 From: claws at thewildbeast.co.uk (Paul) Date: Fri, 7 Dec 2018 18:56:41 -0000 Subject: [Users] Sub-thread sort order missing? In-Reply-To: <20181207185653.14b043da@siddino> References: <20181207185653.14b043da@siddino> Message-ID: <20181207185641.23c5ff34@localhost> On Fri, 7 Dec 2018 18:56:53 +0100 Francesco wrote: > So am I missing something or currently this feature is not present? it's not present. > Will it be in the future? it might be. with regards Paul From jjk at jjacky.com Fri Dec 7 20:12:50 2018 From: jjk at jjacky.com (Olivier Brunel) Date: Fri, 7 Dec 2018 20:12:50 +0100 Subject: [Users] Sub-thread sort order missing? In-Reply-To: <20181207185653.14b043da@siddino> References: <20181207185653.14b043da@siddino> Message-ID: <20181207201250.002bae47@jjacky.com> Hello Francesco, > So am I missing something or currently this feature is not present? > Will it be in the future? (and should I ask for it somewhere else?). It isn't currently possible in claws, however - because I too use date descending sort order with threaded view - I've made a patch that, while not providing an option for it, actually does what (I believe) you're looking for: it sorts by date asc within threads when sorting by date desc (and using thread view). You can find the patch on the following bug report if you're interested: http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=1491 HTH, From buhtz at posteo.de Fri Dec 7 22:50:34 2018 From: buhtz at posteo.de (buhtz at posteo.de) Date: Fri, 7 Dec 2018 22:50:34 +0100 Subject: [Users] Lost my address book and alias accounts In-Reply-To: <43B36x16r5z9rxV@submission02.posteo.de> References: <43B36x16r5z9rxV@submission02.posteo.de> Message-ID: <43BR3f2Vc7z9rxN@submission02.posteo.de> I also still have addrbook-1.xml, addrbook-2.xml and addrbook-3.xml in my claws-mail folder. The content of them looks ok to me - there are my old addresses. But claws doesn't recognize this xml files. On 2018-12-07 07:52 wrote: > I am using Claws for years - currently on Debian stable. > > I am not sure about it but maybe there was an update in the last two > days. But I havened check if Claws was a part of it. > > The current version her is 3.14.1. > > Opening Claws I got the messing "addressbook index missing". The > adressbook is empty. > > Also my two alias accounts are lost. The mailbox in claws and the > folders on the hard disc are still present. > My configuration is so old and long ago that I even don't know how to > configure alias accounts. :D > Is there regular way for aliases in Claws or do I have to create a > full account for each alias just all of them using the same > mbox-folder? > > But the biggest question: Does anyone have an idea what was going on > here? Why do I lost the accounts and addressbook? > > I think the mails themselfs are still here. > _______________________________________________ > Users mailing list > Users at lists.claws-mail.org > https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users From frapox at yahoo.it Fri Dec 7 23:46:55 2018 From: frapox at yahoo.it (Francesco) Date: Fri, 7 Dec 2018 23:46:55 +0100 Subject: [Users] Sub-thread sort order missing? In-Reply-To: <20181207201250.002bae47@jjacky.com> References: <20181207185653.14b043da@siddino> <20181207201250.002bae47@jjacky.com> Message-ID: <20181207234655.7ec98d51@siddino> Il giorno Fri, 7 Dec 2018 20:12:50 +0100 Olivier Brunel ha scritto: > Hello Francesco, > > > So am I missing something or currently this feature is not present? > > Will it be in the future? (and should I ask for it somewhere > > else?). > > It isn't currently possible in claws, however - because I too use date > descending sort order with threaded view - I've made a patch that, > while not providing an option for it, actually does what (I believe) > you're looking for: it sorts by date asc within threads when sorting > by date desc (and using thread view). > > You can find the patch on the following bug report if you're > interested: > http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=1491 Thank you Oliver, but I don't want to patch the code by myself but I hope that your patch (with the option to choose the preferred behavior) will be added soon to Claws mail. I believe it would be very useful especially for those really dependent on mailing lists for their job. ty again. -- fp From noreply at thewildbeast.co.uk Sun Dec 9 18:18:51 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 09 Dec 2018 17:18:51 +0000 Subject: [Users] [Bug 4133] New: trying to read message from an NNTP group (with all expired articles. Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4133 Bug ID: 4133 Summary: trying to read message from an NNTP group (with all expired articles. Classification: Unclassified Product: Claws Mail Version: 3.17.1 Hardware: PC OS: Windows 10 Status: NEW Severity: trivial Priority: P3 Component: NNTP Assignee: users at lists.claws-mail.org Reporter: luuk34 at gmail.com There should be a better way to do it than this way: [18:05:47] NNTP> XHDR newsgroups 101414999-101419998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101419999-101424998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101424999-101429998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101429999-101434998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101434999-101439998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101439999-101444998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101444999-101449998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101449999-101454998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101454999-101459998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101459999-101464998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101464999-101469998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101469999-101474998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101474999-101479998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101479999-101484998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101484999-101489998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101489999-101494998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101494999-101499998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101499999-101504998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101504999-101509998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101509999-101514998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101514999-101519998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101519999-101524998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101524999-101529998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101529999-101534998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101534999-101539998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101539999-101544998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101544999-101549998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101549999-101554998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101554999-101559998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101559999-101564998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101564999-101569998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101569999-101574998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101574999-101579998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101579999-101584998 [18:05:47] NNTP< 221 newsgroups data follows [18:05:47] NNTP< . [18:05:47] NNTP> XHDR newsgroups 101584999-101589998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101589999-101594998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101594999-101599998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101599999-101604998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101604999-101609998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101609999-101614998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101614999-101619998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101619999-101624998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101624999-101629998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101629999-101634998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101634999-101639998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101639999-101644998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101644999-101649998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101649999-101654998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101654999-101659998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101659999-101664998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101664999-101669998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101669999-101674998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101674999-101679998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101679999-101684998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101684999-101689998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101689999-101694998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101694999-101699998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101699999-101704998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101704999-101709998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101709999-101714998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101714999-101719998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101719999-101724998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101724999-101729998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101729999-101734998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101734999-101739998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101739999-101744998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101744999-101749998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101749999-101754998 [18:05:48] NNTP< 221 newsgroups data follows [18:05:48] NNTP< . [18:05:48] NNTP> XHDR newsgroups 101754999-101759998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101759999-101764998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101764999-101769998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101769999-101774998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101774999-101779998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101779999-101784998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101784999-101789998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101789999-101794998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101794999-101799998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101799999-101804998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101804999-101809998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101809999-101814998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101814999-101819998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101819999-101824998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101824999-101829998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101829999-101834998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101834999-101839998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101839999-101844998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101844999-101849998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101849999-101854998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101854999-101859998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101859999-101864998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101864999-101869998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101869999-101874998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101874999-101879998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101879999-101884998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101884999-101889998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101889999-101894998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101894999-101899998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101899999-101904998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101904999-101909998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101909999-101914998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101914999-101919998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101919999-101924998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101924999-101929998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101929999-101934998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101934999-101939998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101939999-101944998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101944999-101949998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101949999-101954998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101954999-101959998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101959999-101964998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101964999-101969998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101969999-101974998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101974999-101979998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101979999-101984998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101984999-101989998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:49] NNTP> XHDR newsgroups 101989999-101994998 [18:05:49] NNTP< 221 newsgroups data follows [18:05:49] NNTP< . [18:05:50] NNTP> XHDR newsgroups 101994999-101999998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 101999999-102004998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102004999-102009998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102009999-102014998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102014999-102019998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102019999-102024998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102024999-102029998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102029999-102034998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102034999-102039998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102039999-102044998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102044999-102049998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102049999-102054998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102054999-102059998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102059999-102064998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102064999-102069998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102069999-102074998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102074999-102079998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102079999-102084998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102084999-102089998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102089999-102094998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102094999-102099998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102099999-102104998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102104999-102109998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102109999-102114998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102114999-102119998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102119999-102124998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102124999-102129998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102129999-102134998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102134999-102139998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102139999-102144998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102144999-102149998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102149999-102154998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102154999-102159998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102159999-102164998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:50] NNTP> XHDR newsgroups 102164999-102169998 [18:05:50] NNTP< 221 newsgroups data follows [18:05:50] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102169999-102174998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102174999-102179998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102179999-102184998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102184999-102189998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102189999-102194998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102194999-102199998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102199999-102204998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102204999-102209998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102209999-102214998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102214999-102219998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102219999-102224998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102224999-102229998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102229999-102234998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102234999-102239998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . [18:05:51] NNTP> XHDR newsgroups 102239999-102244998 [18:05:51] NNTP< 221 newsgroups data follows [18:05:51] NNTP< . (and it's still continuing [18:18:14] NNTP> XHDR newsgroups 246639999-246644998 [18:18:14] NNTP< 221 newsgroups data follows [18:18:14] NNTP< . [18:18:14] NNTP> XHDR newsgroups 246644999-246649998 [18:18:14] NNTP< 221 newsgroups data follows [18:18:14] NNTP< . [18:18:14] NNTP> XHDR newsgroups 246649999-246654998 [18:18:14] NNTP< 221 newsgroups data follows [18:18:14] NNTP< . [18:18:14] NNTP> XHDR newsgroups 246654999-246659998 [18:18:14] NNTP< 221 newsgroups data follows [18:18:14] NNTP< . [18:18:14] NNTP> XHDR newsgroups 246659999-246664998 [18:18:14] NNTP< 221 newsgroups data follows [18:18:14] NNTP< . [18:18:14] NNTP> XHDR newsgroups 246664999-246669998 [18:18:14] NNTP< 221 newsgroups data follows [18:18:14] NNTP< . [18:18:14] NNTP> XHDR newsgroups 246669999-246674998 [18:18:14] NNTP< 221 newsgroups data follows [18:18:14] NNTP< . [18:18:14] NNTP> XHDR newsgroups 246674999-246679998 [18:18:14] NNTP< 221 newsgroups data follows [18:18:14] NNTP< . [18:18:14] NNTP> XHDR newsgroups 246679999-246684998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246684999-246689998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246689999-246694998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246694999-246699998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246699999-246704998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246704999-246709998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246709999-246714998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246714999-246719998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246719999-246724998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246724999-246729998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246729999-246734998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246734999-246739998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246739999-246744998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246744999-246749998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246749999-246754998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246754999-246759998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246759999-246764998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246764999-246769998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246769999-246774998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246774999-246779998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246779999-246784998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246784999-246789998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246789999-246794998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246794999-246799998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246799999-246804998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246804999-246809998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246809999-246814998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246814999-246819998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246819999-246824998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246824999-246829998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246829999-246834998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246834999-246839998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246839999-246844998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246844999-246849998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246849999-246854998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246854999-246859998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246859999-246864998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246864999-246869998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246869999-246874998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246874999-246879998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246879999-246884998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246884999-246889998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246889999-246894998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246894999-246899998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246899999-246904998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246904999-246909998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246909999-246914998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246914999-246919998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246919999-246924998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246924999-246929998 [18:18:15] NNTP< 221 newsgroups data follows [18:18:15] NNTP< . [18:18:15] NNTP> XHDR newsgroups 246929999-246934998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246934999-246939998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246939999-246944998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246944999-246949998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246949999-246954998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246954999-246959998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246959999-246964998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246964999-246969998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246969999-246974998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246974999-246979998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246979999-246984998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246984999-246989998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246989999-246994998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246994999-246999998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 246999999-247004998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247004999-247009998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247009999-247014998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247014999-247019998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247019999-247024998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247024999-247029998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247029999-247034998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247034999-247039998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247039999-247044998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247044999-247049998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247049999-247054998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247054999-247059998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247059999-247064998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247064999-247069998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247069999-247074998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247074999-247079998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247079999-247084998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247084999-247089998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247089999-247094998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247094999-247099998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247099999-247104998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247104999-247109998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247109999-247114998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247114999-247119998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247119999-247124998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247124999-247129998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247129999-247134998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247134999-247139998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247139999-247144998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247144999-247149998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247149999-247154998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247154999-247159998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247159999-247164998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:16] NNTP> XHDR newsgroups 247164999-247169998 [18:18:16] NNTP< 221 newsgroups data follows [18:18:16] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247169999-247174998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247174999-247179998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247179999-247184998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247184999-247189998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247189999-247194998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247194999-247199998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247199999-247204998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247204999-247209998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247209999-247214998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247214999-247219998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247219999-247224998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247224999-247229998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247229999-247234998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247234999-247239998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247239999-247244998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247244999-247249998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247249999-247254998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247254999-247259998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247259999-247264998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247264999-247269998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247269999-247274998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247274999-247279998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247279999-247284998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247284999-247289998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247289999-247294998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247294999-247299998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247299999-247304998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247304999-247309998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247309999-247314998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247314999-247319998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247319999-247324998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247324999-247329998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247329999-247334998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247334999-247339998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247339999-247344998 [18:18:17] NNTP< 221 newsgroups data follows [18:18:17] NNTP< . [18:18:17] NNTP> XHDR newsgroups 247344999-247349998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247349999-247354998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247354999-247359998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247359999-247364998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247364999-247369998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247369999-247374998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247374999-247379998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247379999-247384998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247384999-247389998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247389999-247394998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247394999-247399998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247399999-247404998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247404999-247409998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247409999-247414998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247414999-247419998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247419999-247424998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247424999-247429998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247429999-247434998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247434999-247439998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247439999-247444998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247444999-247449998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247449999-247454998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247454999-247459998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247459999-247464998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . [18:18:18] NNTP> XHDR newsgroups 247464999-247469998 [18:18:18] NNTP< 221 newsgroups data follows [18:18:18] NNTP< . …. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 9 21:33:47 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 09 Dec 2018 20:33:47 +0000 Subject: [Users] [Bug 4133] trying to read message from an NNTP group (with all expired articles. In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4133 --- Comment #1 from Andrej Kacian --- (In reply to comment #0) > There should be a better way to do it than this way: Such as? -- You are receiving this mail because: You are the assignee for the bug. From codeblue at inbox.lv Mon Dec 10 17:30:17 2018 From: codeblue at inbox.lv (John Long) Date: Mon, 10 Dec 2018 16:30:17 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181204193944.6e634f82@g.localdomain> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> Message-ID: <20181210163017.5cf30660@inbox.lv> On Tue, 4 Dec 2018 19:39:44 -0500 George Avrunin wrote: > Maybe try setting up a fresh user and configuring claws-mail from > scratch with one of the accounts that gets the strange tag? (Without > touching any other configuration.) See if that user also gets these > funny tags. The raw text does not have a tag header. I believe this is specific to claws-mail on Fedora. It occurs on every one of a dozen accounts, both POP and IMAP. Your message I'm responding to now shows Tags: $an. Most messages display this way, others say Tags: $encrypted when there is no gpg or S/MIME. I will set up Mutt on an account I have in claws and send a message and look at it on both clients. Thanks /jl Claws Mail version 3.16.0 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From claws at thewildbeast.co.uk Mon Dec 10 18:30:39 2018 From: claws at thewildbeast.co.uk (Paul) Date: Mon, 10 Dec 2018 17:30:39 -0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210163017.5cf30660@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> Message-ID: <20181210173039.14632d50@localhost> On Mon, 10 Dec 2018 16:30:17 +0000 John Long wrote: > I believe this is specific to > claws-mail on Fedora. To reiterate, Claws Mail is not adding these tags. And it has nothing to do with fedora. It can only be the server you are using. with regards Paul From codeblue at inbox.lv Mon Dec 10 18:39:16 2018 From: codeblue at inbox.lv (John Long) Date: Mon, 10 Dec 2018 17:39:16 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210173039.14632d50@localhost> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> Message-ID: <20181210173916.6750e699@inbox.lv> On Mon, 10 Dec 2018 17:30:39 -0000 Paul wrote: > On Mon, 10 Dec 2018 16:30:17 +0000 > John Long wrote: > > > I believe this is specific to > > claws-mail on Fedora. > > To reiterate, Claws Mail is not adding these tags. And it has nothing > to do with fedora. It can only be the server you are using. The tags don't appear in the raw message text. Claws does have Tag display logic, so it's reasonable that there could be a problem with that code. It might be something you wouldn't know about if you are not the maintainer for claws-mail on Fedora, even though you are the main developer. Furthermore, it's 12 different email providers using two different protocols. The common denominator is claws, not anything else. Of course this is not conclusive, but given these facts it suggests claws is involved with this issue. /jl From codeblue at inbox.lv Mon Dec 10 18:45:03 2018 From: codeblue at inbox.lv (John Long) Date: Mon, 10 Dec 2018 17:45:03 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210173039.14632d50@localhost> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> Message-ID: <20181210174503.0ddb96bf@inbox.lv> On Mon, 10 Dec 2018 17:30:39 -0000 Paul wrote: > On Mon, 10 Dec 2018 16:30:17 +0000 > John Long wrote: > > > I believe this is specific to > > claws-mail on Fedora. > > To reiterate, Claws Mail is not adding these tags. And it has nothing > to do with fedora. It can only be the server you are using. > > with regards > > Paul Here is the raw message text from the message I am replying to. Claws-mail is displaying Tags: $an for this message after the From: To: and headers on the first line and then Subject: on the second line Return-Path: Received: from timmy3-clean.inbox.lv ([10.0.1.73]) by brat46 (Cyrus 2.5-113) with LMTPA; Mon, 10 Dec 2018 19:31:25 +0200 Received: from localhost (ham2 [10.0.1.102]) by timmy3-clean.inbox.lv (Postfix) with ESMTP id 8651F17F476 for ; Mon, 10 Dec 2018 19:31:25 +0200 (EET) Received: from kas7.inbox.lv ([10.0.1.97]) by localhost (ham2.inbox.lv [10.0.1.100]) (spamfilter, port 25) with ESMTP id sJJURyDRvNZo for ; Mon, 10 Dec 2018 19:31:27 +0200 (EET) Received: from mx.colino.net (claws-mail.org [163.172.88.172]) by timmy4-world.inbox.lv (Postfix) with ESMTPS id 73FA320000D for ; Mon, 10 Dec 2018 19:31:22 +0200 (EET) Received: by mx.colino.net (Postfix, from userid 1024) id 2F492210053E; Mon, 10 Dec 2018 18:31:19 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=thewildbeast.co.uk; s=mail; t=1544463079; bh=TLiwlSDsglZTMYZjNBU7nFktwxuS8z2jRZlIgTdA60o=; h=Date:From:To:In-Reply-To:References:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=oeb3qBnuBp2aQ3n2G5T0hPrgnbEYpHFhfOovn58eQeu5eSY6FZTE5Wb9h6OaKsAku 1o6iMcLapivxXMkEQGH18NgZ5AaTgFZJG4Wph/Y0LKyx6nWLxxYF0TWEYnvpTZfS9F mEvgRJuaiRoubw4Pd+7yhDb47Fh+rwrdd4xCYpcE= Received: from marv.colino.net (localhost [IPv6:::1]) by mx.colino.net (Postfix) with ESMTP id 9E6D5210052C; Mon, 10 Dec 2018 18:30:44 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=thewildbeast.co.uk; s=mail; t=1544463045; bh=TLiwlSDsglZTMYZjNBU7nFktwxuS8z2jRZlIgTdA60o=; h=Date:From:To:In-Reply-To:References:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=QX3qf8AN9J7Sknu99VhHEC5VpjWKKcD2A6qzYJAT6Pf1pgjgOcxXpxAVsb7zO1UZ/ FFS5BvlRwnEQ/1hGaL9aebn9LGeAjq5uFSm9UjTOFd67+BhOmoROpb6OqD9A0I2V3z 8xhfvS4zyd459naS7+7ILzkYJ99z0Zz2mYYh3uMg= X-Original-To: users at lists.claws-mail.org Delivered-To: users at lists.claws-mail.org Received: by mx.colino.net (Postfix, from userid 1024) id BD3E1210050E; Mon, 10 Dec 2018 18:30:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=thewildbeast.co.uk; s=mail; t=1544463041; bh=ICTWM1dxAAgAQZjpmDjoWY2YBoRvNcBXWOYd3qjzcEk=; h=Date:From:To:Subject:In-Reply-To:References; b=bACgNAS9HP0YVUR3N670iK/CCpMbPXfht3erEQe9GupU0hw/SrTQo6mwChEOVq6PV KeE+Ee1xFM+n4oCiKLzwrX+DQyfkXuhCuXOvmX0atGVpuO487CbxqSFp+GGucfGzlE VMV/Sakv9IXxoeQbA4Zmu2JAlRp2UacjPpy3TpVw= Received: from localhost (unknown [185.44.76.92]) by mx.colino.net (Postfix) with ESMTPSA id 47C1B2100508 for ; Mon, 10 Dec 2018 18:30:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=thewildbeast.co.uk; s=mail; t=1544463041; bh=ICTWM1dxAAgAQZjpmDjoWY2YBoRvNcBXWOYd3qjzcEk=; h=Date:From:To:Subject:In-Reply-To:References; b=bACgNAS9HP0YVUR3N670iK/CCpMbPXfht3erEQe9GupU0hw/SrTQo6mwChEOVq6PV KeE+Ee1xFM+n4oCiKLzwrX+DQyfkXuhCuXOvmX0atGVpuO487CbxqSFp+GGucfGzlE VMV/Sakv9IXxoeQbA4Zmu2JAlRp2UacjPpy3TpVw= Date: Mon, 10 Dec 2018 17:30:39 -0000 From: Paul To: users at lists.claws-mail.org Message-ID: <20181210173039.14632d50 at localhost> In-Reply-To: <20181210163017.5cf30660 at inbox.lv> References: <20181204105235.1e367027 at inbox.lv> <20181204110140.33751aa8 at localhost> <20181204173446.7080c18e at inbox.lv> <20181204185653.4b4919b7 at penny> <20181204180850.07c0d1b2 at inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1 at mx.google.com> <20181204191406.616913ff at inbox.lv> <20181204192754.0c2d29f6 at localhost> <20181204193331.7f62bdab at localhost> <20181204195933.0bd9f538 at inbox.lv> <20181204151907.6216316d.avrunin at math.umass.edu> <20181204204933.288a9704 at inbox.lv> <20181204193944.6e634f82 at g.localdomain> <20181210163017.5cf30660 at inbox.lv> Organization: theWildBeast X-Mailer: Claws Mail 3.17.0git196 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAElBMVEUYGRcvMS5cXlt9f3yoqqfLzcqdjmCMAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAB3RJTUUH1goMCRIkQ/NdBgAAAkhJREFUOMtlU1F22zAMI90dQFR6AJPKARpJ+V8r+QBL7PtfZaDsJO3mD72WEAgCVGiy/76cLRvJj5LllMxKSommn4AjpeScif9pY2ngieJeSC+BlJOlcjBQVxxqLpBdnqaDYhprARJiMWiXb1Ol3nDO7K3swcCRSi9QFRo6Dw210kpvA4jZBkN3BqZvvfd2CVMqyQ4fGtXqsva1lRx4WSHiQDQRua4dfkVQiRIRCaNVVj11FAOREA6asjPSdjd5v3iBmMaHAOEDhkUS6qwaBoEQJRgzGrAFtMdopo7gMqQC41rSYqUU+JiJJVmBc+Qj7MkhExVTgkUXj3YRoVNpqa5AYkB3JIwzakx0aiX19V5ynLEiLMR9JFybaqnt9HEuMBPSaDVymmNtyyraO1L0Xg7Aepq51gUZbgjAfcaxD8XwbLVvy7r0HHbz0PBNBY51XUFo9gI0Rswba186Eo7hiMzHVUEo5wINWH8ycB0EDick0r7U6NlKxOkaWx5PdK8yEuOxoSJLawhyACFg6LAzrnpuvdS7+nUeDHFGuN5TX5beZm8TXFUGIyCQ6q8HW8dtbMgVsCtZbhSxqDC1IcvkjQTGtz8wiQ5vX64NhjCuB4nb3c0Q/frkfShyDolu6wyRC71/Mof9KbFEvPBla9dtu81vvz2pPTBX0WUb341UjrQEM5DaddQxGx2MAG38WB6MT/y7v0a0EcXD2Bnbh/DxfvGH+FM6AJVjJsTirTi+gAeDnCEHsGLCYyge4XI8D+Cu8piWAn8Dbk/GX914hfsO08dUAAAAAElFTkSuQmCC MIME-Version: 1.0 Subject: Re: [Users] Some questions from new/old claws user X-BeenThere: users at lists.claws-mail.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Errors-To: users-bounces at lists.claws-mail.org Sender: "Users" X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Lua-Profiles: 132739 [Dec 10 2018] X-KLMS-AntiSpam-Version: 5.8.3.0 X-KLMS-AntiSpam-Envelope-From: users-bounces at lists.claws-mail.org X-KLMS-AntiSpam-Auth: dmarc=pass header.from=thewildbeast.co.uk policy=none;spf=pass smtp.mailfrom=lists.claws-mail.org;dkim=pass header.d=thewildbeast.co.uk;dkim=pass header.d=thewildbeast.co.uk;dkim=fail header.d=thewildbeast.co.uk;dkim=fail header.d=thewildbeast.co.uk X-KLMS-AntiSpam-Rate: 0 X-KLMS-AntiSpam-Status: not_detected X-KLMS-AntiSpam-Method: none X-KLMS-AntiSpam-Info: LuaCore: 224 224 65f4abc2987f95e88f0cf20279b947c90999015b, {rep_avail}, {Tracking_DKIM, one}, DmarcAF: none X-MS-Exchange-Organization-SCL: -1 X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: not scanned, disabled by settings X-KLMS-AntiVirus: Modern antivirus of Inbox, version 8.0.3.30, bases: 2018/12/10 13:48:00 #12727398 X-KLMS-AntiVirus-Status: Clean, skipped T24gTW9uLCAxMCBEZWMgMjAxOCAxNjozMDoxNyArMDAwMApKb2huIExvbmcgPGNvZGVibHVlQGlu Ym94Lmx2PiB3cm90ZTogCgo+IEkgYmVsaWV2ZSB0aGlzIGlzIHNwZWNpZmljIHRvCj4gY2xhd3Mt bWFpbCBvbiBGZWRvcmEuCgpUbyByZWl0ZXJhdGUsIENsYXdzIE1haWwgaXMgbm90IGFkZGluZyB0 aGVzZSB0YWdzLiBBbmQgaXQgaGFzIG5vdGhpbmcKdG8gZG8gd2l0aCBmZWRvcmEuIEl0IGNhbiBv bmx5IGJlIHRoZSBzZXJ2ZXIgeW91IGFyZSB1c2luZy4KCndpdGggcmVnYXJkcwoKUGF1bApfX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpVc2VycyBtYWlsaW5n IGxpc3QKVXNlcnNAbGlzdHMuY2xhd3MtbWFpbC5vcmcKaHR0cHM6Ly9saXN0cy5jbGF3cy1tYWls Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vdXNlcnMK From bdm at fenrir.org.uk Mon Dec 10 18:47:41 2018 From: bdm at fenrir.org.uk (Brian Morrison) Date: Mon, 10 Dec 2018 17:47:41 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210173039.14632d50@localhost> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> Message-ID: <20181210174741.76518085@peterson.fenrir.org.uk> On Mon, 10 Dec 2018 17:30:39 -0000 Paul wrote: > On Mon, 10 Dec 2018 16:30:17 +0000 > John Long wrote: > > > I believe this is specific to claws-mail on Fedora. > > To reiterate, Claws Mail is not adding these tags. And it has nothing > to do with fedora. It can only be the server you are using. I have only ever used Claws with Fedora, I never see any Tag: headers displayed unless there is a actual Tag: header. I use Dovecot and Exim for IMAP and SMTP, I can't see any Tag: header settings in either. -- Brian Morrison "I am not young enough to know everything" Oscar Wilde From noreply at thewildbeast.co.uk Mon Dec 10 20:03:18 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Mon, 10 Dec 2018 19:03:18 +0000 Subject: [Users] [Bug 4133] trying to read message from an NNTP group (with all expired articles. In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4133 --- Comment #2 from Luuk --- For example this (http://effbot.org/zone/socket-intro-nntp.htm) website has an explanation about this: Client: GROUP comp.lang.python Server: 211 367 13887 14268 comp.lang.python Above means that articles 13887 until 14268 might(!) be available. It's of no use to try to fetch an article outside this range, and an article need not be present! Better/other reference: (https://tools.ietf.org/html/rfc3977#page-36) 6.1.1. GROUP 6.1.1.1. Usage Indicating capability: READER Syntax GROUP group Responses 211 number low high group Group successfully selected 411 No such newsgroup Parameters group Name of newsgroup number Estimated number of articles in the group low Reported low water mark high Reported high water mark -- You are receiving this mail because: You are the assignee for the bug. From claws at thewildbeast.co.uk Mon Dec 10 20:11:28 2018 From: claws at thewildbeast.co.uk (Paul) Date: Mon, 10 Dec 2018 19:11:28 -0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210174503.0ddb96bf@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> Message-ID: <20181210191128.77c7a326@localhost> On Mon, 10 Dec 2018 17:45:03 +0000 John Long wrote: > $an Why not enquire with inbox.lv, asking them why this is added to your messages? with regards Paul From codeblue at inbox.lv Mon Dec 10 20:14:45 2018 From: codeblue at inbox.lv (John Long) Date: Mon, 10 Dec 2018 19:14:45 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210191128.77c7a326@localhost> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> Message-ID: <20181210191445.44310cd3@inbox.lv> On Mon, 10 Dec 2018 19:11:28 -0000 Paul wrote: > On Mon, 10 Dec 2018 17:45:03 +0000 > John Long wrote: > > > $an > > Why not enquire with inbox.lv, asking them why this is added to your > messages? I mentioned it is happening with all 12 accounts I have. It is not specific to inbox.lv. I sent the raw message text in a previous message. I did not see a tag header there but I don't know what to look for. Did you find the cause? Thanks /jl From claws at thewildbeast.co.uk Mon Dec 10 20:22:57 2018 From: claws at thewildbeast.co.uk (Paul) Date: Mon, 10 Dec 2018 19:22:57 -0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210191445.44310cd3@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> <20181210191445.44310cd3@inbox.lv> Message-ID: <20181210192257.088f774b@localhost> On Mon, 10 Dec 2018 19:14:45 +0000 John Long wrote: > Did you find the cause? The cause is external to claws-mail, unless you are using filtering or processing to add tags you have configured, or are manually adding tags to messages. with regards Paul From bdm at fenrir.org.uk Mon Dec 10 20:40:41 2018 From: bdm at fenrir.org.uk (Brian Morrison) Date: Mon, 10 Dec 2018 19:40:41 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210192257.088f774b@localhost> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> <20181210191445.44310cd3@inbox.lv> <20181210192257.088f774b@localhost> Message-ID: <20181210194041.60af8daa@peterson.fenrir.org.uk> On Mon, 10 Dec 2018 19:22:57 -0000 Paul wrote: > On Mon, 10 Dec 2018 19:14:45 +0000 > John Long wrote: > > > Did you find the cause? > > The cause is external to claws-mail, unless you are using filtering > or processing to add tags you have configured, or are manually adding > tags to messages. > I did some Googling and there are references to $an as something to do with proxy authorization, it shows up as related to openSIPS. Might be worth looking at this further? Ralf Mardorf was asking about this on the Claws users list in late 2016, maybe he can help answer why this is appearing. -- Brian Morrison "I am not young enough to know everything" Oscar Wilde From codeblue at inbox.lv Mon Dec 10 20:46:03 2018 From: codeblue at inbox.lv (John Long) Date: Mon, 10 Dec 2018 19:46:03 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210194041.60af8daa@peterson.fenrir.org.uk> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> <20181210191445.44310cd3@inbox.lv> <20181210192257.088f774b@localhost> <20181210194041.60af8daa@peterson.fenrir.org.uk> Message-ID: <20181210194603.2c3ea8c0@inbox.lv> Hi Paul and Brian, On Mon, 10 Dec 2018 19:40:41 +0000 Brian Morrison wrote: > On Mon, 10 Dec 2018 19:22:57 -0000 > Paul wrote: > > > On Mon, 10 Dec 2018 19:14:45 +0000 > > John Long wrote: > > > > > Did you find the cause? > > > > The cause is external to claws-mail, unless you are using filtering > > or processing to add tags you have configured, or are manually > > adding tags to messages. I am not filtering (have filtering unchecked on all accounts) and of course am not adding tags intentionally. Can you see the problem in the raw message text? > I did some Googling and there are references to $an as something to do > with proxy authorization, it shows up as related to openSIPS. > > Might be worth looking at this further? > > Ralf Mardorf was asking about this on the Claws users list in late > 2016, maybe he can help answer why this is appearing. > Thank you, did you find something in the headers? I searched for "tag" and I didn't see anything in my text editor. I realize something else may be triggering it and I am unable to find it. Any pointers to the actual source of the issue in the raw message would be helpful. Thanks /jl From bdm at fenrir.org.uk Mon Dec 10 20:48:39 2018 From: bdm at fenrir.org.uk (Brian Morrison) Date: Mon, 10 Dec 2018 19:48:39 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210194041.60af8daa@peterson.fenrir.org.uk> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> <20181210191445.44310cd3@inbox.lv> <20181210192257.088f774b@localhost> <20181210194041.60af8daa@peterson.fenrir.org.uk> Message-ID: <20181210194839.0a432a38@peterson.fenrir.org.uk> On Mon, 10 Dec 2018 19:40:41 +0000 Brian Morrison wrote: > Ralf Mardorf was asking about this on the Claws users list in late > 2016, maybe he can help answer why this is appearing. Actually it was Cliff Laine... -- Brian Morrison "I am not young enough to know everything" Oscar Wilde From bdm at fenrir.org.uk Mon Dec 10 21:10:43 2018 From: bdm at fenrir.org.uk (Brian Morrison) Date: Mon, 10 Dec 2018 20:10:43 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210194603.2c3ea8c0@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> <20181210191445.44310cd3@inbox.lv> <20181210192257.088f774b@localhost> <20181210194041.60af8daa@peterson.fenrir.org.uk> <20181210194603.2c3ea8c0@inbox.lv> Message-ID: <20181210201043.373e6294@peterson.fenrir.org.uk> On Mon, 10 Dec 2018 19:46:03 +0000 John Long wrote: > Any pointers to the actual source of the issue in the raw message would > be helpful. Could be something to do with the spam filtering perhaps? I really don't know the answer. -- Brian Morrison "I am not young enough to know everything" Oscar Wilde From bdm at fenrir.org.uk Mon Dec 10 21:18:28 2018 From: bdm at fenrir.org.uk (Brian Morrison) Date: Mon, 10 Dec 2018 20:18:28 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210163017.5cf30660@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> Message-ID: <20181210201828.2d4a3ed7@peterson.fenrir.org.uk> On Mon, 10 Dec 2018 16:30:17 +0000 John Long wrote: > Your message I'm responding to now shows Tags: $an. Most > messages display this way, others say Tags: $encrypted when there is no > gpg or S/MIME. I think this could be some sort of PHP script leakage, but I have no idea where exactly that could be injected. Claws doesn't run random PHP scripts AFAIK. -- Brian Morrison "I am not young enough to know everything" Oscar Wilde From codeblue at inbox.lv Mon Dec 10 21:21:20 2018 From: codeblue at inbox.lv (John Long) Date: Mon, 10 Dec 2018 20:21:20 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210201043.373e6294@peterson.fenrir.org.uk> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> <20181210191445.44310cd3@inbox.lv> <20181210192257.088f774b@localhost> <20181210194041.60af8daa@peterson.fenrir.org.uk> <20181210194603.2c3ea8c0@inbox.lv> <20181210201043.373e6294@peterson.fenrir.org.uk> Message-ID: <20181210202120.036adc72@inbox.lv> On Mon, 10 Dec 2018 20:10:43 +0000 Brian Morrison wrote: > On Mon, 10 Dec 2018 19:46:03 +0000 > John Long wrote: > > > Any pointers to the actual source of the issue in the raw message > > would be helpful. > > Could be something to do with the spam filtering perhaps? I really > don't know the answer. I'm sorry. My question is what in the raw message text that I sent is the root cause? /jl From claws at thewildbeast.co.uk Mon Dec 10 22:04:53 2018 From: claws at thewildbeast.co.uk (Paul) Date: Mon, 10 Dec 2018 21:04:53 -0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210202120.036adc72@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> <20181210191445.44310cd3@inbox.lv> <20181210192257.088f774b@localhost> <20181210194041.60af8daa@peterson.fenrir.org.uk> <20181210194603.2c3ea8c0@inbox.lv> <20181210201043.373e6294@peterson.fenrir.org.uk> <20181210202120.036adc72@inbox.lv> Message-ID: <20181210210453.631bb30f@localhost> On Mon, 10 Dec 2018 20:21:20 +0000 John Long wrote: > My question is what in the raw message text that I sent is > the root cause? There's nothing. Which again suggests it's coming from the server. with regards Paul From noreply at thewildbeast.co.uk Mon Dec 10 22:09:18 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Mon, 10 Dec 2018 21:09:18 +0000 Subject: [Users] [Bug 4133] trying to read message from an NNTP group (with all expired articles. In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4133 --- Comment #3 from Andrej Kacian --- (In reply to comment #2) > Client: GROUP comp.lang.python > Server: 211 367 13887 14268 comp.lang.python > > Above means that articles 13887 until 14268 might(!) be available. > It's of no use to try to fetch an article outside this range, > and an article need not be present! That is exactly what Claws Mail is doing in order to learn what range of articles to request from the server. If you look in the network log at the beginning of that NNTP session, you will see a GROUP command sent to the server, and a response, with a huge number as "high water mark". Claws Mail will then start requesting info about articles which are in range between the last seen article it has remembered (or the "low water mark" if this is the first time this newsgroup is being open), and "high water mark". I will hazard a guess that this is a newsgroup on Gmane.org, which is known to advertise absurdly high ranges of articles, despite most of the actual articles not being available anymore. A RFC-compliant newsreader will then dutifully request all the articles from the range advertised in the GROUP command reply, which is what you see in the long snipped you pasted. Now, until last year, Claws Mail just requested full range in one big batch, which made the entire app look frozen for several minutes, while the server was doing god knows what. (This also sometimes triggered bug in the middleware library we use for NNTP[1].). Instead, we changed the code[2] to request articles in batches of 5000, which allowed us to get rid of the long freeze, as well as bypass the mentioned bug. 1. https://github.com/dinhviethoa/libetpan/issues/283 2. https://git.claws-mail.org/?p=claws.git;a=commitdiff;h=9729bf -- You are receiving this mail because: You are the assignee for the bug. From codeblue at inbox.lv Mon Dec 10 22:26:52 2018 From: codeblue at inbox.lv (John Long) Date: Mon, 10 Dec 2018 21:26:52 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210210453.631bb30f@localhost> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> <20181210191445.44310cd3@inbox.lv> <20181210192257.088f774b@localhost> <20181210194041.60af8daa@peterson.fenrir.org.uk> <20181210194603.2c3ea8c0@inbox.lv> <20181210201043.373e6294@peterson.fenrir.org.uk> <20181210202120.036adc72@inbox.lv> <20181210210453.631bb30f@localhost> Message-ID: <20181210212652.2e7a551f@inbox.lv> On Mon, 10 Dec 2018 21:04:53 -0000 Paul wrote: > On Mon, 10 Dec 2018 20:21:20 +0000 > John Long wrote: > > > My question is what in the raw message text that I sent is > > the root cause? > > There's nothing. Which again suggests it's coming from the server. I am more lost than before. I am sorry for not understanding, but it feels like you know something but you are not saying it. Are you saying that you see nothing in the raw message that has anything to do with tags? And if so, doesn't that mean there is some sort of bug in the copy of claws I'm running? Would you please clarify? Thanks /jl From jseymour at LinxNet.com Tue Dec 11 15:41:51 2018 From: jseymour at LinxNet.com (Jim Seymour) Date: Tue, 11 Dec 2018 09:41:51 -0500 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181210212652.2e7a551f@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204110140.33751aa8@localhost> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> <20181210191445.44310cd3@inbox.lv> <20181210192257.088f774b@localhost> <20181210194041.60af8daa@peterson.fenrir.org.uk> <20181210194603.2c3ea8c0@inbox.lv> <20181210201043.373e6294@peterson.fenrir.org.uk> <20181210202120.036adc72@inbox.lv> <20181210210453.631bb30f@localhost> <20181210212652.2e7a551f@inbox.lv> Message-ID: <20181211094151.767e36ba@jimsun.LinxNet.com> On Mon, 10 Dec 2018 21:26:52 +0000 John Long wrote: > > I am more lost than before. I am sorry for not understanding, but it > feels like you know something but you are not saying it. I really don't see how they could have been more clear. > > Are you saying that you see nothing in the raw message that has > anything to do with tags? What they're saying is there's nothing in the official claws-mail source that would inject those tags. > > And if so, doesn't that mean there is some sort of bug in the copy > of claws I'm running? Maybe there is, but the devs of the official source can hardly be expected to know what, or how it got there. Regards, Jim -- Note: My mail server employs *very* aggressive anti-spam filtering. If you reply to this email and your email is rejected, please accept my apologies and let me know via my web form at . From codeblue at inbox.lv Tue Dec 11 16:24:25 2018 From: codeblue at inbox.lv (John Long) Date: Tue, 11 Dec 2018 15:24:25 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181211094151.767e36ba@jimsun.LinxNet.com> References: <20181204105235.1e367027@inbox.lv> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> <20181210191445.44310cd3@inbox.lv> <20181210192257.088f774b@localhost> <20181210194041.60af8daa@peterson.fenrir.org.uk> <20181210194603.2c3ea8c0@inbox.lv> <20181210201043.373e6294@peterson.fenrir.org.uk> <20181210202120.036adc72@inbox.lv> <20181210210453.631bb30f@localhost> <20181210212652.2e7a551f@inbox.lv> <20181211094151.767e36ba@jimsun.LinxNet.com> Message-ID: <20181211152425.7ea7f0ae@inbox.lv> On Tue, 11 Dec 2018 09:41:51 -0500 Jim Seymour wrote: > On Mon, 10 Dec 2018 21:26:52 +0000 > John Long wrote: > > > > > I am more lost than before. I am sorry for not understanding, but it > > feels like you know something but you are not saying it. > > I really don't see how they could have been more clear. They could have been more clear by pointing out exactly where there is a tag in the raw message text I posted to the list. > > Are you saying that you see nothing in the raw message that has > > anything to do with tags? > > What they're saying is there's nothing in the official claws-mail > source that would inject those tags. 1. It is not certain I'm running the official claws-mail source, I'm using the Fedora 28 package. 2. There are bugs in code all the time. If claws-mail never had any bugs, I would be inclined to trust that kind of statement. 3. Since nobody has pointed to a problem in the raw message, it suggests there is a bug in the copy of claws-mail I'm running. If somebody did point out the problem in the message, it could help resolving the issue. > > And if so, doesn't that mean there is some sort of bug in the copy > > of claws I'm running? > > Maybe there is, but the devs of the official source can hardly be > expected to know what, or how it got there. But they could point out the part of the raw message text that contains the tag so we could have something to go on. Simply repeating "the code doesn't do that" is not helpful in resolving the issue. /jl From jn.ml.clwm.729 at letterboxes.org Tue Dec 11 16:53:26 2018 From: jn.ml.clwm.729 at letterboxes.org (Jeremy Nicoll) Date: Tue, 11 Dec 2018 10:53:26 -0500 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181211152425.7ea7f0ae@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204173446.7080c18e@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> <20181210191445.44310cd3@inbox.lv> <20181210192257.088f774b@localhost> <20181210194041.60af8daa@peterson.fenrir.org.uk> <20181210194603.2c3ea8c0@inbox.lv> <20181210201043.373e6294@peterson.fenrir.org.uk> <20181210202120.036adc72@inbox.lv> <20181210210453.631bb30f@localhost> <20181210212652.2e7a551f@inbox.lv> <20181211094151.767e36ba@jimsun.LinxNet.com> <20181211152425.7ea7f0ae@inbox.lv> Message-ID: <5e34a3de-0cbf-443d-808a-32f86a60a8df@sloti2d3t18> On Tue, 11 Dec 2018, at 15:25, John Long wrote: > 3. Since nobody has pointed to a problem in the raw message, it > suggests there is a bug in the copy of claws-mail I'm running. If > somebody did point out the problem in the message, it could help > resolving the issue. I don't think there's anything special about the message whose headers you posted. > But they could point out the part of the raw message text that contains > the tag so we could have something to go on. Simply repeating "the code > doesn't do that" is not helpful in resolving the issue. There's nothing in the raw message that you posted, that I can see. -- Jeremy Nicoll - my opinions are my own. From bdm at fenrir.org.uk Tue Dec 11 17:30:30 2018 From: bdm at fenrir.org.uk (Brian Morrison) Date: Tue, 11 Dec 2018 16:30:30 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181211152425.7ea7f0ae@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> <20181210191445.44310cd3@inbox.lv> <20181210192257.088f774b@localhost> <20181210194041.60af8daa@peterson.fenrir.org.uk> <20181210194603.2c3ea8c0@inbox.lv> <20181210201043.373e6294@peterson.fenrir.org.uk> <20181210202120.036adc72@inbox.lv> <20181210210453.631bb30f@localhost> <20181210212652.2e7a551f@inbox.lv> <20181211094151.767e36ba@jimsun.LinxNet.com> <20181211152425.7ea7f0ae@inbox.lv> Message-ID: <20181211163030.468b1374@peterson.fenrir.org.uk> On Tue, 11 Dec 2018 15:24:25 +0000 John Long wrote: > On Tue, 11 Dec 2018 09:41:51 -0500 > Jim Seymour wrote: > > > On Mon, 10 Dec 2018 21:26:52 +0000 > > John Long wrote: > > > > > > > > I am more lost than before. I am sorry for not understanding, but it > > > feels like you know something but you are not saying it. > > > > I really don't see how they could have been more clear. > > They could have been more clear by pointing out exactly where there is > a tag in the raw message text I posted to the list. There is nothing in that message that appears to be a tag or Tag: header. I don't know where this came from but I made a couple of suggestions based on your comments about the $an and $encrypted strings you mentioned. > > > > Are you saying that you see nothing in the raw message that has > > > anything to do with tags? > > > > What they're saying is there's nothing in the official claws-mail > > source that would inject those tags. > > 1. It is not certain I'm running the official claws-mail source, I'm > using the Fedora 28 package. I use my own locally built git version under Fedora 64 bit, it uses the source code from the Claws-Mail git repository. It has no additional code other than a couple of things to keep the fancy plugin working that actually affect Fedora, not Claws-Mail directly. > > 2. There are bugs in code all the time. If claws-mail never had any > bugs, I would be inclined to trust that kind of statement. Claws has tagging code, it wouldn't display a tag if there wasn't something to display but it's clearly not within Claws itself. > > 3. Since nobody has pointed to a problem in the raw message, it > suggests there is a bug in the copy of claws-mail I'm running. If > somebody did point out the problem in the message, it could help > resolving the issue. There is *nothing* in the message that includes or creates the content of the tag you describe. However we don't know exactly how your mail is processed either with your ISP, mail provider, IMAP host or on your local machine. I suspect the involvement of PHP and/or openSIPS. > > > > And if so, doesn't that mean there is some sort of bug in the copy > > > of claws I'm running? > > > > Maybe there is, but the devs of the official source can hardly be > > expected to know what, or how it got there. > > But they could point out the part of the raw message text that contains > the tag so we could have something to go on. Simply repeating "the code > doesn't do that" is not helpful in resolving the issue. As I have said several times, the raw message has nothing that appears to be any kind of tag nor anything that is the string you describe. To my mind something else is changing the message that Claws has stored on disk, as I said above the $an and $encrypted strings come up in searches for openSIPS and also some PHP scripts that appear to be used in mail handling by some providers. Do you have any global processing rules? -- Brian Morrison "I am not young enough to know everything" Oscar Wilde From dave at howorth.org.uk Tue Dec 11 17:33:22 2018 From: dave at howorth.org.uk (Dave Howorth) Date: Tue, 11 Dec 2018 16:33:22 +0000 Subject: [Users] Some questions from new/old claws user In-Reply-To: <20181211152425.7ea7f0ae@inbox.lv> References: <20181204105235.1e367027@inbox.lv> <20181204185653.4b4919b7@penny> <20181204180850.07c0d1b2@inbox.lv> <5c06cc7b.1c69fb81.f8872.55c1@mx.google.com> <20181204191406.616913ff@inbox.lv> <20181204192754.0c2d29f6@localhost> <20181204193331.7f62bdab@localhost> <20181204195933.0bd9f538@inbox.lv> <20181204151907.6216316d.avrunin@math.umass.edu> <20181204204933.288a9704@inbox.lv> <20181204193944.6e634f82@g.localdomain> <20181210163017.5cf30660@inbox.lv> <20181210173039.14632d50@localhost> <20181210174503.0ddb96bf@inbox.lv> <20181210191128.77c7a326@localhost> <20181210191445.44310cd3@inbox.lv> <20181210192257.088f774b@localhost> <20181210194041.60af8daa@peterson.fenrir.org.uk> <20181210194603.2c3ea8c0@inbox.lv> <20181210201043.373e6294@peterson.fenrir.org.uk> <20181210202120.036adc72@inbox.lv> <20181210210453.631bb30f@localhost> <20181210212652.2e7a551f@inbox.lv> <20181211094151.767e36ba@jimsun.LinxNet.com> <20181211152425.7ea7f0ae@inbox.lv> Message-ID: <20181211163322.6d1cebde@acer-suse.lan> On Tue, 11 Dec 2018 15:24:25 +0000 John Long wrote: > On Tue, 11 Dec 2018 09:41:51 -0500 > Jim Seymour wrote: > > > On Mon, 10 Dec 2018 21:26:52 +0000 > > John Long wrote: > > > > > > > > I am more lost than before. I am sorry for not understanding, but > > > it feels like you know something but you are not saying it. > > > > I really don't see how they could have been more clear. > > They could have been more clear by pointing out exactly where there is > a tag in the raw message text I posted to the list. But there isn't such a tag that anybody has said they can see. > > > Are you saying that you see nothing in the raw message that has > > > anything to do with tags? > > > > What they're saying is there's nothing in the official claws-mail > > source that would inject those tags. > > 1. It is not certain I'm running the official claws-mail source, I'm > using the Fedora 28 package. Right, but in that case you should be discussing this problem with the Fedora distro people who supplied the package you are using, not with the claws upstream developers. > 2. There are bugs in code all the time. If claws-mail never had any > bugs, I would be inclined to trust that kind of statement. Well indeed, but the devs know the code a lot better than you do, and when they make such a claim then the first case assumption should be to trust it. Admittedly, they could be wrong, but that's a rarer case. > 3. Since nobody has pointed to a problem in the raw message, it > suggests there is a bug in the copy of claws-mail I'm running. If > somebody did point out the problem in the message, it could help > resolving the issue. To repeat - as far as everybody can see, the original message(s) are not the source of the problem. > > > And if so, doesn't that mean there is some sort of bug in the copy > > > of claws I'm running? > > > > Maybe there is, but the devs of the official source can hardly be > > expected to know what, or how it got there. > > But they could point out the part of the raw message text that > contains the tag so we could have something to go on. Simply > repeating "the code doesn't do that" is not helpful in resolving the > issue. To repeat - there are no such tags. To say it in a different way: You have a problem on your system that apparently is experienced by nobody else. It occurs with every message from every source you have, I think, and you have several sources, which strongly suggests it is not a problem with the original messages. So it's most likely a problem with the code you are running or something in the path the messages pass through to get to you. Which might conceivably be other software on your machine or some message routing software somewhere. You are using a distro-packaged version of the program, not the version the devs released. There's nothing wrong with that, I do the same although from a different distro, but it does mean there's only a limited amount of help the devs can give. You could compile and run an upstream release to see if it makes any difference. Certainly starting with a freshly installed copy of a known version of claws and seeing whether that shows the same problem would help to decide whether your problem is caused by some obscure configuration set somehow in your existing system. > /jl > _______________________________________________ > Users mailing list > Users at lists.claws-mail.org > https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users From noreply at thewildbeast.co.uk Tue Dec 11 19:55:59 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Tue, 11 Dec 2018 18:55:59 +0000 Subject: [Users] [Bug 4133] trying to read message from an NNTP group (with all expired articles. In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4133 --- Comment #4 from Luuk --- The start of the logging looks actually as this: * Account 'luuk at invalid.lan': Connecting to NNTP server: news.xs4all.nl:119... [19:48:52] NNTP< 200 news.xs4all.nl NNRP Service Ready (posting ok). [19:48:52] NNTP> MODE READER [19:48:52] NNTP< 200 news.xs4all.nl NNRP Service Ready (posting ok). [19:48:52] NNTP> GROUP xs4all.ipv6 [19:48:52] NNTP< 211 1 4132 4132 xs4all.ipv6 * getting xover 4132 - 4132 in xs4all.ipv6... [19:48:52] NNTP> XOVER 4132-4132 [19:48:52] NNTP< 224 data follows [19:48:52] NNTP< . [19:48:52] NNTP> XHDR newsgroups -1-4998 [19:48:52] NNTP< 221 newsgroups data follows [19:48:52] NNTP< . [19:48:52] NNTP> XHDR newsgroups 4999-9998 [19:48:52] NNTP< 221 newsgroups data follows [19:48:52] NNTP< . [19:48:52] NNTP> XHDR newsgroups 9999-14998 [19:48:52] NNTP< 221 newsgroups data follows [19:48:52] NNTP< . [19:48:52] NNTP> XHDR newsgroups 14999-19998 [19:48:52] NNTP< 221 newsgroups data follows [19:48:52] NNTP< . [19:48:52] NNTP> XHDR newsgroups 19999-24998 [19:48:52] NNTP< 221 newsgroups data follows [19:48:52] NNTP< . [19:48:52] NNTP> XHDR newsgroups 24999-29998 [19:48:52] NNTP< 221 newsgroups data follows Article 4132 if from 11-7-2018 (info from my thunderbird-feed) When trying to get that article using telnet I do see this: 200 news.xs4all.nl NNRP Service Ready (posting ok). group xs4all.ipv6 211 1 4132 4132 xs4all.ipv6 article 4132 423 No such article number in this group xover 4132-4132 224 data follows . But claws seems not to stop after this.... B.T.W. The 'discussion' in xs4all.ipv6 was moved to xs4all.general -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Wed Dec 12 08:59:51 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Wed, 12 Dec 2018 07:59:51 +0000 Subject: [Users] [Bug 4133] trying to read message from an NNTP group (with all expired articles. In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4133 --- Comment #5 from Andrej Kacian --- That looks like a bug, likely introduced by the commit I mentioned above. I will have a look at the code, thanks. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Wed Dec 12 20:13:14 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Wed, 12 Dec 2018 19:13:14 +0000 Subject: [Users] [Bug 4133] trying to read message from an NNTP group (with all expired articles. In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4133 Paul changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from users at lists.claws-mail.org --- Changes related to this bug have been committed. Please check latest Git and update the bug accordingly. You can also get the patch from: http://git.claws-mail.org/ ++ ChangeLog 2018-12-12 19:48:04.279307716 +0100 http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=d76f8acd074e1393936923dcfaa7f85a74e00587 Author: Andrej Kacian Date: Wed Dec 12 19:43:13 2018 +0100 Handle corner case in news_get_extra_fields() where msglist is empty This makes the function quit early, instead of requesting XHDR with bogus ranges from the server. Closes bug #4133: trying to read message from an NNTP group (with all expired articles. -- You are receiving this mail because: You are the assignee for the bug. From list+org.claws-mail at io7m.com Thu Dec 13 11:19:46 2018 From: list+org.claws-mail at io7m.com (Mark Raynsford) Date: Thu, 13 Dec 2018 10:19:46 +0000 Subject: [Users] Claws seeing invalid certificates from pop.gmail.com after upgrade Message-ID: <20181213101946.2453f282@almond.int.arc7.info> Hello! I recently upgraded my system and I think this may have updated openssl behind the scenes, causing me to run into certificate errors when trying to fetch mail over POP3 with Gmail. $ claws-mail --version Claws Mail version 3.17.1 $ openssl version OpenSSL 1.1.1a 20 Nov 2018 This is the dialog box that pops up: --8<-- Certificate for pop.gmail.com has changed. Certificate is for invalid2.invalid, but connection is to pop.gmail.com. You may be connecting to a remote server. Do you want to accept it? Signature status: Self-signed certificate. View certificates: Known certificate: Owner: Name: pop.gmail.com Org: Google LLC Location: Mountain View, US Signer: Name: Google Internet Authority G3 Org: Google Trust Services Location: US Status: Fingerprint: MD5: 83:C3:05:91:BA:31:19:5D:0B:AF:97:53:CB:4D:87:8B SHA1: B7:47:47:56:62:D4:D6:F4:BA:FA:F1:E7:A9:6B:C3:60:01:EC:E0:CB Signature status: Correct Expires on: 2019-02-19 14:02:00 +0000 New certificate: Owner: Name: invalid2.invalid Org: Location: Signer: Name: invalid2.invalid Org: Location: Status: Fingerprint: MD5: 90:4A:C8:D5:44:5A:D0:6A:10:FF:CD:8B:11:BE:16 SHA1: 42:59:51:7C:D4:E4:8A:28:9D:33:2A:B3:F0:AB:52:A3:66:32:28:24 Signature status: Self-signed certificate Expires on: 2030-01-01 00:00:00 +0000 --8<-- This is all I see on stderr: ** (claws-mail:5539): WARNING **: 09:40:22.955: size differ 896 1156 ** (claws-mail:5539): WARNING **: 09:40:23.920: can't initialize SSL/TLS. ** (claws-mail:5539): WARNING **: 09:40:23.920: [09:40:23] SSL/TLS handshake failed Other non-Gmail accounts work correctly. Is there anything I can do about this? -- Mark Raynsford | http://www.io7m.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From colin at colino.net Thu Dec 13 11:35:07 2018 From: colin at colino.net (Colin Leroy-Mira) Date: Thu, 13 Dec 2018 11:35:07 +0100 Subject: [Users] Claws seeing invalid certificates from pop.gmail.com after upgrade In-Reply-To: <20181213101946.2453f282@almond.int.arc7.info> References: <20181213101946.2453f282@almond.int.arc7.info> Message-ID: <20181213113507.6ed038df@colin.i-run.lau> On Thu, 13 Dec 2018 10:19:46 +0000, Mark Raynsford wrote: > I recently upgraded my system and I think this may have updated > openssl behind the scenes, causing me to run into certificate errors > when trying to fetch mail over POP3 with Gmail. This is apparently what happens when we don't set SNI: https://bugzilla.redhat.com/show_bug.cgi?id=1611815 -- Colin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From colin at colino.net Thu Dec 13 11:40:12 2018 From: colin at colino.net (Colin Leroy-Mira) Date: Thu, 13 Dec 2018 11:40:12 +0100 Subject: [Users] Claws seeing invalid certificates from pop.gmail.com after upgrade In-Reply-To: <20181213113507.6ed038df@colin.i-run.lau> References: <20181213101946.2453f282@almond.int.arc7.info> <20181213113507.6ed038df@colin.i-run.lau> Message-ID: <20181213114012.1385628a@colin.i-run.lau> On Thu, 13 Dec 2018 11:35:07 +0100, Colin Leroy-Mira wrote: > On Thu, 13 Dec 2018 10:19:46 +0000, Mark Raynsford > wrote: > > > I recently upgraded my system and I think this may have updated > > openssl behind the scenes, causing me to run into certificate errors > > when trying to fetch mail over POP3 with Gmail. > > This is apparently what happens when we don't set SNI: > > https://bugzilla.redhat.com/show_bug.cgi?id=1611815 Could you try that patch ? -- Colin -------------- next part -------------- A non-text attachment was scrubbed... Name: SNI.patch Type: text/x-patch Size: 518 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From list+org.claws-mail at io7m.com Thu Dec 13 11:46:07 2018 From: list+org.claws-mail at io7m.com (Mark Raynsford) Date: Thu, 13 Dec 2018 10:46:07 +0000 Subject: [Users] Claws seeing invalid certificates from pop.gmail.com after upgrade In-Reply-To: <20181213114012.1385628a@colin.i-run.lau> References: <20181213101946.2453f282@almond.int.arc7.info> <20181213113507.6ed038df@colin.i-run.lau> <20181213114012.1385628a@colin.i-run.lau> Message-ID: <20181213104607.4b630873@almond.int.arc7.info> On 2018-12-13T11:40:12 +0100 Colin Leroy-Mira wrote: > Could you try that patch ? > > -- > Colin I've never built Claws before so it might take me a while to get set up. Should I be patching against any particular version? -- Mark Raynsford | http://www.io7m.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From claws at thewildbeast.co.uk Thu Dec 13 12:12:41 2018 From: claws at thewildbeast.co.uk (Paul) Date: Thu, 13 Dec 2018 11:12:41 -0000 Subject: [Users] Claws seeing invalid certificates from pop.gmail.com after upgrade In-Reply-To: <20181213101946.2453f282@almond.int.arc7.info> References: <20181213101946.2453f282@almond.int.arc7.info> Message-ID: <20181213111241.02557118@localhost> On Thu, 13 Dec 2018 10:19:46 +0000 Mark Raynsford wrote: > $ claws-mail --version > Claws Mail version 3.17.1 > $ openssl version > OpenSSL 1.1.1a 20 Nov 2018 BTW, claws-mail does not use openSSL, it uses gnuTLS. with regards Paul From buhtz at posteo.de Thu Dec 13 13:36:31 2018 From: buhtz at posteo.de (buhtz at posteo.de) Date: Thu, 13 Dec 2018 13:36:31 +0100 Subject: [Users] Lost my address book and alias accounts In-Reply-To: <43B36x16r5z9rxV@submission02.posteo.de> References: <43B36x16r5z9rxV@submission02.posteo.de> Message-ID: <43FtTZ2nN6z9rxV@submission02.posteo.de> Does no one have an idea about it? On 2018-12-07 07:52 wrote: > I am using Claws for years - currently on Debian stable. > > I am not sure about it but maybe there was an update in the last two > days. But I havened check if Claws was a part of it. > > The current version her is 3.14.1. > > Opening Claws I got the messing "addressbook index missing". The > adressbook is empty. > > Also my two alias accounts are lost. The mailbox in claws and the > folders on the hard disc are still present. > My configuration is so old and long ago that I even don't know how to > configure alias accounts. :D > Is there regular way for aliases in Claws or do I have to create a > full account for each alias just all of them using the same > mbox-folder? > > But the biggest question: Does anyone have an idea what was going on > here? Why do I lost the accounts and addressbook? > > I think the mails themselfs are still here. > _______________________________________________ > Users mailing list > Users at lists.claws-mail.org > https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users From list+org.claws-mail at io7m.com Thu Dec 13 13:59:05 2018 From: list+org.claws-mail at io7m.com (Mark Raynsford) Date: Thu, 13 Dec 2018 12:59:05 +0000 Subject: [Users] Claws seeing invalid certificates from pop.gmail.com after upgrade In-Reply-To: <20181213114012.1385628a@colin.i-run.lau> References: <20181213101946.2453f282@almond.int.arc7.info> <20181213113507.6ed038df@colin.i-run.lau> <20181213114012.1385628a@colin.i-run.lau> Message-ID: <20181213125905.5d43dbde@almond.int.arc7.info> On 2018-12-13T11:40:12 +0100 Colin Leroy-Mira wrote: > On Thu, 13 Dec 2018 11:35:07 +0100, Colin Leroy-Mira > wrote: > > > On Thu, 13 Dec 2018 10:19:46 +0000, Mark Raynsford > > wrote: > > > > > I recently upgraded my system and I think this may have updated > > > openssl behind the scenes, causing me to run into certificate errors > > > when trying to fetch mail over POP3 with Gmail. > > > > This is apparently what happens when we don't set SNI: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1611815 > > Could you try that patch ? I've built 3.17.1 with that patch and can verify that yes, it solves the issue. -- Mark Raynsford | http://www.io7m.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From colin at colino.net Thu Dec 13 14:02:28 2018 From: colin at colino.net (Colin Leroy-Mira) Date: Thu, 13 Dec 2018 14:02:28 +0100 Subject: [Users] Claws seeing invalid certificates from pop.gmail.com after upgrade In-Reply-To: <20181213125905.5d43dbde@almond.int.arc7.info> References: <20181213101946.2453f282@almond.int.arc7.info> <20181213113507.6ed038df@colin.i-run.lau> <20181213114012.1385628a@colin.i-run.lau> <20181213125905.5d43dbde@almond.int.arc7.info> Message-ID: <20181213140228.70364ec2@colin.i-run.lau> On Thu, 13 Dec 2018 12:59:05 +0000, Mark Raynsford wrote: > On 2018-12-13T11:40:12 +0100 > Colin Leroy-Mira wrote: > > > On Thu, 13 Dec 2018 11:35:07 +0100, Colin Leroy-Mira > > wrote: > > > > > On Thu, 13 Dec 2018 10:19:46 +0000, Mark Raynsford > > > wrote: > > > > > > > I recently upgraded my system and I think this may have updated > > > > openssl behind the scenes, causing me to run into certificate > > > > errors when trying to fetch mail over POP3 with Gmail. > > > > > > This is apparently what happens when we don't set SNI: > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1611815 > > > > Could you try that patch ? > > I've built 3.17.1 with that patch and can verify that yes, it solves > the issue. Thanks for the quick update! -- Colin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From ricardo at mones.org Thu Dec 13 14:13:48 2018 From: ricardo at mones.org (Ricardo Mones) Date: Thu, 13 Dec 2018 14:13:48 +0100 Subject: [Users] Claws seeing invalid certificates from pop.gmail.com after upgrade In-Reply-To: <20181213114012.1385628a@colin.i-run.lau> References: <20181213101946.2453f282@almond.int.arc7.info> <20181213113507.6ed038df@colin.i-run.lau> <20181213114012.1385628a@colin.i-run.lau> Message-ID: <20181213131348.GA11845@busgosu> On Thu, Dec 13, 2018 at 11:40:12AM +0100, Colin Leroy-Mira wrote: > On Thu, 13 Dec 2018 11:35:07 +0100, Colin Leroy-Mira > wrote: > > > On Thu, 13 Dec 2018 10:19:46 +0000, Mark Raynsford > > wrote: > > > > > I recently upgraded my system and I think this may have updated > > > openssl behind the scenes, causing me to run into certificate errors > > > when trying to fetch mail over POP3 with Gmail. > > > > This is apparently what happens when we don't set SNI: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1611815 > > Could you try that patch ? http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4103 regards, -- Ricardo Mones ~ Don't take the name of root in vain. /usr/src/linux/README -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From colin at colino.net Thu Dec 13 16:06:29 2018 From: colin at colino.net (Colin Leroy-Mira) Date: Thu, 13 Dec 2018 16:06:29 +0100 Subject: [Users] Claws seeing invalid certificates from pop.gmail.com after upgrade In-Reply-To: <20181213131348.GA11845@busgosu> References: <20181213101946.2453f282@almond.int.arc7.info> <20181213113507.6ed038df@colin.i-run.lau> <20181213114012.1385628a@colin.i-run.lau> <20181213131348.GA11845@busgosu> Message-ID: <20181213160629.132c9c0c@colin.i-run.lau> On Thu, 13 Dec 2018 14:13:48 +0100, Ricardo Mones wrote: > http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4103 > > regards, Ah, great :) I see Hoa merged the changes in libetpan, we should probably do the same. Alex's patch is more complete than mine. We'd need Hoa to release libetpan and add a version check around the mailstream_ssl_set_server_name() call too. I'll contact him. -- Colin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From ricardo at mones.org Thu Dec 13 16:14:26 2018 From: ricardo at mones.org (Ricardo Mones) Date: Thu, 13 Dec 2018 16:14:26 +0100 Subject: [Users] Claws seeing invalid certificates from pop.gmail.com after upgrade In-Reply-To: <20181213160629.132c9c0c@colin.i-run.lau> References: <20181213101946.2453f282@almond.int.arc7.info> <20181213113507.6ed038df@colin.i-run.lau> <20181213114012.1385628a@colin.i-run.lau> <20181213131348.GA11845@busgosu> <20181213160629.132c9c0c@colin.i-run.lau> Message-ID: <20181213151426.GB11845@busgosu> On Thu, Dec 13, 2018 at 04:06:29PM +0100, Colin Leroy-Mira wrote: > On Thu, 13 Dec 2018 14:13:48 +0100, Ricardo Mones > wrote: > > > http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4103 > > > > regards, > > Ah, great :) I see Hoa merged the changes in libetpan, we should > probably do the same. Alex's patch is more complete than mine. > > We'd need Hoa to release libetpan and add a version check around the > mailstream_ssl_set_server_name() call too. Yep, that libetpan release would be nice to have. > I'll contact him. Cool, thanks! -- Ricardo Mones ~ Absence of evidence is not evidence of absence. Carl Sagan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From sylpheed at 911networks.com Thu Dec 13 19:19:35 2018 From: sylpheed at 911networks.com (sylpheed at 911networks.com) Date: Thu, 13 Dec 2018 10:19:35 -0800 Subject: [Users] Switching system Message-ID: <20181213101935.408b074b@frogguski.911networks.com> I've been using CM with RSSyl for many, many moons... I'm using xfce and now I'm switching to kde. What do I need to backup (data & configs) to switch? ~/.claws-mail ~/Mail What else do I need to backup? -- sknahT vyS From claws at thewildbeast.co.uk Thu Dec 13 20:23:02 2018 From: claws at thewildbeast.co.uk (Paul) Date: Thu, 13 Dec 2018 19:23:02 -0000 Subject: [Users] Switching system In-Reply-To: <20181213101935.408b074b@frogguski.911networks.com> References: <20181213101935.408b074b@frogguski.911networks.com> Message-ID: <20181213192302.244e571f@localhost> On Thu, 13 Dec 2018 10:19:35 -0800 sylpheed at 911networks.com wrote: > ~/.claws-mail > ~/Mail > > What else do I need to backup? That's it. ~/.claws-mail contains all the config files (and imap cache if you're using IMAP). ~/Mail is the default location for the MH mailbox, so if you didn't change that, then that is all. Remember to preserve timestamps when you copy/restore. with regards Paul From sylpheed at 911networks.com Thu Dec 13 20:45:33 2018 From: sylpheed at 911networks.com (sylpheed at 911networks.com) Date: Thu, 13 Dec 2018 11:45:33 -0800 Subject: [Users] Switching system In-Reply-To: <20181213192302.244e571f@localhost> References: <20181213101935.408b074b@frogguski.911networks.com> <20181213192302.244e571f@localhost> Message-ID: <20181213114533.178f2d67@frogguski.911networks.com> On Thu, 13 Dec 2018 19:23:02 -0000 Paul wrote: >On Thu, 13 Dec 2018 10:19:35 -0800 >sylpheed at 911networks.com wrote: > >> ~/.claws-mail >> ~/Mail >> >> What else do I need to backup? > >That's it. ~/.claws-mail contains all the config files (and imap >cache if you're using IMAP). > >~/Mail is the default location for the MH mailbox, so if you didn't >change that, then that is all. > >Remember to preserve timestamps when you copy/restore. Thank you for: 1. quick response 2. making (not just you, but also all the developers) a "clean system" -- sknahT vyS From ticho at claws-mail.org Thu Dec 13 21:10:01 2018 From: ticho at claws-mail.org (Andrej Kacian) Date: Thu, 13 Dec 2018 21:10:01 +0100 Subject: [Users] Switching system In-Reply-To: <20181213192302.244e571f@localhost> References: <20181213101935.408b074b@frogguski.911networks.com> <20181213192302.244e571f@localhost> Message-ID: <20181213211001.561c1076@penny> On Thu, 13 Dec 2018 19:23:02 -0000 Paul wrote: > Remember to preserve timestamps when you copy/restore. Mentioning this just for completeness - also make sure that dotfiles (files with names beginning with a dot) get copied too - some tools skip them by default. Regards, -- Andrej -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From silver.bullet at zoho.com Thu Dec 13 21:47:21 2018 From: silver.bullet at zoho.com (Ralf Mardorf) Date: Thu, 13 Dec 2018 21:47:21 +0100 Subject: [Users] Switching system In-Reply-To: <20181213211001.561c1076@penny> References: <20181213101935.408b074b@frogguski.911networks.com> <20181213192302.244e571f@localhost> <20181213211001.561c1076@penny> Message-ID: <20181213214721.61af22c0@utnubu> If you should use plugins, then don't miss to copy plugin related directories/files, such as '~/.bogofilter'. From list at eworm.de Thu Dec 13 23:12:01 2018 From: list at eworm.de (Christian Hesse) Date: Thu, 13 Dec 2018 23:12:01 +0100 Subject: [Users] mixed search server error Message-ID: <20181213231201.4256738b@leda> Hello everybody, starting a mixed search (choose "From/To/Cc/Subject/Tag" in quick search bar) makes claws-mail pop up a number of messages on one of my accounts: Search failed due to server error. The network log gives: [23:09:51] IMAP> 8 UID SEARCH KEYWORD x [23:09:51] IMAP< 8 BAD Command Argument Error. 11 ** IMAP error on mail.example.com: protocol error (very probably non-RFC compliance from the server) ** IMAP connection broken I think this is because the server does not support client defined keywords in flags. Any chance to fix this? https://tools.ietf.org/html/rfc3501#section-2.3.2 -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);} -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From claws at thewildbeast.co.uk Fri Dec 14 00:07:54 2018 From: claws at thewildbeast.co.uk (Paul) Date: Thu, 13 Dec 2018 23:07:54 -0000 Subject: [Users] Switching system In-Reply-To: <20181213214721.61af22c0@utnubu> References: <20181213101935.408b074b@frogguski.911networks.com> <20181213192302.244e571f@localhost> <20181213211001.561c1076@penny> <20181213214721.61af22c0@utnubu> Message-ID: <20181213230754.65cc4c9d@localhost> On Thu, 13 Dec 2018 21:47:21 +0100 Ralf Mardorf wrote: > If you should use plugins, then don't miss to copy plugin related > directories/files, such as '~/.bogofilter'. That's an answer to an equivalent bogofilter question. You surely don't want to list all the different aspects of the system that claws-mail might make use of in order to answer the question? with regards Paul From ticho at claws-mail.org Fri Dec 14 01:22:26 2018 From: ticho at claws-mail.org (Andrej Kacian) Date: Fri, 14 Dec 2018 01:22:26 +0100 Subject: [Users] mixed search server error In-Reply-To: <20181213231201.4256738b@leda> References: <20181213231201.4256738b@leda> Message-ID: <20181214012206.49410650@penny> On Thu, 13 Dec 2018 23:12:01 +0100 Christian Hesse wrote: > Hello everybody, > > starting a mixed search (choose "From/To/Cc/Subject/Tag" in quick search bar) > makes claws-mail pop up a number of messages on one of my accounts: > > Search failed due to server error. > > The network log gives: > > [23:09:51] IMAP> 8 UID SEARCH KEYWORD x > [23:09:51] IMAP< 8 BAD Command Argument Error. 11 > ** IMAP error on mail.example.com: protocol error (very probably > non-RFC compliance from the server) > ** IMAP connection broken > > I think this is because the server does not support client defined keywords > in flags. Any chance to fix this? > > https://tools.ietf.org/html/rfc3501#section-2.3.2 There was a bit of a discussion, albeit inconclusive, about it on this ML in August, see https://lists.claws-mail.org/pipermail/users/2018-August/022393.html -- Andrej -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From list at eworm.de Fri Dec 14 08:04:39 2018 From: list at eworm.de (Christian Hesse) Date: Fri, 14 Dec 2018 08:04:39 +0100 Subject: [Users] mixed search server error In-Reply-To: <20181214012206.49410650@penny> References: <20181213231201.4256738b@leda> <20181214012206.49410650@penny> Message-ID: <20181214080439.28f3f523@leda> Andrej Kacian on Fri, 2018/12/14 01:22: > On Thu, 13 Dec 2018 23:12:01 +0100 > Christian Hesse wrote: > > > Hello everybody, > > > > starting a mixed search (choose "From/To/Cc/Subject/Tag" in quick search > > bar) makes claws-mail pop up a number of messages on one of my accounts: > > > > Search failed due to server error. > > > > The network log gives: > > > > [23:09:51] IMAP> 8 UID SEARCH KEYWORD x > > [23:09:51] IMAP< 8 BAD Command Argument Error. 11 > > ** IMAP error on mail.example.com: protocol error (very probably > > non-RFC compliance from the server) > > ** IMAP connection broken > > > > I think this is because the server does not support client defined > > keywords in flags. Any chance to fix this? > > > > https://tools.ietf.org/html/rfc3501#section-2.3.2 > > There was a bit of a discussion, albeit inconclusive, about it on this > ML in August, see > https://lists.claws-mail.org/pipermail/users/2018-August/022393.html Damn, I missed that discussing and it is already purged from my inbox. However, citing the RFC: > A keyword is defined by the server implementation. Keywords do not > begin with "\". Servers MAY permit the client to define new keywords > in the mailbox (see the description of the PERMANENTFLAGS response > code for more information). So this is optional and should not result in an error. The server gives PERMANENTFLAGS indeed: [07:56:58] IMAP< * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags So this is something to take into consideration... -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);} -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From claws at thewildbeast.co.uk Fri Dec 14 09:17:29 2018 From: claws at thewildbeast.co.uk (Paul) Date: Fri, 14 Dec 2018 08:17:29 -0000 Subject: [Users] Claws Mail 3.17.2 unleashed!!! Message-ID: <20181214081729.4b4be577@localhost> 14th December 2018 Claws Mail 3.17.2 CLAWS MAIL RELEASE NOTES http://www.claws-mail.org Claws Mail is a GTK+ based, user-friendly, lightweight, and fast email client. New in this release: ~~~~~~~~~~~~~~~~~~~~ * Message List: A context menu has been added to the column headers, it has two entries: a new option, 'Lock column headers', and 'Set displayed colums'. * Folder List: A context menu has been added to the column headers, containing 'Set displayed columns'. * Preferences: The Display/Summaries option page has been split into three notebook pages: Folder List, Message List, and Defaults. The Message List page contains the new 'Lock column headers' option. The Defaults page contains several new options for new folders. * New Folder Properties: It is now possible to control signing and encrypting options on the Compose page. By default it follows the Account preferences, but they can be overridden to always sign and/or encrypt, or never sign/encrypt. * Saving sent messages: The global preference, 'Save sent messages', can now be overriden by the Folder Property and Account preferences. The global preference no longer needs to be activated for the Account Preference, 'Put sent messages in ...' option to function. Likewise, the Folder Property, 'Save copy of outgoing messages to this folder instead of Sent', no longer relies on the global preference being set. * SSL/TLS certificates: The SHA-256 fingerprint is now displayed, and the MD5 fingerprint has been removed. * SSL/TLS certificates list: Status and Expiry columns have been added, and expired and invalid certificates are now clearly indicated. * QuickSearch: body searches are now quicker. * QuickSearch: symbols used in Extended searches are now expanded in the 'Edit' dialogue. * Re-editing: Flags and tags are now preserved when re-editing a message. * Fancy plugin: The minimum required webkitgtk version is now 1.10.0. * PDF Viewer plugin: Ctrl+scroll now zooms. * Tools: added cm-break.pl script, which breaks thread references for the selected messages; textviewer.pl has been updated and now requires perl 5.14.1. * The legacy "sylpheed-claws" symlink is no longer installed in the bindir. * New translation: Portuguese. * Updated translations: Brazilian Portuguese, Catalan, Czech, Danish, Dutch, French, German, Russian, Slovak, Spanish, Swedish, Turkish. * bug fixes: o bug 3418, 'Building on a Cross Compiling toolchain doesn't work' o bug 3889, 'Address and quoted message inconsistent in reply' o bug 4114, 'autogen.sh: Fix argument quoting' o bug 4115, 'autogen: avoid unwarranted re-configure' o bug 4120, 'New cert files are created in $HOME instead of in ~/.claws-mail/certs' o byg 4121, 'Moving a subfolder in another folder erases its processing rules' (sic) o bug 4132, '"Mark all as (un)read" dialog appears when acting on 1 message only' o bug 4133, 'trying to read message from an NNTP group (with all expired articles.' o regression where mail was not being checked at startup when it should have been o links not being opened in browser when Fancy menu is opened with a keyboard o show correct address:port in SOCKS5 proxy connection failure message o prevent unexpected loss of drafted message o Quicksearch eating keypresses it didn't handle o build on Debian 7 o build on FreeBSD, sys/wait.h is needed for WEXITSTATUS macro o Reply from mainwindow menu and toolbar when mainwindow's messageview is hidden o CID 1438531 Fix wrong test leading to dead code o CID 1439871 and validate Unicode char strictly o CID 1439996 and remove unnecessary comparison o Fancy: left-click on links not opening in browser o RSSyl: lost processing rules when renaming folder o annoyance where your current reading is disturbed when a new msg is filtered into the current folder o don't leave the user in limbo when privacy system is 'none' and auto signing/encrypting is set o several memory leaks For further details of the numbered bugs and RFEs listed above see https://www.claws-mail.org/bug/[BUG NUMBER] --------------------------------------------------------------------- See ChangeLog for full information regarding changes in this release. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From dave at howorth.org.uk Fri Dec 14 10:39:46 2018 From: dave at howorth.org.uk (Dave Howorth) Date: Fri, 14 Dec 2018 09:39:46 +0000 Subject: [Users] Switching system In-Reply-To: <20181213230754.65cc4c9d@localhost> References: <20181213101935.408b074b@frogguski.911networks.com> <20181213192302.244e571f@localhost> <20181213211001.561c1076@penny> <20181213214721.61af22c0@utnubu> <20181213230754.65cc4c9d@localhost> Message-ID: <20181214093946.7bd0beb4@acer-suse.lan> On Thu, 13 Dec 2018 23:07:54 -0000 Paul wrote: > On Thu, 13 Dec 2018 21:47:21 +0100 > Ralf Mardorf wrote: > > > If you should use plugins, then don't miss to copy plugin related > > directories/files, such as '~/.bogofilter'. > > That's an answer to an equivalent bogofilter question. You surely > don't want to list all the different aspects of the system that > claws-mail might make use of in order to answer the question? That's true, but to be fair to Ralf, he just used it as an example to point out that there are other directories that might be needed to be backed up to preserve a working claws installation. It seems to me though that this whole discussion has very little point. Syv should be backing up his whole system, certainly his home space, as a matter of course anyway. So there should be no need to make any special backups of claws. And most importantly, changing desktop shouldn't need any backup at all (though of course it's prudent to have one in an excess of caution). From claws at thewildbeast.co.uk Fri Dec 14 11:03:09 2018 From: claws at thewildbeast.co.uk (Paul) Date: Fri, 14 Dec 2018 10:03:09 -0000 Subject: [Users] Switching system In-Reply-To: <20181214093946.7bd0beb4@acer-suse.lan> References: <20181213101935.408b074b@frogguski.911networks.com> <20181213192302.244e571f@localhost> <20181213211001.561c1076@penny> <20181213214721.61af22c0@utnubu> <20181213230754.65cc4c9d@localhost> <20181214093946.7bd0beb4@acer-suse.lan> Message-ID: <20181214100309.12e4e58b@localhost> On Fri, 14 Dec 2018 09:39:46 +0000 Dave Howorth wrote: > That's true, but to be fair to Ralf, he just used it as an example > to point out that there are other directories that might be needed > to be backed up to preserve a working claws installation. Well, that's very fair indeed, since nowhere did he say it was just an example. And not backing up ~/.bogofilter would not prevent claws-mail from working. But you're right - changing DE should not need any backup of the homedir. with regards Paul From littlergirl at gmail.com Fri Dec 14 17:11:12 2018 From: littlergirl at gmail.com (Little Girl) Date: Fri, 14 Dec 2018 11:11:12 -0500 Subject: [Users] Lost my address book and alias accounts In-Reply-To: <43FtTZ2nN6z9rxV@submission02.posteo.de> References: <43B36x16r5z9rxV@submission02.posteo.de> <43FtTZ2nN6z9rxV@submission02.posteo.de> Message-ID: <5c13d63a.1c69fb81.a5ba3.096e@mx.google.com> Hey there, buhtz at posteo.de wrote: >Does no one have an idea about it? I can't help with this, but would someone else please jump in? There are three messages in this thread, besides this one, and they're all from the OP, starting on December 7. See them here: https://lists.claws-mail.org/pipermail/users/2018-December/023400.html -- Little Girl There is no spoon. From iwkse at claws-mail.org Fri Dec 14 17:17:08 2018 From: iwkse at claws-mail.org (Salvatore De Paolis) Date: Fri, 14 Dec 2018 17:17:08 +0100 Subject: [Users] Lost my address book and alias accounts In-Reply-To: <43FtTZ2nN6z9rxV@submission02.posteo.de> References: <43B36x16r5z9rxV@submission02.posteo.de> <43FtTZ2nN6z9rxV@submission02.posteo.de> Message-ID: <20181214171708.2ea40e25@net24.it> Hi buhtz at posteo.de, On Thu, 13 Dec 2018 13:36:31 +0100 wrote: > Does no one have an idea about it? It might happen to have some file corruption, for example if you experienced some power loss or hard reboot. Generally in the configuration folder for claws mail (~./claws-mail ) you should also have the backups as claws mail automatically do save backups. Check in there to recover what you lost. Without further info it's hard to diagnose what could have happened. Cheers, -- Salvatore From noreply at thewildbeast.co.uk Fri Dec 14 19:08:39 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Fri, 14 Dec 2018 18:08:39 +0000 Subject: [Users] [Bug 3519] Links including umlauts are broken In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3519 Andrej Kacian changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|DUPLICATE |FIXED --- Comment #3 from users at lists.claws-mail.org --- Changes related to this bug have been committed. Please check latest Git and update the bug accordingly. You can also get the patch from: http://git.claws-mail.org/ ++ ChangeLog 2018-12-14 18:55:07.281528611 +0100 http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=74e46ecdb43be8fb8d79683426eed3b917f0430d Author: Andrej Kacian Date: Fri Dec 14 18:51:40 2018 +0100 Added unit tests for get_uri_part(). http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=476d7eca501ac7a5b367567297e028e89cc7e716 Author: Andrej Kacian Date: Fri Dec 14 18:50:38 2018 +0100 Make URI highlighting in textview and compose Unicode-aware. Fixes bug #3519: Links including umlauts are broken --- Comment #4 from Andrej Kacian --- Better late than never, I guess. :) -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sat Dec 15 22:22:39 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sat, 15 Dec 2018 21:22:39 +0000 Subject: [Users] [Bug 3519] Links including umlauts are broken In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3519 --- Comment #5 from Ralf Mardorf --- Thank you, the issue is fixed. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sat Dec 15 23:35:14 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sat, 15 Dec 2018 22:35:14 +0000 Subject: [Users] [Bug 4134] New: Claws does not save sent mails Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 Bug ID: 4134 Summary: Claws does not save sent mails Classification: Unclassified Product: Claws Mail Version: 3.17.2 Hardware: PC OS: Linux Status: NEW Severity: critical Priority: P3 Component: Folders/MH Assignee: users at lists.claws-mail.org Reporter: info.mardorf at rocketmail.com If 3.17.2 is installed and I send mails from at least one of my POP accounts, the sent mail is lost. For at least one of my other POP accounts this doesn't happen. If I downgrade to 3.17.1, mails sent from this account are saved again. I tested this by upgrading and downgrading two times: $ grep claws-mail /var/log/pacman.log | grep grade | tail -4 [2018-12-15 18:35] [ALPM] upgraded claws-mail (3.17.1-1 -> 3.17.2-1) [2018-12-15 23:09] [ALPM] downgraded claws-mail (3.17.2-1 -> 3.17.1-1) [2018-12-15 23:10] [ALPM] upgraded claws-mail (3.17.1-1 -> 3.17.2-1) [2018-12-15 23:12] [ALPM] downgraded claws-mail (3.17.2-1 -> 3.17.1-1) Running claws-mail in a terminal doesn't show anything. -- You are receiving this mail because: You are the assignee for the bug. From buhtz at posteo.de Sat Dec 15 23:50:38 2018 From: buhtz at posteo.de (buhtz at posteo.de) Date: Sat, 15 Dec 2018 23:50:38 +0100 Subject: [Users] Lost my address book and alias accounts In-Reply-To: <20181214171708.2ea40e25@net24.it> References: <43B36x16r5z9rxV@submission02.posteo.de> <43FtTZ2nN6z9rxV@submission02.posteo.de> <20181214171708.2ea40e25@net24.it> Message-ID: <43HN1B57ryz9rxH@submission02.posteo.de> Thank you very much for your unswer. So there is hope. But how can I recreate the data? There is e.g. a "addrbook-1.xml" file in the Mail folder. But how do I "reconnect" it with Claws? From noreply at thewildbeast.co.uk Sun Dec 16 00:11:30 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sat, 15 Dec 2018 23:11:30 +0000 Subject: [Users] [Bug 4134] Claws does not save sent mails In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #1 from Paul --- You need to give more details than just 'it fails'. What types of Account (pop, imap)? Do you have the global option set to save sent msgs? What are your account settings (on the Advanced page) for saving sent messages? Do you have the Folder Property set for saving sent msgs in the current folder? etc -- You are receiving this mail because: You are the assignee for the bug. From claws at thewildbeast.co.uk Sun Dec 16 00:16:37 2018 From: claws at thewildbeast.co.uk (Paul) Date: Sat, 15 Dec 2018 23:16:37 -0000 Subject: [Users] Lost my address book and alias accounts In-Reply-To: <43HN1B57ryz9rxH@submission02.posteo.de> References: <43B36x16r5z9rxV@submission02.posteo.de> <43FtTZ2nN6z9rxV@submission02.posteo.de> <20181214171708.2ea40e25@net24.it> <43HN1B57ryz9rxH@submission02.posteo.de> Message-ID: <20181215231637.62857a34@localhost> On Sat, 15 Dec 2018 23:50:38 +0100 wrote: > Thank you very much for your unswer. So there is hope. > > But how can I recreate the data? > > There is e.g. a "addrbook-1.xml" file in the Mail folder. But how > do I "reconnect" it with Claws? In ~/claws-mail/addrbook/ you should have a file called addrbook--index.xml If you don't have it, create it. For connecting your address book folder it should look like this: ----------8<------------------8<----------- ---------->8------------------>8----------- Be sure to edit it or create when claws-mail is not running. with regards Paul From noreply at thewildbeast.co.uk Sun Dec 16 02:04:49 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 01:04:49 +0000 Subject: [Users] [Bug 4134] Claws does not save sent mails In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #2 from Ralf Mardorf --- >What types of Account (pop, imap)? I already mentioned that it is a POP account. >Do you have the global option set to save sent msgs? "Save sent messages" is checked. >What are your account settings (on the Advanced page) for saving sent >messages? Nothing is checked, everything is blank. >Do you have the Folder Property set for saving sent msgs in >the current folder? No. >etc What additional information do you need? -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 16 11:24:54 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 10:24:54 +0000 Subject: [Users] [Bug 4134] Claws does not save sent mails In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #3 from Paul --- (In reply to comment #2) > What additional information do you need? In the Compose window, when you use the failing account, what is the state of the Others tab? Is the checkbox checked? What is the value shown? If a folder is shown, does it exist? -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 16 12:10:43 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 11:10:43 +0000 Subject: [Users] [Bug 4134] Claws does not save sent mails In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #4 from Ralf Mardorf --- If I use 3.17.1 it is [√] Save Message to [#mh/Claws Mail/sent] it's checked and an existing folder. After upgrading to 3.17.2 it becomes [ ] Save message to [#mh/Claws Mail/sent] so it's still the same existing folder, but it's unchecked. This happens to all folders with the same account settings described by my previous reply, excepted of the default account, with the same settings. For the default account it doesn't become unchecked. Accounts with a folder specified by the advanced settings also don't suffer from this bug. All accounts are POP accounts. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 16 12:36:53 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 11:36:53 +0000 Subject: [Users] [Bug 4134] Claws does not save sent mails In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #5 from Paul --- I cannot reproduce this. Is your #mh/Claws Mail/sent folder actually a folder of type 'Outbox'? Right-click #mh/Claws Mail/sent, choose 'Properties'. On the General page, is Folder Type set to 'Outbox'? -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 16 12:52:56 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 11:52:56 +0000 Subject: [Users] [Bug 4134] Claws does not save sent mails In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #6 from Ralf Mardorf --- For 3.17.1 and 3.17.2 it is folder type "Outbox" and it's checked. It's shadowed, I can't uncheck it or select another folder type. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 16 13:21:26 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 12:21:26 +0000 Subject: [Users] [Bug 4134] Claws does not save sent mails In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #7 from Paul --- run this command and tell me the output: grep -rn save_message ~/.claws-mail/clawsrc -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 16 14:28:17 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 13:28:17 +0000 Subject: [Users] [Bug 4134] Claws does not save sent mails In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #8 from Ralf Mardorf --- Created attachment 1942 --> https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=1942&action=edit Advanced settings -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 16 14:28:51 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 13:28:51 +0000 Subject: [Users] [Bug 4134] Claws does not save sent mails In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #9 from Ralf Mardorf --- $ grep -rn save_message ~/.claws-mail/clawsrc 18:save_message=1 -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 16 17:06:09 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 16:06:09 +0000 Subject: [Users] [Bug 4134] Claws does not save sent mails In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #10 from brad at fineby.me.uk --- I experienced mail loss with v3.17.2git1 on one of my accounts. The lost mails were only those that were replies to messages in the account's inbox. Replies to messages filtered to other folders appeared in Sent as they should have. I'm now at 3.17.2git6 and, so far (from a small test sample), replies from the affected account appear in the Sent folder, as expected. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 16 17:14:05 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 16:14:05 +0000 Subject: [Users] [Bug 4134] Claws does not save sent mails In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #11 from Paul --- (In reply to comment #10) > I experienced mail loss with v3.17.2git1 on one of my accounts. The lost > mails were only those that were replies to messages in the account's inbox. > Replies to messages filtered to other folders appeared in Sent as they > should have. > > I'm now at 3.17.2git6 and, so far (from a small test sample), replies from > the affected account appear in the Sent folder, as expected. That's not 'mail loss', it's lack of saving a copy of a sent mail. If it happened at v3.17.2git1 but not 3.17.2git6 than that suggests that it was entirely random. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 16 17:18:23 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 16:18:23 +0000 Subject: [Users] [Bug 4134] Claws does not save sent mails In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #12 from Paul --- (In reply to comment #10) > The lost > mails were only those that were replies to messages in the account's inbox. > Replies to messages filtered to other folders appeared in Sent as they > should have. Did you inspect the Others tab in the Compose window during that? This is about the option to save the sent message not being set when it should be. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 16 17:19:54 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 16:19:54 +0000 Subject: [Users] [Bug 4134] 'Save message to' option not set when it should be In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 Paul changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Folders/MH |UI/Compose Window Summary|Claws does not save sent |'Save message to' option |mails |not set when it should be -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 16 17:44:30 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 16:44:30 +0000 Subject: [Users] [Bug 4134] 'Save message to' option not set when it should be In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #13 from Paul --- Ralf, what are the values of 'inbox' for each of the accounts in ~/.claws-mail/accountrc? Please also indicate which is the default account. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 16 18:26:11 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 16 Dec 2018 17:26:11 +0000 Subject: [Users] [Bug 4134] 'Save message to' option not set when it should be In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #14 from Ralf Mardorf --- I added comments and empty lines as separator to the grep output and shortened the addresses. $ grep -e address -e inbox -e sent ~/.claws-mail/accountrc address=[snip]alice-dsl.net inbox=#mh/Claws Mail/inbox local_inbox=#mh/Claws Mail/inbox set_sent_folder=0 sent_folder= address=[snip]rocketmail.com ### This is the default account inbox=#mh/Claws Mail/inbox local_inbox=#mh/Claws Mail/inbox set_sent_folder=0 sent_folder= address=[snip]rocketmail.com inbox=#mh/Claws Mail/inbox local_inbox=#mh/Claws Mail/inbox set_sent_folder=0 sent_folder= address=[snip]zoho.com inbox=#mh/Claws Mail/inbox local_inbox=#mh/Claws Mail/inbox set_sent_folder=1 sent_folder=#mh/Claws Mail/The shared/KDE+Ubuntu+ address=[snip]yahoo.com inbox=#mh/Claws Mail/inbox local_inbox=#mh/Claws Mail/inbox set_sent_folder=0 sent_folder= address=[snip]rocketship.com ### For this account 'Get Mail' is disabled inbox=#mh/Claws Mail/trash local_inbox=#mh/Claws Mail/inbox set_sent_folder=1 sent_folder=#mh/Claws Mail/trash ### moving to trash is wanted for this account Incoming mails are filtered, the last filter rule is $ tail -2 ~/.claws-mail/matcherrc enabled rulename "End Share Inbox" all move "#mh/Claws Mail/The shared" so mails are not stored in the default inbox, they either have their own folders or are saved in 'The shared' folder. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Mon Dec 17 06:51:40 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Mon, 17 Dec 2018 05:51:40 +0000 Subject: [Users] [Bug 4135] New: Open last opened folder at start-up Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4135 Bug ID: 4135 Summary: Open last opened folder at start-up Classification: Unclassified Product: Claws Mail Version: GIT Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P3 Component: UI Assignee: users at lists.claws-mail.org Reporter: pf at pfortin.com When this preference is selected, it would be great if the currently open message was re-opened at start-up instead of the last/most current one. -- You are receiving this mail because: You are the assignee for the bug. From jimmy.patch at gmail.com Mon Dec 17 09:29:11 2018 From: jimmy.patch at gmail.com (Jim Pachowski) Date: Mon, 17 Dec 2018 13:59:11 +0530 Subject: [Users] Lost my address book and alias accounts In-Reply-To: <43B36x16r5z9rxV@submission02.posteo.de> References: <43B36x16r5z9rxV@submission02.posteo.de> Message-ID: On Fri, Dec 7, 2018 at 12:22 PM wrote: > Opening Claws I got the messing "addressbook index missing". The > adressbook is empty. I found this on the mailing list archives that could be helpful in recovering the address books: https://lists.claws-mail.org/pipermail/users/2015-July/013543.html From noreply at thewildbeast.co.uk Mon Dec 17 11:19:49 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Mon, 17 Dec 2018 10:19:49 +0000 Subject: [Users] [Bug 4134] 'Save message to' option not set when it should be In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #15 from brad at fineby.me.uk --- (In reply to comment #11) > That's not 'mail loss', it's lack of saving a copy of a sent mail. Indeed. My apologies. A poor choice of words on my part. > If it happened at v3.17.2git1 but not 3.17.2git6 than that suggests that it > was entirely random. Except that two people experienced a similar sequence of events, and those events were repeatable. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Mon Dec 17 11:22:18 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Mon, 17 Dec 2018 10:22:18 +0000 Subject: [Users] [Bug 4134] 'Save message to' option not set when it should be In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #16 from brad at fineby.me.uk --- (In reply to comment #12) > Did you inspect the Others tab in the Compose window during that? This is > about the option to save the sent message not being set when it should be. Set to "Save to Sent" -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Mon Dec 17 11:47:26 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Mon, 17 Dec 2018 10:47:26 +0000 Subject: [Users] [Bug 4135] Open last opened email at start-up In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4135 Paul changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Open last opened folder at |Open last opened email at |start-up |start-up -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Mon Dec 17 12:26:52 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Mon, 17 Dec 2018 11:26:52 +0000 Subject: [Users] [Bug 4134] 'Save message to' option not set when it should be In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 Paul changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #17 from users at lists.claws-mail.org --- Changes related to this bug have been committed. Please check latest Git and update the bug accordingly. You can also get the patch from: http://git.claws-mail.org/ ++ ChangeLog 2018-12-17 12:21:05.099462324 +0100 http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=6f9b6e1626343e64e5ef038bb4236aad0cdd9373 Author: Paul Date: Mon Dec 17 11:20:13 2018 +0000 fix bug 4134, ''Save message to' option not set when it should be' --- Comment #18 from Paul --- Eventually, I managed to reproduce this, (thanks to extra diagnostic by Andrej). It only happen[s|ed] when changing account in the Compose window. I assume this is the same for you but it is a detail you left out. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Tue Dec 18 07:13:32 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Tue, 18 Dec 2018 06:13:32 +0000 Subject: [Users] [Bug 4134] 'Save message to' option not set when it should be In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4134 --- Comment #19 from Ralf Mardorf --- Thank you, the issue is fixed. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Tue Dec 18 09:40:31 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Tue, 18 Dec 2018 08:40:31 +0000 Subject: [Users] [Bug 4136] New: Quick search throws bad command argument error 11 on Microsoft Exchange Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4136 Bug ID: 4136 Summary: Quick search throws bad command argument error 11 on Microsoft Exchange Classification: Unclassified Product: Claws Mail Version: 3.17.1 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P3 Component: Filtering Assignee: users at lists.claws-mail.org Reporter: pierre.berthier at bioinformatics.unibe.ch Right after Upgrading from Ubuntu 18.04 to 18.10 (hence claws-mail from 3.16.0 to 3.17.1) I get the following problem. With a quicksearch "From/To/Subject/Tag" equal to "blah" (or any other non empty value) and Flags: Recursive, Sticky I get an error (here IMAP log:) IMAP> 6 UID SEARCH KEYWORD blah IMAP< 6 BAD Command Argument Error. 11 ** IMAP error on mail.campus.unibe.ch: protocol error (very probably non-RFC compliance from the server) ** IMAP connection broken Server is Microsoft Exchange client: Claws Mail 3.17.1 on Ubuntu 18.10 (package version: 3.17.1-1) Reproducibility: always. This looks identical to an old Bug 2744. Maybe this is a regression? -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Tue Dec 18 09:44:35 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Tue, 18 Dec 2018 08:44:35 +0000 Subject: [Users] [Bug 4136] Quick search throws bad command argument error 11 on Microsoft Exchange In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4136 --- Comment #1 from pierre.berthier at bioinformatics.unibe.ch --- BTW when I click on close on the error message window, the search results appear correctly, it's just that there is always first this error message popping up. so it's not super critical, but annoying. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Tue Dec 18 11:27:41 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Tue, 18 Dec 2018 10:27:41 +0000 Subject: [Users] [Bug 4103] TLS SNI (Server Name Indication) support for IMAP, POP & SMTP In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4103 --- Comment #1 from Andrej Kacian --- Libetpan 1.9.2 has been released with SNI support (https://github.com/dinhviethoa/libetpan/releases/tag/1.9.2). However, I am wondering whether using SNI unconditionally is a good idea from security point of view, since it sends the domain name in plaintext. I certainly don't need it for my personal servers. -- You are receiving this mail because: You are the assignee for the bug. From ticho at claws-mail.org Tue Dec 18 16:48:57 2018 From: ticho at claws-mail.org (Andrej Kacian) Date: Tue, 18 Dec 2018 16:48:57 +0100 Subject: [Users] Screenshots of Claws gtk2 and gtk3 In-Reply-To: <20181107210419.4f1950bb@utnubu> References: <20181107210419.4f1950bb@utnubu> Message-ID: <20181218164857.78ec4c45@penny> On Wed, 7 Nov 2018 21:04:19 +0100 Ralf Mardorf wrote: > Hi, > > the gtk3 version doesn't look bad. > > claws gtk2 https://i.imgur.com/vczASne.png > claws gtk3 https://i.imgur.com/X1XDeHk.png Wow, this actually looks much better (or rather much less different from GTK2 version) than the GTK3 version on my system. You must have a nicer theme. :) > Ensure that the screenshots are shown full size, by a mouse click. > > There are several graphic issues, if I move the mouse pointer or use > the mouse scroll wheel. I believe you are referring to broken redrawing of folder and message lists when scrolling. This is something that has been bothering me for a long time, but today I finally found a way to fix it. Let me know if you see some more weird graphical issues like that, anywhere in the program. > The "Compose Email" button doesn't work at all. Works for me just fine. Does this happen only for a particular account or always? Can you send me debug output that appears when you click the button? > It was a very short test... > > [rocketmouse at archlinux aur]$ grep claws-mail /var/log/pacman.log | grep 2018-11-07 > [2018-11-07 20:32] [PACMAN] Running 'pacman -U claws-mail-gtk3-git-3.16.0.r463.g04185a6e4-1-x86_64.pkg.tar.xz' > [2018-11-07 20:32] [ALPM] removed claws-mail (3.17.1-1) > [2018-11-07 20:32] [ALPM] installed claws-mail-gtk3-git (3.16.0.r463.g04185a6e4-1) > [2018-11-07 20:40] [PACMAN] Running 'pacman -S claws-mail' > [2018-11-07 20:40] [ALPM] removed claws-mail-gtk3-git (3.16.0.r463.g04185a6e4-1) > [2018-11-07 20:40] [ALPM] installed claws-mail (3.17.1-1) > > ...but I'll test it again. Thanks, more testers are always appreciated. I am hoping that once we make Fancy work on the GTK3 version, that together with the scrolling fix I mentioned, the GTK3 version should be free of any major bugs, and that more people start using and testing it, and report issues. :) Regards, -- Andrej -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From noreply at thewildbeast.co.uk Tue Dec 18 21:09:26 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Tue, 18 Dec 2018 20:09:26 +0000 Subject: [Users] [Bug 4137] New: When changing back to Inbox clawsmail 3.16.0 jumps to oldest Mail Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4137 Bug ID: 4137 Summary: When changing back to Inbox clawsmail 3.16.0 jumps to oldest Mail Classification: Unclassified Product: Claws Mail Version: other Hardware: PC OS: Linux Status: NEW Severity: minor Priority: P3 Component: Folders Assignee: users at lists.claws-mail.org Reporter: biosflash at web.de Please, delete this if any doubt, just is that reproducably I have no clue how to NOT use the scrollbar to get to the latest mail, when changing back to INBOX. any way I sort for "date" it will fall back to the second oldest,when changing back to INBOX. otherwise great app. my first manual bugreport. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Tue Dec 18 22:38:50 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Tue, 18 Dec 2018 21:38:50 +0000 Subject: [Users] [Bug 4137] When changing back to Inbox clawsmail 3.16.0 jumps to oldest Mail In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4137 Paul changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Paul --- There are options for that. Go to /Configuration/Preferences/Display/Summaries Click the button 'Set message selection when entering a folder', and choose and/or rearrange what you want from the available choices. Please use either users' mailing list or the IRC channel for help in future. https://www.claws-mail.org/MLs.php -- You are receiving this mail because: You are the assignee for the bug. From removed-gdpr at example.com Wed Dec 19 11:34:19 2018 From: removed-gdpr at example.com (Removed after GDPR request) Date: Wed, 19 Dec 2018 12:34:19 +0200 Subject: [Users] Replies appear as unread in ignored thread In-Reply-To: <20181203210345.6d1ab874@penny> References: <20181127185620.56f0ac79@localhost> <20181201105142.3c873cd1@localhost> <20181202000027.00006925@prost.fenrir.org.uk> <20181202124123.584ae97e@localhost> <20181203210345.6d1ab874@penny> Message-ID: <20181219123419.6b8102b7@localhost> On Mon, 3 Dec 2018 21:03:45 +0100 Andrej Kacian wrote: > Do you have the "Thread using subject in addition to > standard headers" option enabled in preferences? No. > Messages are only considered as "belonging to > thread" if they are connected by their In-Reply-To > and/or References headers. I understand that and they do display as threaded. > I'm not sure if that's correct, but it does make > certain sense - a message which has those two > headers can be considered belonging to a different > thread, so we do not want to have the "ignored > thread" flag spread to this thread from the original > thread. The last 3 messages are the exact same ones from my last screenshot and there are no threads with that subject from any older archived month in 2018: http://lists.llvm.org/pipermail/cfe-dev/2018-November/thread.html So it seems to me this is not a case of a partial (sub)thread. I will email you the 3 messages so you can have a deeper look. -- George From removed-gdpr at example.com Wed Dec 19 12:00:57 2018 From: removed-gdpr at example.com (Removed after GDPR request) Date: Wed, 19 Dec 2018 13:00:57 +0200 Subject: [Users] Clawsker: Can't locate object method "name" via package "Gtk3::Accelerator" Message-ID: <20181219130057.2949ecc9@localhost> Hi, I haven't used Clawsker much after it was made to use Gtk3. Today I wanted to assign a new shortcut key. When running the program from console and double clicking a menu entry in order to assign the shortcut these messages show: *** unhandled exception in callback: *** Can't locate object method "name" via package "Gtk3::Accelerator" (perhaps you forgot to load "Gtk3::Accelerator"?) at /opt/clawsker/bin/clawsker line 2109. *** ignoring at /home/████/perl5/lib/perl5/Gtk3.pm line 558. And in Clawsker itself I cannot assign the key. It simply scrolls up to the very top of the menu list that's all. I suppose I am missing some module. What do I have to do to fix this? -- George From jjk at jjacky.com Wed Dec 19 18:07:03 2018 From: jjk at jjacky.com (Olivier Brunel) Date: Wed, 19 Dec 2018 18:07:03 +0100 Subject: [Users] Tweak date_after/date_before criteria Message-ID: <20181219180703.629b2d12@jjacky.com> Hey Colin, everyone, So after upgrading to 3.17.2 I discovered the new criteria date_after/date_before (nice additions btw) and as I was using them a bit, I found myself in presence of a few little annoyances, nothing major, but here's a patch to see about resolving them. - when editing date criteria, having the calendar always visible was not good for me. I'm sure other people/setup will have different experiences, and my window may not be as tall as others, but for me it made things quite ugly, and worse, because the calendar eats up so much space the list of rules was basically reduced down to be unreadable/invisible, which I find to be a big usability issue. So, instead have a button for the date, that will pop up the calendar on demand. - I was also unhappy with the time selection and the long list of times, so switched to three spin buttons. I find it makes it easier to set a specific time (esp. via middle/right click on arrows) and also fixes the issue that previously only time with seconds worked but seconds weren't actually recognized/loaded in the UI, so they would be lost/reset to zero (And trying to set seconds in the entry would result in a "invalid hour" error.) - Lastly, changed the way the parsing is done so that it's not just the entire time that is optional, but each elements. I.e. one can use "2018-7-4 14:18" and it'll work without having to specify seconds. I find that quite useful as often times one might not care about seconds, but it was required to specify them anyhow (else the entire time was ignored). Also, when time is not specified, default to 23:59:59 for date_after (and 00:00:00 for date_before, ofc). This feels better/more likely to match use expectations to me, because if one wants all messages before the 4th, one indeed usually expected messages from the 3rd or before, but not the 4th. But similarly, if one wants messages after the 4th, one would usually expect messages from the 5th or after, but not the 4th (so long as they're not from 00:00:00). Hopefully this all makes sense. Those criteria were a nice addition, and IMO these little changes help make them even a bit better. Here's to hoping I'm not alone there. Cheers, PS: Unless I missed it, it seems the addition of those criteria was left out of the release notes. I assume this wasn't on purpose, and maybe something to keep in mind for next release, as it might be worth pointing out. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Filtering-Tweak-date_after-date_before-criteria.patch Type: text/x-patch Size: 15444 bytes Desc: not available URL: From jjk at jjacky.com Wed Dec 19 17:12:18 2018 From: jjk at jjacky.com (Olivier Brunel) Date: Wed, 19 Dec 2018 17:12:18 +0100 Subject: [Users] Couple of small patches Message-ID: <20181219171218.02cb704d@jjacky.com> Hey all, Just a couple of small independant patches, one to process (GTK) events more often during a search (to try and make UI a bit more responsive), and another so pressing ESC during a quicksearch will actually/only cancel said search. Cheers, -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Make-UI-more-responsive-during-searches.patch Type: text/x-patch Size: 806 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-quicksearch-ESC-will-only-abort-running-search.patch Type: text/x-patch Size: 1168 bytes Desc: not available URL: From subscript at free.fr Wed Dec 19 18:50:55 2018 From: subscript at free.fr (wwp) Date: Wed, 19 Dec 2018 18:50:55 +0100 Subject: [Users] Tweak date_after/date_before criteria In-Reply-To: <20181219180703.629b2d12@jjacky.com> References: <20181219180703.629b2d12@jjacky.com> Message-ID: <20181219185036.31976d8f@ladybug> Hello Olivier, On Wed, 19 Dec 2018 18:07:03 +0100 Olivier Brunel wrote: > Hey Colin, everyone, > > So after upgrading to 3.17.2 I discovered the new criteria > date_after/date_before (nice additions btw) and as I was using them a > bit, I found myself in presence of a few little annoyances, nothing > major, but here's a patch to see about resolving them. [snip] > > Hopefully this all makes sense. Those criteria were a nice addition, Indeed! > and IMO these little changes help make them even a bit better. Here's to > hoping I'm not alone there. [snip] I'm in a complete agreement w/ all the above-mentioned points. Patch applied locally, testing.. Regards, -- wwp -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: From ricardo at mones.org Wed Dec 19 20:43:43 2018 From: ricardo at mones.org (Ricardo Mones) Date: Wed, 19 Dec 2018 20:43:43 +0100 Subject: [Users] Clawsker: Can't locate object method "name" via package "Gtk3::Accelerator" In-Reply-To: <20181219130057.2949ecc9@localhost> References: <20181219130057.2949ecc9@localhost> Message-ID: <20181219204343.42b371bb@busgosu> On Wed, 19 Dec 2018 13:00:57 +0200 Removed after GDPR request wrote: > I haven't used Clawsker much after it was made to use > Gtk3. Today I wanted to assign a new shortcut key. > When running the program from console and double > clicking a menu entry in order to assign the shortcut > these messages show: > > *** unhandled exception in callback: > *** Can't locate object method "name" via package > "Gtk3::Accelerator" (perhaps you forgot to load "Gtk3::Accelerator"?) > at /opt/clawsker/bin/clawsker line 2109. *** ignoring > at /home/████/perl5/lib/perl5/Gtk3.pm line 558. > > And in Clawsker itself I cannot assign the key. It > simply scrolls up to the very top of the menu list > that's all. > > I suppose I am missing some module. > What do I have to do to fix this? Not missing anything, this was a bug, and it's already fixed in master. If you're running git just pull latest head, otherwise wait a bit for the upcoming bugfix release. thanks for reporting, -- Ricardo Mones ~ The world will end in 5 minutes. Please log out. Unknown -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: Firma digital OpenPGP URL: From noreply at thewildbeast.co.uk Wed Dec 19 22:45:10 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Wed, 19 Dec 2018 21:45:10 +0000 Subject: [Users] [Bug 4103] TLS SNI (Server Name Indication) support for IMAP, POP & SMTP In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4103 --- Comment #2 from Alex Smith --- (In reply to comment #1) > However, I am wondering whether using SNI unconditionally is a good idea > from security point of view No, I was always planning to make it optional in the proper patch. The experimental patch I attached was very much the bare minimum necessary to allow people to test and provide feedback as to whether the low-level changes work or not. I'm thinking of adding a check box to the SSL/TLS page of the account settings window so that SNI can be enabled only on those accounts that need it, or at least, can be disabled on accounts that don't need it. I'm leaning towards making it on by default on the following grounds: - The privacy / security implications of the name being transmitted in the clear are most relevant where SNI *is* needed; typically if it isn't needed then the destination IP address uniquely maps to a single domain name anyway and hence the information can typically be obtained regardless. - Those who know that SNI is not needed and who care about hiding which domain name the connection is for are reasonably likely to have the knowledge and experience required to find and turn off the option. - Some widely used services like gmail require it so those who will need it and will want things to "Just Work(tm)" without much effort may be the majority. - A future TLS version is likely to fill the known hole in SNI so at some point the concern may well go away of its own accord. Arguments to the contrary welcome! -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Wed Dec 19 23:32:14 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Wed, 19 Dec 2018 22:32:14 +0000 Subject: [Users] [Bug 4103] TLS SNI (Server Name Indication) support for IMAP, POP & SMTP In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4103 --- Comment #3 from Andrej Kacian --- Yes, an account preference, enabled by default, is what we agreed upon on IRC as well, so full agreement there. :) We are planning a quick bugfix release this week, but since adding the checkbox to account preferences dialog would mean adding new translatable string(s), I think it would be best to introduce it as a hidden preference (controllable only by directly editing accountrc file) for now, and add the proper checkbox in a future release. Any other opinions on this? We definitely need to add that preference from the get go, in order to avoid issues for users who might be using servers without SNI support. -- You are receiving this mail because: You are the assignee for the bug. From colin at colino.net Thu Dec 20 09:00:04 2018 From: colin at colino.net (Colin Leroy-Mira) Date: Thu, 20 Dec 2018 09:00:04 +0100 Subject: [Users] Couple of small patches In-Reply-To: <20181219171218.02cb704d@jjacky.com> References: <20181219171218.02cb704d@jjacky.com> Message-ID: <20181220090004.48a2424a@colin.i-run.lau> On Wed, 19 Dec 2018 17:12:18 +0100, Olivier Brunel wrote: > procmsg_msginfo_free(&msg); > > + gtk_main_iteration_do (FALSE); > if (progress_cb != NULL Doesn't performing a gtk iteration each message drop search performance badly ? -- Colin From colin at colino.net Thu Dec 20 09:01:53 2018 From: colin at colino.net (Colin Leroy-Mira) Date: Thu, 20 Dec 2018 09:01:53 +0100 Subject: [Users] Tweak date_after/date_before criteria In-Reply-To: <20181219180703.629b2d12@jjacky.com> References: <20181219180703.629b2d12@jjacky.com> Message-ID: <20181220090153.3583b177@colin.i-run.lau> On Wed, 19 Dec 2018 18:07:03 +0100, Olivier Brunel wrote: Hi, Seems like a good patch! > PS: Unless I missed it, it seems the addition of those criteria was > left out of the release notes. I assume this wasn't on purpose, and > maybe something to keep in mind for next release, as it might be worth > pointing out. I think it arrived in 3.17.1 :) -- Colin From noreply at thewildbeast.co.uk Thu Dec 20 09:03:58 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Thu, 20 Dec 2018 08:03:58 +0000 Subject: [Users] [Bug 4103] TLS SNI (Server Name Indication) support for IMAP, POP & SMTP In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4103 --- Comment #4 from Colin Leroy --- Completely agree with you guys :) -- You are receiving this mail because: You are the assignee for the bug. From removed-gdpr at example.com Thu Dec 20 11:29:50 2018 From: removed-gdpr at example.com (Removed after GDPR request) Date: Thu, 20 Dec 2018 12:29:50 +0200 Subject: [Users] Clawsker: Can't locate object method "name" via package "Gtk3::Accelerator" In-Reply-To: <20181219204343.42b371bb@busgosu> References: <20181219130057.2949ecc9@localhost> <20181219204343.42b371bb@busgosu> Message-ID: <20181220122950.40c2adae@localhost> On Wed, 19 Dec 2018 20:43:43 +0100 Ricardo Mones wrote: > Not missing anything, this was a bug, and it's > already fixed in master. > > If you're running git just pull latest head, > otherwise wait a bit for the upcoming bugfix release. Thanks Ricardo! I have done that and now I can assign the shortcut. However when I double click the item I want to associate Clawsker still scrolls all the way up (if I am trying to associate say View->Expand All Threads). Is that probably another bug that needs fixing? -- George From noreply at thewildbeast.co.uk Thu Dec 20 12:59:04 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Thu, 20 Dec 2018 11:59:04 +0000 Subject: [Users] [Bug 4103] TLS SNI (Server Name Indication) support for IMAP, POP & SMTP In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4103 --- Comment #5 from Andrej Kacian --- Created attachment 1943 --> https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=1943&action=edit claws-mail-SNI-v2.diff Attached a new patch, based on Alex' original patch: - added "use_tls_sni" account pref - added libetpan version check - use sockinfo->hostname instead of sockinfo->canonical_name, since the latter usually contains non-canonical (go figure) name resolved from the IP address, e.g. "gmail-pop.l.google.com", which we do not want to set our SNI to -- You are receiving this mail because: You are the assignee for the bug. From jjk at jjacky.com Thu Dec 20 16:33:21 2018 From: jjk at jjacky.com (Olivier Brunel) Date: Thu, 20 Dec 2018 16:33:21 +0100 Subject: [Users] Couple of small patches In-Reply-To: <20181220090004.48a2424a@colin.i-run.lau> References: <20181219171218.02cb704d@jjacky.com> <20181220090004.48a2424a@colin.i-run.lau> Message-ID: <20181220163321.7748c689@jjacky.com> On Thu, 20 Dec 2018 09:00:04 +0100 Colin Leroy-Mira wrote: > On Wed, 19 Dec 2018 17:12:18 +0100, Olivier Brunel > wrote: > > > procmsg_msginfo_free(&msg); > > > > + gtk_main_iteration_do (FALSE); > > if (progress_cb != NULL > > Doesn't performing a gtk iteration each message drop search > performance badly ? Well, I didn't do extensive testing, but I couldn't really notice any diferences when I tried things. Also, I (obviously) have this applied here, and - though I'm not doing comparison - my searches don't seem slow(er) to me. Of course, it might also depends on other factors, one's setup, etc. YMMV. (I'd say most of the times GTK should just check that there are no pending events and return immediately anyways.) So I would say 'no' to the "hurt badly" idea; And though I'm sure it does affect it somewhat, for me it doesn't seem noticeable. From subscript at free.fr Thu Dec 20 16:41:48 2018 From: subscript at free.fr (wwp) Date: Thu, 20 Dec 2018 16:41:48 +0100 Subject: [Users] Couple of small patches In-Reply-To: <20181220163321.7748c689@jjacky.com> References: <20181219171218.02cb704d@jjacky.com> <20181220090004.48a2424a@colin.i-run.lau> <20181220163321.7748c689@jjacky.com> Message-ID: <20181220164148.01c3b4b1@ladybug> Hello Olivier, On Thu, 20 Dec 2018 16:33:21 +0100 Olivier Brunel wrote: > On Thu, 20 Dec 2018 09:00:04 +0100 > Colin Leroy-Mira wrote: > > > On Wed, 19 Dec 2018 17:12:18 +0100, Olivier Brunel > > wrote: > > > > > procmsg_msginfo_free(&msg); > > > > > > + gtk_main_iteration_do (FALSE); > > > if (progress_cb != NULL > > > > Doesn't performing a gtk iteration each message drop search > > performance badly ? > > Well, I didn't do extensive testing, but I couldn't really notice any > diferences when I tried things. Also, I (obviously) have this applied > here, and - though I'm not doing comparison - my searches don't seem > slow(er) to me. Of course, it might also depends on other factors, > one's setup, etc. YMMV. > > (I'd say most of the times GTK should just check that there are no > pending events and return immediately anyways.) > > So I would say 'no' to the "hurt badly" idea; And though I'm sure it > does affect it somewhat, for me it doesn't seem noticeable. I was already doubtful but there you're not really convincing me this patch could make things better ;-). Regards, -- wwp -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: From h.m.brand at xs4all.nl Thu Dec 20 16:46:04 2018 From: h.m.brand at xs4all.nl (H.Merijn Brand) Date: Thu, 20 Dec 2018 16:46:04 +0100 Subject: [Users] Couple of small patches In-Reply-To: <20181220163321.7748c689@jjacky.com> References: <20181219171218.02cb704d@jjacky.com> <20181220090004.48a2424a@colin.i-run.lau> <20181220163321.7748c689@jjacky.com> Message-ID: <20181220164604.72665d5f@pc09.procura.nl> On Thu, 20 Dec 2018 16:33:21 +0100, Olivier Brunel wrote: > On Thu, 20 Dec 2018 09:00:04 +0100 > Colin Leroy-Mira wrote: > > > On Wed, 19 Dec 2018 17:12:18 +0100, Olivier Brunel > > wrote: > > > > > procmsg_msginfo_free(&msg); > > > > > > + gtk_main_iteration_do (FALSE); > > > if (progress_cb != NULL > > > > Doesn't performing a gtk iteration each message drop search > > performance badly ? > > Well, I didn't do extensive testing, but I couldn't really notice any > diferences when I tried things. Also, I (obviously) have this applied > here, and - though I'm not doing comparison - my searches don't seem > slow(er) to me. Of course, it might also depends on other factors, > one's setup, etc. YMMV. > > (I'd say most of the times GTK should just check that there are no > pending events and return immediately anyways.) > > So I would say 'no' to the "hurt badly" idea; And though I'm sure it > does affect it somewhat, for me it doesn't seem noticeable. GUI related slowdowns can be noticed by using a (long) ssh tunnel with X11 forwarding (something I use on a regular basis) -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.29 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From jjk at jjacky.com Thu Dec 20 17:02:31 2018 From: jjk at jjacky.com (Olivier Brunel) Date: Thu, 20 Dec 2018 17:02:31 +0100 Subject: [Users] Couple of small patches In-Reply-To: <20181220164148.01c3b4b1@ladybug> References: <20181219171218.02cb704d@jjacky.com> <20181220090004.48a2424a@colin.i-run.lau> <20181220163321.7748c689@jjacky.com> <20181220164148.01c3b4b1@ladybug> Message-ID: <20181220170231.09f6bb66@jjacky.com> On Thu, 20 Dec 2018 16:41:48 +0100 wwp wrote: > Hello Olivier, > > > On Thu, 20 Dec 2018 16:33:21 +0100 Olivier Brunel > wrote: > > > On Thu, 20 Dec 2018 09:00:04 +0100 > > Colin Leroy-Mira wrote: > > > > > On Wed, 19 Dec 2018 17:12:18 +0100, Olivier Brunel > > > wrote: > > > > > > > procmsg_msginfo_free(&msg); > > > > > > > > + gtk_main_iteration_do (FALSE); > > > > if (progress_cb != NULL > > > > > > Doesn't performing a gtk iteration each message drop search > > > performance badly ? > > > > Well, I didn't do extensive testing, but I couldn't really notice > > any diferences when I tried things. Also, I (obviously) have this > > applied here, and - though I'm not doing comparison - my searches > > don't seem slow(er) to me. Of course, it might also depends on > > other factors, one's setup, etc. YMMV. > > > > (I'd say most of the times GTK should just check that there are no > > pending events and return immediately anyways.) > > > > So I would say 'no' to the "hurt badly" idea; And though I'm sure it > > does affect it somewhat, for me it doesn't seem noticeable. > > I was already doubtful but there you're not really convincing me this > patch could make things better ;-). Well, obviously this wasn't intended to make things better wrt speed. And since more code is added, as little as it may be, one could argue it has to have an impact, and that can only go one way. What I'm saying is that, AFAICS, said impact seem minimal (not noticeable in fact) whilst the impact for what the patch is intended, i.e. making the UI more responsive, is clearly there. At least for me, when running long/slow searches, I can cancel them quite easily/rapidly with this patch. Without, it's quite another story... From jseymour at LinxNet.com Thu Dec 20 17:15:50 2018 From: jseymour at LinxNet.com (Jim Seymour) Date: Thu, 20 Dec 2018 11:15:50 -0500 Subject: [Users] Couple of small patches In-Reply-To: <20181220164604.72665d5f@pc09.procura.nl> References: <20181219171218.02cb704d@jjacky.com> <20181220090004.48a2424a@colin.i-run.lau> <20181220163321.7748c689@jjacky.com> <20181220164604.72665d5f@pc09.procura.nl> Message-ID: <20181220111550.2150d408@jimsun.LinxNet.com> On Thu, 20 Dec 2018 16:46:04 +0100 "H.Merijn Brand" wrote: > On Thu, 20 Dec 2018 16:33:21 +0100, Olivier Brunel > wrote: > [snip] > > > > So I would say 'no' to the "hurt badly" idea; And though I'm sure > > it does affect it somewhat, for me it doesn't seem noticeable. > > GUI related slowdowns can be noticed by using a (long) ssh tunnel > with X11 forwarding (something I use on a regular basis) > Or, one suspects, on a really large mail store? Regards, Jim -- Note: My mail server employs *very* aggressive anti-spam filtering. If you reply to this email and your email is rejected, please accept my apologies and let me know via my web form at . From subscript at free.fr Thu Dec 20 17:56:05 2018 From: subscript at free.fr (wwp) Date: Thu, 20 Dec 2018 17:56:05 +0100 Subject: [Users] Couple of small patches In-Reply-To: <20181220170231.09f6bb66@jjacky.com> References: <20181219171218.02cb704d@jjacky.com> <20181220090004.48a2424a@colin.i-run.lau> <20181220163321.7748c689@jjacky.com> <20181220164148.01c3b4b1@ladybug> <20181220170231.09f6bb66@jjacky.com> Message-ID: <20181220175605.66729e0b@ladybug> Hello Olivier, On Thu, 20 Dec 2018 17:02:31 +0100 Olivier Brunel wrote: > On Thu, 20 Dec 2018 16:41:48 +0100 > wwp wrote: > > > Hello Olivier, > > > > > > On Thu, 20 Dec 2018 16:33:21 +0100 Olivier Brunel > > wrote: > > > > > On Thu, 20 Dec 2018 09:00:04 +0100 > > > Colin Leroy-Mira wrote: > > > > > > > On Wed, 19 Dec 2018 17:12:18 +0100, Olivier Brunel > > > > wrote: > > > > > > > > > procmsg_msginfo_free(&msg); > > > > > > > > > > + gtk_main_iteration_do (FALSE); > > > > > if (progress_cb != NULL > > > > > > > > Doesn't performing a gtk iteration each message drop search > > > > performance badly ? > > > > > > Well, I didn't do extensive testing, but I couldn't really notice > > > any diferences when I tried things. Also, I (obviously) have this > > > applied here, and - though I'm not doing comparison - my searches > > > don't seem slow(er) to me. Of course, it might also depends on > > > other factors, one's setup, etc. YMMV. > > > > > > (I'd say most of the times GTK should just check that there are no > > > pending events and return immediately anyways.) > > > > > > So I would say 'no' to the "hurt badly" idea; And though I'm sure it > > > does affect it somewhat, for me it doesn't seem noticeable. > > > > I was already doubtful but there you're not really convincing me this > > patch could make things better ;-). > > Well, obviously this wasn't intended to make things better wrt speed. > And since more code is added, as little as it may be, one could argue > it has to have an impact, and that can only go one way. > > What I'm saying is that, AFAICS, said impact seem minimal (not > noticeable in fact) whilst the impact for what the patch is intended, > i.e. making the UI more responsive, is clearly there. > At least for me, when running long/slow searches, I can cancel them > quite easily/rapidly with this patch. Without, it's quite another > story... Thanks .Making the UI more responsive was my concern in that case, I'll see if I observe some progress there w/ the patch applied. Regards, -- wwp -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: From noreply at thewildbeast.co.uk Thu Dec 20 18:22:05 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Thu, 20 Dec 2018 17:22:05 +0000 Subject: [Users] [Bug 4113] Add option to never mark mails read In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4113 Bernhard changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #1930|0 |1 is obsolete| | --- Comment #1 from Bernhard --- Created attachment 1944 --> https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=1944&action=edit v5, rebase after recent re-arrangements in summaries rebase after recent Display/Summaries/Message List changes in 411656df3122636a5ba0abc3952d678ace69de5a 7e1fec1467f2414c01d5cdac05e5cd2a25b16067 faee87fc98fdf322a3f493ecf8be26c9cf287581 No other changes wrt v4. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Fri Dec 21 12:14:22 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Fri, 21 Dec 2018 11:14:22 +0000 Subject: [Users] [Bug 4138] New: Base64 subject gives bad spam rating Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4138 Bug ID: 4138 Summary: Base64 subject gives bad spam rating Classification: Unclassified Product: Claws Mail Version: other Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P3 Component: Other Assignee: users at lists.claws-mail.org Reporter: hanno at hboeck.de I have a special character in my surname (Böck), so it gets encoded in the "From" line. Claws mail uses an utf8/base64 encoding, thus it becomes =?UTF-8?B?QsO2Y2s=?=. Base64 encoded mail headers are often used for obfuscation by spammers, and spamassassin has a filter rule (FROM_EXCESS_BASE64) which can give - depending on the configuration - up to 1 point in spam rating. I'd rather like to avoid that, but I think right now claws has no way to configure the header encoding. (As a workaround I can however set an already encoded name in the account config.) Would it be possible to change claws to use quoted printable encoding instead of base64? -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Fri Dec 21 13:09:38 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Fri, 21 Dec 2018 12:09:38 +0000 Subject: [Users] [Bug 4138] Base64 subject gives bad spam rating In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4138 Paul changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Paul --- Go to the /Configuration/Preferences/Send page and set 'Transfer encoding' to 'quoted-printable' -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Fri Dec 21 14:53:05 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Fri, 21 Dec 2018 13:53:05 +0000 Subject: [Users] [Bug 4103] TLS SNI (Server Name Indication) support for IMAP, POP & SMTP In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4103 Paul changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from users at lists.claws-mail.org --- Changes related to this bug have been committed. Please check latest Git and update the bug accordingly. You can also get the patch from: http://git.claws-mail.org/ ++ ChangeLog 2018-12-21 10:31:05.788909400 +0100 http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=01179f2c11f78a72f59bb606a6ba5f73c22a7c09 Author: Andrej Kacian Date: Fri Dec 21 10:21:10 2018 +0100 Add Server Name Indication support to TLS connections, if applicable. Adds a hidden pref "use_tls_sni". Patch by Alex Smith. Closes bug #4103: TLS SNI (Server Name Indication) support for IMAP, POP & SMTP -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Fri Dec 21 15:42:40 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Fri, 21 Dec 2018 14:42:40 +0000 Subject: [Users] [Bug 4138] add option to choose header encoding (from/subject) In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4138 Paul changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- Summary|Base64 subject gives bad |add option to choose header |spam rating |encoding (from/subject) --- Comment #2 from Paul --- ignore comment #1, i was mistaken -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Fri Dec 21 18:18:27 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Fri, 21 Dec 2018 17:18:27 +0000 Subject: [Users] [Bug 4139] New: Clawsker broken with perl 5.22+ Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4139 Bug ID: 4139 Summary: Clawsker broken with perl 5.22+ Classification: Unclassified Product: clawsker Version: GIT Hardware: PC OS: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: default Assignee: users at lists.claws-mail.org Reporter: glitsj16 at gmail.com One of the recent commits in claws-mail adds a new hidden pref "use_tls_sni" [https://git.claws-mail.org/?p=claws.git;a=commit;h=01179f2c11f78a72f59bb606a6ba5f73c22a7c09]. When trying to set that I noticed clawsker is quite broken Arch Linux. Besides an issue caused by incorrect dependencies in the Arch Linux packaging of clawsker (easily fixed by rebuilding with the correct ones), the program refuses to start and throws a message about an uninitialized value (details below). Here's what I've done: OS: Arch Linux (fully updated) $ clawsker Can't locate Gtk3.pm in @INC (you may need to install the Gtk3 module) (@INC contains: /usr/lib/perl5/5.28/site_perl /usr/share/perl5/site_perl /usr/lib/perl5/5.28/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5/5.28/core_perl /usr/share/perl5/core_perl) at /usr/bin/clawsker line 22. BEGIN failed--compilation aborted at /usr/bin/clawsker line 22. That's the packaging bug showing. Clawsker needs different dependencies than those currently stated in the official package [https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/clawsker]. I'll be filing an issue for that asap. Installing perl-gtk3 and try again: $ sudo pacman -S perl-gtk3 ... $ clawsker Can't locate File/Which.pm in @INC (you may need to install the File::Which module) (@INC contains: /usr/lib/perl5/5.28/site_perl /usr/share/perl5/site_perl /usr/lib/perl5/5.28/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5/5.28/core_perl /usr/share/perl5/core_perl) at /usr/bin/clawsker line 23. BEGIN failed--compilation aborted at /usr/bin/clawsker line 23. Another faulty dependency... $ sudo pacman -S perl-file-which ... $ clawsker Use of uninitialized value $fver[2] in string eq at /usr/bin/clawsker line 298. Invalid version string at /usr/bin/clawsker line 298. I'm not at all experienced in Perl, but I'm getting the same error on Ubuntu, albeit on different lines of the script: OS: Ubuntu 16.04 (fully updated) $ apt-cache policy clawsker clawsker: Installed: 0.7.13-1 Candidate: 0.7.13-1 Version table: *** 0.7.13-1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy perl perl: Installed: 5.22.1-9ubuntu0.6 Candidate: 5.22.1-9ubuntu0.6 Version table: *** 5.22.1-9ubuntu0.6 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 5.22.1-9 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages $ clawsker Use of uninitialized value $fver[2] in string eq at /usr/bin/clawsker line 260. Invalid version string at /usr/bin/clawsker line 260. Please note that I have very little experience with Perl, and it might be yet too soon to expect to see the newly added hidden pref "use_tls_sni", but clawsker seems broken with these perl versions. Don't have access to different perl versions currently, so the actual version number mentioned in this bug summary might not be fully correct. Please advise. Regards -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Fri Dec 21 18:41:31 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Fri, 21 Dec 2018 17:41:31 +0000 Subject: [Users] [Bug 4139] Clawsker broken with perl 5.22+ In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4139 --- Comment #1 from glitsj16 at gmail.com --- Follow-up: here's the packaging bug on Arch Linux https://bugs.archlinux.org/task/61150 -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Fri Dec 21 19:02:16 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Fri, 21 Dec 2018 18:02:16 +0000 Subject: [Users] [Bug 4139] Clawsker broken in Archlinux In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4139 Ricardo Mones changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Clawsker broken with perl |Clawsker broken in |5.22+ |Archlinux -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Fri Dec 21 19:11:22 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Fri, 21 Dec 2018 18:11:22 +0000 Subject: [Users] [Bug 4139] Clawsker broken in Archlinux In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4139 Ricardo Mones changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Ricardo Mones --- We're not the packagers for Archlinux, not sure why did you open this bug. -- You are receiving this mail because: You are the assignee for the bug. From ethy.brito at inexo.com.br Fri Dec 21 19:23:34 2018 From: ethy.brito at inexo.com.br (Ethy H. Brito) Date: Fri, 21 Dec 2018 16:23:34 -0200 Subject: [Users] two finger touchpad scroll is different from mouse middle button scroll Message-ID: <20181221162334.1656a03f@babalu> Hi Today I noticed that scrolling text via mouse middle button at the message reading panel is the other way around that scrolling it via two finger at touchpad. The left panel and messages listing panel has the same behavior: dragging two fingers down scrolls text down. Message reading panel scrolls text UP. Is there a way to make the three panels scroll text down when dragging two finger down at the touchpad? Notebook is a Dell Inspiron 5570 running Ubuntu 18.04. Claws version is 3.16.0. Regards Ethy From rol at witbe.net Fri Dec 21 19:44:20 2018 From: rol at witbe.net (Paul Rolland (=?UTF-8?B?44Od44O844Or44O744Ot44Op44Oz?=)) Date: Fri, 21 Dec 2018 19:44:20 +0100 Subject: [Users] two finger touchpad scroll is different from mouse middle button scroll In-Reply-To: <20181221162334.1656a03f@babalu> References: <20181221162334.1656a03f@babalu> Message-ID: <20181221194420.64878f74@riri.DEF.witbe.net> Hello, On Fri, 21 Dec 2018 16:23:34 -0200 "Ethy H. Brito" wrote: > The left panel and messages listing panel has the same behavior: dragging > two fingers down scrolls text down. Message reading panel scrolls text UP. > > Is there a way to make the three panels scroll text down when dragging > two finger down at the touchpad? On my machine, with Claws 3.17.2, the behavior is the same for all the panels, and consistant between the touchpad and the mouse... > Claws version is 3.16.0. What about upgrading to the most recent version ? Best, Rol -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From dave at howorth.org.uk Fri Dec 21 20:11:55 2018 From: dave at howorth.org.uk (Dave Howorth) Date: Fri, 21 Dec 2018 19:11:55 +0000 Subject: [Users] [Bug 4139] Clawsker broken in Archlinux In-Reply-To: References: Message-ID: <20181221191155.19d24536@acer-suse.lan> On Fri, 21 Dec 2018 18:11:22 +0000 noreply at thewildbeast.co.uk wrote: > https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4139 > > Ricardo Mones changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution|--- |INVALID > > --- Comment #2 from Ricardo Mones --- > We're not the packagers for Archlinux, not sure why did you open this > bug. > Well, a perl program should not report Use of uninitialized value $fver[2] in string eq and since the fault was reported on both arch and ubuntu, it clearly isn't a distro issue. I don't run either arch or ubuntu so I don't know for sure, but I suggest running the relevant version of 'claws -v' on either distribution and seeing whether the string that is output contains a space. IMHO, there's probably a test needed in clawsker as to whether there was a space, and probably some consideration of whether that version of claws is actually outputting the usual output. From noreply at thewildbeast.co.uk Fri Dec 21 20:28:14 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Fri, 21 Dec 2018 19:28:14 +0000 Subject: [Users] [Bug 3609] path in File -> Add Mailbox -> MH dialogue In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3609 --- Comment #2 from Bernhard --- Created attachment 1945 --> https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=1945&action=edit Switch Add mailbox MH dialog to dir-chooser I'd suggest the following: >From 2eabd85a64121df7e0d9ad417d470aacb4408d2d Mon Sep 17 00:00:00 2001 From: Bernhard Reutner-Fischer Date: Fri, 21 Dec 2018 19:46:12 +0100 Subject: [PATCH 4/4] Switch Add mailbox MH dialog to dir-chooser Fix bug #3609 Switch the dialog to add MH mailbox dir to a file chooser based directory picker. -- You are receiving this mail because: You are the assignee for the bug. From h.m.brand at xs4all.nl Fri Dec 21 21:46:07 2018 From: h.m.brand at xs4all.nl (H.Merijn Brand) Date: Fri, 21 Dec 2018 21:46:07 +0100 Subject: [Users] [Bug 4139] New: Clawsker broken with perl 5.22+ In-Reply-To: References: Message-ID: <20181221214607.7a3f7105@pc09.procura.nl> On Fri, 21 Dec 2018 17:18:27 +0000, noreply at thewildbeast.co.uk wrote: Which version of clawsker are you working on? > $ clawsker > Can't locate Gtk3.pm in @INC (you may need to install the Gtk3 module) > > That's the packaging bug showing. Clawsker needs different > dependencies than those currently stated in the official package > [https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/clawsker]. > I'll be filing an issue for that asap. Installing perl-gtk3 and try > again: > > $ sudo pacman -S perl-gtk3 > ... > > $ clawsker > Can't locate File/Which.pm in @INC (you may need to install the > File::Which module) > > Another faulty dependency... > > $ sudo pacman -S perl-file-which > ... > > $ clawsker > Use of uninitialized value $fver[2] in string eq at /usr/bin/clawsker > line 298. Invalid version string at /usr/bin/clawsker line 298. > > I'm not at all experienced in Perl, but I'm getting the same error on > Ubuntu, albeit on different lines of the script: > > OS: Ubuntu 16.04 (fully updated) > > $ apt-cache policy clawsker > clawsker: > Installed: 0.7.13-1 > Candidate: 0.7.13-1 > Version table: > *** 0.7.13-1 500 > 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 > Packages 100 /var/lib/dpkg/status > > $ apt-cache policy perl > perl: > Installed: 5.22.1-9ubuntu0.6 > Candidate: 5.22.1-9ubuntu0.6 > Version table: > *** 5.22.1-9ubuntu0.6 500 > 500 http://archive.ubuntu.com/ubuntu xenial-updates/main > amd64 Packages 500 http://archive.ubuntu.com/ubuntu > xenial-security/main amd64 Packages > 100 /var/lib/dpkg/status > 5.22.1-9 500 > 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 > Packages > > $ clawsker > Use of uninitialized value $fver[2] in string eq at /usr/bin/clawsker > line 260. Invalid version string at /usr/bin/clawsker line 260. That must be this code: sub get_claws_version { $_ = which ('claws-mail'); return "" unless defined $_; # not installed my $res = ""; $_ = qx/$_ -v/; chomp; my @fver = split (/ /); die "Invalid version string" unless ($fver[2] eq "version"); my @ver = split (/\./, $fver[3]); As the script requires perl-5.10, as simple and save quick fix would be die "Invalid version string" unless (($fver[2] // "") eq "version"); but the root cause is in the qx// if/when the full path to claws-mail contains a space. The code makes it really hard to debug, as $_ is abused and altered, so you cannot show the full path on failure. Here is a safe version: sub get_claws_version { my $cm_path = which ('claws-mail') or return ""; # not found open my $ph, "-|", $cm_path, "-v" or return ""; # no pipe chomp (my $v = <$ph>); close $ph; # Claws Mail version 3.17.2git17 $v =~ m/\bversion\s+(\d[\w.]+)/ or die "Invalid version string: '$v'"; my $cmv = $1; my @ver = split m/\./ => $cmv; my $res = "$ver[0].$ver[1]."; return $res . ($ver[3] =~ m/(\d+)git(\d+)/ ? "$1.$2" : "$ver[2].0"; } > Please note that I have very little experience with Perl, and it > might be yet too soon to expect to see the newly added hidden pref > "use_tls_sni", but clawsker seems broken with these perl versions. > Don't have access to different perl versions currently, so the actual > version number mentioned in this bug summary might not be fully > correct. Please advise. > > Regards -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.29 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From h.m.brand at xs4all.nl Fri Dec 21 21:51:09 2018 From: h.m.brand at xs4all.nl (H.Merijn Brand) Date: Fri, 21 Dec 2018 21:51:09 +0100 Subject: [Users] [Bug 4139] New: Clawsker broken with perl 5.22+ In-Reply-To: <20181221214607.7a3f7105@pc09.procura.nl> References: <20181221214607.7a3f7105@pc09.procura.nl> Message-ID: <20181221215109.59690cde@pc09.procura.nl> On Fri, 21 Dec 2018 21:46:07 +0100, "H.Merijn Brand" wrote: > but the root cause is in the qx// if/when the full path to claws-mail > contains a space. The code makes it really hard to debug, as $_ is > abused and altered, so you cannot show the full path on failure. Here > is a safe version: > > sub get_claws_version { > my $cm_path = which ('claws-mail') or return ""; # not found > open my $ph, "-|", $cm_path, "-v" or return ""; # no pipe > chomp (my $v = <$ph>); > close $ph; > # Claws Mail version 3.17.2git17 > $v =~ m/\bversion\s+(\d[\w.]+)/ or die "Invalid version string: > '$v'"; my $cmv = $1; > my @ver = split m/\./ => $cmv; > my $res = "$ver[0].$ver[1]."; > return $res . ($ver[3] =~ m/(\d+)git(\d+)/ ? "$1.$2" : > "$ver[2].0"; } Now simpler and without syntax error: sub get_claws_version { my $cm_path = which ('claws-mail') or return ""; # not found open my $ph, "-|", $cm_path, "-v" or return ""; # no pipe chomp (my $v = <$ph>); close $ph; # Claws Mail version 3.17.2git17 $v =~ m/\bversion\s+(\d[\w.]+)/ or die "Invalid version string: '$v'"; my $cmv = $1; my @ver = split m/(?:\.|git)/ => $cmv; @ver < 4 and push @ver, 0; return join "." => @ver; } -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.29 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From noreply at thewildbeast.co.uk Fri Dec 21 22:25:47 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Fri, 21 Dec 2018 21:25:47 +0000 Subject: [Users] [Bug 4139] Clawsker broken in Archlinux In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4139 --- Comment #3 from glitsj16 at gmail.com --- Fully aware this isn't Arch Linux packaging bug tracker. I opened the clawsker bug report here because I honestly think that is where the aforementioned Perl issue lies: $ clawsker Use of uninitialized value $fver[2] in string eq at /usr/bin/clawsker line 260. Invalid version string at /usr/bin/clawsker line 260. That should have been the most important part. I admit that the presented context could be misleading, but I wanted to provide some context. And that context includes packaging issues (on Arch Linux only). Still, *after* fixing those issues (rebuilt clawsker from git with correct dependencies) I keep getting the same message as on a Ubuntu machine. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Fri Dec 21 22:35:47 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Fri, 21 Dec 2018 21:35:47 +0000 Subject: [Users] [Bug 4139] Clawsker broken in Archlinux In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4139 --- Comment #4 from glitsj16 at gmail.com --- My sincere apologies. Something messed with my PATH. Twice, on both machines/OS'es. I stand corrected. Regards. -- You are receiving this mail because: You are the assignee for the bug. From claws at thewildbeast.co.uk Sat Dec 22 11:55:18 2018 From: claws at thewildbeast.co.uk (Paul) Date: Sat, 22 Dec 2018 10:55:18 -0000 Subject: [Users] Claws Mail 3.17.3 Unleashed!! Chngnamh! Message-ID: <20181222105410.2a2db9df@localhost> 22nd December 2018 Claws Mail 3.17.3 CLAWS MAIL RELEASE NOTES http://www.claws-mail.org Claws Mail is a GTK+ based, user-friendly, lightweight, and fast email client. New in this release: ~~~~~~~~~~~~~~~~~~~~ * Add support for TLS Server Name Indication (SNI). This enables the sending of your hostname, if available, to the server so that it can select the appropriate certificate for your domain. This is useful for servers which host multiple domains on the same IP address. This is a hidden Account preference, 'use_tls_sni', and is enabled by default. * SSL/TLS certificate manager: The Delete key will now delete the selected certificate. * Window sizes are now remembered for the 'Apply tags' and SSL/TLS certificate manager windows. * bug fixes: o bug 3519, 'Links including umlauts are broken' o bug 4134, ''Save message to' option not set when it should be' o prevent the Tools/SSL/TLS Certificates dialogue from crashing when certificate filenames contain a fingerprint. o build on GNU Hurd. o various build fixes when building without GnuTLS. For further details of the numbered bugs and RFEs listed above see https://www.claws-mail.org/bug/[BUG NUMBER] --------------------------------------------------------------------- See ChangeLog for full information regarding changes in this release. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From jjk at jjacky.com Sat Dec 22 13:30:05 2018 From: jjk at jjacky.com (Olivier Brunel) Date: Sat, 22 Dec 2018 13:30:05 +0100 Subject: [Users] Tweak date_after/date_before criteria In-Reply-To: <20181220090153.3583b177@colin.i-run.lau> References: <20181219180703.629b2d12@jjacky.com> <20181220090153.3583b177@colin.i-run.lau> Message-ID: <20181222133005.0a3d3b7c@jjacky.com> On Thu, 20 Dec 2018 09:01:53 +0100 Colin Leroy-Mira wrote: > > PS: Unless I missed it, it seems the addition of those criteria was > > left out of the release notes. I assume this wasn't on purpose, and > > maybe something to keep in mind for next release, as it might be > > worth pointing out. > > I think it arrived in 3.17.1 :) No, it did not. Just checked in git log, and I think it was commited before 3.17.1 was released yes, but 3.17.1 was released from a different branch with only a few bugfixes cherry picked. So effectively, those were new/introduced in 3.17.2 From subscript at free.fr Sat Dec 22 13:47:50 2018 From: subscript at free.fr (wwp) Date: Sat, 22 Dec 2018 13:47:50 +0100 Subject: [Users] Tweak date_after/date_before criteria In-Reply-To: <20181222133005.0a3d3b7c@jjacky.com> References: <20181219180703.629b2d12@jjacky.com> <20181220090153.3583b177@colin.i-run.lau> <20181222133005.0a3d3b7c@jjacky.com> Message-ID: <20181222134750.2b650c2b@ladybug> Hello Olivier, On Sat, 22 Dec 2018 13:30:05 +0100 Olivier Brunel wrote: > On Thu, 20 Dec 2018 09:01:53 +0100 > Colin Leroy-Mira wrote: > > > > PS: Unless I missed it, it seems the addition of those criteria was > > > left out of the release notes. I assume this wasn't on purpose, and > > > maybe something to keep in mind for next release, as it might be > > > worth pointing out. > > > > I think it arrived in 3.17.1 :) > > No, it did not. Just checked in git log, and I think it was commited > before 3.17.1 was released yes, but 3.17.1 was released from a different > branch with only a few bugfixes cherry picked. So effectively, those > were new/introduced in 3.17.2 === commit 5783d2a913dfd980d77c0be13557a54ad5c75e6a Author: Colin Leroy Date: Fri Aug 24 13:51:32 2018 +0200 Better GUI (with calendar) for date filtering condition. === (3.17.0-16-g5783d2a) IOW, 3.17.1 should have had it, unless 3.17.1 has been branched before (I'm not sure but this reminds me of smth). Regards, -- wwp -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: From ricardo at mones.org Sat Dec 22 14:06:54 2018 From: ricardo at mones.org (Ricardo Mones) Date: Sat, 22 Dec 2018 14:06:54 +0100 Subject: [Users] Clawsker: Can't locate object method "name" via package "Gtk3::Accelerator" In-Reply-To: <20181220122950.40c2adae@localhost> References: <20181219130057.2949ecc9@localhost> <20181219204343.42b371bb@busgosu> <20181220122950.40c2adae@localhost> Message-ID: <20181222130654.GC20732@busgosu> On Thu, Dec 20, 2018 at 12:29:50PM +0200, George wrote: > On Wed, 19 Dec 2018 20:43:43 +0100 Ricardo Mones wrote: > > > Not missing anything, this was a bug, and it's > > already fixed in master. > > > > If you're running git just pull latest head, > > otherwise wait a bit for the upcoming bugfix release. > > Thanks Ricardo! I have done that and now I can assign > the shortcut. However when I double click the item I > want to associate Clawsker still scrolls all the way > up (if I am trying to associate say View->Expand All > Threads). > > Is that probably another bug that needs fixing? Yes, it was. Should be fixed now in master. best regards, -- Ricardo Mones ~ Quantity derives from measurement, figures from quantities, comparisons from figures, and victories from comparisons. Sun Tzu -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From jn.ml.clwm.729 at letterboxes.org Sat Dec 22 15:29:50 2018 From: jn.ml.clwm.729 at letterboxes.org (Jeremy Nicoll) Date: Sat, 22 Dec 2018 09:29:50 -0500 Subject: [Users] Claws Mail 3.17.3 Unleashed!! Chngnamh! In-Reply-To: <20181222105410.2a2db9df@localhost> References: <20181222105410.2a2db9df@localhost> Message-ID: <48c1b3ec-824c-456d-ade0-95016810559a@www.fastmail.com> On Sat, 22 Dec 2018, at 10:55, Paul wrote: ... What does "Chngnamh" mean? -- Jeremy Nicoll - my opinions are my own. From jerry at seibercom.net Sat Dec 22 17:56:08 2018 From: jerry at seibercom.net (Jerry) Date: Sat, 22 Dec 2018 11:56:08 -0500 Subject: [Users] Claws Mail 3.17.3 Unleashed!! Chngnamh! In-Reply-To: <48c1b3ec-824c-456d-ade0-95016810559a@www.fastmail.com> References: <20181222105410.2a2db9df@localhost> <48c1b3ec-824c-456d-ade0-95016810559a@www.fastmail.com> Message-ID: <20181222115608.00006de6@seibercom.net> On Sat, 22 Dec 2018 09:29:50 -0500, Jeremy Nicoll stated: >On Sat, 22 Dec 2018, at 10:55, Paul wrote: > >... > >What does "Chngnamh" mean? Chungnam National University -- Jerry From jn.ml.clwm.729 at letterboxes.org Sat Dec 22 19:26:29 2018 From: jn.ml.clwm.729 at letterboxes.org (Jeremy Nicoll) Date: Sat, 22 Dec 2018 13:26:29 -0500 Subject: [Users] Claws Mail 3.17.3 Unleashed!! Chngnamh! In-Reply-To: <20181222115608.00006de6@seibercom.net> References: <20181222105410.2a2db9df@localhost> <48c1b3ec-824c-456d-ade0-95016810559a@www.fastmail.com> <20181222115608.00006de6@seibercom.net> Message-ID: <5eac0762-6bf8-4eb4-9e2c-051083402f8f@www.fastmail.com> On Sat, 22 Dec 2018, at 16:56, Jerry wrote: > On Sat, 22 Dec 2018 09:29:50 -0500, Jeremy Nicoll stated: > > >On Sat, 22 Dec 2018, at 10:55, Paul wrote: > > > >... > > > >What does "Chngnamh" mean? > > Chungnam National University I looked at previous "unleashed" posts and it is not normal for there to be any words at the end. I don't understand its significance here. -- Jeremy Nicoll - my opinions are my own. From mark+claws at carnildo.com Sat Dec 22 22:47:46 2018 From: mark+claws at carnildo.com (Mark Wagner) Date: Sat, 22 Dec 2018 13:47:46 -0800 Subject: [Users] Claws Mail 3.17.3 Unleashed!! Chngnamh! In-Reply-To: <5eac0762-6bf8-4eb4-9e2c-051083402f8f@www.fastmail.com> References: <20181222105410.2a2db9df@localhost> <48c1b3ec-824c-456d-ade0-95016810559a@www.fastmail.com> <20181222115608.00006de6@seibercom.net> <5eac0762-6bf8-4eb4-9e2c-051083402f8f@www.fastmail.com> Message-ID: <20181222134746.17379e37@puma.carnildo.com> On Sat, 22 Dec 2018 13:26:29 -0500 "Jeremy Nicoll" wrote: > On Sat, 22 Dec 2018, at 16:56, Jerry wrote: > > On Sat, 22 Dec 2018 09:29:50 -0500, Jeremy Nicoll stated: > > > > >On Sat, 22 Dec 2018, at 10:55, Paul wrote: > > > > > >... > > > > > >What does "Chngnamh" mean? > > > > Chungnam National University > > I looked at previous "unleashed" posts and it is not normal > for there to be any words at the end. I don't understand its > significance here. > It sounds like this version wasn't released, it escaped. -- Mark From epodata at gmail.com Sun Dec 23 08:54:33 2018 From: epodata at gmail.com (Erik P. Olsen) Date: Sun, 23 Dec 2018 08:54:33 +0100 Subject: [Users] Quoted printable broken. Message-ID: <20181223085433.5b82fbbe.erik@epo.dk> Unable to decode Danish special letters which have been encoded using quoted printable. They are all substituted with _ (underscore). Using claws-mail 3.17.1 and Fedora 29. -- Regards, Erik P. Olsen From paulsteyn1 at afrihost.co.za Sun Dec 23 10:06:36 2018 From: paulsteyn1 at afrihost.co.za (Paul Steyn) Date: Sun, 23 Dec 2018 11:06:36 +0200 Subject: [Users] Claws Mail 3.17.3 Unleashed!! Chngnamh! In-Reply-To: <20181222134746.17379e37@puma.carnildo.com> References: <20181222105410.2a2db9df@localhost> <48c1b3ec-824c-456d-ade0-95016810559a@www.fastmail.com> <20181222115608.00006de6@seibercom.net> <5eac0762-6bf8-4eb4-9e2c-051083402f8f@www.fastmail.com> <20181222134746.17379e37@puma.carnildo.com> Message-ID: <20181223110636.5652f0c5@afrihost.co.za> On Sat, 22 Dec 2018 13:47:46 -0800 Mark Wagner wrote: > On Sat, 22 Dec 2018 13:26:29 -0500 > "Jeremy Nicoll" wrote: > > It sounds like this version wasn't released, it escaped. Leaving a path of bloody destruction in its wake? Sounds like Klingon software... [1] http://wiki.c2.com/?KlingonProgramming From ticho at claws-mail.org Sun Dec 23 11:18:57 2018 From: ticho at claws-mail.org (Andrej Kacian) Date: Sun, 23 Dec 2018 11:18:57 +0100 Subject: [Users] Quoted printable broken. In-Reply-To: <20181223085433.5b82fbbe.erik@epo.dk> References: <20181223085433.5b82fbbe.erik@epo.dk> Message-ID: <20181223111857.28b38b01@penny> On Sun, 23 Dec 2018 08:54:33 +0100 Erik P. Olsen wrote: > Unable to decode Danish special letters which have been encoded using quoted printable. > They are all substituted with _ (underscore). > > Using claws-mail 3.17.1 and Fedora 29. Can you forward (as attachment) an e-mail where this can be seen? Quoted-printable is basically just transfer encoding to sneak non-ASCII bytes through the text-based SMTP protocol. The actual meaning of those bytes (the character set) is dictated by other means, e.g. e-mail headers. I'm guessing that you have some e-mails where this is set incorrectly, leading to incorrect display of these e-mails. Regards, -- Andrej -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From ricardo at mones.org Sun Dec 23 11:38:45 2018 From: ricardo at mones.org (Ricardo Mones) Date: Sun, 23 Dec 2018 11:38:45 +0100 Subject: [Users] [Bug 4139] New: Clawsker broken with perl 5.22+ In-Reply-To: <20181221215109.59690cde@pc09.procura.nl> References: <20181221214607.7a3f7105@pc09.procura.nl> <20181221215109.59690cde@pc09.procura.nl> Message-ID: <20181223113845.55d8bd34@busgosu> On Fri, 21 Dec 2018 21:51:09 +0100 "H.Merijn Brand" wrote: > Now simpler and without syntax error Added to master, thanks! :-) best regards, -- Ricardo Mones ~ Don't take the name of root in vain. /usr/src/linux/README -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: Firma digital OpenPGP URL: From silver.bullet at zoho.com Sun Dec 23 12:35:38 2018 From: silver.bullet at zoho.com (Ralf Mardorf) Date: Sun, 23 Dec 2018 12:35:38 +0100 Subject: [Users] Claws Mail 3.17.3 Unleashed!! Chngnamh! In-Reply-To: <20181223110636.5652f0c5@afrihost.co.za> References: <20181222105410.2a2db9df@localhost> <48c1b3ec-824c-456d-ade0-95016810559a@www.fastmail.com> <20181222115608.00006de6@seibercom.net> <5eac0762-6bf8-4eb4-9e2c-051083402f8f@www.fastmail.com> <20181222134746.17379e37@puma.carnildo.com> <20181223110636.5652f0c5@afrihost.co.za> Message-ID: <20181223123538.254fe9c7@utnubu> On Sun, 23 Dec 2018 11:06:36 +0200, Paul Steyn wrote: >http://wiki.c2.com/?KlingonProgramming IIRC I read exactly this in the Hagakure, https://en.wikipedia.org/wiki/Hagakure. To be honest I only read half of the Hagakure, because I couldn't stand this warrior crap. But I might be mistaken, I might have read this in the Bhagavad Gita, https://en.wikipedia.org/wiki/Bhagavad_Gita. IIRC I read less of the half of the Bhagavad Gita, because it also suffers from warrior crap. From silver.bullet at zoho.com Sun Dec 23 13:02:25 2018 From: silver.bullet at zoho.com (Ralf Mardorf) Date: Sun, 23 Dec 2018 13:02:25 +0100 Subject: [Users] Claws Mail 3.17.3 Unleashed!! Chngnamh! In-Reply-To: <20181223123538.254fe9c7@utnubu> References: <20181222105410.2a2db9df@localhost> <48c1b3ec-824c-456d-ade0-95016810559a@www.fastmail.com> <20181222115608.00006de6@seibercom.net> <5eac0762-6bf8-4eb4-9e2c-051083402f8f@www.fastmail.com> <20181222134746.17379e37@puma.carnildo.com> <20181223110636.5652f0c5@afrihost.co.za> <20181223123538.254fe9c7@utnubu> Message-ID: <20181223130225.334e51d8@utnubu> On Sun, 23 Dec 2018 12:35:38 +0100, Ralf Mardorf wrote: >Chngnamh! PS: Ok, "Chngnamh" sounds less like a word you'll find in the Hagakure. "Chngnamh" sounds Klingon, but it also fits to the spelling of translations, of many words in the Bhagavad Gita. Let alone that "Bhagavad" already looks similar to "Chngnamh". From silver.bullet at zoho.com Sun Dec 23 13:18:36 2018 From: silver.bullet at zoho.com (Ralf Mardorf) Date: Sun, 23 Dec 2018 13:18:36 +0100 Subject: [Users] Claws Mail 3.17.3 Unleashed!! Chngnamh! In-Reply-To: <20181223110636.5652f0c5@afrihost.co.za> References: <20181222105410.2a2db9df@localhost> <48c1b3ec-824c-456d-ade0-95016810559a@www.fastmail.com> <20181222115608.00006de6@seibercom.net> <5eac0762-6bf8-4eb4-9e2c-051083402f8f@www.fastmail.com> <20181222134746.17379e37@puma.carnildo.com> <20181223110636.5652f0c5@afrihost.co.za> Message-ID: <20181223131836.0d603b5b@utnubu> On Sun, 23 Dec 2018 11:06:36 +0200, Paul Steyn wrote: >Leaving a path of bloody destruction in its wake? The question mark makes clear that you are a hesitant person! You dishonours this hard software. From epodata at gmail.com Sun Dec 23 13:23:41 2018 From: epodata at gmail.com (Erik P. Olsen) Date: Sun, 23 Dec 2018 13:23:41 +0100 Subject: [Users] Quoted printable broken. In-Reply-To: <20181223111857.28b38b01@penny> References: <20181223085433.5b82fbbe.erik@epo.dk> <20181223111857.28b38b01@penny> Message-ID: <20181223132341.1b6947f3@Erik-PC.epolan.dk> On 2018-12-23 at 11:18:57 Andrej Kacian wrote: > On Sun, 23 Dec 2018 08:54:33 +0100 > Erik P. Olsen wrote: > > > Unable to decode Danish special letters which have been encoded using quoted > > printable. They are all substituted with _ (underscore). > > > > Using claws-mail 3.17.1 and Fedora 29. > > Can you forward (as attachment) an e-mail where this can be seen? > > Quoted-printable is basically just transfer encoding to sneak non-ASCII > bytes through the text-based SMTP protocol. The actual meaning of those > bytes (the character set) is dictated by other means, e.g. e-mail > headers. I'm guessing that you have some e-mails where this is set > incorrectly, leading to incorrect display of these e-mails. Sure I'll send the source listing but I've also tried to read it with thunderbird and there it is read correctly. -- Regards, Erik P. Olsen From msuchanek at suse.de Sun Dec 23 14:03:18 2018 From: msuchanek at suse.de (Michal =?UTF-8?B?U3VjaMOhbmVr?=) Date: Sun, 23 Dec 2018 14:03:18 +0100 Subject: [Users] Claws Mail 3.17.3 Unleashed!! Chngnamh! In-Reply-To: <20181223130225.334e51d8@utnubu> References: <20181222105410.2a2db9df@localhost> <48c1b3ec-824c-456d-ade0-95016810559a@www.fastmail.com> <20181222115608.00006de6@seibercom.net> <5eac0762-6bf8-4eb4-9e2c-051083402f8f@www.fastmail.com> <20181222134746.17379e37@puma.carnildo.com> <20181223110636.5652f0c5@afrihost.co.za> <20181223123538.254fe9c7@utnubu> <20181223130225.334e51d8@utnubu> Message-ID: <20181223140318.76031d9b@naga> On Sun, 23 Dec 2018 13:02:25 +0100 Ralf Mardorf wrote: > On Sun, 23 Dec 2018 12:35:38 +0100, Ralf Mardorf wrote: > >Chngnamh! > > PS: Ok, "Chngnamh" sounds less like a word you'll find in the Hagakure. > "Chngnamh" sounds Klingon, but it also fits to the spelling of > translations, of many words in the Bhagavad Gita. Let alone that > "Bhagavad" already looks similar to "Chngn ". I beg to differ. Sanskrit is proper language with reasonable syllabic structure. So no Chngn nor amh has any place in it. When I don't understand something at all I assume it's Cthulhu language. It saves a lot of time. It might be Cthulhu doing even if it's not Cthulhu language anyway. My personal opinion is this extra suffix to the release announcement was added exactly to trigger people obsessed with knowing everything like everyone participating in the thread so far ;-) As somebody already pointed out it may very well be an interjection of Claws release breaking free with no deep meaning, too. Have a nice Christmas Michal From rol at witbe.net Mon Dec 24 11:05:45 2018 From: rol at witbe.net (Paul Rolland (=?UTF-8?B?44Od44O844Or44O744Ot44Op44Oz?=)) Date: Mon, 24 Dec 2018 11:05:45 +0100 Subject: [Users] Claws Mail 3.17.3 Unleashed!! Chngnamh! In-Reply-To: <20181223140318.76031d9b@naga> References: <20181222105410.2a2db9df@localhost> <48c1b3ec-824c-456d-ade0-95016810559a@www.fastmail.com> <20181222115608.00006de6@seibercom.net> <5eac0762-6bf8-4eb4-9e2c-051083402f8f@www.fastmail.com> <20181222134746.17379e37@puma.carnildo.com> <20181223110636.5652f0c5@afrihost.co.za> <20181223123538.254fe9c7@utnubu> <20181223130225.334e51d8@utnubu> <20181223140318.76031d9b@naga> Message-ID: <20181224110545.34e79989@riri.DEF.witbe.net> Hello, On Sun, 23 Dec 2018 14:03:18 +0100 Michal Suchánek wrote: > As somebody already pointed out it may very well be an interjection of > Claws release breaking free with no deep meaning, too. "no deep meaning" would be so disappointing ! Not a Klingon fan, I second the Cthulhu analysis... Paul -- Paul Rolland E-Mail : rol(at)witbe.net CTO - Witbe.net SA Tel. +33 (0)1 47 67 77 77 Les Collines de l'Arche Fax. +33 (0)1 47 67 77 99 F-92057 Paris La Defense RIPE : PR12-RIPE LinkedIn : http://www.linkedin.com/in/paulrolland Skype : rollandpaul "I worry about my child and the Internet all the time, even though she's too young to have logged on yet. Here's what I worry about. I worry that 10 or 15 years from now, she will come to me and say 'Daddy, where were you when they took freedom of the press away from the Internet?'" --Mike Godwin, Electronic Frontier Foundation -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From linux at slavino.sk Mon Dec 24 12:56:04 2018 From: linux at slavino.sk (Slavko) Date: Mon, 24 Dec 2018 12:56:04 +0100 Subject: [Users] IMAP and CM Message-ID: <20181224125604.2e7aefc4@bonifac.skk> Hi, after years of using CM for POP accounts i recently switch to use IMAP. But i noticed some problems with it and i really don't k now if it is feature or my configuration. I have own Dovecot and exim4 for delivering via dovecot's LMTP (bot used for long time via POP3), then problems can be on this side too. Please, can someone help my/pont me with these problems: 1. incoming emails are not checked by bogofilter, or at least no X-Bogosity header is added into them (configured in bogofilter plugin to add it). What i need to to get it? 2. new emails are noticed by the notification plugin, but i have set the "run command" when a new mail arrive (to use TTS), and this command is not run (yes it worked, until aj switch to IMAP). Have i do something extra to get this work with IMAP? 3. i see persistent connection to IMAP server and NOOP command every 60 sec. I have enabled dovecot's push_notification plugin (https://wiki2.dovecot.org/Plugins/PushNotification) but i not see anything on NOOP response, when new mail is delivered by the dovecot's LMTP. It is not working in CM or i have something wrong? 4. beside the NOOP command, the server is pulled at global interval. Is polling really needed? Can i choose if to do polling or to use NOOP? regards -- Slavko http://slavino.sk -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: Digitálny podpis OpenPGP URL: From mir at miras.org Mon Dec 24 13:11:27 2018 From: mir at miras.org (Michael Rasmussen) Date: Mon, 24 Dec 2018 13:11:27 +0100 Subject: [Users] IMAP and CM In-Reply-To: <20181224125604.2e7aefc4@bonifac.skk> References: <20181224125604.2e7aefc4@bonifac.skk> Message-ID: <20181224131127.7e944850@sleipner.datanom.net> On Mon, 24 Dec 2018 12:56:04 +0100 Slavko wrote: > > 1. incoming emails are not checked by bogofilter, or at least no > X-Bogosity header is added into them (configured in bogofilter plugin > to add it). What i need to to get it? > > 2. new emails are noticed by the notification plugin, but i have set > the "run command" when a new mail arrive (to use TTS), and this > command is not run (yes it worked, until aj switch to IMAP). Have i do > something extra to get this work with IMAP? > This could be caused by dovecot and/or exim4 running chroot. > 3. i see persistent connection to IMAP server and NOOP command every > 60 sec. I have enabled dovecot's push_notification plugin > (https://wiki2.dovecot.org/Plugins/PushNotification) but i not see > anything on NOOP response, when new mail is delivered by the dovecot's > LMTP. It is not working in CM or i have something wrong? > > 4. beside the NOOP command, the server is pulled at global interval. > Is polling really needed? Can i choose if to do polling or to use > NOOP? > Claws does neither supports IMAP-IDLE (RFC 2177) nor IMAP-NOTIFY (RFC 5465) so polling is your only option. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E mir datanom net http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C mir miras org http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917 -------------------------------------------------------------- /usr/games/fortune -es says: Kids always brighten up a house; mostly by leaving the lights on. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From linux at slavino.sk Mon Dec 24 14:00:50 2018 From: linux at slavino.sk (Slavko) Date: Mon, 24 Dec 2018 14:00:50 +0100 Subject: [Users] IMAP and CM In-Reply-To: <20181224131127.7e944850@sleipner.datanom.net> References: <20181224125604.2e7aefc4@bonifac.skk> <20181224131127.7e944850@sleipner.datanom.net> Message-ID: <20181224140050.6fec6206@bonifac.skk> Hi, Dňa Mon, 24 Dec 2018 13:11:27 +0100 Michael Rasmussen napísal: > On Mon, 24 Dec 2018 12:56:04 +0100 > Slavko wrote: > > > > > 1. incoming emails are not checked by bogofilter, or at least no > > X-Bogosity header is added into them (configured in bogofilter > > plugin to add it). What i need to to get it? > > > > 2. new emails are noticed by the notification plugin, but i have set > > the "run command" when a new mail arrive (to use TTS), and this > > command is not run (yes it worked, until aj switch to IMAP). Have i > > do something extra to get this work with IMAP? > > > This could be caused by dovecot and/or exim4 running chroot. I am sure, that this has nothing with dovecot/exim, because a) these both are on remote machine and b) "run command" is CM (local) setting. mail are arriving, desktop notification is shown, but TTS is not invoked nor X-Bogosity header added. > > 3. i see persistent connection to IMAP server and NOOP command every > > 60 sec. I have enabled dovecot's push_notification plugin > > (https://wiki2.dovecot.org/Plugins/PushNotification) but i not see > > anything on NOOP response, when new mail is delivered by the > > dovecot's LMTP. It is not working in CM or i have something wrong? > > > > 4. beside the NOOP command, the server is pulled at global interval. > > Is polling really needed? Can i choose if to do polling or to use > > NOOP? > > > Claws does neither supports IMAP-IDLE (RFC 2177) nor IMAP-NOTIFY (RFC > 5465) so polling is your only option. OK, thanks regard -- Slavko http://slavino.sk -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: Digitálny podpis OpenPGP URL: From linux at slavino.sk Mon Dec 24 19:11:41 2018 From: linux at slavino.sk (Slavko) Date: Mon, 24 Dec 2018 19:11:41 +0100 Subject: [Users] IMAP and CM In-Reply-To: <20181224125604.2e7aefc4@bonifac.skk> References: <20181224125604.2e7aefc4@bonifac.skk> Message-ID: <20181224191141.3504cf61@bonifac.skk> Hi, Dňa Mon, 24 Dec 2018 12:56:04 +0100 Slavko napísal: > Please, can someone help my/pont me with these problems: > > 1. incoming emails are not checked by bogofilter, or at least no > X-Bogosity header is added into them (configured in bogofilter plugin > to add it). What i need to to get it? > > 2. new emails are noticed by the notification plugin, but i have set > the "run command" when a new mail arrive (to use TTS), and this > command is not run (yes it worked, until aj switch to IMAP). Have i do > something extra to get this work with IMAP? Hmm, it seems, that the notify plugin only works, when message is filtered from IMAP to MH mailbox. When it is not touched by filter no notification appears. regarads -- Slavko http://slavino.sk -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: Digitálny podpis OpenPGP URL: From noreply at thewildbeast.co.uk Wed Dec 26 11:15:10 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Wed, 26 Dec 2018 10:15:10 +0000 Subject: [Users] [Bug 4141] New: To: column content not correctly preparing addresses... Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4141 Bug ID: 4141 Summary: To: column content not correctly preparing addresses... Classification: Unclassified Product: Claws Mail Version: 3.17.2 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P3 Component: UI/Message List Assignee: users at lists.claws-mail.org Reporter: rol at as2917.net Hello, This is not only related to 3.17.2, it has been there for quite a long time, maybe forever... My setup includes the "From" and the "To" columns in the message list, but there are some annoying behavior of the "To" content : 1 - if the To: recipients are listed on two (or more) lines, the extra lines are starting with multiple spaces, but these are not reduced to a single space for display, resulting in extra space in the column, 2 - Some magic processing occurs on the adresses, and sometimes results in an empty string returned. This is occuring when you have : To: These two are shown in the attached images. I'm ready to cook a patch if someone tells me where to look at... I've tried (very quickly) to find something in src/common/utils.c, looking at eliminate_address_comment(), extract_address(), but they seem to be called only for the From: addresses... -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Wed Dec 26 11:16:34 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Wed, 26 Dec 2018 10:16:34 +0000 Subject: [Users] [Bug 4141] To: column content not correctly preparing addresses... In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4141 --- Comment #1 from Paul Rolland --- Created attachment 1946 --> https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=1946&action=edit screen capture showing what I have on screen.... -- You are receiving this mail because: You are the assignee for the bug. From jerry at seibercom.net Thu Dec 27 14:27:27 2018 From: jerry at seibercom.net (Jerry) Date: Thu, 27 Dec 2018 08:27:27 -0500 Subject: [Users] Alignment of column names Message-ID: <20181227082727.00001dc3@seibercom.net> I am probably overlooking the obvious; however, how do I "left" align the "size" element name in "message view"? All of the other column names are left aligned except for the "size" column name, which is "right" aligned. It just seems rather strange to me. -- Jerry From subscript at free.fr Thu Dec 27 17:05:49 2018 From: subscript at free.fr (wwp) Date: Thu, 27 Dec 2018 17:05:49 +0100 Subject: [Users] Alignment of column names In-Reply-To: <20181227082727.00001dc3@seibercom.net> References: <20181227082727.00001dc3@seibercom.net> Message-ID: <20181227170549.5a498557@ladybug> Hello Jerry, On Thu, 27 Dec 2018 08:27:27 -0500 Jerry wrote: > I am probably overlooking the obvious; however, how do I "left" align the > "size" element name in "message view"? All of the other column names are left > aligned except for the "size" column name, which is "right" aligned. It just > seems rather strange to me. Your only chance would be to modify the source code. Same for the other 'number' columns. Frankly, aligning numbers to the left, I don't see the point. Regards, -- wwp -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: From ricardo at mones.org Thu Dec 27 17:36:26 2018 From: ricardo at mones.org (Ricardo Mones) Date: Thu, 27 Dec 2018 17:36:26 +0100 Subject: [Users] Alignment of column names In-Reply-To: <20181227170549.5a498557@ladybug> References: <20181227082727.00001dc3@seibercom.net> <20181227170549.5a498557@ladybug> Message-ID: <20181227163626.GA3973@busgosu> On Thu, Dec 27, 2018 at 05:05:49PM +0100, wwp wrote: > Hello Jerry, > > > On Thu, 27 Dec 2018 08:27:27 -0500 Jerry wrote: > > > I am probably overlooking the obvious; however, how do I "left" > > align the "size" element name in "message view"? All of the other > > column names are left aligned except for the "size" column name, > > which is "right" aligned. It just seems rather strange to me. > > Your only chance would be to modify the source code. Same for the > other 'number' columns. Frankly, aligning numbers to the left, I don't > see the point. Maybe when using some RTL scripts perhaps? regards, -- Ricardo Mones ~ You have the capacity to learn from mistakes. You'll learn a lot today. /usr/games/fortune -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From jerry at seibercom.net Thu Dec 27 19:52:44 2018 From: jerry at seibercom.net (Jerry) Date: Thu, 27 Dec 2018 13:52:44 -0500 Subject: [Users] Alignment of column names In-Reply-To: <20181227163626.GA3973@busgosu> References: <20181227082727.00001dc3@seibercom.net> <20181227170549.5a498557@ladybug> <20181227163626.GA3973@busgosu> Message-ID: <20181227135244.00004c3a@seibercom.net> On Thu, 27 Dec 2018 17:36:26 +0100, Ricardo Mones stated: >On Thu, Dec 27, 2018 at 05:05:49PM +0100, wwp wrote: >> Hello Jerry, >> >> >> On Thu, 27 Dec 2018 08:27:27 -0500 Jerry wrote: >> >> > I am probably overlooking the obvious; however, how do I "left" >> > align the "size" element name in "message view"? All of the other >> > column names are left aligned except for the "size" column name, >> > which is "right" aligned. It just seems rather strange to me. >> >> Your only chance would be to modify the source code. Same for the >> other 'number' columns. Frankly, aligning numbers to the left, I >> don't see the point. > >Maybe when using some RTL scripts perhaps? I am not interested in aligning the column contents, only the column heading. -- Jerry From subscript at free.fr Thu Dec 27 20:19:50 2018 From: subscript at free.fr (wwp) Date: Thu, 27 Dec 2018 20:19:50 +0100 Subject: [Users] Alignment of column names In-Reply-To: <20181227135244.00004c3a@seibercom.net> References: <20181227082727.00001dc3@seibercom.net> <20181227170549.5a498557@ladybug> <20181227163626.GA3973@busgosu> <20181227135244.00004c3a@seibercom.net> Message-ID: <20181227201950.4ccd916e@ladybug> Hello Jerry, On Thu, 27 Dec 2018 13:52:44 -0500 Jerry wrote: > On Thu, 27 Dec 2018 17:36:26 +0100, Ricardo Mones stated: > > >On Thu, Dec 27, 2018 at 05:05:49PM +0100, wwp wrote: > >> Hello Jerry, > >> > >> > >> On Thu, 27 Dec 2018 08:27:27 -0500 Jerry wrote: > >> > >> > I am probably overlooking the obvious; however, how do I "left" > >> > align the "size" element name in "message view"? All of the other > >> > column names are left aligned except for the "size" column name, > >> > which is "right" aligned. It just seems rather strange to me. > >> > >> Your only chance would be to modify the source code. Same for the > >> other 'number' columns. Frankly, aligning numbers to the left, I > >> don't see the point. > > > >Maybe when using some RTL scripts perhaps? > > I am not interested in aligning the column contents, only the column > heading. Right, sorry, but I'm afraid both alignments are bound together, nothing I can suggest there. Regards, -- wwp -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: From shai at platonix.com Thu Dec 27 22:12:09 2018 From: shai at platonix.com (Shai Berger) Date: Thu, 27 Dec 2018 23:12:09 +0200 Subject: [Users] Alignment of column names In-Reply-To: <20181227163626.GA3973@busgosu> References: <20181227082727.00001dc3@seibercom.net> <20181227170549.5a498557@ladybug> <20181227163626.GA3973@busgosu> Message-ID: <20181227231209.63747f34.shai@platonix.com> On Thu, 27 Dec 2018 17:36:26 +0100 Ricardo Mones wrote: > On Thu, Dec 27, 2018 at 05:05:49PM +0100, wwp wrote: > > > > Your only chance would be to modify the source code. Same for the > > other 'number' columns. Frankly, aligning numbers to the left, I > > don't see the point. > > Maybe when using some RTL scripts perhaps? > Just for the record -- RTL script user here, and numbers are written LTR. This is true not only when Western[1] numerals are being used, as in Hebrew, but even for RTL scripts which have their own digit symbols (the Indic numerals used with Arabic scripts). This is the main reason we refer to these scripts as "BiDi" (bi-directional). Shai. [1] The proper name of the digit symbols used in Western scripts is Arabic numerals, but the goal of this message was to clarify, not confuse. [2] Hebrew does have a numeric system based on Hebrew letters, which are then written RTL; it is somewhat similar to Roman numerals. And like Roman numerals, it is only used for dates and ordinals. From reni at vivaldi.net Fri Dec 28 08:31:52 2018 From: reni at vivaldi.net (RN) Date: Fri, 28 Dec 2018 08:31:52 +0100 Subject: [Users] openSUSE - Leap 15.0 - claws-mail im Systray Message-ID: <20181228083152.58b509ee@laptop.leoni.daheim> Hallo, auf meinem Laptop mit openSUSE LEAP 15.0 hab ich ein Problem mit claws-Mail und dem Systray-Icon. Manchmal ist es nach dem Anmelden da, verschwindet aber nach kurzer Zeit wieder. Manchmal ist es schon nach dem Anmelden nicht da, da hilft ein Abmelden/Anmelden, aber auch nicht immer. Hat jemand eine Idee dazu, wo das Problem liegen könnte? Installiert ist: claws-mail-3.16.0-lp150.2.3.1 claws-mail-lang-3.16.0-lp150.2.3.1 Systeminformationen GTK+ 2.24.32 / GLib 2.58.2 Locale: de_DE.UTF-8 (Zeichensatz: UTF-8) Betriebssystem: Linux 4.12.14-lp150.12.28-default (x86_64) Vielen Dank vorab, reni in english (Google-Übersetzer): Hello, on my laptop with openSUSE LEAP 15.0 I have a problem with claws-mail and the systray icon. Sometimes it is there after logging in, but it disappears after a short time. Sometimes it is not there after logging in, it helps to log out / log in, but not always. Does anyone have any idea where the problem might be? Thanks, reni From noreply at thewildbeast.co.uk Sat Dec 29 17:12:10 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sat, 29 Dec 2018 16:12:10 +0000 Subject: [Users] [Bug 4140] Plugins Window crash In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4140 Andrej Kacian changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Andrej Kacian --- This has now been fixed in git, and the fix will be included in the next release, due Really Soon(tm). https://git.claws-mail.org/?p=claws.git;a=commitdiff;h=35bfe2 -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 30 00:36:02 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sat, 29 Dec 2018 23:36:02 +0000 Subject: [Users] [Bug 1920] No automatic NNTP filtering In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=1920 Andrej Kacian changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #11 from Andrej Kacian --- Both patches tested and pushed to git, (belated) thanks! :) -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 30 00:41:34 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sat, 29 Dec 2018 23:41:34 +0000 Subject: [Users] [Bug 2172] RSSyl plugin insists on creating unnecessary directories In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2172 Andrej Kacian changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Andrej Kacian --- This was "fixed" by the plugin rewrite back in 2014, closing. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 30 00:51:55 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sat, 29 Dec 2018 23:51:55 +0000 Subject: [Users] [Bug 2045] address book blocks focus on email window In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2045 Andrej Kacian changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from users at lists.claws-mail.org --- Changes related to this bug have been committed. Please check latest Git and update the bug accordingly. You can also get the patch from: http://git.claws-mail.org/ ++ ChangeLog 2018-12-30 00:50:11.427432933 +0100 http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=9b9f3f130d908908d111dd168af91508420d957f Author: Andrej Kacian Date: Sun Dec 30 00:48:43 2018 +0100 Make "Edit Person Details" window not modal Patch by Salvatore De Paolis. Fixes bug #2045. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 30 01:15:07 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 30 Dec 2018 00:15:07 +0000 Subject: [Users] [Bug 2131] Focus stealing after mail check In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2131 Andrej Kacian changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from users at lists.claws-mail.org --- Changes related to this bug have been committed. Please check latest Git and update the bug accordingly. You can also get the patch from: http://git.claws-mail.org/ ++ ChangeLog 2018-12-30 01:14:04.998753756 +0100 http://git.claws-mail.org/?p=claws.git;a=commitdiff;h=3982d3e615ab83b8da70617df46be2cf52ed1cc5 Author: Andrej Kacian Date: Sun Dec 30 01:12:27 2018 +0100 Respect quicksearch focus when refreshing summaryview to show new messages Fixes bug #2131: Focus stealing after mail check -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 30 01:17:21 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 30 Dec 2018 00:17:21 +0000 Subject: [Users] [Bug 2357] Subfolder with same feed name: entries will appear on the subfolder... In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2357 Andrej Kacian changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 30 01:27:26 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 30 Dec 2018 00:27:26 +0000 Subject: [Users] [Bug 2843] Reply 'autowrap' eats \n in certain conditions In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2843 Andrej Kacian changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Andrej Kacian --- *** This bug has been marked as a duplicate of bug 2676 *** -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 30 01:27:26 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 30 Dec 2018 00:27:26 +0000 Subject: [Users] [Bug 2676] Word wrap merges with later paragraphs In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2676 Andrej Kacian changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marcel at hsdev.com --- Comment #1 from Andrej Kacian --- *** Bug 2843 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 30 14:11:47 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 30 Dec 2018 13:11:47 +0000 Subject: [Users] [Bug 2914] SIGSEGV when doing an LDAP lookup and hostname can not be looked up In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2914 Andrej Kacian changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Andrej Kacian --- Does not happen anymore. Feel free to reopen if this crash occurs again. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Sun Dec 30 14:14:48 2018 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Sun, 30 Dec 2018 13:14:48 +0000 Subject: [Users] [Bug 3090] Claws Mail crashes right after configuration In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3090 Andrej Kacian changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Andrej Kacian --- There has been a number of crash fixes since, please reopen if this is still a problem. I wasn't able to reproduce it. It would be useful to know what exact configuration was entered in the initial wizard. -- You are receiving this mail because: You are the assignee for the bug. From ricardo at mones.org Mon Dec 31 01:14:18 2018 From: ricardo at mones.org (Ricardo Mones) Date: Mon, 31 Dec 2018 01:14:18 +0100 Subject: [Users] Clawsker 1.3.1 released Message-ID: <20181231011418.48f93b93@busgosu> Hi all, A bit later than expected Clawsker, the Claws Mail hidden preferences editor and tweaker has been released. Changes from NEWS file: 1.3.1: - Support new account hidden preference “use_tls_sni” - Add SSL manager window size to windows tab - Rearranged and fixed behaviour of hotkeys tab - Make getting Claws Mail version more robust - Added test suite for some functions - Translations: • Updated: French, Swedish, Portuguese, Turkish, Dutch, Catalan, Danish, Spanish and Brazilian Portuguese • Dropped: Indonesian More details, updated screenshots and download links on homepage: http://www.claws-mail.org/clawsker.php Enjoy and happy new year to everybody! -- Ricardo Mones ~ 00:45 < hammar> cool.. have you used rssyl? 00:46 <@Ticho> um, yes Seen on #sylpheed -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: Firma digital OpenPGP URL: From h.m.brand at xs4all.nl Mon Dec 31 14:21:50 2018 From: h.m.brand at xs4all.nl (H.Merijn Brand) Date: Mon, 31 Dec 2018 14:21:50 +0100 Subject: [Users] Better defaults for clawsker In-Reply-To: <20181223113845.55d8bd34@busgosu> References: <20181221214607.7a3f7105@pc09.procura.nl> <20181221215109.59690cde@pc09.procura.nl> <20181223113845.55d8bd34@busgosu> Message-ID: <20181231142150.7dca8b93@pc09.procura.nl> On Sun, 23 Dec 2018 11:38:45 +0100, Ricardo Mones wrote: > On Fri, 21 Dec 2018 21:51:09 +0100 > "H.Merijn Brand" wrote: > > > Now simpler and without syntax error > > Added to master, thanks! :-) 👍 A few more remarks • hashbang clawsker starts with "#!/usr/bin/perl -w", which will horribly fail on all systems where "perl"'s $PATH is not /usr/bin, as it it is likely not the perl where the required modules are installed. Many other parts of clawsker are more or less dynamic and changed by the make process (e.g. @PREFIX@) $ perl -V:startperl startperl='#!/pro/bin/perl'; might be a start to create a clawsker that runs correct in the users environment I would suggest changing the Makefile: sed -e "s, at PREFIX@,${PREFIX},;s, at LIBDIR@,${LIBDIR},;s, at VERSION@,${VERSION},;s, at DATADIR@,${DATADIR}," < ${NAME} > build/${NAME} → perl -MConfig -p -e'1..1 and s/.*/$$Config{startperl}/;' \ -e's,\@PREFIX\@,${PREFIX},;' \ -e's,\@LIBDIR\@,${LIBDIR},;' \ -e's,\@VERSION\@,${VERSION},;' \ -e's,\@DATADIR\@,${DATADIR},' ${NAME} > build/${NAME}.2 and add "use warnings;" below "use strict;" in clawsker itself to compensate for the old-fashioned -w • PREFIX Again, I don't think /usr/local is a good default. The script itself uses the File::Which module to find out, so why not use the same for the transistion? PREFIX ?= /usr/local → PREFIX ?= $(shell perl -MFile::Which -E'say which ("claws-mail") =~ s{/[^/]+\z}{}r') or PREFIX ?= $(shell which claws-mail | perl -pe's{/[^/]+\z}{}') -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.29 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From boxcars at gmx.net Mon Dec 31 15:19:25 2018 From: boxcars at gmx.net (=?UTF-8?B?wrtRwqs=?=) Date: Mon, 31 Dec 2018 08:19:25 -0600 Subject: [Users] [Bug 1920] No automatic NNTP filtering In-Reply-To: References: Message-ID: <20181231081925.032fb670@sepulchrave.remarqs> On Sat, 29 Dec 2018 23:36:02 +0000 noreply at thewildbeast.co.uk wrote: > https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=1920 > > Andrej Kacian changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|REOPENED |RESOLVED > Resolution|--- |FIXED > > --- Comment #11 from Andrej Kacian --- > Both patches tested and pushed to git, (belated) thanks! :) Thank you! From nordquest at gmail.com Mon Dec 31 17:52:58 2018 From: nordquest at gmail.com (D. A. Nordquest) Date: Mon, 31 Dec 2018 11:52:58 -0500 Subject: [Users] Address Book Query Message-ID: I'm new to claws-mail and I like the clean layout. However, I can't find any simple way to add single addresses to the address book. Nor do I see how to make the program automatically add the addresses on sent (or received) messages to the address book. I don't want to convert another address book to claws-mail: I want to build one within claws-mail. Also, is there any place ready-to-use plugins are available so that the program does not have to be recompiled to use them? Thank very much for the help! Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From shai at platonix.com Mon Dec 31 18:03:43 2018 From: shai at platonix.com (Shai Berger) Date: Mon, 31 Dec 2018 19:03:43 +0200 Subject: [Users] Address Book Query In-Reply-To: References: Message-ID: <20181231190343.13964537.shai@platonix.com> On Mon, 31 Dec 2018 11:52:58 -0500 "D. A. Nordquest" wrote: > I'm new to claws-mail and I like the clean layout. However, I can't > find any simple way to add single addresses to the address book. In the message body display, the addresses show up in the small list of headers. Right clicking an address there opens a menu with an option to add to address-book. > Nor do I see how to make the program automatically add the addresses on > sent (or received) messages to the address book. I think there's a plugin which does that (address keeper?). Plugins are not on by default, you need to load them (via Configuation->Plugins). > > Also, is there any place ready-to-use plugins are available so that > the program does not have to be recompiled to use them? > How did you install Claws? If you built it from source, then the plugins are normally built and installed with it (in $PREFIX/lib/claws-mail/plugins). HTH, Shai. From nordquest at gmail.com Mon Dec 31 18:13:36 2018 From: nordquest at gmail.com (D. A. Nordquest) Date: Mon, 31 Dec 2018 12:13:36 -0500 Subject: [Users] Fwd: Address Book Query In-Reply-To: References: <20181231190343.13964537.shai@platonix.com> Message-ID: Thanks, Shai! I installed the version in the Fedora 29 repository. I'll follow your advice on right-clicking the address to add it! Thanks., again. Dave On Mon, Dec 31, 2018 at 12:05 PM Shai Berger wrote: > On Mon, 31 Dec 2018 11:52:58 -0500 > "D. A. Nordquest" wrote: > > > I'm new to claws-mail and I like the clean layout. However, I can't > > find any simple way to add single addresses to the address book. > > In the message body display, the addresses show up in the small list of > headers. Right clicking an address there opens a menu with an option to > add to address-book. > > > Nor do I see how to make the program automatically add the addresses on > > sent (or received) messages to the address book. > > I think there's a plugin which does that (address keeper?). Plugins are > not on by default, you need to load them (via Configuation->Plugins). > > > > > Also, is there any place ready-to-use plugins are available so that > > the program does not have to be recompiled to use them? > > > > How did you install Claws? If you built it from source, then the > plugins are normally built and installed with it (in > $PREFIX/lib/claws-mail/plugins). > > HTH, > Shai. > _______________________________________________ > Users mailing list > Users at lists.claws-mail.org > https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nordquest at gmail.com Mon Dec 31 18:17:21 2018 From: nordquest at gmail.com (D. A. Nordquest) Date: Mon, 31 Dec 2018 12:17:21 -0500 Subject: [Users] Address Book Query Message-ID: Shai, That solved my problem! Thanks! Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From lbickley at bickleywest.com Mon Dec 31 19:43:04 2018 From: lbickley at bickleywest.com (Lyle Bickley) Date: Mon, 31 Dec 2018 10:43:04 -0800 Subject: [Users] Happy New Year!!! Message-ID: <20181231104304.61700de3@asrock> Happy New Year! Especially so to the development team supporting Claws. Thank you for another year of excellent support! Cheers, Lyle -- 73 NM6Y Bickley Consulting West Inc. http://bickleywest.com "Black holes are where God is dividing by zero"