Re: Backend-specific nnmail-spool-file?

[Lloyd Zusman <ljz@asfast.com>]

dsg@mitre.org (David S. Goldberg) writes:

> I haven't tried this (I'm not sure I understand why you'd want to have
> a separate nnml instance (I assume you mean server?) for each file,
> but does something like this work?
> 
> (setq nnmail-spool-file nil)
> (setq nnml-get-new-mail t)
> (setq gnus-secondary-select-methods '((nnml "a" 
> 					     (nnml-directory "/path/to/a")
> 					     (nnmail-spool-file "a.spool"))
> 				      (nnml "b"
> 					     (nnml-directory "/path/to/b")
> 					     (nnmail-spool-file "b.spool"))))

When I said "instance", I meant what you call "server"; i.e., I'm calling
each secondary select method an "instance".

The reason I asked my question to begin with is that I believe that
the `nnmail-spool-file' cannot be used as you have specified here.  I
believe that its setting within the secondary select methods is
ignored ... it doesn't seem to be one of those special variables such
as `nnml-directory' which can have instance-specific (or, if you
prefer, "server-specific") settings.


-- 
 Lloyd Zusman
 ljz@asfast.com