From: lee <lee@yagibdah.de>
To: ding@gnus.org
Subject: Re: storing messages into an mbox file
Date: Fri, 08 May 2015 01:14:44 +0200 [thread overview]
Message-ID: <87lhh0j7yz.fsf@heimdali.yagibdah.de> (raw)
In-Reply-To: <87sibcvps0.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 04 May 2015 14:07:59 +0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> lee <lee@yagibdah.de> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> lee <lee@yagibdah.de> writes:
>>>
>>>> Andreas Schwab <schwab@linux-m68k.org> writes:
>>>>
>>>>> Perhaps you want to G m (gnus-group-make-group) a group with the nnmbox
>>>>> backend, then B m (gnus-summary-move-article) the articles in there.
>>>>
>>>> That might work better, thanks. But how do I get rid of the groups I
>>>> already created in order to figure this out? There has to be some way
>>>> to delete nndoc groups.
>>>
>>> I haven't found a way yet :)
>>
>> Maybe that's a missing feature ...
>>
>>> Presumably you could close gnus, and edit the newsrc.eld file by hand.
>>> That's usually a sign that you're doing something wrong, but in this
>>> case I don't know what the alternative is!
>>
>> Unfortunately, that file isn't very editing-friendly.
>
> Most definitely not!
>
>> Now I have over a hundred spam messages in nnmbox:spam. But where is
>> the mbox file they are in? I wanted to feed it to sa-learn and couldn't
>> find it.
>
> That ought to be a group parameter: try hitting "G p" on the group
> itself. You're looking for "nnmbox-mbox-file".
That gives me a buffer with timestamp information.
> It's possible I'm confused about this and it's actually a server
> setting, in which case go into the *Server* buffer and hit "S" on the
> server in question.
... gives me a buffer with '(nnmbox: "")' in it
I don't even have a file called "*spam*" which could be relevant, and I
searched my whole home directory with find for it. There are mails in
that group, just no place where they are stored. What kind of magic is
that?
--
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us. Finally, this fear has become reasonable.
next prev parent reply other threads:[~2015-05-07 23:14 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 19:03 lee
2015-04-28 20:03 ` Andreas Schwab
2015-04-29 19:32 ` lee
2015-04-29 20:10 ` Andreas Schwab
2015-04-29 20:37 ` this group and gnu.emacs.gnus (was: Re: storing messages into an mbox file) Emanuel Berg
2015-04-29 23:02 ` storing messages into an mbox file lee
2015-04-30 0:40 ` Eric Abrahamsen
2015-05-04 5:50 ` lee
2015-05-04 6:01 ` Adam Sjøgren
2015-05-07 23:11 ` lee
2015-05-08 9:22 ` Adam Sjøgren
2015-05-09 14:49 ` lee
2015-05-09 15:16 ` Adam Sjøgren
2015-05-10 12:39 ` Eric S Fraga
2015-05-12 8:06 ` Steinar Bang
2015-05-12 9:04 ` Eric S Fraga
2015-05-13 20:07 ` lee
2015-05-13 21:48 ` Adam Sjøgren
2015-05-17 8:46 ` lee
2015-05-13 23:17 ` Dan Christensen
2015-05-14 6:13 ` Steinar Bang
2015-05-17 9:02 ` lee
2015-05-14 6:10 ` Steinar Bang
2015-05-17 9:06 ` lee
2015-05-17 19:42 ` Steinar Bang
2015-05-17 20:45 ` Peter Münster
2015-05-14 9:19 ` e.fraga
2015-05-17 9:40 ` lee
2015-05-17 13:04 ` Eric S Fraga
2015-05-04 6:07 ` Eric Abrahamsen
2015-05-07 23:14 ` lee [this message]
2015-04-30 9:47 ` Andreas Schwab
2015-05-04 5:45 ` lee
2015-05-07 23:53 ` Dan Christensen
2015-05-08 22:10 ` lee
2015-05-18 2:25 ` Nikolaus Rath
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=87lhh0j7yz.fsf@heimdali.yagibdah.de \
--to=lee@yagibdah.de \
--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).