From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 5178C1F461; Thu, 27 Jun 2019 19:50:11 +0000 (UTC) Date: Thu, 27 Jun 2019 19:50:11 +0000 From: Eric Wong To: Konstantin Ryabitsev Cc: meta@public-inbox.org Subject: Re: RFC: marking spam via refs/notes/spam to hide it Message-ID: <20190627195011.sitvi76s6x3d5k67@whir> References: <20190627184251.GC14570@chatter.i7.local> <20190627185236.2mwuoygclytf5m7x@whir> <20190627185723.GE14570@chatter.i7.local> <20190627193332.gjzwkuiotp6fgmcf@whir> <20190627194511.GF14570@chatter.i7.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190627194511.GF14570@chatter.i7.local> List-Id: Konstantin Ryabitsev wrote: > On Thu, Jun 27, 2019 at 07:33:32PM +0000, Eric Wong wrote: > > > > Aside from the git note, public-inbox-learn already does that: > > > > > > > > public-inbox-learn spam > > > > > > > (scans everything in ~/.public-inbox/config since spam is > > > > frequently cross-posted) > > > > > > Ah, that shows how carefully I read docs, I guess. :) Is it possible to just > > > specify a message-id, so that there's no extra step to dump the spam message > > > into a file? > > > > Not exactly with the Message-ID arg. It would be dangerous if > > somebody malicious wanted to get you to remove a legit message > > by sending a spam message which reuses a Message-ID of a legit > > message. I'd definitely want to verify a message is what I'd > > want to remove, first. > > This makes sense, thanks. I tried it out and it works to remove spam from > the frontend, but spamc step seems to fail with a somewhat incongruous error > code: > > spamc failed with: 18944 Oops, might be $? in Perl needs to be >> 8 to get the exit code. That gives 74, which spamc(1) says is EX_IOERR > Any pointers where I should look to figure out which part is failing? Anything in syslog? you can also check spamc or sa-learn on the message directly.