From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: nnrss group and auto-expire
Date: Mon, 22 Jan 2018 09:34:46 -0800 [thread overview]
Message-ID: <87efmhdcg9.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <yxwr2qicdhq.fsf@socbm220.bbn.verigy.net>
Rud1ger Sch1erz <nospam_tigre@yahoo.es> writes:
> I'd like to use auto-expire for my nnrss groups, thus mark read articles
> as expirable automatically.
>
> While this works fine form my nnml groups, nnrss groups seem to ignore
> it. However I can mark single articles in nnrss group as expirable using
> the `E' command.
>
> Any ideas?
I'm not certain, but I wouldn't expect expiry to work at all in nnrss
groups. They are essentially read-only, whereas expiry means you want
the articles to *go* somewhere after a certain period of time. I
wouldn't expect you could make nnrss articles go anywhere.
Eric
next prev parent reply other threads:[~2018-01-22 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 11:57 Rud1ger Sch1erz
2018-01-22 17:34 ` Eric Abrahamsen [this message]
[not found] ` <mailman.7766.1516642551.27995.info-gnus-english@gnu.org>
2018-01-23 16:40 ` Rud1ger Sch1erz
2018-01-23 17:38 ` Eric Abrahamsen
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=87efmhdcg9.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=info-gnus-english@gnu.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).