Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: spam move is very slow
Date: Fri, 29 Sep 2017 15:51:09 -0400	[thread overview]
Message-ID: <87o9pt9tci.fsf@lifelogs.com> (raw)
In-Reply-To: <871smqmvhl.fsf@chopper>

On Thu, 28 Sep 2017 22:14:14 +0200 joakim@verona.se wrote: 
j> I mark spam with $ while reading a group, and then press q.
j> The spam is very slowly moved to the spamlearn group I've configured.

j> Sometimes spam-move just hangs, and then I press c-g and it continues
j> for some reason. If I dont press c-g the spam move process often never terminates.

That's very strange. The actual method used to move the articles is
`spam-copy-or-move-routine' and it just relies on the Gnus internals
(mark articles, then move them). So if the normal method to move the
articles is fast, but spam.el is slow, something is not right.

j> The spam eventually winds up in the correct spamlearn group, but there
j> it is marked as E, for expired. I'm not sure why I'd want this, but the
j> documentation says it is normal.

Typically people don't want to keep spam. You can then set the policy
for what to do with expired articles, but if you think there's a need
for marking them as something else, what would it be?

j> How can I debug this slowness? I dont think its dovecot being slow,
j> because dovecot isnt usually very slow.

Process-mark articles and copy/move them to your spamlearn group.

Ted




  parent reply	other threads:[~2017-09-29 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28 20:14 joakim
2017-09-29 16:42 ` Steinar Bang
2017-09-29 19:44   ` joakim
2017-09-30 10:00     ` Steinar Bang
2017-09-29 19:51 ` Ted Zlatanov [this message]
2017-10-02  6:31   ` joakim
2017-10-02 14:54     ` Ted Zlatanov

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=87o9pt9tci.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.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).