From: Seth Falcon <sethfalcon@comcast.net>
Subject: Re: nnimap and expiry-target
Date: Tue, 10 May 2005 06:53:30 -0700 [thread overview]
Message-ID: <m2acn3nq5h.fsf@macaroni.local> (raw)
In-Reply-To: <87wtq8xlzq.fsf@rocksteady.printf.se>
Henrik Enberg <henrik.enberg@telia.com> writes:
> Henrik Enberg <henrik.enberg@telia.com> writes:
>
>> When I use an expiry target for nnimap group pointing to another nnimap
>> group on the same server, the expired articles end up being marked as
>> expirable in the target group. This is a bit suboptimal as I want the
>> target to be an archive. Is this intended behaviour?
Don't know, but I'm seeing the same thing:
I have expiry setup for an nnimap group going to an nnimap archive.
Also using dovecot.
Having things marked expirable made exiting these archive groups
extremely painful until I figured out:
;; Don't automatically do expiry when exiting groups
(setq gnus-summary-prepare-exit-hook nil)
+ seth
prev parent reply other threads:[~2005-05-10 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 18:28 Henrik Enberg
2005-05-09 19:00 ` Henrik Enberg
2005-05-10 13:53 ` Simon Josefsson
2005-05-11 2:20 ` Henrik Enberg
2005-05-10 13:53 ` Seth Falcon [this message]
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=m2acn3nq5h.fsf@macaroni.local \
--to=sethfalcon@comcast.net \
/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).