From: NAGY Andras <nagya@inf.elte.hu>
Subject: Re: nnimap-expiry-target?
Date: 28 Dec 2000 01:29:32 +0100 [thread overview]
Message-ID: <87lmt1mlqr.fsf@lovi.inf.elte.hu> (raw)
In-Reply-To: <iluae9nrw18.fsf@barbar.josefsson.org>
Simon Josefsson <sj@extundo.com> writes:
> NAGY Andras <nagya@inf.elte.hu> writes:
>
> > Shouldn't nnimap support nnmail-expiry-target (which allows expired
> > articles to be moved to a specific group instead of being deleted)
>
> Yup, I've added support for it in CVS. Does it work?
Depends.
Given a group, INBOX.test.foo, with parameters (total-expire . t) and
(expiry-wait . immediate), and nnmail-expiry-target set to
"INBOX.test.arch", where the latter group does not exist and the
default select method is something different from imap. C-c C-x on
INBOX.test.foo results in:
Signaling: (void-function nnspool-request-accept-article)
nnspool-request-accept-article("INBOX.test.arch" "" nil)
gnus-request-accept-article("INBOX.test.arch" nil nil t)
nnmail-expiry-target-group("INBOX.test.arch" "INBOX.test.foo")
nnimap-expiry-target((4 . 6) "INBOX.test.foo" "mailbox")
nnimap-request-expire-articles((4 5 6) "INBOX.test.foo" "mailbox" nil)
gnus-request-expire-articles((4 5 6) "nnimap+mailbox:INBOX.test.foo")
gnus-group-expire-articles-1("nnimap+mailbox:INBOX.test.foo")
gnus-group-expire-articles(nil)
call-interactively(gnus-group-expire-articles)
#<compiled-function (topic) "...(37)" [topic call-interactively gnus-group-expire-articles gnus-message 5 "Expiring groups in %s..." mapcar #<compiled-function ... "...(5)" ... 2> gnus-topic-find-groups gnus-level-killed t gnus-group-marked nil "Expiring groups in %s...done"] 6 ("/home/nagya/gnus/gnus-build/lisp/gnus-topic.elc" . 23870) (list (gnus-group-topic-name))>(nil)
call-interactively(gnus-topic-expire-articles)
It tries to use the default select method for storing the article,
instead of imap, therefore the fully qualified group name should be
given in expiry-target. Not sure if this is a bug. Anyway, it seems
to me that it downloads the article in question, then respools it in
the target group. On imap targets, this should be optimized out, by
using server side copying. (Like in the case of splitting.)
Fails to save if the archive group does not exist (autocreate?), but
deletes anyway.
Using imap target by default and autocreate would be nice, as they
allow constructs like this (store expired foo.bar aritcles in
archive.foo.bar):
(setq nnmail-expiry-target
(lambda (group)
(replace-in-string group
"\\`\\(INBOX\\.\\|\\)\\(.*\\)"
"INBOX.archive.\\2")))
Otherwise (with existsing, fully qualified target group) works fine.
Andras
next prev parent reply other threads:[~2000-12-28 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-23 3:20 nnimap-expiry-target? NAGY Andras
2000-12-23 15:34 ` nnimap-expiry-target? Simon Josefsson
2000-12-28 0:29 ` NAGY Andras [this message]
2000-12-28 9:50 ` nnimap-expiry-target? Kai Großjohann
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=87lmt1mlqr.fsf@lovi.inf.elte.hu \
--to=nagya@inf.elte.hu \
/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).