From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: storing messages into an mbox file
Date: Sat, 09 May 2015 17:16:37 +0200 [thread overview]
Message-ID: <87618193xm.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87egmpq00q.fsf@heimdali.yagibdah.de>
lee writes:
> They appear to be in single files named "Incoming*" and not in an mbox
> file.
The ~/Mail/Incoming* files are copies of email that Gnus has imported -
these are generated by development versions of Gnus as a safety feature
in case email is lost due to a new bug:
,----[ C-h v mail-source-delete-incoming RET ]
| mail-source-delete-incoming is a variable defined in `mail-source.el'.
| Its value is 10
|
| Documentation:
| If non-nil, delete incoming files after handling.
| If t, delete immediately, if nil, never delete. If a positive number, delete
| files older than number of days.
|
| Removing of old files happens in `mail-source-callback', i.e. no
| old incoming files will be deleted unless you receive new mail.
| You may also set this variable to nil and call
| `mail-source-delete-old-incoming' interactively.
`----
(I don't think they are related to your task at hand.)
> Sometimes gnus is really awful --- if I can't do this without creating
> unremovable groups and great fuss, perhaps it's time to use a different
> MUA.
It is always good to reevaluate your options and choose the tool that
suits you the best.
> As much as I like gnus, it always has quirks like this which make life
> extremely difficult, and I really don't have time for this.
Then you certainly shouldn't spend it.
> You can't even have more than one account without messing everything
> up badly, and all sorts of deleted stuff remains forever :(
Multiple accounts work fine for me; I use spam.el to train my
spam-filter of choice (crm114) [note however that spam.el isn't trivial
to set up, as it is _very_ generalized], but email *is* a very personal
thing, and everybody wants it handled in a different way.
Best of luck in finding something that works for you!
Best regards,
Adam
--
"Where there's a will, there's a won't" Adam Sjøgren
asjo@koldfront.dk
next prev parent reply other threads:[~2015-05-09 15:16 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 [this message]
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
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=87618193xm.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--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).