From: David Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: gnus-extra-headers and gnus-summary-limit-to-extra (was: nnimap and sticky cache)?
Date: Mon, 30 Mar 2009 16:15:22 -0400 [thread overview]
Message-ID: <m2ab72hin9.fsf_-_@boostpro.com> (raw)
In-Reply-To: <87prg01bkw.fsf@thinkpad.tsdh.de>
on Sun Mar 29 2009, Tassilo Horn <tassilo-AT-member.fsf.org> wrote:
> David Abrahams <dave@boostpro.com> writes:
>
> Hi David,
>
>>>>> Do you use the agent for you imap server?
>>>>
>>>> Yup. But even if I turn the agent off I still see this problem.
>>>
>>> As Tassilo already said, turn the agent off and delete the agent
>>> files still in ~/News/agent. Next, you could try to set the server
>>> variable nnimap-nov-is-evil for your nnimap server definition and
>>> also delete all overview files for the server (usually
>>> ~/News/overview/nnimap/SERVER). (I think all of this is safe to do,
>>> but better keep a backup when deleting stuff from ~/News).
>>
>> OK, did all that. Unfortunately nothing I do seems to make it
>> possible for Gnus to limit to a particular regexp in the Message-Id
>> field. What am I missing?
>
> How is that related to phantom articles and the agent?
Well, it's not. I merely thought that was the problem, i.e. I assumed
Gnus didn't have a cache of that field.
> Anyway, you should be able to limit to the message-id using `/ h
> Message-Id: <regexp>'.
Cool, thanks. But why doesn't this work with gnus-extra-headers?
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2009-03-30 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 20:32 nnimap and sticky cache David Abrahams
2009-03-24 21:04 ` Tassilo Horn
2009-03-25 1:33 ` David Abrahams
2009-03-25 7:46 ` Tassilo Horn
2009-03-25 10:48 ` David Engster
2009-03-28 19:50 ` David Abrahams
2009-03-29 17:30 ` Tassilo Horn
2009-03-30 20:15 ` David Abrahams [this message]
2009-03-31 6:41 ` gnus-extra-headers and gnus-summary-limit-to-extra Tassilo Horn
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=m2ab72hin9.fsf_-_@boostpro.com \
--to=dave@boostpro.com \
--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).