From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: I think I might have mistreated spam.el...
Date: Mon, 27 Jan 2003 20:34:58 -0500 [thread overview]
Message-ID: <m3ptqi83b1.fsf@heechee.beld.net> (raw)
In-Reply-To: <87n0lmdy8s.fsf@eris.void.at> (Andreas Fuchs's message of "Mon, 27 Jan 2003 22:26:05 +0000 (UTC)")
On Mon, 27 Jan 2003, asf@void.at wrote:
> I just found out why I had believed there was no more spam coming to
> me. I use spam.el splitting, and I saw many "filing into
> nnml+private:spambox" (that's my spambox) messages, but not one mail
> appeared there. So now.
> After a few days of having an empty spambox, I looked into my
> nnml+private active file, and saw this:
>
> [...]
> 412: newsticker
> 1: not-a-mailing-list
> [...]
> K 222: nnml+private:spambox
> [...]
> 1: spambox
>
> Ugggh. Which of these variables is responsible for this group name?
> Is it `spam-split-group'? If so, which value should it use? Just
> "spambox"?
Splitting functions will return a short group name, and the backend
will convert that to the fully qualified group name. Thus,
spam-split-group should be just "spambox" or whatever you like, and
that will translate into "nnml+private:spambox" automatically.
This is a Gnus convention (nnmail-split-fancy and nnimap-split-fancy),
not something spam.el controls AFAIK.
> After that is resolved, my only problem is how to get the articles
> from nnml+private:nnml+private:spambox into nnml+private:spambox. mv
> should do it (plus faking the right .active article cound, plus
> rebuilding nov), right?
I would enter the group, select all the articles, and move them.
Should be very quick with nnml.
Ted
next prev parent reply other threads:[~2003-01-28 1:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 22:26 Andreas Fuchs
2003-01-28 1:34 ` Ted Zlatanov [this message]
2003-01-28 10:40 ` Andreas Fuchs
2003-01-28 11:37 ` Andreas Fuchs
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=m3ptqi83b1.fsf@heechee.beld.net \
--to=tzz@lifelogs.com \
/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).