Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ssSslang <sssslang@163.com>
Cc: ding@gnus.org
Subject: Re: Strange mail file
Date: Tue, 17 Apr 2007 15:16:50 +0900	[thread overview]
Message-ID: <b4m4pnfttil.fsf@jpl.org> (raw)
In-Reply-To: <87fy6ztx2f.fsf@gmail.com>

>>>>> In <87fy6ztx2f.fsf@gmail.com> ssSslang wrote:

> I change to Gnus CVS yesterday when I use v5.11 before. I found it makes
> some strange file in my mail folder. let me describe in detail:

> I use fetchmail and procmail to drop new mail in ~/Mail/.incoming, then
> I use the following setting to make Gnus read the new message:

> (setq
>    mail-sources '((file :path "~/Mail/.incoming" :plugged t))
>    gnus-select-method '(nnml "mail" (nnml-directory "~/Mail")
>                              (nnml-active-file "~/Mail/active")))

> and then they go though mail spliter. But when using new Gnus from cvs,
> there are some file appeared in the ~/Mail folder like Incoming3416cdp
> and so on. I saw that when I hit "g" in group buffer and the
> ~/Mail/.incoming file contains new mail, the Incomingxxxx file appeared,
> which has the same text as ~/Mail/.incoming. Is it a new feature? How to
> disable it? Thanks.

(info "(gnus)Mail Source Customization")
,----
| `mail-source-delete-incoming'
|      If non-`nil', delete incoming files after handling them.  If `t',
|      delete the files immediately, if `nil', never delete any files.
|      If a positive number, delete files older than number of days (This
|      will only happen, when receiving new mail).  You may also set
|      `mail-source-delete-incoming' to `nil' and call
|      `mail-source-delete-old-incoming' from a hook or interactively.
`----

(info "(gnus)Gnus Development")
,----
|    Some variable defaults differ between alpha Gnusae and released
| Gnusae.  In particular, `mail-source-delete-incoming' defaults to `nil'
| in alpha Gnusae and `t' in released Gnusae.  This is to prevent lossage
| of mail if an alpha release hiccups while handling the mail.
`----

So, you can set it to t at your own risk.

Regards,



      reply	other threads:[~2007-04-17  6:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17  5:00 ssSslang
2007-04-17  6:16 ` Katsumi Yamaoka [this message]

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=b4m4pnfttil.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.org \
    --cc=sssslang@163.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).