Re: [Mailman-Users] Serialize?

2002-08-30 Thread Norbert Bollow

G. Armour Van Horn [EMAIL PROTECTED] wrote:

 If you're running a number of servers it does get easier, and I suspect that
 there are quite a few users here who are in that situation. One system for
 Mailman is plenty for my needs, particularly since Mailman has that machine
 all to itself, so other upgrades can't interfere with it. I can't justify
 another system as a sandbox for 2.1, and wouldn't have time to figure out
 reasonable tests to run on it anyway.

There's no problem whatsoever with running several (a few) separate
Mailman installs on the same machine.  It's just when you haven dozens
of hundreds of installs that it become necessary to change a few
things.

Greetings, Norbert.

-- 
Founder  Steering Committee member of http://gnu.org/projects/dotgnu/
Norbert Bollow, Weidlistr.18, CH-8624 Gruet (near Zurich, Switzerland)
Tel +41 1 972 20 59Fax +41 1 972 20 69   http://norbert.ch
List hosting with GNU Mailman on your own domain name http://cisto.com

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/



Re: [Mailman-Users] Serialize?

2002-08-30 Thread Raquel Rice

On Fri, 30 Aug 2002 10:28:02 +0200
Norbert Bollow [EMAIL PROTECTED] wrote:

 G. Armour Van Horn [EMAIL PROTECTED] wrote:
 
  If you're running a number of servers it does get easier, and I
  suspect that there are quite a few users here who are in that
  situation. One system for Mailman is plenty for my needs,
  particularly since Mailman has that machine all to itself, so
  other upgrades can't interfere with it. I can't justify another
  system as a sandbox for 2.1, and wouldn't have time to figure
  out reasonable tests to run on it anyway.
 
 There's no problem whatsoever with running several (a few)
 separate Mailman installs on the same machine.  It's just when you
 haven dozens of hundreds of installs that it become necessary to
 change a few things.
 
 Greetings, Norbert.

This is something I was thinking of doing.  I only run about 20
lists, but I don't want them messed with right now.  I would like to
do a seperate install of 2.1, testing it and them putting a couple
of new lists onto it to see how it works.  Is there anything special
I need to be aware of in doing that?

-- 
Raquel

When you are joyous, look deep into your heart and you shall find it
is only that which has given you sorrow that is giving you joy. When
you are sorrowful look again in your heart, and you shall see that
in truth you are weeping for that which has been your delight.
  --Kahlil Gibran


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/



Re: [Mailman-Users] Serialize?

2002-08-29 Thread J C Lawrence

On Wed, 28 Aug 2002 15:08:00 -0700 
G Armour Van Horn [EMAIL PROTECTED] wrote:

 But not until you say so!

As with all software upgrades you get to decide when something is ready
for deployment on your systems, nobody else.  The criteria you use for
those decisions is private to you and has no necessary relations to the
criteria or statements of anyone else.

  Translation: Make up your own mind, make your own choices, support
  your arguments with your own reasoning.

There are several production systems that I'm runnign straight out of
that source base's CVS repository.  You can't get much more raw than
that.  Similarly there are several other production systems that are two
or three whole major versions back in the past purely becuase I don't
trust the current versions.

Inform youself of the layout and values of the the field and then pick.
This is OSS.  There are no magic This product is now golden bullets.

-- 
J C Lawrence
-(*)Satan, oscillate my metallic sonatas. 
[EMAIL PROTECTED]   He lived as a devil, eh?  
http://www.kanga.nu/~claw/  Evil is a name of a foeman, as I live.





--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/



Re: [Mailman-Users] Serialize?

2002-08-29 Thread Ashley M. Kirchner


I did it again, reply instead of reply-all.  Sorry claw...  - AMK4

--

J C Lawrence wrote:

 0) That is what the password reminders are for: They remind people that
 they are subscribed, and under what address etc.

Therein lies the problem.  These people aren't using passwords to begin
with.  Subscribers don't get reminders of what they are subscribed as either.
That would've been the easy way out, unfortunately, I don't have that choice.

--
W | I haven't lost my mind; it's backed up on tape somewhere.
  +
  Ashley M. Kirchner mailto:[EMAIL PROTECTED]   .   303.442.6410 x130
  IT Director / SysAdmin / WebSmith . 800.441.3873 x130
  Photo Craft Laboratories, Inc.. 3550 Arapahoe Ave. #6
  http://www.pcraft.com . .  ..   Boulder, CO 80303, U.S.A.


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/



Re: [Mailman-Users] Serialize?

2002-08-29 Thread Dan Mick

G. Armour Van Horn wrote:

 At this point, Barry clearly says (on the website) it isn't ready, but he
 has legal constraints to worry about, or at least a reputation to protect,
 if everyone runs the beta and then problems develop. You only risk one
 machine (and its users) at a time.

Surely not legal, but yes.

 Mailman is a very small part of my business, and a little hobby interest on
 the side. This means I need it to be stable, I don't have time to move to
 2.1 and have to move back. I'd rather move to 2.1 and leave it for a while,
 not run 2.1b3, 2.1b4, maybe 2.1b5, and then 2.1.0.

It should be noted that it's *very* trivial to upgrade.  I do this probably
four times a week when Barry's busy:

mmstop (a wrapper for /etc/init.d/mailman stop)
cvs -q update -dAP
resolve any conflicts from my local hacks (usually 30 seconds)
./doconfig (wrapper for ./configure with flags)
make install
mmstart (see above)

total time about 5 minutes; total number of problems I've seen from
interim software: probably 10 over the lifetime of 2.0.x, most having
to do with broken email messages that get evolving parsing code's panties
all bunched.

It's been my experience that interim CVS versions of Mailman are *very*
stable.  As usual: your mileage *will* vary.  But Mailman is not very fragile,
in my experience.

And if you want to, keeping track of your last-stable date or
revision tag, and rolling back with CVS, is pretty easy too.
If you add in back up the critical config.pck's it's even easier to
roll back.  (Not that I've ever had to.)


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/



Re: [Mailman-Users] Serialize?

2002-08-28 Thread Ashley M. Kirchner

G. Armour Van Horn wrote:

 Those groups of multiple recipients are large - several hundred at a time. To make
 the change you suggest means multiplying your bandwidth and server requirements by
 the average size of your active lists. My most active list has 240 digest
 subscribers and 300 regular subscribers. Both appear to be handled in a single
 command. Done one at a time there would be a huge increase in CPU load and
 bandwidth, and folks at the end of a list would get their messages later than those
 at the head of the list.

Ya, I realize all of this, however I have clients who would like, are requesting,
and generally want this type of mechanism built in.  The main reason is because many of
the subscribers no longer remember what e-mail address they used to subscribe, and
consequently don't know what to use to UNsubscribe.  Having Mailman serialize its
messages will provide a simple way for them to unsubscribe.

--
W | I haven't lost my mind; it's backed up on tape somewhere.
  +
  Ashley M. Kirchner mailto:[EMAIL PROTECTED]   .   303.442.6410 x130
  IT Director / SysAdmin / WebSmith . 800.441.3873 x130
  Photo Craft Laboratories, Inc.. 3550 Arapahoe Ave. #6
  http://www.pcraft.com . .  ..   Boulder, CO 80303, U.S.A.




--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/