Gnus development mailing list
 help / color / mirror / Atom feed
From: Sai-Lai Lo <S.Lo@orl.co.uk>
Subject: temporary files left behind by nnfolder
Date: 07 Dec 1998 12:36:52 +0000	[thread overview]
Message-ID: <3or9ucqgbf.fsf@neem.cam-orl.co.uk> (raw)

Not long ago I began to try out pgnus. One thing I noticed since the
changeover is that in my nnfolder-directory, there are lots of Incoming*
files. It seems that these files are created every time pgnus fetch mail
from incoming mail folders in nnmail-procmail-directory. I guess these are
temporary files which normally would be deleted. But for some reason they are
left behind.

My setup is:

(setq nnfolder-directory "~/private/Mail")

(setq nnmail-use-procmail t)
(setq nnmail-spool-file (list (getenv "MAIL")))

(setq nnmail-use-long-file-names t)
(setq nnmail-procmail-directory "/home/sll/private/Mail/incoming/")
(setq gnus-secondary-select-methods '((nnfolder "")))
(setq nnmail-procmail-suffix "")
(setq gnus-auto-expirable-newsgroups
    "axp-kernel-list.mail\\|axplinux.mail\\|corba.mail\\|egcs.mail\\|egcs-bugs.mail\\|hurricane.mail\\|linux-atm.mail\\|wmaker.mail\\|corba-dev.mail")
(setq nnmail-expiry-wait 7)
(setq nnmail-keep-list-article t)
(remove-hook 'gnus-mark-article-hook
             'gnus-summary-mark-read-and-unread-as-read)
(add-hook 'gnus-mark-article-hook 'gnus-summary-mark-unread-as-read)


I hope I've provided sufficent information for the bug(?) to be reproduced.

I had a look at nnmail-get-new-mail which seems to delete the temporary
files before the function returns and it is the same code as
the released version of gnus. 

Regards,
Sai-Lai Lo


             reply	other threads:[~1998-12-07 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-07 12:36 Sai-Lai Lo [this message]
1998-12-07 12:47 ` Lee Willis
1998-12-07 17:19   ` Christian Kurz

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=3or9ucqgbf.fsf@neem.cam-orl.co.uk \
    --to=s.lo@orl.co.uk \
    /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).