From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Nicolas Cavigneaux <cavigneaux@gmail.com>
Cc: info-gnus-english@gnu.org
Subject: Re: Expiring nnimap messages automatically
Date: Tue, 07 Apr 2020 20:45:47 -0700 [thread overview]
Message-ID: <87zhbmiqs4.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m2r1wzhqpf.fsf@gmail.com> (Nicolas Cavigneaux's message of "Wed, 08 Apr 2020 00:32:44 +0200")
Nicolas Cavigneaux <cavigneaux@gmail.com> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>>> It returns nil so I guess it's not good?
>>
>> Yup, that would cause the problem. And you're sure that the group name
>> you're testing is a valid one, right? What do you get for just:
>>
>> (gnus-group-find-parameter <group-name>)
>>
>> ?
>
> Yes I think that the group name I'm using for my tests is a valid one. I
> added a screenshot so you can see by yourself.
>
> Evaluating:
>
> (gnus-group-find-parameter "nnimap+home:INBOX")
>
> returns:
>
> ((display . all) (expiry-wait . 2)
Whoa hang on, why did explicitly asking for the 'expiry-wait parameter
return nil before, then? Can you test that again? If 'expiry-wait is
present in the alist, we should have gotten 2 from the earlier call.
Anyway, something is setting this parameter to two days, so I'm guessing
that your imap messages are getting expired, but not until two days
later, so it might look like nothing is happening. Is that possible?
Have you configured the `gnus-parameters' option? Or set an
`expiry-wait' parameter for this group in particular? Two days isn't a
default value anywhere...
Eric
_______________________________________________
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-08 3:46 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 [this message]
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=87zhbmiqs4.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=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).