notspam: a notmuch interface to spamassassin

Hey, folks. I put together a little python program as an interface between notmuch and spamassassin (sa) that I thought others might be interested in: git://finestructure.net/notspam It's only dependencies are a running local sa daemon and python-notmuch. It's pretty straightforward: it's just a

notspam: a notmuch interface to spamassassin

n't tweaked it out yet, in which case if anyone has any suggestions on how to improve sa's classification I'm also all ears. -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20130305/2709bb18/attachment-0001.pgp>

[PATCH] test/README: mention the test_expect_equal_json and *sanitize* functions

also fix one typo --- test/README | 22 +- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/test/README b/test/README index 81c232d..d12cff2 100644 --- a/test/README +++ b/test/README @@ -178,11 +178,18 @@ library for your script to use. test_expect_equal_file

[PATCH 2/2] lib/database.cc: change how the parent of a message is calculated

Presently, the code which finds the parent of a message as it is being added to the database assumes that the first Message-ID-like substring of the In-Reply-To header is the parent Message ID. Some mail clients, however, put stuff other than the Message-ID of the parent in the In-Reply-To header,

[PATCH 1/2] test: add tests for the handling of References and In-Reply-To headers

These tests are known_broken, the following commit fixes them. --- Thanks to David and Tomi for pointing out test_expect_equal_json. In the process of implementing that, I discovered notmuch_json_show_sanitize, which I had also not been using. This patch fixes the test to use both these convenie

[PATCH v4 03/12] cli: add insert command

Peter Wang writes: > The notmuch insert command reads a message from standard input, > writes it to a Maildir folder, and then incorporates the message into > the notmuch database. Essentially it moves the functionality of > notmuch-deliver into notmuch. The first three patches in this series l

[PATCH 2/2] lib/database.cc: change how the parent of a message is calculated

Presently, the code which finds the parent of a message as it is being added to the database assumes that the first Message-ID-like substring of the In-Reply-To header is the parent Message ID. Some mail clients, however, put stuff other than the Message-ID of the parent in the In-Reply-To header,

[PATCH 1/2] test: add tests for the handling of References and In-Reply-To headers

These tests are known_broken, the following commit fixes them. --- Thanks to David and Tomi for pointing out test_expect_equal_json. In the process of implementing that, I discovered notmuch_json_show_sanitize, which I had also not been using. This patch fixes the test to use both these convenie

Re: [PATCH v4 03/12] cli: add insert command

Peter Wang writes: > The notmuch insert command reads a message from standard input, > writes it to a Maildir folder, and then incorporates the message into > the notmuch database. Essentially it moves the functionality of > notmuch-deliver into notmuch. The first three patches in this series l

afew filter rules

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/03/13 01:23, Patrick Totzke wrote: > Hey Reiner, > > Quoting Rainer M Krug (2013-02-28 15:29:33) >> Based on the the filter, it seems that list_id is used to tag the emails - >> correct? > > Seems so, yea [0]. > >> But in addition, I have som

Re: afew filter rules

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/03/13 01:23, Patrick Totzke wrote: > Hey Reiner, > > Quoting Rainer M Krug (2013-02-28 15:29:33) >> Based on the the filter, it seems that list_id is used to tag the emails - >> correct? > > Seems so, yea [0]. > >> But in addition, I have som