Re: Backend-specific nnmail-spool-file?

[Lloyd Zusman <ljz@asfast.com>]

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:

> Lloyd Zusman <ljz@asfast.com> writes:
> 
>   > I would like to do my email splitting outside of Gnus and Emacs.
>   > This would result in a group of mail spool files that I would need
>   > to check from within Gnus.  I want to use the `nnml' backend, and
>   > I want to create a separate backend instance for each of these
>   > spool files.
> 
> Do you mean groups rather than backends?
> 
> If so, nnmail-use-procmail is your friend.  Also see
> nnmail-procmail-directory and nnmail-procmail-suffix.  In a nutshell:
> 
> If nnmail-use-procmail is t and nnmail-procmail-directory is
> "~/spool/" and nnmail-procmail-suffix is ".in", then Gnus puts all
> mails from the file "~/spool/foo.bar.in" into the group
> "nnml:foo.bar".  (It does not make a difference whether procmail wrote
> these files, or Mailagent, or slocal, or something else, they just
> need to be mbox format files.)

Well, this could work for me, but my preferred way of doing this would
be to have one spool file called `/var/spool/mail/oneuser', another
called `/var/spool/mail/anotheruser', etc. ... i.e., no special
suffixes.  Note that I would run Gnus as user `root', which is easy
for me to do from my personal Linux machine at home.

Any chance for this?

-- 
 Lloyd Zusman
 ljz@asfast.com