Subject: Majordomo 1.94.1 released!
Date: Tue, 24 Dec 1996 13:44:25 +0100
From: Chan Wilson <firstname.lastname@example.org>
because a .1
is always better
than no dot one at all.
Available as a patch to Majordomo-1.94 or as a complete tarball.
See the included NEWS file for a description of what has changed
between 1.94 and 1.94.1. Many thanks to Jason Tibbitts, Dave Barr,
and Dave Wolfe for doing the bulk of the work for this patch!
Majordomo can be found at the following locations:
(Silicon Valley, USA)
(Silicon Valley, USA)
The following mailing lists will be of interest to those using or
Discussions on using Majordomo
Development discussion about Majordomo
Announcements of new Majordomo releases
To subscribe to any of these lists, send the appropriate "subscribe"
command to "Majordomo@greatcircle.com"
Report bugs, suggestions, and kudos to the Majordomo Workers list;
Changes from 1.94 to 1.94.1
The installation process has been improved. The Makefile is now simpler
and makes use of an external "install" program (included as install.sh).
The permissions for all installed files can be easily set in the Makefile.
In addition, the default permission for $homedir has been made slightly
more lenient, to avoid problems with the mailer not being able to execute
The installation checker, config-test, has been improved with more checks
and better detection of situations where it's being run improperly. It
will automatically warn of new configuration variables that should be set
The digest and archive2.pl programs have been moved from the Tools
directory to the main directory since they are usually run by the wrapper
and must be there anyway.
Changes visible to the Majordomo owner:
The default $sendmail_command now includes the -oee option to force
sendmail to mail as many errors as possible instead of exiting with nonzero
exit code at unpredictable times.
Code is provided in majordomo.cf to prevent majordomo, resend and the
tools from running when the system load average exceeds a configurable
limit. This code is disabled by default. It requires the standard
The default umask for all majordomo-created files is now set in
majordomo.cf, and defaults to 007.
The variable $shlock'retries has been renamed to $shlock'waittime to better
match its actual meaning as the maximum time (in seconds) that the locking
system will wait for a lock.
A new variable, $majordomo_dont_reply, has been added. Majordomo will not
respond to any piece of mail sent from an address matching this regular
expression. It defaults to '(mailer-daemon|uucp|listserv|majordomo)\@'.
The locking system has been improved and should have much greater
resistance to looping and otherwise uncontrolled behavior in the face of
improperly set permissions and nonexistent files.
Many bugs relating to an improperly set $bounce_mailer have been fixed.
This should end the abort messages complaining about null mailers not being
Changes visible to list owners:
If a list adds its own Reply-To: header, any Reply-To: header in
incoming messages will be removed.
Changes visible to end users:
Requests for confirmation have been made more detailed, and the backslash
syntax for splitting long lines has been explained in those messages.
Confirmation messages sent by the "subscribe" command have been
improved. They contain more reasons why a confirmation request
may not be received.
Many more checks for illegal addresses have been included. Users are
informed when they supply only their name or otherwise supply a nonsense
The response to the who command includes a subscriber count.
[ current Majordomo Release Coordinator ]
Chan Wilson --- email@example.com --- +4138-433-760
Silicon Graphics, SA. Cortaillod, Switzerland.
"Network Analyst" && Irix Guru && Gravitational Engineer
"Shallow ideas can be assimilated, ideas that require people
to reorganize their picture of the world provoke hostility."