Re: Getting new mail with nnml

[steve@miranova.com (Steven L. Baur)]

>>>>> "Sean" == Sean Lynch <nc0273@netcom.com> writes:

    Sean> When I'm in the middle of a September 0.12 session, if I
    Sean> receive new mail, and I type "2g" to get my new mail (all my
    Sean> mail groups are at level 2 or below), it all ends up in an
    Sean> mbox in my home directory rather than being put into the
    Sean> appropriate nnml groups.  However, if I respool articles
    Sean> from other groups, they get split up properly.

    Sean> Anyone have any insight on this one?

If this is what I think it is, it's not sgnus specific, the problem is
also with Gnus 5.0 too.

The code paths taken during 1) Gnus startup, 2) a batch fetch new mail
and 3) fetch new mail for specific group are all different.

First off, I use procmail splitting where each nnml: folder gets fed
by a file named ~/spool/nnml-folder-name.spool.

A current problem with splitting mail exists if you have nnml folders
with names including "."s, and gnus-use-long-file-name is t.  You can
make some of the bad behavior go away by eliminating the (nasty)
routine in nnmail which converts strings with dots in them to strings
with slashes in them (paths 1 & 3 work, 2 does not).  

Another problem which manifests itself similarly is Gnus will bogusly
match a shorter nnml folder name to a spool file (in case 2 above) but
get it correct for cases 1 & 3.  Eg.  I have a nnml folder named
gnus-list which is intended to have messages inserted *manually only*
to it.  I have another nnml folder dgnus-list which is intended to be
filled by mail split by procmail from ~/spool/dgnus-list.spool.  When
I do M-2 g all of the dgnus-list.spool gets put into nnml:gnus-list.

Therefore, for my configuration, case 2 (M-2 g) is badly broken, and
I've stopped using it.

-- 
steve@miranova.com baur