From: Nicolas Cavigneaux <cavigneaux@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: Expiring nnimap messages automatically
Date: Tue, 07 Apr 2020 20:24:52 +0200 [thread overview]
Message-ID: <m21rozjgqz.fsf@gmail.com> (raw)
In-Reply-To: <87v9mbgqwc.fsf@ericabrahamsen.net>
Hi Eric, thank a lot for your reply.
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> I'm not entirely sure, but it looks like nnimap has its own server
> variable governing expiration/expunging: ‘nnimap-expunge’
>
> From the manual:
>
> When to expunge deleted messages. If ‘never’, deleted articles are
> marked with the IMAP ‘\\Delete’ flag but not automatically
> expunged. If ‘immediately’, deleted articles are immediately
> expunged (this requires the server to support the UID EXPUNGE
> command). If ‘on-exit’, deleted articles are flagged, and all
> flagged articles are expunged when the group is closed.
>
> For backwards compatibility, this variable may also be set to t or
> nil. If the server supports UID EXPUNGE, both t and nil are
> equivalent to ‘immediately’. If the server does not support UID
> EXPUNGE nil is equivalent to ‘never’, while t will immediately
> expunge ALL articles that are currently flagged as deleted (i.e.,
> potentially not only the article that was just deleted).
>
> Does that help?
I just tried to set 'nnimap-expunge' to both 'on-exit and then
'immediate but it doesn't seems to do anything at all.
Every single doc or blog post I read about imap setting only talk about
'nnmail-expiry-wait' so I'm a bit confused. I don't think that everybody
missed the point and didn't realized that there mails were only hidden
not really deleted from the server (or moved to Trash).
I had some good hope when I saw your reply and this variable I didn't know
about :D but unfortunately it doesn't seems to be the answer.
Anyway than a lot for your time and help.
--
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-07 18:25 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 [this message]
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
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=m21rozjgqz.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).