Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!orion.oac.uci.edu!uci-ics!jromine
From: jromine@ics.uci.edu (John Romine)
Newsgroups: comp.mail.mh
Subject: Re: bboards auto-archiving
Keywords: help
Message-ID: <25F58E4F.18857@paris.ics.uci.edu>
Date: 7 Mar 90 22:42:23 GMT
References: <100265@linus.UUCP>
Reply-To: jromine@ics.uci.edu (John Romine)
Organization: UC Irvine Department of ICS
Lines: 23

lamour@smiley.mitre.org (Michael Lamoureux) writes:
>I have a question about bboard auto-archiving.
>I can't seem to find this stuff documented anywhere.

See the MH System Administrator's Guide, part of the MH documentation set.

>Is there any way to control the archive age of
>bboards other than spacing the cron jobs farther apart?
>
>#define   BB_ASAV	0x0001	/*   save in archives/ directory */
>#define   BB_AREM	0x0002	/*   remove without saving */

The flags you're interested in are BB_ASAV and BB_AREM.  These
correspond to the last field in the ~bboards/BBoards file.  If the
bb_flags is 0, the bboard isn't touched.  If it's 01, "old" messages
are saved in ~bboards/archive/<foo>.mbox, if it's 02, they're just
deleted.

See the program bbexp.c in mh-6.6/support/bboards.  There are a couple
constants defined for how long messages last until they're considered
"old".
--
John Romine