From owner-freebsd-questions Mon Sep 16 12:26:54 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA00753 for questions-outgoing; Mon, 16 Sep 1996 12:26:54 -0700 (PDT) Received: from glacier.cold.org (glacier.sunrem.com [206.81.134.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA00746 for ; Mon, 16 Sep 1996 12:26:52 -0700 (PDT) Received: (from brandon@localhost) by glacier.cold.org (8.7.5/8.7.3) id NAA07712; Mon, 16 Sep 1996 13:28:32 -0600 (MDT) Date: Mon, 16 Sep 1996 13:28:32 -0600 (MDT) From: Brandon Gillespie To: freebsd-questions@freebsd.org Subject: sendmail, majordomo and list servers, optimizing? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Out of curiosity, does sendmail do any sort of delivery optimizing. For instance, if you use :include: on a list of addresses does it sort that list, attempting to get all addresses in a certain domain in order, so it can pass all of them off to a local system at once, or at the very least so it can deliver them over an already established route on or about the same time. On a similar note, currently majordomo takes a secondary role in delivery, acting more as a filter than anything. I was thinking on a heavilly hit list server (i.e. more than ~100 addresses per list and more than 1 post every few seconds) it may be smarter to have a list server automatically group the messages, holding off delivery a few seconds (depending upon the load and ratio of addresses/hits) and hooking back to call sendmail. Is there any software that does this? Some of the lists I manage have upwards of 4,000 email addresses (fortunately they are not heavilly hit). I've hacked a program which sorts them by domain, but I think other optimizations could be made. Is there a newer version of Majordomo which does this? And lastly, is there an option available to 'multi-plex' sendmail / majordomo? In order to get it to deliver more than one message at a time (such as delivering the first 10-n messages at a time, handling multiple sockets and forking appropriately). This would slam a machine, but if its a dedicated machine and you capped the max it would work on at a time I dont see a problem with that--if the end result was faster delivery. -Brandon Gillespie