user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: "W. Trevor King" <wking@tremily.us>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [RFC] ssoma-mda: Use the email subject as the commit message
Date: Sun, 26 Oct 2014 17:19:24 -0700	[thread overview]
Message-ID: <20141027001924.GE15570@odin.tremily.us> (raw)
In-Reply-To: <20141026225740.GA1338@dcvr.yhbt.net>

[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]

On Sun, Oct 26, 2014 at 10:57:40PM +0000, Eric Wong wrote:
> 1) "notmuch insert" (Xapian index + Maildir delivery)
> 2) remove from Maildir immediately (keep message in ssoma)
> 
>   <some time passes...>
> 
> 3) a message is decided to be spam after human review,
>    use ssoma-rm (via public-inbox-learn) to remove it
>    from current history.
> 
> But notmuch/Xapian still knows about the message.
> 
> "notmuch new" does not work here because the Maildir is
> maintained in a constantly empty state.

That sounds like a reasonable use case for me.  I'll work up notmuch
patches for:

  $ notmuch insert --index-only

so you can skip step 2, and a new:

  $ notmuch remove

that removes a message (read from stdin) from the index.

> I wonder if it is better for public-inbox/ssoma to use (the already
> available) Xapian Perl bindings directly; likely using the notmuch
> configuration of Xapian as a guide.

I'm not going to stand in your way, but 98% of what you need is
already in notmuch.  I'd suggest seeing how long it takes me to write
those patches, and how well they are received upstream, before
dropping notmuch.

Cheers,
Trevor

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy


      reply	other threads:[~2014-10-27  0:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-18 20:19 [RFC] ssoma-mda: Use the email subject as the commit message W. Trevor King
2014-10-18 21:04 ` Eric Wong
2014-10-18 21:50   ` W. Trevor King
2014-10-18 23:43     ` Eric Wong
2014-10-19  3:48       ` W. Trevor King
2014-10-19  5:30         ` Eric Wong
2014-10-19 17:31           ` W. Trevor King
2014-10-20  0:49             ` Eric Wong
2014-10-20 15:36               ` W. Trevor King
2014-10-20 19:26                 ` Eric Wong
2014-10-20 19:53                   ` W. Trevor King
2014-10-26 22:57         ` Eric Wong
2014-10-27  0:19           ` W. Trevor King [this message]

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=20141027001924.GE15570@odin.tremily.us \
    --to=wking@tremily.us \
    --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).