Re: Multiple nnml hierarchies, with separate procmail spools

[Sten Drescher <sten.drescher@tivoli.com>]

>>>>> Kai Grossjohann writes:

>>>>> Sten Drescher writes:
LMI> Ah.  So you basically want to have `nnmail-procmail-directory' be
LMI> a list of directories?  Or do you need something more advanced
LMI> than that?

Sten> More advanced.

KG> IMHO you can do the `more advanced' part with group names.  If,
KG> say, your Tivoli groups are all named t.foo, the problem wouldn't
KG> arise.

KG> Am I wrong?

	Unfortunately, yes.  First, the nnml trees aren't, and can't
be, in the same directory, so the active files need to be discrete.
If I symlinked the tivoli.* and support.* trees and procmail spool
files into my home directories, the discrete active files would
potentially result in articles being overwritten (Gnus-office looks in
it's active file, sees that the high article number in it's active
file for support.mail is 3456, and proceeds to write articles
3457-3498.  Then Gnus-home looks at it's active file, sees that the
high article number is 3432, and writes 3433-3459).  Second, yes,
there are name collisions: mail.misc, mail.daemon, list.ding, etc.

	The problem here seems to be that, while Gnus knows how to
deal with multiple backends, and multiple nntp backends, the nnml
backend isn't designed to handle multiple instances.  That's what I
need: dual nnml 'servers'.

-- 
+----------------------  Tivoli Customer Support  ----------------------+
|   Sten Drescher                     Tivoli Systems, Inc               |
|   email: sten.drescher@tivoli.com   9442 Capital of Texas Hwy North   |
|   phone: (512) 794-9070             Arboretum Plaza One, Suite 500    |
|   fax  : (512) 345-2784             Austin, Texas 78759               |
+-----------------------------------------------------------------------+