Multiple nnml hierarchies, with separate procmail spools

Multiple nnml hierarchies, with separate procmail spools

[Sten Drescher]

	I keep both my personal and my work email in nnml trees, but
on different systems.  I'd like to be able to mount my work nnml
hierarchy on my home system, and read the procmail spool for it, while
still having my personal nnml hierarchy separate and accessable.  Is
it possible to get rGnus 0.53 to do this?

-- 
+----------------------  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               |
+-----------------------------------------------------------------------+

Re: Multiple nnml hierarchies, with separate procmail spools

[Scott Blachowicz]

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> wrote:

> Gnus uses movemail to move mail from the spool directories.  movemail
> doesn't understand ange-ftp file names, so you'll have to use
> something else.  Which is a problem, because then you won't get file
> locking...

Sounds like a job for a nnimap backend?

Scott Blachowicz  Ph: 206/283-8802x240   Mathsoft (Data Analysis Products Div)
                                         1700 Westlake Ave N #500
scott@statsci.com                        Seattle, WA USA   98109
Scott.Blachowicz@seaslug.org

Re: Multiple nnml hierarchies, with separate procmail spools

[Lars Magne Ingebrigtsen]

Sten Drescher <sten.drescher@tivoli.com> writes:

> 	I keep both my personal and my work email in nnml trees, but
> on different systems.  I'd like to be able to mount my work nnml
> hierarchy on my home system, and read the procmail spool for it, while
> still having my personal nnml hierarchy separate and accessable.  Is
> it possible to get rGnus 0.53 to do this?

Gnus uses movemail to move mail from the spool directories.  movemail
doesn't understand ange-ftp file names, so you'll have to use
something else.  Which is a problem, because then you won't get file
locking...

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Ingebrigtsen

Re: Multiple nnml hierarchies, with separate procmail spools

[Sten Drescher]

>>>>> Lars Magne Ingebrigtsen writes:

LMI> Sten Drescher <sten.drescher@tivoli.com> writes:
>> I keep both my personal and my work email in nnml trees, but on
>> different systems.  I'd like to be able to mount my work nnml
>> hierarchy on my home system, and read the procmail spool for it,
>> while still having my personal nnml hierarchy separate and
>> accessable.  Is it possible to get rGnus 0.53 to do this?

LMI> Gnus uses movemail to move mail from the spool directories.
LMI> movemail doesn't understand ange-ftp file names, so you'll have
LMI> to use something else.  Which is a problem, because then you
LMI> won't get file locking...

	No ftp necessary, as I have everything NFS mounted.  The
problem is that I'll have 2 procmail spool directories, and 2 nnml
directories: ~/Mail for my home mail (both procmail and nnml), and
~/Tivoli/mail and ~/Tivoli/Mail for my office mail.  They need to
remain separate (the ISDN link isn't 100% reliable), but I'd like to
be able to read both in one Gnus session.  That I'd end up seeing the
office email twice isn't necessarily a bad thing (although being able
to have separate newsrc.eld files, in differing directories, for each
server would be a nice thing, IMNSHO (; ), but the nnml trees
themselves do need to reside in different directories.

-- 
+----------------------  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               |
+-----------------------------------------------------------------------+

Re: Multiple nnml hierarchies, with separate procmail spools

[Sten Drescher]

>>>>> Lars Magne Ingebrigtsen writes:

LMI> Sten Drescher <sten.drescher@tivoli.com> writes:
>> No ftp necessary, as I have everything NFS mounted.  The problem is
>> that I'll have 2 procmail spool directories, and 2 nnml
>> directories: ~/Mail for my home mail (both procmail and nnml), and
>> ~/Tivoli/mail and ~/Tivoli/Mail for my office mail.  They need to
>> remain separate (the ISDN link isn't 100% reliable), but I'd like
>> to be able to read both in one Gnus session.

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?

	More advanced.  I understand what your to be suggestion is for
everything from all the directories in the nnmail-procmail-directory
list would go into the (single) nnml-directory.  What I need is for
mail from nnmail-procmail-directory-1 (~/Mail) needs to go into
nnml-directory-1 (~/Mail), and mail from nnmail-procmail-directory-2
(~/Tivoli/mail) needs to go into nnml-directory-2 (~/Tivoli/Mail).

-- 
+----------------------  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               |
+-----------------------------------------------------------------------+

Re: Multiple nnml hierarchies, with separate procmail spools

[Kai Grossjohann]

>>>>> 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.

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

Am I wrong?
kai
-- 
I wonder why nobody don't like me,
or is it de fact dat I'm ugly? -- Harry Belafonte

Re: Multiple nnml hierarchies, with separate procmail spools

[Sudish Joseph]

Sten Drescher <sten.drescher@tivoli.com> writes:
> 	More advanced.  I understand what your to be suggestion is for
> everything from all the directories in the nnmail-procmail-directory
> list would go into the (single) nnml-directory.  What I need is for
> mail from nnmail-procmail-directory-1 (~/Mail) needs to go into
> nnml-directory-1 (~/Mail), and mail from nnmail-procmail-directory-2
> (~/Tivoli/mail) needs to go into nnml-directory-2 (~/Tivoli/Mail).

I've suggested this before: it'd be cool if we allowed per-group new
mail sources.  In this case, you'd associate a different spool file
with each of the above groups.

-Sudish

Re: Multiple nnml hierarchies, with separate procmail spools

[David Moore]

Sten Drescher <sten.drescher@tivoli.com> writes:
> >>>>> Lars Magne Ingebrigtsen writes:
> LMI> Sten Drescher <sten.drescher@tivoli.com> 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?
> 
> 	More advanced.  I understand what your to be suggestion is for
> everything from all the directories in the nnmail-procmail-directory
> list would go into the (single) nnml-directory.  What I need is for
> mail from nnmail-procmail-directory-1 (~/Mail) needs to go into
> nnml-directory-1 (~/Mail), and mail from nnmail-procmail-directory-2
> (~/Tivoli/mail) needs to go into nnml-directory-2 (~/Tivoli/Mail).


	Hmm, could you overbind nnmail-procmail-directory in the
secondary select method?  Mayhaps it'd need to be defvoo'd rather than
defvar'd.

	Something like this rather untested code.

(setq
 gnus-secondary-select-methods
 '((nnml "email-1"
    (nnml-directory "~/Mail")
    (nnmail-procmail-directory "~/Mail"))
   (nnml "email-2"
    (nnml-directory "~/Tivoli/Mail")
    (nnmail-procmail-directory "~/Tivoli/Mail")))
 )

