From: Esben Stien <b0ef@esben-stien.name>
To: help-gnu-emacs@gnu.org
Subject: Re: gnus Split Rules to SIEVE
Date: Mon, 21 Sep 2015 05:17:18 +0200 [thread overview]
Message-ID: <1953836f0b9bc457dca2b32a4b9b39f7@esben-stien.name> (raw)
In-Reply-To: <87bncw3atc.fsf@debian.uxu>
On 21.09.2015 01:55, Emanuel Berg wrote:
> (By the way, why don't the OP publish all or a couple
> of his Gnus splitting rules so we can reason about the
> real thing?)
Fortunately, my requirements are not that hard;)
I basically have a list of 400 entries, like this:
("gnuprinting-general"
"^\\(Mailing-List:\\|X-Mailing-List:\\|List-Id:\\).*printing-user-general.lists.freestandards.org*")
("gnuprinting-hp"
"^\\(Mailing-List:\\|X-Mailing-List:\\|List-Id:\\).*hp-list.linuxprinting.org*")
("gnuprinting-xerox"
"^\\(Mailing-List:\\|X-Mailing-List:\\|List-Id:\\).*xerox-list.linuxprinting.org*")
("gnuprinting-oce"
"^\\(Mailing-List:\\|X-Mailing-List:\\|List-Id:\\).*oce-list.linuxprinting.org*")
("gnuprinting-canon"
"^\\(Mailing-List:\\|X-Mailing-List:\\|List-Id:\\).*printing-user-canon.lists.freestandards.org*")
("linux-kernel"
"^\\(Mailing-List:\\|X-Mailing-List:\\|List-Id:\\).*linux-kernel@vger.kernel.org*")
("festival"
"^\\(Mailing-List:\\|Sender:\\|List-Id:\\).*festival-talk@metronomicon.com*")
("festvox-talk"
"^\\(Mailing-List:\\|Sender:\\|List-Id:\\).*festvox-talk@metronomicon.com*")
("www-math"
"^\\(Mailing-List:\\|X-Mailing-List:\\|List-Id:\\).*www-math.w3.org*")
("blug"
"^\\(Mailing-List:\\|X-Mailing-List:\\|List-Id:\\).*blug.blug.linux.no*")
("full-disclosure"
"^\\(Mailing-List:\\|List-Id:\\).*full-disclosure.lists.grok.org.uk*")
("honeypot"
"^\\(Mailing-List:\\|X-Mailing-List:\\|List-Id:\\).*honeypots.list-id.securityfocus.com*")
("vulnwatch"
"^\\(Mailing-List:\\|X-Mailing-List:\\|List-Id:\\).*vulnwatch-help@vulnwatch.org*")
..which could easily be parsed to [name][list-id]
Most mailing lists use the List-Id header, so all my lines are exactly
like this.
next prev parent reply other threads:[~2015-09-21 3:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3d1b340d392ba0a0f6a044c4b5bd0f35@esben-stien.name>
2015-09-20 17:45 ` gnus Split Rules to SIEVE b0ef
2015-09-20 18:27 ` Ian Zimmerman
2015-09-20 22:20 ` Emanuel Berg
2015-09-20 22:44 ` Ian Zimmerman
2015-09-20 23:55 ` Emanuel Berg
2015-09-21 0:45 ` Ian Zimmerman
2015-09-21 1:06 ` Emanuel Berg
2015-09-21 2:36 ` Emanuel Berg
2015-09-21 3:17 ` Esben Stien [this message]
2015-09-22 0:00 ` Emanuel Berg
2015-09-22 23:57 ` Esben Stien
2015-09-23 0:23 ` Emanuel Berg
2015-09-23 1:16 ` Ian Zimmerman
2015-09-23 1:52 ` Emanuel Berg
2015-09-23 8:46 ` tomas
2015-09-25 0:28 ` Emanuel Berg
2015-09-25 7:16 ` tomas
2015-09-26 1:58 ` Emanuel Berg
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1953836f0b9bc457dca2b32a4b9b39f7@esben-stien.name \
--to=b0ef@esben-stien.name \
--cc=help-gnu-emacs@gnu.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.
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).