Re: Problem with "group writable"

[Dan Liston <sonny @ sonny . org>]

Roderick Padilla wrote:
> 
> At 01:18 PM 4/25/00 -0500, Dan Liston wrote:
> 
> >  My preference is to have "lists", "digests", and "archive" all
> >on the same level of the tree.
> 
> After thinking more about it .. I liked that idea .. I have moved the 3
> dirs to the same level.
> 
> >   If $listdir = $homedir/lists, then I use
> >$digest_work_dir = $homedir/digests, and $filedir = $homedir/archive with
> >$filedir_suffix = "".
> 
> when I send 3 messages to test@host these 2 are created automatically, so I
> suppose it is working.
> 
> /object_research/system/majordomo-1.94.5/archive/test.archive.0004 (with 3
> messages on it)

The reason test.archive.0004 is created is because of the way you have your
outgoing alias written.
...-outgoing: "|/object_research/system/majordomo-1.94.4/wrapper archive2.pl 
	-a -m -f /object_research/system/majordomo-1.94.5/archive/test.archive"
This tells the archiver that the base filename (not directory) is
test.archive which the -m adds a suffix of .0004 to.  If you send an 
index test
command to majordomo, does it find the test.archive.0004 file?

The majordomo.cf in 1.94.4 defined how the $filedir and $filedir_suffix
variables works better than the "shortened" definition in the sample.cf
included with 1.94.5 does.  Examples changed to fit my system

# Majordomo will look for "get" and "index" files related to $list in
# the directory "$filedir/$list$filedir_suffix", so set $filedir and
# $filedir_suffix appropriately.  For instance, to look in
# /var/majordomo/archive/$list, use:  # $list is directory, not a file
#   $filedir = "/var/majordomo/archive";
#   $filedir_suffix = "";               # empty string
# or to look in $listdir/$list.archive, use: # $list.archive directory
#   $filedir = "$listdir";
#   $filedir_suffix = ".archive";
I use the first example.

> /object_research/system/majordomo-1.94.5/digests/test-digest/001
> /object_research/system/majordomo-1.94.5/digests/test-digest/002
> /object_research/system/majordomo-1.94.5/digests/test-digest/003

These look correct.  At least, my system does this also.
> 
> >If you adopt this approach, keep in mind that you need subdirectories under
> >each of digests and archive with listname-digest, and potentially one under
> >archive called listname.  This is inline with sample.cf for digests, but
> >varies from sample.cf for archive.  This means your aliases would look
> >different from the examples when doing archiving.  My test-archive alias
> >looks like this;
> >test-archiver:  "|/var/majordomo/wrapper archive2.pl
> >         -f /var/majordomo/archive/test/test -M -a"
> 
> Actually I have my cba-employers-outgoing like this ....
> 
> ::include:/object_research/system/majordomo-1.94.5/lists/cba-employers,
> "|/object_research/system/majordomo-1.94.5/wrapper digest -r -C -l
> cba-employers-digest
> cba-employers-digest-outgoing","|/object_research/system/majordomo-1.94.4/wr
> apper archive2.pl -a -m -f
> /object_research/system/majordomo-1.94.5/archive/cba-employers.archive"

Here again, to prevent line length problems for sendmail, and to keep
aliases
easier to read for me, I create two additional aliases and use them in my
$ougoing alias.

test-archiver, and test-digestify.  I also use a creation date in my alias
for the outgoing deliveries.

test:	"|/var/majordomo/wrapper resend -l test test-000425,nobody"
test-000425: :include:/var/majordomo/lists/test,test-archiver,test-digestify
test-archiver:  "|/var/majordomo/wrapper archive2.pl
	-f /var/majordomo/archive/test/test -M -a"
#note - this creates test.200004 in /var/majordomo/archive/test/
test-digestify: "|/var/majordomo/wrapper digest
	-r -C -l test-digest test-digest-000425"
#note - this creates ### files in /var/majordomo/digests/test-digest/
test-digest: test
test-digest-000425: :include:/var/majordomo/lists/test-digest

Owner, request, and approval addresses ignored for the moment.

> 
> >You did know you could split an alias across multiple lines by indenting
> >the additional lines right?
> >test is a the base name of the archive, and will be suffixed with .YYYYMM
> >because of the -M.  test.200004 will live in /var/majordomo/archive/test.
> >If you decide to use digestified lists, digest needs a listname-digest
> >directory under archive to store the files it creates. (v01.n001)
> 
> I have a question ... not sure how this is suppose to work ..  if the list
> is digested, why my message is distributed immediately?  I would like to
> digest and sent the digested message(s) around 10PM ... cron?

All messages sent to test are distributed immediately to subscribers of
test.
Since you still have 001, 002, 003 in the $digest_work_dir, the digest has
not been sent immediately.  When it IS distributed, it is sent to the email
addresses in test-digest, not the email addresses in test.

Digests can be sent "automatically" based on settings in test-digest.config.
Age:   digest_maxdays =
Size:  maxlength =
Lines: digest_maxlines =
If any of these values is "exceeded" a digest is created and sent.  If you
want a daily digest via cron, set these values high enough not to interfere
with cron.  Any time a digest IS created, your ### files are removed from
/object_research/system/majordomo-1.94.5/digests/test-digest/

> 
> How about  Mhonarc for archives?

Never used it.  Lots of people like it though.  I am not making anything
related to my lists available via web browsing, and I am quite happy with 
archive2.pl so I have not felt the need to experiment with it.  

> 
> Roderick Padilla
> rpadilla@gsu.edu