From owner-freebsd-hackers Sat Dec 21 16:13:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA09388 for hackers-outgoing; Sat, 21 Dec 1996 16:13:04 -0800 (PST) Received: from po2.glue.umd.edu (root@po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA09382 for ; Sat, 21 Dec 1996 16:13:01 -0800 (PST) Received: from packet.eng.umd.edu (packet.eng.umd.edu [129.2.98.184]) by po2.glue.umd.edu (8.8.3/8.7.3) with ESMTP id TAA15303; Sat, 21 Dec 1996 19:12:58 -0500 (EST) Received: from localhost (chuckr@localhost) by packet.eng.umd.edu (8.8.3/8.7.3) with SMTP id TAA24260; Sat, 21 Dec 1996 19:12:58 -0500 (EST) X-Authentication-Warning: packet.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 21 Dec 1996 19:12:57 -0500 (EST) From: Chuck Robey X-Sender: chuckr@packet.eng.umd.edu To: "Jonathan M. Bresler" cc: garycorc@mail.idt.net, hackers@FreeBSD.ORG Subject: Re: Posting to multiple lists In-Reply-To: <199612212332.PAA07849@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 21 Dec 1996, Jonathan M. Bresler wrote: > sendmail expands the mail aliases, such as freebsd-hackers and > freebsd-questions, not majordomo. by the time the "message" > reaches majordomo (actually the resend perl program of majordomo) > it is already 2 or more separate, distinct messages. John, would it be possible to ask sendmail to reject any message (with some kindly worded reminder) that is addressed to multiple majordomo targets? Simply reject it out of hand, so if multiple copies get to freebsd.org (with loaded cc lists) majordomo wouldn't have to handle it? If something like that had existed, I would have been stopped from replying to the multiple post (which I admit, I didn't actually even notice the cc list). > > one might do this by having resend note the Message-id: header > in a random access data structure stored on disk. entries > would be purged after 24 hours, for example. or one could > configure a Message-id: server process that each invokation > of resend could query. the resultwould determine whether or > not the message was killed. > > the correct solution is not a technical one but rather a > human one. trim the cc: list. the original sender may well > be in the dark as to which list to send his question to. > the responders should be better informed and trim the cc: > list accordingly. (this is my opinion, for what it is worth) ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------