Re: Mapping of group names to filenames with nnml

[Andrew Nesbit <alnesbit@optushome.com.au>]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Andrew Nesbit <alnesbit@optushome.com.au> writes:
> 
> > I take it from experience that periods in group names cause nnml to
> > store these groups as a directory hierarchy.
> 
> Also see the variables gnus-use-long-file-name and
> nnmail-use-long-file-names.

Yep, that explains a lot for me.

> 
> > If I have a procmail-generated spool file named, say,
> > `debian.user.spool', combined with a mail-source specifier like
> >
> >         (directory :path "~/Mail/Spool/"
> >                    :suffix ".spool")
> >
> > then does that mean that the group will be called `debian.user' and
> > that nnml will create a directory hierarchy, as described above, to
> > store its messages?
> 
> This means that messages from the file ~/Mail/Spool/foo.bar.spool
> will be written to the group nnml:foo.bar.  So there is a direct
> correlation between the file name and the group name -- independent
> of what is the directory name used for the nnml:foo.bar group!

Okay, I see, now.

I do have one extra question now, though.  If a previously-nonexistent
spool file is created by Procmail whilst Gnus is running, then how do
I get the group associated with that spool file automatically created?
At present, the only way I know is to either quit and restart, or to
manually create the group with 'G m'.  Is there any automatic way?

Thankyou for the help :)

Andrew.