From: Nicolas Cavigneaux <cavigneaux@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Expiring nnimap messages automatically
Date: Thu, 09 Apr 2020 10:22:27 +0200 [thread overview]
Message-ID: <m2ftddhytm.fsf@gmail.com> (raw)
In-Reply-To: <87v9mahvsn.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Trying going into the *Groups* buffer, putting point on
> "nnimap+home:INBOX", and hitting "G p" to edit the group parameters. You
> should see the 'expiry-wait entry in there. How it got in there I
> couldn't tell you, but Gnus saves group parameters along with marks in
> your.newsrc.eld file, so that's why you weren't seeing it in your config
> file.
Oh! I didn't know that .newsrc.eld was storing these info. I learned
about "G p" too, pretty handy.
So I took a look and the 'expiry-wait was in there.
How do it got there? I played a lot with all kind of Gnus options and
commands when I started using it. I didn't know what I was doing but
wanted to discover Gnus features so I played with things I didn't
understand… Guess I played with 'expiry-wait on this group.
> Simply removing this entry should be enough to let your server parameter
> take effect. Delete that and see if it works.
I did remove it then "C-c C-c". I also hit "s" in groups buffer to save
my changes in .newsrc.eld.
I checked that the file was up-to-date and it is.
I started a new instance of Emacs / Gnus. The 'expiry-wait is really
gone when I check the group using "G p". But deleting / moving of
expired email is also gone with it… My expired messages now stay in the
group.
I could manually set 'expiry-wait on each group and it would do the job
but I'm pretty sure it's not the right way .
--
Nicolas Cavigneaux
http://www.bounga.org
http://www.cavigneaux.net
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2020-04-09 8:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 8:42 Nicolas Cavigneaux
2020-04-07 17:13 ` Eric Abrahamsen
2020-04-07 18:24 ` Nicolas Cavigneaux
2020-04-07 19:49 ` Eric Abrahamsen
2020-04-07 20:22 ` Nicolas Cavigneaux
2020-04-07 21:29 ` Eric Abrahamsen
2020-04-07 22:32 ` Nicolas Cavigneaux
2020-04-08 3:45 ` Eric Abrahamsen
2020-04-08 8:38 ` Nicolas Cavigneaux
2020-04-08 14:55 ` Eric Abrahamsen
2020-04-09 8:22 ` Nicolas Cavigneaux [this message]
2020-04-09 16:47 ` Eric Abrahamsen
2020-04-09 19:26 ` Nicolas Cavigneaux
2020-04-09 20:23 ` Eric Abrahamsen
2020-04-09 20:27 ` Eric Abrahamsen
2020-04-09 21:15 ` Nicolas Cavigneaux
2020-04-09 21:32 ` 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=m2ftddhytm.fsf@gmail.com \
--to=cavigneaux@gmail.com \
--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).