Re: Unsubscribing from mailing-list threads (was: Preferred way to get imap emails)

2019-07-30 Thread Grant Edwards
On 2019-07-30, José María Mateos  wrote:
> On Tue, Jul 30, 2019 at 10:08:02AM -0400, Mark H. Wood wrote:
>
>> You may want to examine some netnews clients for ideas. They tend to
>> have exactly this: a database of killed threads, easily augmented with
>> a simple keystroke.
>
> This. Having used slrn in the past, I was surprised mutt didn't have 
> some kind of killfile mechanism readily available (or, if it's 
> available, I have completely missed it).

That's one of the reasons I use slrn rather than mutt for following
mailing lists (including this one).

-- 
Grant Edwards   grant.b.edwardsYow! Quick, sing me the
  at   BUDAPEST NATIONAL ANTHEM!!
  gmail.com



Re: Unsubscribing from mailing-list threads (was: Preferred way to get imap emails)

2019-07-30 Thread José María Mateos
On Tue, Jul 30, 2019 at 10:08:02AM -0400, Mark H. Wood wrote:

> You may want to examine some netnews clients for ideas. They tend to
> have exactly this: a database of killed threads, easily augmented with
> a simple keystroke.

This. Having used slrn in the past, I was surprised mutt didn't have 
some kind of killfile mechanism readily available (or, if it's 
available, I have completely missed it).

Cheers,

-- 
José María (Chema) Mateos || https://rinzewind.org/


Re: Unsubscribing from mailing-list threads (was: Preferred way to get imap emails)

2019-07-30 Thread Mark H. Wood
On Tue, Jul 30, 2019 at 07:40:02AM +0200, Matthias Apitz wrote:
> El día martes, julio 30, 2019 a las 06:36:35a. m. +0200, Francesco Ariis 
> escribió:
> 
> > On Tue, Jul 30, 2019 at 06:31:42AM +0200, Matthias Apitz wrote:
> > >
> > > I'm a mutt user for many years. From time to time I do miss a feature in
> > > mutt to mark a given thread as "do not present any mail of this thread
> > > anymore, just collapse them and mark for deletion on exit".
> > >
> > > This is such a thread I would mark as this.
> > 
> > Maybe this link can be of interest
> > 
> > http://ariis.it/static/articles/mutt-ml/page.html
> 
> Thanks for this pointer. The doc describes exactly the problem. But, the
> proposed solution with a macro deleting threads which follow the rule
> (copied from the doc):
> 
> "Threads with only replies means threads where the originating post
> isn’t present; if it is not present is because we deleted it; if we
> deleted it we didn’t like it and we don’t want replies to it, too."
> 
> is not good. Sometimes (many times) I have saved the original post of a
> "good" thread in some place, for example into the mbox file ~/Mail/mutt and 
> so the
> above pattern would touch/delete a "good" thread also as a "bad" one.
> 
> A solution must be based on some kind of a local "database" file of threads 
> marked as
> "bad" threads (perhaps as patterns) and one must actively store the given
> "bad" thread into it, for example with M and then a D would
> later, even in the next mutt session, read this "database" file and delete
> all threads from the actual mailbox for all patterns in it.

You may want to examine some netnews clients for ideas.  They tend to
have exactly this: a database of killed threads, easily augmented with
a simple keystroke.

-- 
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu


signature.asc
Description: PGP signature


Re: Unsubscribing from mailing-list threads (was: Preferred way to get imap emails)

2019-07-30 Thread Samir Benmendil

On Jul 30, 2019 at 7:40, Matthias Apitz wrote:
A solution must be based on some kind of a local "database" file of 
threads marked as "bad" threads (perhaps as patterns) and one must 
actively store the given "bad" thread into it, for example with M 
and then a D would later, even in the next mutt session, read 
this "database" file and delete all threads from the actual mailbox 
for all patterns in it.


Would it be possible to keep this information in the email by, say, 
adding a header to it. And have mutt mark any message whose parent 
contains this header as read.


Something like this as a macro or hook (untested):

   ~h X-Mark-Thread-Read\n

An external tool can probably add the header if mutt can't do it.

One could also (ab)use the spam detection mechanism

   spam "X-Mark-Thread-Read" "100/NotInterested"

I'm reading this out of the NeoMutt manual, I suppose Mutt has similar 
functionality.




I Cc'ed the author of the article: fa...@ariis.it
Please keep him/her in Cc when you reply.

matthias

--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub


signature.asc
Description: PGP signature


Re: Unsubscribing from mailing-list threads (was: Preferred way to get imap emails)

2019-07-30 Thread Francesco Ariis
Hello Matthias,

On Tue, Jul 30, 2019 at 07:40:02AM +0200, Matthias Apitz wrote:
> I Cc'ed the author of the article: fa...@ariis.it
> Please keep him/her in Cc when you reply.

Big smile, the author and the poster are in this case the
same person: myself. :P

> Thanks for this pointer. The doc describes exactly the problem. But, the
> proposed solution with a macro deleting threads which follow the rule
> (copied from the doc):
> 
> "Threads with only replies means threads where the originating post
> isn’t present; if it is not present is because we deleted it; if we
> deleted it we didn’t like it and we don’t want replies to it, too."
> 
> is not good. Sometimes (many times) I have saved the original post of a
> "good" thread in some place, for example into the mbox file ~/Mail/mutt and 
> so the
> above pattern would touch/delete a "good" thread also as a "bad" one.
> 
> A solution must be based on some kind of a local "database" file of threads 
> marked as
> "bad" threads (perhaps as patterns) and one must actively store the given
> "bad" thread into it, for example with M and then a D would
> later, even in the next mutt session, read this "database" file and delete
> all threads from the actual mailbox for all patterns in it.

Useful remarks! Indeed a 100% solution *has* to pass from some kind
of database/list of good/bad threads. For not, marking a message
as "important" saves the thread (even if broken) from touch/delete;
this alleviates the pain in some cases.
-F


Re: Unsubscribing from mailing-list threads (was: Preferred way to get imap emails)

2019-07-29 Thread Matthias Apitz
El día martes, julio 30, 2019 a las 06:36:35a. m. +0200, Francesco Ariis 
escribió:

> On Tue, Jul 30, 2019 at 06:31:42AM +0200, Matthias Apitz wrote:
> >
> > I'm a mutt user for many years. From time to time I do miss a feature in
> > mutt to mark a given thread as "do not present any mail of this thread
> > anymore, just collapse them and mark for deletion on exit".
> >
> > This is such a thread I would mark as this.
> 
> Maybe this link can be of interest
> 
> http://ariis.it/static/articles/mutt-ml/page.html

Thanks for this pointer. The doc describes exactly the problem. But, the
proposed solution with a macro deleting threads which follow the rule
(copied from the doc):

"Threads with only replies means threads where the originating post
isn’t present; if it is not present is because we deleted it; if we
deleted it we didn’t like it and we don’t want replies to it, too."

is not good. Sometimes (many times) I have saved the original post of a
"good" thread in some place, for example into the mbox file ~/Mail/mutt and so 
the
above pattern would touch/delete a "good" thread also as a "bad" one.

A solution must be based on some kind of a local "database" file of threads 
marked as
"bad" threads (perhaps as patterns) and one must actively store the given
"bad" thread into it, for example with M and then a D would
later, even in the next mutt session, read this "database" file and delete
all threads from the actual mailbox for all patterns in it.

I Cc'ed the author of the article: fa...@ariis.it
Please keep him/her in Cc when you reply.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub