lamour@smiley.uucp (Michael Lamoureux) (03/07/90)
I have a question about bboard auto-archiving. I can't seem to
find this stuff documented anywhere. I found the following in the
bboards.h file, but it's not very explicit. I think I can figure out
the save & remove part, but what are the other flags for, and what else
can I set with these. Is there any way to control the archive age of
bboards other than spacing the cron jobs farther apart?
unsigned int bb_flags; /* various flags */
#define BB_NULL 0x0000
#define BB_ARCH 0x0007 /* archive policy */
#define BB_ASAV 0x0001 /* save in archives/ directory */
#define BB_AREM 0x0002 /* remove without saving */
#define BB_INVIS 0x0010 /* invisible to bbc */
#define BB_REMOTE 0x0020 /* remote to bbc */
#define BB_SEEN 0x0040 /* seen by bbc */
#define BBITS "\020\01ARCHIVE\02REMOVE\05INVIS\06REMOTE\07SEEN"
I'd rather not get 70 replies on how to use bbl. The entire purpose
of this question is so I don't have to use bbl, because, frankly, I don't have
the time to read all of the bboards we have here.
thanks,
+=====================================================+
| Michael Lamoureux (lamour%smiley@gateway.mitre.org) |
| The MITRE Corporation, McLean VA (703) 883-5370 |
+=====================================================+
The directory /var/spool/uucppublic is also traditionally left wide
open. UUCP is such a security problem that this directory is a minor
issue, anyway.
-- Sun Security Administrator's Guide
test,
Michaeljromine@ics.uci.edu (John Romine) (03/08/90)
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