From majordomo-docs-owner Sat Aug 17 10:13:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id KAA23899 for majordomo-docs-outgoing; Sat, 17 Aug 1996 10:03:24 -0700 (PDT) Received: from poynting.phy.ulaval.ca (poynting.phy.ulaval.ca [132.203.76.90]) by miles.greatcircle.com (8.7.4/Miles-951221-1) with SMTP id KAA23892; Sat, 17 Aug 1996 10:03:14 -0700 (PDT) Received: from localhost by poynting.phy.ulaval.ca with smtp id m0urntb-0001euC (Debian /\oo/\ Smail3.1.29.1 #29.37); Sat, 17 Aug 96 12:06 EDT Date: Sat, 17 Aug 1996 12:06:43 -0400 (EDT) From: Jean-Bernard ADDOR To: Majordomo-Users@greatcircle.com, Majordomo-Docs@greatcircle.com Subject: .passwd file readble by everybody Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-docs-owner@GreatCircle.COM Precedence: bulk In the README file in section 2.1 it said to put .passwd file in mode 664 ie everybody can read the password ! Is that normal ? I'm setting up lists for the first time Jean-Bernard PS: reply to me too, I'm not in the list From majordomo-docs-owner Sat Aug 17 11:58:13 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id LAA28219 for majordomo-docs-outgoing; Sat, 17 Aug 1996 11:53:36 -0700 (PDT) Received: from weaver-gw.netapp.com (weaver-gw.netapp.com [198.95.224.2]) by miles.greatcircle.com (8.7.4/Miles-951221-1) with ESMTP id LAA28192; Sat, 17 Aug 1996 11:53:05 -0700 (PDT) Received: from netapp.com ([192.9.200.1]) by weaver.netapp.com with SMTP id <15859-6935>; Sat, 17 Aug 1996 11:54:13 +0100 Received: from forestlawn.netapp.com by netapp.com (4.1/SMI-4.1) id AA18224; Sat, 17 Aug 96 11:52:50 PDT Received: by forestlawn.netapp.com (SMI-8.6/SMI-SVR4) id LAA07603; Sat, 17 Aug 1996 11:49:45 -0700 Date: Sat, 17 Aug 1996 11:49:45 -0700 From: lancej@netapp.com (Lance) Message-Id: <199608171849.LAA07603@forestlawn.netapp.com> To: Majordomo-Users@GreatCircle.COM, Majordomo-Docs@GreatCircle.COM, jbaddor@poynting.phy.ulaval.ca Subject: Re: .passwd file readble by everybody X-Sun-Charset: US-ASCII Sender: majordomo-docs-owner@GreatCircle.COM Precedence: bulk I have mine set up with 640 and everything appears to be working fine. Lance >From majordomo-users-owner@GreatCircle.COM Sat Aug 17 10:18:06 1996 >To: Majordomo-Users@greatcircle.com, Majordomo-Docs@greatcircle.com >Subject: .passwd file readble by everybody >Mime-Version: 1.0 >Sender: majordomo-users-owner@GreatCircle.COM >Precedence: bulk >X-Lines: 12 > > >In the README file in section 2.1 it said to put .passwd file in mode 664 >ie everybody can read the password ! > >Is that normal ? > >I'm setting up lists for the first time > > Jean-Bernard > >PS: reply to me too, I'm not in the list > > From majordomo-docs-owner Fri Aug 30 12:59:35 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-960417-1) id MAA12374 for majordomo-docs-outgoing; Fri, 30 Aug 1996 12:46:24 -0700 (PDT) Received: from stargate.concorde.com ([206.137.224.2]) by miles.greatcircle.com (8.7.4/Miles-951221-1) with SMTP id MAA12332 for ; Fri, 30 Aug 1996 12:46:08 -0700 (PDT) Received: (from smap@localhost) by stargate.concorde.com (8.6.8.1/8.6.6) id PAA14813 for ; Fri, 30 Aug 1996 15:41:39 -0400 Received: from milan.concorde.com(198.242.54.229) by stargate.concorde.com via smap (V1.3) id sma014811; Fri Aug 30 15:41:24 1996 Received: from localhost (kevink@localhost) by milan.concorde.com (8.7.5/8.7.3) with SMTP id PAA08595 for ; Fri, 30 Aug 1996 15:47:44 -0400 (EDT) Date: Fri, 30 Aug 1996 15:47:44 -0400 (EDT) From: Kevin Kelleher X-Sender: kevink@milan To: majordomo-docs@greatcircle.com Subject: digest man pages Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: majordomo-docs-owner@GreatCircle.COM Precedence: bulk NAME digest - receive a file for a digest, or create and mail a digest SYNOPSIS digest -r|m -C -l majordomo-listname recipient digest -r|m [-c configuration-file] AVAILABILITY Provided with distributions of Majordomo. DESCRIPTION The digest script is a perl script which automates the management of digests of electronic mail. It can be run in a standalone configuration or as part of Majordomo. It requires two directories: a work directory and an archive directory. Incoming e-mail messages are stored in the work directory. Digests are created and stored in the archive directory. When invoked with the -r option, the digest script reads the incoming e-mail message from standard input and stores the file in the work directory. These files are given numerical names starting with "001" and are numbered in order of arrival. Each time that a file is added to the directory, digest checks the total size of the files in bytes. If the sum exceeds the digest's size limit (a configured value), a digest is created and mailed. When invoked with the -m option, the digest script will create and mail a digest, if there are any numbered files in the work directory. It should be noted that digest needs a configuration file to define all of its operating parameters. If no such file is specified, digest will use the $HOME/.digestrc file. OPTIONS -r Receive an email message via standard input and place the file into the working directory. If the total size (in bytes) of files in the working directory exceeds the digest's size limit, create and mail a digest. -m If there are any numbered files in the working directory, create and mail a digest. Store the digest in the archive directory. -c configuration-file Use the parameters defined in configuration-file. -C Use Majordomo configuration values: read the configuration file for Majordomo (majordomo.cf) and for the Majordomo list specified by the -l option. If both -C and -c options are specified (not recommended) the -C option will be used. -l majordomo-listname This option is ignored if used without the -C option. Specifies the Majordomo e-mail list. OPERANDS recipient Email recipient of the digest. This operand is ignored if used without the -C option. It specifies one of the system mail aliases created for the Majordomo list named in the -l option. MAJORDOMO DIGEST CONFIGURATION When used as a part of Majordomo, digest takes these parameters from /etc/majordomo.cf: $listdir - the location of the mailing lists $digest_work_dir - parent directory for the digests' work directories $filedir - parent directory for archive directories $filedir_suffix - an optional identifier (may be the null string) Incoming messages for $listname-digest will be held in $digest_work_dir/$listname-digest. Digests will be stored in $filedir/$listname-digest$filedir_suffix. The list's configuration file will be $listdir/$listname-digest.config. Examples of these values are given in EXAMPLES, below. The list's configuration file contains several digest parameters that are not yet implemented and/or should NOT be changed from their defaults (blank): digest_archive, digest_rm_footer, digest_rm_fronter, digest_work_dir. The parameters which specifically deal with digest creation and maintenance are: digest_name - the title of the digest digest_volume - volume number digest_issue - issue number maxlength - maximum number of characters in a digest message_fronter - text prepended to the digest message_footer - text appended to the digest The last three parameters are also used in the configuration of an ordinary (non-digest) Majordomo list. Each digest begins with the a line containing the digest_name, current date, digest_volume and digest_issue. The digest script will update the issue number in the configuration file. A blank line follows, and then the text from the message_fronter, if any. The message fronter may contain the _SUBJECT_ token, which will be replaced by the subject lines from the messages in the digest. The text in the message_footer, if any, will be appended to the digest. To embed a blank line in the message_footer or message_fronter, put a '-' as the first and ONLY character on the line. To preserve whitespace at the beginning of a line, put a '-' on the line before the whitespace to be preserved. To put a literal '-' at the beginning of a line, double it. Both message_footer and message_fronter may also use the tokens $LIST, $SENDER, and $VERSION, which will be expanded to, respectively: the name of the current list, the sender as taken from the from line, and the current version of majordomo. Examples of the aliases usually used with the digest are given in EXAMPLES, below. The list owner can prompt Majordomo to build a digest by sending the command "mkdigest digest-name [digest-password]" to majordomo either via email or from cron. The cron command has the format: echo mkdigest digest-name [digest-password] | mail majordomo@domain.com STANDALONE DIGEST CONFIGURATION The Majordomo distribution comes with a "digest" subdirectory. The sample configuration file is called firewalls-digest.cf. A file in this format must be used if digest is invoked in standalone configuration. If no configuration file is specified when digest is invoked, it looks for a file named $HOME/.digestrc that must be in the same format as the example file. The configuration file defines the email addresses of the sender and recipient of the digest. It also locates the work and archive directories, the digest's size limit, and the names of the files that contain the digest's volume, number, header and footer. The easiest way to configure a standalone digest is to copy the five files (firewalls-digest.*) and edit them to taste. Incoming mail is piped to digest with the -r option. This can be done from some mail-reading programs, through the command line, or via mail aliases similar to those found in EXAMPLES, below. EXAMPLES 1. Example values from /etc/majordomo.cf: $listdir = "/usr/local/mail/lists"; $digest_work_dir "/usr/local/mail/digest"; $filedir = "$listdir"; $filedir_suffix ".archive": If our digest's name is banjo-digest, the work directory will be /usr/local/mail/digest/banjo-digest; the archive directory will be /usr/local/mail/lists/banjo-digest.archive. Note that these are names of directories, not files. 2. Typical aliases for Majordomo digests: Usually a Majordomo digest is associated to a regular (non-digest) list. The digest's name is the regular listname plus "-digest". The list "banjo" will have the digest "banjo-digest". banjo-digest-approval: kevink banjo-digest-outgoing: :include:/usr/local/lists/banjo-digest owner-banjo-digest-outgoing: kevink banjo-digest-digestify: "|/usr/majordomo/wrapper digest -r -C -l banjo-digest banjo-digest-outgoing" banjo-digest: banjo Note that mail to "banjo-digest" is routed to the regular list. The "digestify" alias must be added to the regular list's outgoing alias: banjo-outgoing: :include:/usr/local/lists/banjo,banjo-digestify EXIT STATUS The following exit values are returned: 0 Successful completion. >0 An error occurred. FILES /etc/aliases /etc/majordomo.cf SEE ALSO majordomo(8) AUTHOR The digest script was written by Brent Chapman . It is available with distributions of Majordomo via anonymous FTP from FTP.GreatCircle.COM, in the directory pub/majordomo. This man page was written by Kevin Kelleher .