From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nnimap expiry
Date: Wed, 22 Sep 2010 08:02:36 -0500 [thread overview]
Message-ID: <87fwx2hqxf.fsf@lifelogs.com> (raw)
In-Reply-To: <m3d3s6ncp2.fsf@quimbies.gnus.org>
On Tue, 21 Sep 2010 21:01:13 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I get:
>>
>> nnimap-request-expire-articles: Symbol's value as variable is void: nnml-inhibit-expiry
>>
>> when I try "expire now".
LMI> Cut'n'paste error. Fixed and pushed.
Now expiry runs when I trigger it manually but the article is not
actually expunged: the mark remains `E' instead of `G' and I can still
select it. The group parameters have (auto-expire t) but that shouldn't
matter since the article definitely has the `E' mark.
08:00:24 116 SELECT "INBOX"
08:00:24 117 UID FETCH 274369:274372,274374:274375 (UID RFC822.SIZE BODYSTRUCTURE BODY.PEEK[HEADER.FIELDS (Subject From Date Message-Id References In-Reply-To Xref X-Face Keywords Gcc Cc X-Spam-Status X-Bogosity X-CRM114-Status To Newsgroups)])
08:00:33 118 UID FETCH 274375 BODY.PEEK[]
08:00:40 119 UID SEARCH SENTBEFORE 22-SEP-2010
(I run `gnus-summary-expire-articles-now' here, then `q'uit the group)
08:00:40 119 UID SEARCH SENTBEFORE 22-SEP-2010
next prev parent reply other threads:[~2010-09-22 13:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 18:01 Lars Magne Ingebrigtsen
2010-09-21 18:36 ` Robert Pluim
2010-09-21 18:56 ` Ted Zlatanov
2010-09-21 19:01 ` Lars Magne Ingebrigtsen
2010-09-22 13:02 ` Ted Zlatanov [this message]
2010-09-22 13:19 ` Ted Zlatanov
2010-09-22 16:40 ` Lars Magne Ingebrigtsen
2010-09-22 17:21 ` Ted Zlatanov
2010-09-22 17:27 ` Lars Magne Ingebrigtsen
2010-09-22 18:25 ` Ted Zlatanov
2010-09-22 18:38 ` Lars Magne Ingebrigtsen
2010-09-22 19:20 ` Ted Zlatanov
2010-09-22 19:28 ` Lars Magne Ingebrigtsen
2010-09-22 19:56 ` Ted Zlatanov
2010-09-22 20:08 ` Lars Magne Ingebrigtsen
2010-09-22 21:00 ` Ted Zlatanov
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=87fwx2hqxf.fsf@lifelogs.com \
--to=tzz@lifelogs.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).