Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Alexander Baier <alexander.baier@mailbox.org>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: info-gnus-english@gnu.org
Subject: Re: expiry-target group parameter does not have any effect
Date: Mon, 16 Mar 2015 14:48:32 +0100	[thread overview]
Message-ID: <87twxl12a7.fsf@mailbox.org> (raw)
In-Reply-To: <m2y4n6xs3b.fsf@charm-ecran.irisa.fr> (Alan Schmitt's message of "Mon, 09 Mar 2015 13:39:36 +0100")

Hello Alan!

On 2015-03-09 13:39 Alan Schmitt wrote:
> I have something similar here (except that I edit the parameter
> programmatically):
>
> #+begin_src emacs-lisp
> (setq gnus-parameters
>       '(("^old.*"
>          (total-expire . t)
>          (expiry-wait . 1)
>          (expiry-target . "nnimap+zimbra:archive"))
> ...))
> #+end_src

I migrated all my group parameters to a setq form as you did above, the
articles are still not moved.  All the other group parameters (of this
group and other groups) are applied as expected.

>> Did I mess up my configuration?  Is there a way to "track" the expiry
>> process, so I can find out, what is going wrong?
>
> You can look in the *Messages* buffer, there should be logs about
> expiring. If there isn't, try increasing gnus's verbosity (setting
> `gnus-verbose' to 10 for very very verbose, for instance).

Even with setting it to 10 I only get:

Retrieving newsgroup: nnmaildir+mailbox:INBOX.daily...
Fetching headers for nnmaildir+mailbox:INBOX.daily...done
Sorting threads...done
Generating summary...done
No more unseen articles
No more unread articles
Exiting summary buffer and applying spam rules
Expiring articles...done


Is there another way for me to track the path of an email along the
expiry process? Or does anyone else have an idea about what might be at
fault here?

Regards,
-- 
Alexander Baier


  reply	other threads:[~2015-03-16 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07 10:59 Alexander Baier
2015-03-09 12:39 ` Alan Schmitt
2015-03-16 13:48   ` Alexander Baier [this message]
2015-03-16 17:21     ` Alan Schmitt

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=87twxl12a7.fsf@mailbox.org \
    --to=alexander.baier@mailbox.org \
    --cc=alan.schmitt@polytechnique.org \
    --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).