IP Mailing Lists (was Re: Major/listproc (fwd))

Date: Tue, 10 Dec 1996 14:13:50 -0400
From: Gerard MacNeil <macneil@ns.ca>
To: CSuite Development <csuite-dev@chebucto.ns.ca>
cc: Neale Partington <neale@gpfn.sk.ca>,

next message in archive
no next message in thread
previous message in archive
Index of Subjects


On Mon, 9 Dec 1996, Neale Partington wrote:
> ---------- Forwarded message ----------
> Date: Sun, 8 Dec 1996 19:16:53 -0600
> From: Daryle Niedermayer <daryle@gpfn.sk.ca>
> 
> On Sun, 8 Dec 1996, Gord Fisch wrote:
> 
> > registration a public thing. The funny part is that csuite _insists_ that
> > you have a at least a private list. So you can't just comment out the html
> > in the application form, you must go through the scripts and remove checks
> > for existance of mailing list names, and so on.

The mailing list that goes with an IP is to ensure that the Lynx 'c' -
Comment - command functions correctly, sending mail to the group that is
responsible for the content.  Originally, we were maintaining the lists by
hand (through zmailer lists) but when we got to >100 IPs, it ended up
being a real maintenance problem.  So we switched to majordomo lists to
enable the IP to maintain the recipient list themselves.  Usually, these
are low volume lists so the system resource consumption is not excessive. 

Where it shows up is on the IP "Install", which calls 'rcsinit' which
calls 'headerinit'. 'headerinit' pastes the RCS line and a <link
rev="made" ...> on the top of every HTML file installed.  Eliminating the
mailing list will mean you also have to do something about the install. 


Gerard MacNeil, P. Eng.                 Volunteer Technical Liaison
Webmaster, NMD Manufacturing            Chebucto Community Net
macneil@nmd.purdyswharf.com             macneil@chebucto.ns.ca



next message in archive
no next message in thread
previous message in archive
Index of Subjects