From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: Why expiry of drafts?
Date: Mon, 26 Apr 2004 22:35:08 +0200 [thread overview]
Message-ID: <87ekqapjer.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: <yovad65ug5hz.fsf@relaskop.wsl.ch>
Adrian Lanz <lanz@fowi.ethz.ch> writes:
> The funny thing is (besides that I do not see why a draft - in the
> intermediate draft state - is expired at all!), that the expiry target
> is correctly evaluated from my nnmail-fancy-expiry-targets variable
> (in the example above it resolves to "wsl-2004"), but that the
> destination "/home/lanz/mail/gnus" seems to be derived from some
> "general value" of nnml-directory. Usually my mail messages are
> expired to the nnml-directory "/home/lanz/mail/gnus/expired/" as
> configured in variable gnus-secondary-select-methods. The relevant
> parts of my configuration are:
You didn't say what's your expiry-target configuration ;-)
I'm not sure if it is possible to specify fully qualified group names
in nnmail-fancy-expiry-targets. (Looks.) It seems to be possible.
But there is no obvious place to put server-specific configuration.
Hm. Is it possible to add nnmail-fancy-expiry-targets as a server
parameter? Does anyone know?
> (setq gnus-home-directory "/home/lanz/mail/gnus/")
> (setq gnus-directory gnus-home-directory)
> (setq message-directory gnus-home-directory)
> (setq message-auto-save-directory (concat message-directory "drafts"))
> (setq gnus-secondary-select-methods
> '(
> (nnfolder "mail"
> ...
> (nnfolder-get-new-mail t)
> (nnfolder-inhibit-expiry nil))
> (nnml "expired"
> (nnml-directory "/home/lanz/mail/gnus/expired/")
> ...
> (nnfolder-get-new-mail nil)
> (nnfolder-inhibit-expiry t))))
> (setq nnmail-expiry-wait-function
> (lambda (group)
> (cond ((string= group "spam.mail")
> 5)
> (t
> 30))))
> (setq gnus-total-expirable-newsgroups "nnfolder\\+mail:.*")
>
> So if ever expiring of messages happens, it should be only in
> "nnfolder\\+mail:.*" groups (definitively not in the "nndraft:drafts"
> group), after 5 (spam) or 30 days (not immediately as it seems to be
> the case for drafts) and into a subdirectory of
> "/home/lanz/mail/gnus/expired/" (not "/home/lanz/mail/gnus/" as for
> drafts).
No, no, no. Total-expire means that Gnus considers read articles
(marks r, R, K, Y and so on) to be expirable, in addition to the
articles explicitly marked as expirable (mark E).
If you mark a message as expirable, using the E key (not e), then it
will be expirable in any group. You can set nnchoke-inhibit-expiry,
and you can tweak expiry-wait, but you didn't do any of those for
nndraft:drafts.
next parent reply other threads:[~2004-04-26 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yovad65ug5hz.fsf@relaskop.wsl.ch>
2004-04-26 20:35 ` Kai Grossjohann [this message]
[not found] ` <yovapt9tem9o.fsf@relaskop.wsl.ch>
2004-05-01 11:18 ` Kai Grossjohann
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=87ekqapjer.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.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).