Re: Insulin pumpers headers

On 02 May 2006, - Patty entered spamcop and left 
news:[email protected]:

> On Tue, 2 May 2006 07:25:31 -0700, Mike Easter wrote:
> 
>> 
>> The necessary reconfiguration would have to be done by Michael, and
>> following that reconfiguration, some adjustment to the pages of
>> guidelines which were written in 1999.  It is possible that the
>> majordomo version is of an old vintage.  It is possible that the old
>> majordomo is not so configurable.  Majordomo's 'evolution' is described
>> at the GreatCircle website -- in which the different versions may be
>> incompatible with different versions of the Perl script and similar
>> tediums.

That is correct, however I don't know how far back you have to go before 
that isn't an option. I installed Majordomo 1.94.5 on a FreeBSD server, the 
config file checks for Perl version 4.019 (or greater), however this port 
is configured specifically for my server, and the port available at 
freebsd.org claims to require Perl 5.8.8, and the bizsystems server is 
running UNIX (not FreeBSD). Even that doesn't really tell us much, however 
the headers that Mike supplied imply that "majordomo" on the bizsystems 
network is using Sendmail 8.11.4, which is significantly old (but isn't 
necessarily an upgrade factor). I still adhere to the "if it ain't broke 
don't fix it" mentality, but if +confirm isn't an option upgrading is, even 
though that could require some other upgrade as well.

>> 
>> Currently the headers do not parse to name the server, for whatever
>> reason and significance that is at this point.
>> 

I think, if I have time, I may run a test for that. I do have 3 mail-list 
managers available, MailMan, Majordomo and Dada Mail. I may try out all 
three. I don't currently need them, but I should be familiar with them so 
that they could be available.

>> The admin thinks it would be very difficult to reconfigure the majordomo
>> or the majordomo plus the guidelines for the remote administration
>> process.  Ric doesn't think so.

majordomo.cf

# Set the default subscribe policy for new lists here.
# If not defined, defaults to "open", but in today's increasingly
# imbecile Internet, "open+confirm" or "auto+confirm" is a wiser
# choice for publicly available Majordomo servers.
#
$config'default_subscribe_policy = "open+confirm";

#

I expect that each list has it's own subscribe policy. Still, whats harder: 
typing a couple words and writing a couple lines of instructions, or 
spending time dealing with abuse reports?

> 
> I would like to know, however, where Ric got his information about the
> majordomo guidelines.  I've searched the web and got some limited
> information about majordomo systems, but nothing that appeared to be as
> concise as what Ric had.  I would love to read it, granted I may not
> understand a lot of it, but I still would like to be able to more
> familiarize myself with the process.   
> 

You really need to install it and read the man files and the doc files. I 
don't expect you to be able to do this, but you can install on Windows 
Texpad (textpad.com)(or a UNIX-compatable text reader for your OS) and 
either WinZip or WinRar (I think you already have one of those, or 
something compatable with tar files), and then you can attempt to read 
through the .pl doc and/or man files in the majordomo archive (WinRar's 
View command works well on text files), but that's a bit like sorting 
through trash that's been through a shredder.

The info I posted is from documentation I had, the Majordomo and MajorCool 
sites, and the config_parse.pl file.

-- 
| Ric
|