Gnus development mailing list
 help / color / mirror / Atom feed
From: Reid Rivenburgh <reid@lanl.gov>
Cc: ding@gnus.org
Subject: Re: Mail splitting questions or feature requests
Date: 22 Mar 2001 15:44:32 -0700	[thread overview]
Message-ID: <vetae6dpgof.fsf@toespaz.c3.lanl.gov> (raw)
In-Reply-To: <vafbsqtv4lf.fsf@lucy.cs.uni-dortmund.de>

 Kai Großjohann writes:

 > For the first question: see the variable nnmail-crosspost which
 > controls whether the first match in nnmail-split-methods fires, or
 > all of them do.

Thanks for the info, Kai, but I don't think that quite does what I'd
like.  Let me explain again.  Say I have an email message with 5
addresses in it (including From and Cc's).  Three of them are on my
nnmail-split-methods list, and two aren't.  I understand that with
nnmail-crosspost set to t, it'll get filed in the three matching
groups.  I'd like it to also file a copy in my default misc-mail group
in this case, because of the two non-matches.  I'd like any instance
of a non-match to trigger a dump to the default split-method group.

Does that make sense?  The rationale is that I sometimes get mail from
a non-match address about a topic that happens to be Cc'ed to someone
that is a match.  I don't associate the topic with the person that was
matched, so I don't think to look in their group when looking for the
mail later.  It'd be nice to know a copy went to misc-mail in that
case.

Reid


  reply	other threads:[~2001-03-22 22:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 19:15 Reid Rivenburgh
2001-03-22 22:09 ` Kai Großjohann
2001-03-22 22:44   ` Reid Rivenburgh [this message]
2001-03-22 23:05     ` Kai Großjohann
2001-03-22 23:31       ` Reid Rivenburgh
2001-03-22 23:41         ` Kai Großjohann
2001-03-22 23:47           ` Reid Rivenburgh
2001-03-22 23:55             ` Kai Großjohann
2001-03-23 18:44               ` Reid Rivenburgh

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=vetae6dpgof.fsf@toespaz.c3.lanl.gov \
    --to=reid@lanl.gov \
    --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).