From: Alberto L <alberto.l@nospam.net>
Subject: No Gnus 0.3 slower than Oort Gnus 0.24 spam handling
Date: Fri, 17 Mar 2006 11:33:09 -0800 [thread overview]
Message-ID: <y201wx0lvd6.fsf@newsserver.nospam.net> (raw)
Hi all,
I recently upgraded from Oort 0.24 to No 0.30 and my spam handling has
become quite slow. Here is my situation:
- I use nnfolder mail storage
my spam handling configuration (using bogofilter):
- splits spam into mail.spam.temp
- on exiting, spam in all groups is moved to mail.spam.save
- mail.spam.temp and mail.spam.save are spam groups
- the spam process destination for mail.spam.save is nil
When I enter mail.spam.temp to check for false spam positives, on
quitting it all spam-marked messages are moved to mail.spam.save.
This is quite slower with No 0.30 w.r.t. Oort 0.24 because,
apparently, both mail.spam.temp and mail.spam.save are written to
disk each time a single message is moved. With Oort 0.24 as far as I
can understand both groups are written to disk only once.
I include some bits of my spam configuration:
(setq
spam-split-group "mail.spam.temp"
spam-junk-mailgroups
'("mail.spam.temp" "mail.spam.save")
gnus-spam-process-newsgroups
'(
("^mail\\.incoming\\.....-..-..$"
((spam spam-use-bogofilter)))
("^mail\\.spam\\.train$"
;; ((spam spam-use-blacklist))
;; ((ham spam-use-whitelist))
((ham spam-use-bogofilter))
((spam spam-use-bogofilter)))
("^mail\\.spam\\.save$"
((ham spam-use-bogofilter)))
)
gnus-spam-process-destinations
'(
("^mail\\.spam\\.save$" nil)
("^mail\\..*$" "mail.spam.save")
)
gnus-ham-process-destinations
'(
("^mail\\.spam\\..*$" "mail.incoming.nospam")
)
)
Greetings,
--
Alberto
next reply other threads:[~2006-03-17 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 19:33 Alberto L [this message]
2006-03-21 16:02 ` Ted Zlatanov
[not found] ` <4nek0vdbwf.fsf@asimov.bwh.harvard.edu>
2006-03-21 17:31 ` Alberto L
2006-03-22 15:22 ` 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=y201wx0lvd6.fsf@newsserver.nospam.net \
--to=alberto.l@nospam.net \
/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).