Re: RFC: marking spam via refs/notes/spam to hide it

[Eric Wong <e@80x24.org>]

Konstantin Ryabitsev <konstantin@linuxfoundation.org> 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 </path/to/message
> > > >
> > > >   (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.