From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: gnus-summary-limit-to-recipient and
Date: Fri, 03 Dec 2004 09:49:41 +0100 [thread overview]
Message-ID: <v94qj3u5p6.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87u0r34yvu.fsf@orebokech.com>
On Fri, Dec 03 2004, Romain Francoise wrote:
> Small nit: it doesn't appear to be willing to limit on Cc in my
> nnfolder+archive groups, I have:
>
> (setq nnmail-extra-headers '(To Cc Newsgroups)
> gnus-extra-headers '(To Cc Newsgroups))
>
> It just says `Found no matches for ..'. It catches addresses in To:
> just fine. Limiting on Cc works in nnml groups. Would you have any
> idea of what I'm missing?
After adding entries to `nnmail-extra-headers' you need to regenerate
the overview files[1]. Did you? Else I don't know. (I only tested
it on nnml and nnimap.)
Thanks for your feedback.
Bye, Reiner.
[1]
,----[ (info "(gnus)To From Newsgroups") ]
| A related variable is `nnmail-extra-headers', which controls when to
| include extra headers when generating overview (NOV) files. If you
| have old overview files, you should regenerate them after changing this
| variable, by entering the server buffer using `^', and then `g' on the
| appropriate mail server (e.g. nnml) to cause regeneration.
`----
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-12-03 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 22:44 gnus-summary-limit-to-recipient and gnus-summary-sort-by-recipient Reiner Steib
2004-12-03 0:05 ` Tassilo Horn
2005-09-07 16:17 ` Reiner Steib
2004-12-03 7:36 ` Romain Francoise
2004-12-03 8:49 ` Reiner Steib [this message]
2004-12-03 11:10 ` gnus-summary-limit-to-recipient and Romain Francoise
2004-12-03 16:02 ` Reiner Steib
2004-12-04 21:30 ` Karl Pflästerer
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=v94qj3u5p6.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).