Gnus development mailing list
 help / color / mirror / Atom feed
From: Emanuel Berg <moasenwood@zoho.eu>
To: ding@gnus.org
Subject: Re: per group split rules
Date: Mon, 08 Nov 2021 22:06:52 +0100	[thread overview]
Message-ID: <87wnli2w7n.fsf@zoho.eu> (raw)
In-Reply-To: <87wnlipien.fsf@gnus.jao.io>

Jose A. Ortega Ruiz wrote:

> i have my mail-sources set to '((group)), so that each of my
> nnml groups has a mail-source of its own (typically reading
> a spool file or a local maildir, populated asynchronously).
> is there a way of having split rules (fancy or not) that
> apply /only/ to a given nnml group, rather than globally to
> all incoming mail?

Respooling perhaps ... how often/when is this supposed
to happen?

> or, alternatively, is it possible to have a (global) split
> rule that says (when nnmail-resplit-incoming is t) something
> like: "leave this message in the group which fetched it via
> its mail-source parameter"?

You can use functions instead of regexps both with fancy and
regular so put it there if so, I guess?

> A: Because it fouls the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on usenet and in e-mail?

Ha. See RFC 3676, section 4.3 (Usenet Signature Convention)

  https://www.ietf.org/rfc/rfc3676.txt
  
for the second most annoying thing. (Actually it isn't
so annoying.)

-- 
underground experts united
https://dataswamp.org/~incal



  reply	other threads:[~2021-11-08 21:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08 19:16 Jose A. Ortega Ruiz
2021-11-08 21:06 ` Emanuel Berg [this message]
2021-11-08 22:38   ` Jose A. Ortega Ruiz
2021-11-08 23:46     ` Emanuel Berg
2021-11-08 23:21   ` Jose A. Ortega Ruiz

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=87wnli2w7n.fsf@zoho.eu \
    --to=moasenwood@zoho.eu \
    --cc=ding@gnus.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 NNTP newsgroup(s).