user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: RFC: marking spam via refs/notes/spam to hide it
Date: Thu, 27 Jun 2019 15:45:11 -0400	[thread overview]
Message-ID: <20190627194511.GF14570@chatter.i7.local> (raw)
In-Reply-To: <20190627193332.gjzwkuiotp6fgmcf@whir>

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

Any pointers where I should look to figure out which part is failing?

-K

  reply	other threads:[~2019-06-27 19:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-27 18:42 RFC: marking spam via refs/notes/spam to hide it Konstantin Ryabitsev
2019-06-27 18:52 ` Eric Wong
2019-06-27 18:57   ` Konstantin Ryabitsev
2019-06-27 19:33     ` Eric Wong
2019-06-27 19:45       ` Konstantin Ryabitsev [this message]
2019-06-27 19:50         ` Eric Wong
2019-06-27 20:18           ` Konstantin Ryabitsev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190627194511.GF14570@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).