From owner-freebsd-chat  Fri Jul 17 16:31:27 1998
Return-Path: <owner-freebsd-chat@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA15226
          for freebsd-chat-outgoing; Fri, 17 Jul 1998 16:31:27 -0700 (PDT)
          (envelope-from owner-freebsd-chat@FreeBSD.ORG)
Received: (from jmb@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA15220;
          Fri, 17 Jul 1998 16:31:23 -0700 (PDT)
          (envelope-from jmb)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199807172331.QAA15220@hub.freebsd.org>
Subject: Majordomo [was Re: And it's back]
In-Reply-To: <19980717225920.A1388@stade.co.uk> from Adrian Wontroba at "Jul 17, 98 10:59:20 pm"
To: aw1@stade.co.uk
Date: Fri, 17 Jul 1998 16:31:23 -0700 (PDT)
Cc: chat@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-chat@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Adrian Wontroba wrote:
> On Fri, Jul 17, 1998 at 02:09:33PM -0700, Sean Eric Fagan wrote:
> <re being removed from mailing lists>
> > Is this a majordomo problem, or a freebsd-load-related problem?  Any one have
> > any ideas?
> 
> In my opinion, both.
> 
> I used to look after a system using Majordomo on a relatively small
> FreeBSD system (P120, 16MB). Majordomo can somewhat process happy - and
> if it runs in to the process limit while attempting to claim a lock
> file evil things happen to the alias list. I ruined several list by
> mailing 32 separate subscription approvals to Majordomo from my dialup
> machine. When I connected they they arrived in quick succession on the
> server, and the machine and majordomo went nuts, with sendmail and perl
> processes everywhere. When the dust settled I discovered that the alias
> file was empty. After restoring from a backup and perusing log files for

	wow! please be careful here.  i read "aliases files" and 
	nearly filled my shorts!  i dont see how /etc/aliases 
	could have been affected....majordomo doesnt have root.

	so your list file (or subscribers file) got toasted.
	hmm....  

	which version of majordomo?

	are you grouping addresses, say 10 per outbound email, or 
	are you sending 1 message per address and creating a sendmail
	process for each?

	we run in daemon mode.  1 message per 10 addresses (generally).
	addresses sorted by domain (not MX) but we use relays to 
	handle outbound mail sorted by domain.

jmb

> later subscriptions, I circumvented the problem by setting sendmail to
> queued delivery only, with a queue run every 5 minutes. Not ideal, but
> the machine carries a light mail load. It is arguable that I should have
> tuned it better.
> 
> A majordomo list I subscribe to recently lost all its subscribers, I
> assume due to a similar event.
> 
> -- 
> Adrian Wontroba, Stade Computers Limited.       phone:  (+44) 121 681 6677
> Mail info@accu.org for information about the Association of C and C++ Users
> or see <http://www.accu.org/>
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-chat" in the body of the message
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-chat" in the body of the message