Date: Sat, 21 Dec 1996 15:32:32 -0800 (PST) From: "Jonathan M. Bresler" <jmb> To: garycorc@mail.idt.net Cc: hackers@freebsd.org Subject: Re: Posting to multiple lists Message-ID: <199612212332.PAA07849@freefall.freebsd.org> In-Reply-To: <32BC6919.9EA@mail.idt.net> from "Gary Corcoran" at Dec 21, 96 05:47:53 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Gary Corcoran wrote: > > Jordan K. Hubbard wrote: > > > > > I fully second your reply. However, if it is really possible to do > > > what the poster says (configure majordomo not to send duplicate > > > emails for different mail lists) that is something that would be > > > useful anyways. > > > > I'm not sure how it could, unless it always just chose the first > > mailing list as the "target" and then somehow registered this fact > > so that a reject would occur for any other mailing lists the user > > tried to post it to. > > > > I don't know if it's _practical_ to do this, but sure, send it to > the first mailing list a recipient is on. Then, when traversing > through the next mail list, if a particular recipient has already > been "tagged", don't send another copy of the email. > This *would* be a useful feature, both for the poster of the mail > (who isn't sure which list should get the mail, or who thinks it > may legitimately cover several lists), and obviously for the > subscribers, who won't get the emailboxes clogged with duplicates... > [sorry, I don't know Perl, which I believe majordomo is written in?] 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. 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) jmb -- Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG FreeBSD--4.4BSD Unix for PC clones, source included. http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612212332.PAA07849>