🚀 go-pugleaf

In article <vafhgdnos4h.fsf@ls6.cs.uni-dortmund.de> 
	Kai Grossjohann <grossjohann@ls6.cs.uni-dortmund.de> writes:

	....

> If you use Gnus, the nnmh backend might be for you, as the other
> poster said.

> However, I'd like to warn you that you're asking for trouble by having
> procmail deliver mail directly into folders.  What happens if procmail
> and you try to both write into the same folder at the same time?
> You're going to lose mail, sooner or later.  At least with Gnus, you
> are.  I'm unsure whether exmh and procmail lock the folders in a way
> that they both understand.

	MH folders are directories.  There should be any problem of 
	collision -- procmail knows how to do locking -- but no one
	should be opening existing mh files for writing.  MH programs
	all seek for the next available number and create a new file
	named by that number.

> If you intend to use Gnus for your mail reading, I advise you to tell
> procmail to write its mail into spool files and to tell Gnus to get
> the mail from the spool files into the folders.  You'll need to set
> nnmail-use-procmail and nnmail-procmail-directory and
> nnmail-procmail-suffix.  Let's say nnmail-use-procmail is t and
> nnmail-procmail-directory is ~/proc.spool and nnmail-procmail-suffix
> is ".in", then Gnus will read ~/proc.spool/foo.bar.in for incoming
> mail for the foo.bar folder.

	I can believe this for the nnmail backend -- but
	I can't see why it would be necessary for the nnmh
	method.
-- 
Jim Dennis,                                info@mail.starshine.org
Proprietor,                          consulting@mail.starshine.org
Starshine Technical Services              http://www.starshine.org

        PGP  1024/2ABF03B1 Jim Dennis <jim@starshine.org>
        Key fingerprint =  2524E3FEF0922A84  A27BDEDB38EBB95A