-- 
David Moore <dmoore@ucsd.edu>       | Computer Systems Lab      __o
UCSD Dept. Computer Science - 0114  | Work: (619) 534-8604    _ \<,_
La Jolla, CA 92093-0114             | Fax:  (619) 534-1445   (_)/ (_)
<URL:http://oj.egbt.org/dmoore/>    | Solo Furnace Creek 508 -- 1996!

Re: Multiple nnml hierarchies, with separate procmail spools

[Sten Drescher]

>>>>> 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               |
+-----------------------------------------------------------------------+

Re: Multiple nnml hierarchies, with separate procmail spools

[Hrvoje Niksic]

Sudish Joseph (sudish@mindspring.com) wrote:
> I've suggested this before: it'd be cool if we allowed per-group new
> mail sources.  In this case, you'd associate a different spool file
> with each of the above groups.

Yes, it would be fun -- I've always wanted to reach some groups
through procmail, and some from the main spool, etc.  Thus you could
combine procmail and Gnus mail splitting.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
The end of the world is coming...  SAVE YOUR BUFFERS!

Re: Multiple nnml hierarchies, with separate procmail spools

[Lars Magne Ingebrigtsen]

David Moore <dmoore@UCSD.EDU> writes:

> (setq
>  gnus-secondary-select-methods
>  '((nnml "email-1"
>     (nnml-directory "~/Mail")
>     (nnmail-procmail-directory "~/Mail"))
>    (nnml "email-2"
>     (nnml-directory "~/Tivoli/Mail")
>     (nnmail-procmail-directory "~/Tivoli/Mail")))
>  )

Yes, this should work, and if it doesn't, it's a bug.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Ingebrigtsen

Re: Multiple nnml hierarchies, with separate procmail spools

[Lars Magne Ingebrigtsen]

Sten Drescher <sten.drescher@tivoli.com> writes:

> 	No ftp necessary, as I have everything NFS mounted.  The
> problem is that I'll have 2 procmail spool directories, and 2 nnml
> directories: ~/Mail for my home mail (both procmail and nnml), and
> ~/Tivoli/mail and ~/Tivoli/Mail for my office mail.  They need to
> remain separate (the ISDN link isn't 100% reliable), but I'd like to
> be able to read both in one Gnus session. 

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

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@ifi.uio.no * Lars Ingebrigtsen

Re: Multiple nnml hierarchies, with separate procmail spools

[Sten Drescher]

>>>>> Lars Magne Ingebrigtsen writes:

LMI> David Moore <dmoore@UCSD.EDU> writes:
>> (setq gnus-secondary-select-methods '((nnml "email-1"
>> (nnml-directory "~/Mail") (nnmail-procmail-directory "~/Mail"))
>> (nnml "email-2" (nnml-directory "~/Tivoli/Mail")
>> (nnmail-procmail-directory "~/Tivoli/Mail"))) )

LMI> Yes, this should work, and if it doesn't, it's a bug.

	Then it's a bug.  It _almost_ works, but it ignored the active
file in the nnmail-directory ~/Tivoli/Mail, and started reusing
article numbers.  Example: The high article number in
~/Tivoli/Mail/mail/grendel is 2576, and it put a new mail down as
article 10.

-- 
+----------------------  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               |
+-----------------------------------------------------------------------+

Re: Multiple nnml hierarchies, with separate procmail spools

[Sten Drescher]

>>>>> Sten Drescher writes:

>>>>> Lars Magne Ingebrigtsen writes:
LMI> David Moore <dmoore@UCSD.EDU> writes:
>>> (setq gnus-secondary-select-methods '((nnml "email-1"
>>> (nnml-directory "~/Mail") (nnmail-procmail-directory "~/Mail"))
>>> (nnml "email-2" (nnml-directory "~/Tivoli/Mail")
>>> (nnmail-procmail-directory "~/Tivoli/Mail"))) )

LMI> Yes, this should work, and if it doesn't, it's a bug.

SD> 	Then it's a bug.  It _almost_ works, but it ignored the active
SD> file in the nnmail-directory ~/Tivoli/Mail, and started reusing
SD> article numbers.  Example: The high article number in
SD> ~/Tivoli/Mail/mail/grendel is 2576, and it put a new mail down as
SD> article 10.

	And the solution was another variable in the list:
(nnml-active-file "~/Mail/active") or (nnml-active-file
"~/Tivoli/Mail/active").  Mow the only thing I'm left wanting is using
the .newsrc.eld files from both ~ and ~/Tivoli. (;

-- 
+----------------------  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               |
+-----------------------------------------------------------------------+