This patch cleans up some small problems in the 1.94.1 NEWLIST file.
(Comments, anyone?) The only halfway-important changes are:
- Nuking the sentence that says you must move archive2.pl into the
top-level directory.
- Changing the filename sample.aliases to majordomo.aliases.
(I don't have diff -u.)
--
Jerry Peek, jpeek@jpeek.com, http://www.jpeek.com/~jpeek/
---------------------------------------------------------------------------
*** NEWLIST Wed Sep 4 09:01:32 1996
--- NEWLIST.new Sat Jan 18 18:00:12 1997
***************
*** 19,25 ****
the initial introductory info for the list in it.
3) Create the appropriate entries for the list in your Sendmail
! aliases file (/etc/aliases or a seperate majordomo.aliases file.)
Each list requires several aliases. For an example list called
'test', these aliases are required:
--- 19,25 ----
the initial introductory info for the list in it.
3) Create the appropriate entries for the list in your Sendmail
! aliases file (/etc/aliases or a separate majordomo.aliases file.)
Each list requires several aliases. For an example list called
'test', these aliases are required:
***************
*** 99,107 ****
Hopefully in a future release of majordomo archive2.pl will be
integrated into majordomo so that the frequency of archive rollover
(daily, monthly, yearly) will be controllable via the config file
! mechanism. If you wish to use archive2 in the current release, you
! MUST move it from the Tools subdirectory into the top level majordomo
! directory.
***** NOTE: CONVERTING FROM A PREVIOUS MAJORDOMO VERSION *****
For those who are converting from an earlier version of
--- 99,105 ----
Hopefully in a future release of majordomo archive2.pl will be
integrated into majordomo so that the frequency of archive rollover
(daily, monthly, yearly) will be controllable via the config file
! mechanism.
***** NOTE: CONVERTING FROM A PREVIOUS MAJORDOMO VERSION *****
For those who are converting from an earlier version of
***************
*** 111,133 ****
values for resend will be incorrect.
! More examples of alias setups can be found in the file sample.aliases.
For sendmail users, don't forget to run 'newaliases' to rebuild the
alias database.
! 4) Optional, create an archive directory for the list, in the location
! specified by the $filedir and $filedir_suffix variables.
! 5) Optional, create a digest work (incoming) directory for the list,
! in the $digest_work_dir/<list-name>. you must create an archive
! directory for the digest list as well as a work directory.
6) Finally, make sure everything is owned by user majordomo, group
majordomo, and writable by both owner and group (i.e., mode 664 for
files and mode 775 for directories).
! 7) Now issue a 'config <listname> <listname.admin> command to
Majordomo. This will cause it to create a default configuration
file for the list, and send it back to you. Make any desired
changes, SUCH AS CHANGING THE DEFAULT PASSWORDS, as well as adding
--- 109,132 ----
values for resend will be incorrect.
! More examples of alias setups can be found in the file majordomo.aliases.
For sendmail users, don't forget to run 'newaliases' to rebuild the
alias database.
! 4) If the list will be archived, create an archive directory in the
! location specified by the $filedir and $filedir_suffix variables.
! 5) If the list has a digest, create a digest work (incoming) subdirectory
! under $digest_work_dir. Use the same name as the digest list (example:
! test-digest). You also must create an archive directory for the digest
! list as explained in step 4.
6) Finally, make sure everything is owned by user majordomo, group
majordomo, and writable by both owner and group (i.e., mode 664 for
files and mode 775 for directories).
! 7) Now issue a 'config <listname> <listname>.admin' command to
Majordomo. This will cause it to create a default configuration
file for the list, and send it back to you. Make any desired
changes, SUCH AS CHANGING THE DEFAULT PASSWORDS, as well as adding
|
|
