On Sun 07 Jul 2019 at 07:47:58 (-0400), rhkra...@gmail.com wrote: > On Friday, July 05, 2019 02:35:46 AM Reco wrote: > > > > So, assuming that you wish to block threads that are started by me, > > > > participated by me, etc, you'll need (:h should correctly process a > > > > multiline header): > > > > > > > > if ( /^From:.*recovery...@enotuniq.net/:h ) > > > > > > > > to /dev/null > > > > > > > > if ( /^References:.*enotuniq.net/:h ) > > > > > > > > to /dev/null > > > > > > > > But that assumes that everybody in the thread are using a sane e-mail > > > > client. And relies on Message-ID that can include literally anything > > > > (but it does include a domain most of the time). > > > > > > Wait, but wouldn't that block any threads referring to any mail sent > > > from any address at the specified domain? This might work fine for a > > > small domain, but it's going to be bad for mail coming from Gmail > > > accounts ... > > I haven't been following this thread carefully, nor do I understand the > syntax > used above, but couldn't the * be replaced with a specific name to limit > which > emails get sent to /dev/null?
The method is very hit-or-miss. Firstly, it assumes that clients are maintaining a References field, but some only use In-Reply-To. Secondly, any domain in the References might look unique (like mine) but might not be. (Anyone could use wren.corp, and I could change mine from day to day if I like.) Thirdly, the local part (before the @) might contain a static name (like yours does), but might not. For an rough indication, try running $ grep '@gmail.com>' /tmp/deblis | cut -d '<' -f 2 | sort -u | less on an email mbox if you have one stored locally. (Your own outbox could suffice.) You'll see the local part sometimes contains specific information, but many use unique, random strings like 999cd080-9e74-c40d-0650-f4277d563...@gmail.com. > > That's another disadvantage, I agree. But it's a feature at the same > > time. For instance, outlook.com sents nothing but spam to this maillist, > > so any e-mails from that domain can be safely 'blocked' this way. If you're going to try this, I'd send the emails to a "spam" mbox rather than /dev/null as you can't recover from the latter when you find that your rule is too draconian. For example, much of my private correspondence originates from or passes through outlook.com. Trashing them all could be a costly mistake. Cheers, David.
