Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: per-message automatic splitting (with Sieve)
Date: Fri, 02 Nov 2001 14:31:30 -0500	[thread overview]
Message-ID: <2n4rodynot.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <vafitcti167.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 02 Nov 2001 17:32:16 +0100")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> I wonder if anybody is interested in the following which I've cooked
> up for better use of nnimap with Sieve splitting on the Cyrus server.
>
> You know, I used to be a great fan of nnmail-split-fancy-with-parent
> which split a followup into the same group as the original.  I wanted
> to have this for Sieve splitting, too, but there it is not so simple.
>
> So I came up with the following method: I create custom Message-ID
> headers which contain the right group name, and I do some Sieve rules
> which grok this special Message-ID format.
>
> Here's the code which creates my Message-ID headers:

[...]

> This piece of code takes a Sieve script and inserts rules which split
> incoming messages based on the tokens in the Message-ID.

Sounds cool. What if I use your trick too, but I use folder
INBOX.sung.otua for Gnus mailing-list (I read some group name from
right to left and use folder INBOX.auto.gnus for automobile news :-).
Then my MID is blahblah.fsf@INBOX.sung.otua.tok.zsh.cs.rochester.edu.
Your trick breaks :-(.

ShengHuo



  parent reply	other threads:[~2001-11-02 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02 16:32 Kai Großjohann
2001-11-02 18:43 ` Amos Gouaux
2001-11-02 19:38   ` Simon Josefsson
2001-11-02 19:31 ` ShengHuo ZHU [this message]
2001-11-02 22:34   ` Kai Großjohann
2001-11-02 22:58 ` Paul Jarc
2001-11-03 16:15   ` Kai Großjohann

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

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

  git send-email \
    --in-reply-to=2n4rodynot.fsf@zsh.cs.rochester.edu \
    --to=zsh@cs.rochester.edu \
    /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.
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 NNTP newsgroup(s).