From list-managers-owner Thu Feb 1 00:08:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id AAA26347 for list-managers-outgoing; Thu, 1 Feb 1996 00:01:42 -0800 (PST) Received: from peg.apc.org (peg.apc.org [192.131.13.1]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id AAA26322 for ; Thu, 1 Feb 1996 00:01:31 -0800 (PST) Received: from guest1.peg.apc.org (t40.dialup.peg.apc.org [192.203.176.168]) by peg.apc.org (8.6.9/Revision: 1.10 ) with SMTP id SAA18238 for ; Thu, 1 Feb 1996 18:59:43 +1000 Date: Thu, 1 Feb 1996 18:59:43 +1000 Message-Id: <199602010859.SAA18238@peg.apc.org> X-Sender: janderson@peg.apc.org X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: list-managers@greatcircle.com From: janderson@peg.apc.org (Jeff Anderson) Subject: Re: Ghost members Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >If you're using restrict_post, he could be forging his From header, using a >member's address. If you're using moderation, I'll bet he knows or has >guessed one of the list passwords (there are 3, at least in 1.93). > >-- >Byron > No, there is nothing untoward about the posts, the person doing it was a business acquaintance who was away during the new year break, was unsubscribed at his request and sent a message to the list instead of me to inform me that he was back. I have tried it myself, if I subscribe and then unsubscribe one of my work accounts, after being unsubscribed, I can still send to the list. I have now tried it with four account using four different service providers. All of them, once unsubscribed can still send to the list. It would make it difficult if I had occasion to ban someone. They would no longer receive mail but would still be able to send. Hopefully, once they stopped receiving they would also stop sending. I am wondering if this is unique to my installation of majordomo or general. Jeff Anderson From list-managers-owner Thu Feb 1 07:03:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id GAA14434 for list-managers-outgoing; Thu, 1 Feb 1996 06:38:42 -0800 (PST) Received: from discovery.igc.net (discovery.igc.net [205.198.244.20]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id GAA14429 for ; Thu, 1 Feb 1996 06:38:38 -0800 (PST) Received: from igc.net.igc.net (runabout1-67.igc.net [205.198.245.67]) by discovery.igc.net (8.6.12/8.6.12) with SMTP id JAA02780 for ; Thu, 1 Feb 1996 09:37:38 -0500 Date: Thu, 1 Feb 1996 09:37:38 -0500 Message-Id: <199602011437.JAA02780@discovery.igc.net> X-Sender: cus@igc.net X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: List-Managers@GreatCircle.COM From: Brian Wolfsohn Subject: Cost of mailing List Setup/Admin Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I don't know if this is on topic for this list, but i haven't seen this discussed anywhere else. I've seen ads for virtual hosts, and home pages, but not the cost for setting up &/or administrating mailing lists. Ok... I'm interested in setting up a couple of private subscription mailing lists. They would be no charge items for the first year (approx). The lists would be for our clients, for the auction industry in general, and for auctioneers. So it would probably be 1 list to start, going to 2 or 3 total. membership would be light at first, but i see it growing into 3 digits on some of the lists within a year. I don't know about message traffic, but i would imaging it would remain light (10 messages a day) over the first 6 months. I have no desire to learn or get involved with Unix, but i could also do administration if it was laid out for me.. (me, that's a DOS expert, windows novice+, clipper programmer). Can anyone give me an idea of what is should cost to have someone set up and host and help me when i need it in running these lists ? I currently have your basic ppp connection, and we've obtained our domain name cus.com. I plan on setting up a virtual server by the end of April and moving to a "real" one as the cost becomes justified. Again, sorry if i'm off topic, i know this isn't an administration question, but if anybody has any clues as to where else to ask, or any answers, i'd be grateful. Regards, Brian L. Wolfsohn Fort Lauderdale, FL C-U-S Business Systems - Software for Auctioneers blw@cus.com From list-managers-owner Thu Feb 1 15:53:33 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id PAA06721 for list-managers-outgoing; Thu, 1 Feb 1996 15:51:51 -0800 (PST) Received: from maki.wwa.com (maki.wwa.com [198.49.174.21]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id PAA06716 for ; Thu, 1 Feb 1996 15:51:45 -0800 (PST) Received: from miso.wwa.com by maki.wwa.com with smtp (Smail3.1.29.1 #3) id m0ti8m1-000rY3C; Thu, 1 Feb 96 17:50 CST Received: by miso.wwa.com (Smail3.1.29.1 #2) id m0ti8lz-000YOSC; Thu, 1 Feb 96 17:50 CST Message-Id: From: dattier@wwa.com (David W. Tamkin) Subject: Re: X-Header: To: list-managers@greatcircle.com Date: Thu, 1 Feb 1996 17:50:38 -0600 (CST) In-Reply-To: from "Richard Tryzno Ellsberry" at Jan 31, 96 10:04:55 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Richard Ellsberry asked, | 1. Can one 'customize' any reasonable header by simply | appending 'X-' to it -- 'X-Copyright:', 'X-Hi-Mom:', | 'X-Communicated:', 'X-Post-Facto:', 'X-Cetera:' ? Yes. Even X-Tatic: and X-Kuze-Me:. RFC822 (I think) forbids any reserved header to have a name beginning with "X-". That in effect allows one to insert ad hoc headers (by giving them names starting with "X-") that will be safely ignored by compliant mail transports. From list-managers-owner Fri Feb 2 11:54:14 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id LAA13898 for list-managers-outgoing; Fri, 2 Feb 1996 11:34:52 -0800 (PST) Received: from mailgate.ericsson.se (mailgate.ericsson.se [130.100.2.2]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id LAA13893 for ; Fri, 2 Feb 1996 11:34:47 -0800 (PST) Received: from ervgwy.eritel.se (ervgwy.eritel.se [192.71.49.65]) by mailgate.ericsson.se (8.6.11/1.0) with SMTP id UAA24717; Fri, 2 Feb 1996 20:33:49 +0100 Received: by ervgwy.eritel.se (4.1/SMI-4.1) id AA15339; Fri, 2 Feb 96 20:33:28 +0100 Received: from nasse.eritel.se(193.234.208.1) by ervgwy.eritel.se via smap (V1.3) id sma015337; Fri Feb 2 20:33:25 1996 Received: from pappa.eritel.se by nasse (5.x/SMI-SVR4) id AA25963; Fri, 2 Feb 1996 20:33:44 +0100 Received: by pappa.eritel.se (5.x/SMI-SVR4) id AA22757; Fri, 2 Feb 1996 20:33:43 +0100 Date: Fri, 2 Feb 1996 20:33:43 +0100 (MET) From: Matz Engstrom X-Sender: matz@pappa To: jkg@epx.cis.umn.edu Cc: List-Managers@GreatCircle.COM Subject: Re: Document comparing mailing list software In-Reply-To: <001310e4b6f016339@epx.cis.umn.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Have a look at: ftp://ftp.uu.net/usenet/news.answers/mail/list-admin/software-faq.Z Matz Engstrom, Eritel AB Sweden On Tue, 30 Jan 1996 jkg@epx.cis.umn.edu wrote: > Does anyone have a document that compares various mailing > list packages? I saw one in the past comparing listserv, > procmail, and majordomo. From list-managers-owner Fri Feb 2 13:16:06 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id MAA16886 for list-managers-outgoing; Fri, 2 Feb 1996 12:48:27 -0800 (PST) Received: from digital.netvoyage.net (digital.netvoyage.net [205.162.154.10]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id KAA25378 for ; Thu, 1 Feb 1996 10:30:38 -0800 (PST) Received: from digital.netvoyage.net (digital.netvoyage.net [205.162.154.10]) by digital.netvoyage.net (8.6.11/8.6.9) with SMTP id KAA25320; Thu, 1 Feb 1996 10:29:34 -0800 Date: Thu, 1 Feb 1996 10:29:34 -0800 (PST) From: Brock Rozen To: Steve Portigal cc: list-managers@greatcircle.com Subject: Re: Problems with Prodigy In-Reply-To: <199602010711.AA09155@jive.rahul.net> Message-ID: X-URL: http://www.netvoyage.net/~brozen MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On Wed, 31 Jan 1996, Steve Portigal wrote: > I had a person from Prodigy tell me they couldn't unsub cuz the -request > address from my list has too many characters to fit into their > address window. God only knows how they managed to sub. > > Is this person just an idiot, or is Prodigy that crippled? My guess is that they sent the original message directly to majordomo or used a web form to subscribe (I've seen quite a few out there). If they used the latter, they should've been smart enough to use it to unsub (unless this particular form doesn't allow that). ------------------------------------------------------------------------- | Brock Rozen | brozen@netvoyage.net | http://www.netvoyage.net/~brozen | ------------------------------------------------------------------------- From list-managers-owner Fri Feb 2 13:21:57 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id MAA16770 for list-managers-outgoing; Fri, 2 Feb 1996 12:46:30 -0800 (PST) Received: from tango.rahul.net (tango.rahul.net [192.160.13.5]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id XAA23613 for ; Wed, 31 Jan 1996 23:12:17 -0800 (PST) Received: from bolero.rahul.net by tango.rahul.net with SMTP id AA22237 (5.67b8/IDA-1.5 for ); Wed, 31 Jan 1996 23:11:12 -0800 Received: from jive.rahul.net by bolero.rahul.net with SMTP id AA15812 (5.67b8/IDA-1.5); Wed, 31 Jan 1996 23:11:11 -0800 From: Steve Portigal Received: by jive.rahul.net (5.67b8/jive-a2i-1.0) id AA09155; Wed, 31 Jan 1996 23:11:07 -0800 Message-Id: <199602010711.AA09155@jive.rahul.net> Subject: Re: Problems with Prodigy To: brozen@netvoyage.net (Brock Rozen) Date: Wed, 31 Jan 1996 23:11:06 -0800 (PST) Cc: list-managers@greatcircle.com In-Reply-To: from "Brock Rozen" at Jan 31, 96 10:44:41 pm Organization: GVO - Interface Design Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I had a person from Prodigy tell me they couldn't unsub cuz the -request address from my list has too many characters to fit into their address window. God only knows how they managed to sub. Is this person just an idiot, or is Prodigy that crippled? Steve -- | steve portigal G V O | user interface dude | culturally aware interface design From list-managers-owner Sat Feb 3 12:08:39 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id MAA05332 for list-managers-outgoing; Sat, 3 Feb 1996 12:03:20 -0800 (PST) Received: from vent.pipex.net (vent.pipex.net [158.43.128.5]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id MAA05326 for ; Sat, 3 Feb 1996 12:03:15 -0800 (PST) Received: from tadpole.intertrader.com by vent.pipex.net (8.6.12/PIPEX simple 1.20) id UAA16770; Sat, 3 Feb 1996 20:02:19 GMT Received: by tadpole.intertrader.com (Smail3.1.29.1 #8) id m0tioDK-0004BfC; Sat, 3 Feb 96 20:05 GMT Message-Id: Date: Sat, 3 Feb 96 20:05 GMT From: Rachel Willmer To: list-managers@GreatCircle.com Subject: Is Hypermail or equivalent available for Linux/FreeBSD? Sender: list-managers-owner@GreatCircle.COM Precedence: bulk subject says it all... -- Intertrader Ltd - Internet Services for Business Internet Services: Web Design, Online Databases, Online Commerce, etc. Email rachel@intertrader.com or visit us at http://www.intertrader.com/ Mail autoresponders: info@intertrader.com, prices@intertrader.com From list-managers-owner Sun Feb 4 15:38:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id PAA11388 for list-managers-outgoing; Sun, 4 Feb 1996 15:38:06 -0800 (PST) Received: from moose.tiac.net (moose.tiac.net [199.0.65.7]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id PAA11383 for ; Sun, 4 Feb 1996 15:38:00 -0800 (PST) Received: from worldmachine.com (worldmachine.com [204.215.133.237]) by moose.tiac.net (8.6.9/8.6.6.Beta9) with ESMTP id SAA22576 for ; Sun, 4 Feb 1996 18:37:48 -0500 Received: (from eric@localhost) by worldmachine.com (8.6.11/8.6.9) id SAA11653 for list-managers@greatcircle.com; Sun, 4 Feb 1996 18:38:44 -0500 From: "Eric J. Hansen" Message-Id: <199602042338.SAA11653@worldmachine.com> Subject: Pattern matching for SPAM To: list-managers@greatcircle.com Date: Sun, 4 Feb 1996 18:38:43 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Folks, two of my lists have now been hit with the same free magazine SPAM message three times. For reference, two of the subject headers were: From: Sandee Loring Subject: Amazing FREE offer I found. From: Ellen Fox Subject: ===>> FREE 1 yr. USA Magazine Sub sent worldwide- up to $50.00 value!!! Given that the same message content seems to be getting forwarded around, what do you all think of some sort of fuzzy pattern matching for "known spams"? It's easy enough to change the subject heading of one of these messages, but changing the entire content is unlikely if the message is just getting forwarded. A possibly successful mechanism for filtering this crud would be to run a multiple pattern match on all incoming messages and bounce ones which have a high number of matches (i.e., run an egrep-like program on twenty or so unique or uncommon words that appear in the message). For you folks with high-volume lists, I know that the prospect of having to search/egrep through each incoming post is unrealistic, but it is still something to think about. I'm running SmartList, and my largest mailing list is about 260 members with average of 10 messages a day (digest only). Note that my suggestion here is based on the fact that I've received the *same* SPAM several times (from different senders, though). This mailing list (list-managers) could periodically post a list of patterns to filter known SPAM -- kind of like a virus detection program update. -Eric Level 42 Digest, Go West Digest, Incognito Digest -- Eric J. Hansen ...................... http://www.worldmachine.com/users/hansen SW Developer / Worldmachine Technologies ........ mailto:eric@worldmachine.com From list-managers-owner Sun Feb 4 16:23:39 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id QAA12554 for list-managers-outgoing; Sun, 4 Feb 1996 16:09:50 -0800 (PST) Received: from hera.cuci.nl (hera.cuci.nl [194.183.100.1]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id QAA12540 for ; Sun, 4 Feb 1996 16:09:40 -0800 (PST) Received: (from srb@localhost) by hera.cuci.nl (8.7.3/BuGless_1.02) id BAA22823 for list-managers@greatcircle.com; Mon, 5 Feb 1996 01:07:09 +0100 Message-Id: <199602050007.BAA22823@hera.cuci.nl> From: srb@cuci.nl (Stephen R. van den Berg) Date: Mon, 5 Feb 1996 01:07:09 +0100 In-Reply-To: "Eric J. Hansen"'s message as of 1996 Feb 4 Sun 18:38. <199602042338.SAA11653@worldmachine.com> To: list-managers@greatcircle.com Subject: Re: Pattern matching for SPAM Sender: list-managers-owner@GreatCircle.COM Precedence: bulk "Eric J. Hansen" wrote: >two of my lists have now been hit with the same free magazine SPAM message >three times. For reference, two of the subject headers were: Actually, the procmail and SmartList mailinglists (both maintained by me) have been hit by this spam about every two weeks since September. After the first two hits, I installed a very crude filter which does an ad hoc match for this exact spam. Has caught it every time since, even though the content changed a little over time as well. >getting forwarded. A possibly successful mechanism for filtering this crud >would be to run a multiple pattern match on all incoming messages and bounce >ones which have a high number of matches (i.e., run an egrep-like program on >twenty or so unique or uncommon words that appear in the message). As a matter of fact, I'm currently in the mail-spam collector market. In order to pick up a representative sample against which a generic spam filter can be tested. >Note that my suggestion here is based on the fact that I've received the >*same* SPAM several times (from different senders, though). This mailing >list (list-managers) could periodically post a list of patterns to filter >known SPAM -- kind of like a virus detection program update. That would never work for one-shot spams. -- Sincerely, srb@cuci.nl Stephen R. van den Berg (AKA BuGless). "And now for something *completely* different!" From list-managers-owner Sun Feb 4 18:08:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id SAA18907 for list-managers-outgoing; Sun, 4 Feb 1996 18:02:42 -0800 (PST) Received: from netcom12.netcom.com (netcom12.netcom.com [192.100.81.124]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id SAA18902 for ; Sun, 4 Feb 1996 18:02:38 -0800 (PST) Received: by netcom12.netcom.com (8.6.12/Netcom) id SAA10758; Sun, 4 Feb 1996 18:00:57 -0800 Date: Sun, 4 Feb 1996 18:00:57 -0800 Message-Id: <199602050200.SAA10758@netcom12.netcom.com> From: Jerry Peek References: <199602042338.SAA11653@worldmachine.com> Subject: Re: Pattern matching for SPAM To: list-managers@GreatCircle.COM Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I've been thinking about ways to stop spammers. Here's a system that might automatically cancel spam messages before they hit mailing lists. This is brainstorming, which means I purposely *haven't* thought out every detail. Brainstorms work best when other people find problems with the ideas and come up with new ideas that are more workable. I've been thinking about the "cancelbot" setup on Usenet. It isn't keeping spammers off of Usenet, but it's helping. (For those of you who don't know, Usenet netnews articles can be removed -- cancelled -- after they've been sent out. This is done with a "cancel" message that's sent after the original article has been sent. People, and automated systems, send out cancel messages for spams.) The problem on mailing lists is that messages can't be cancelled: Once the message is sent, the spam has hit the fan and it's too late. How could we do something like that on mailing lists? On moderated lists, it's easy: the moderator rejects most spam. The problem is unmoderated lists, eh? Here are some sorta random thoughts. Maybe these will move us toward a manageable cancel setup. 1. For lists where messages don't have to go out immediately, build in a one-day (or so) delay. The outgoing messages would sit in a mail file for a day, waiting to be (possibly) cancelled before they're distributed to the list. This should be easy to add to Unix MLMs as a front-end, with no MLM code change: Archive incoming mail from the alias file. For example, for a list named "gumbo", sendmail aliases for Majordomo could be: gumbo: /archive/dir/gumbo gumbo-real: "|/usr/local/majordomo/wrapper resend -l gumbo ..." Approved messages from /archive/dir/gumbo would be emailed to gumbo-real or could be directed straight to "wrapper resend". 2. Have an "Anti-Spam Central" (ASC) -- a (virtual) organization with one or more volunteers who agree to coordinate spam cancels. Moderators and other list owners (and maybe even regular subscribers?) who got a spam could forward the entire message to ASC. 3. ASC would evaluate messages submitted to see which were really spams. For verified spams, they would distribute spam-searching "stop lists." The stop lists they distribute could contain: - MD5 body checksums, and/or - message-IDs, and/or - lists of 20 uncommon words (from an automated dictionary match) or other "fuzzy" patterns that would match a slightly-modified spam. 4. These "stop lists" could be put on well-known Internet sites: ftp sites and dedicated telnettable ports. The stop lists could also be sent by PGP-signed email (etc.) to sites that don't have direct connections to the Internet. The MLM front-ends could retrieve these lists several times a day, then search their queued messages for spams. At each site, queued messages that match the stop lists would be forwarded to the list's owner (or someone) for approval... the rest would go automatically to their list. 5. This system could also stop "slow spams", where a spammer sends out the same spam once a day to a different list over a period of months. (ASC's stop list could hold info on old and "slow" spams as well as the latest ones.) Though this might be overdoing things, ASC could even be hooked into Usenet cancelbots. It could read Usenet cancel messages and grab the cancelled spam from Usenet. This would stop spam forwarded by Usenet gateways -- or spammers who spam both Usenet and mailing lists. Well, this isn't complete, but I think you get the idea. Comments? --Jerry Peek, jpeek@netcom.com From list-managers-owner Sun Feb 4 18:38:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id SAA19498 for list-managers-outgoing; Sun, 4 Feb 1996 18:28:55 -0800 (PST) Received: from pyrenees.org (pyrenees.org [199.2.117.228]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id SAA19493 for ; Sun, 4 Feb 1996 18:28:51 -0800 (PST) Received: by pyrenees.org (Smail3.1.29.1 #4) id m0tjGdt-0008QBC; Sun, 4 Feb 96 18:26 PST Message-Id: Date: Sun, 4 Feb 96 18:26 PST From: jeffg@pyrenees.org (Jeff Glover) To: Jerry Peek Subject: Re: Pattern matching for SPAM Cc: list-managers@GreatCircle.COM References: <199602042338.SAA11653@worldmachine.com> Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > [a fairly complete description of an anti-spam proposal for mailing lists] I'd add a mechanism to notify the person sending the spam that the message was rejected and why. This needs to be polite, since sometimes (hopefully not too often) the message will be from a legit subscriber and they will get upset if the determination was incorrect. This mechanism would also carbon-copy to the list maintainer address. A problem with the FTP sites/dedicated telnettable ports idea is that a spammer could use the database to make spams that are unstoppable. I don't know what could be done here except to "register" mailing list sites/hosts as trusted users of the database, with a fairly good (minimum: telephone conversation) investigation of the trusted users... Of course, this is a major maintenance headache. Just how many "major" mailing lists are there that would want to use this service? Just my $0.02 Jeff jeffg@pyrenees.org Administrator, PYR-L From list-managers-owner Sun Feb 4 18:53:28 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id SAA19897 for list-managers-outgoing; Sun, 4 Feb 1996 18:40:34 -0800 (PST) Received: from digital.netvoyage.net (digital.netvoyage.net [205.162.154.10]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id SAA19892 for ; Sun, 4 Feb 1996 18:40:31 -0800 (PST) Received: from digital.netvoyage.net (digital.netvoyage.net [205.162.154.10]) by digital.netvoyage.net (8.6.11/8.6.9) with SMTP id SAA21565; Sun, 4 Feb 1996 18:39:36 -0800 Date: Sun, 4 Feb 1996 18:39:33 -0800 (PST) From: Brock Rozen To: Jerry Peek cc: list-managers@GreatCircle.COM Subject: Re: Pattern matching for SPAM In-Reply-To: <199602050200.SAA10758@netcom12.netcom.com> Message-ID: X-URL: http://www.netvoyage.net/~brozen MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I think that that's putting WAY too much effort into this. Obviously, it would be nice if we had AI to cancel spams, but we don't. There is no generic spam, although some (very few) get sent out a few times. Spams are something that we have to live with, like crime. We can try and do our best to reduce it, but we also have to realize that the effort we put into this has to be realized, and if it only stops one or two spams over the course of a month or two, it's not worth our time! The lists I manage are all moderated and there are a few I manage which allow posting by the readers (one is a list that relays news from various sources, another is a discussion list; all are moderated). Truly, it does not take much time to moderate lists and remove spams. Truthfully, if your list is moderated, the spammer knows the message won't get through and won't waste their time in the future! Seriously though, if you're willing to have a message put in a queue, why not make that queue your INBOX? If you can live with a spam every so often, then you'll have no need to spend anymore time than you currently do on your list. I'm not saying we shouldn't discourage spams, but there is a limit to how much effort we should put in. ------------------------------------------------------------------------- | Brock Rozen | brozen@netvoyage.net | http://www.netvoyage.net/~brozen | | Check out my Auto-Reply System -- Send me mail with subject SEND HELP | ------------------------------------------------------------------------- From list-managers-owner Sun Feb 4 21:53:34 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id VAA26507 for list-managers-outgoing; Sun, 4 Feb 1996 21:42:18 -0800 (PST) Received: from dr-babe.atg.aol.com (dr-babe.atg.aol.com [152.163.64.100]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id NAA08018 for ; Sun, 4 Feb 1996 13:45:00 -0800 (PST) Received: by dr-babe.atg.aol.com (8.7.3/8.6.12) id QAA11681; Sun, 4 Feb 1996 16:43:57 -0500 (EST) Date: Sun, 4 Feb 1996 16:43:57 -0500 (EST) From: "David B. O'Donnell" X-Sender: atropos@dr-babe.atg.aol.com To: list-managers@greatcircle.com Subject: They did it again. Message-ID: Organization: America Online Inc. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Please pass this on to any majordomo list owners: I have, once again, been forge-subscribed to hundreds of majordomo lists. While I will be mass-unsubscribing from what I can, I'd appreciate it you could do me the favor of (1) removing atropos@aol.com and/or atropos@aol.net from your list (2) filtering any future subscriptions from those addresses. If I want to join more lists, I'll write the list owners directly. Thanks in advance. -- __ David B. O'Donnell (atropos@aol.net, PMDAtropos@aol.com, Atropos@gnn.com) \/ AOL Internet Feedback/Response/Information Team Manager, LISTSERV Manager Tel. 703/453-4000 x4255 FAX 703/453-4102 Pager 800/759-8888 PIN 128-5338 WWW: http://www.cais.com/atropos/ "The spam stops here." From list-managers-owner Sun Feb 4 22:53:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id WAA28856 for list-managers-outgoing; Sun, 4 Feb 1996 22:47:43 -0800 (PST) Received: from sacusr.mp.usbr.gov (sacusr.mp.usbr.gov [140.214.12.2]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id WAA28849 for ; Sun, 4 Feb 1996 22:47:38 -0800 (PST) Received: by sacto.mp.usbr.gov (MX V4.2 VAX) id 1; Sun, 04 Feb 1996 22:45:53 PST Date: Sun, 04 Feb 1996 22:45:47 PST From: "Henry W. Miller" To: atropos@aol.net CC: list-managers@greatcircle.com, henrym@sacto.mp.usbr.gov Message-ID: <0099D6DA.FD81B0A2.1@sacto.mp.usbr.gov> Subject: RE: They did it again. Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > From: MX%"atropos@aol.net" 4-FEB-1996 22:03:23.65 > Subj: They did it again. > Please pass this on to any majordomo list owners: > > I have, once again, been forge-subscribed to hundreds of majordomo lists. > While I will be mass-unsubscribing from what I can, I'd appreciate it you > could do me the favor of > > (1) removing atropos@aol.com and/or atropos@aol.net from your list > (2) filtering any future subscriptions from those addresses. > > If I want to join more lists, I'll write the list owners directly. > > Thanks in advance. > > -- > __ David B. O'Donnell (atropos@aol.net, PMDAtropos@aol.com, Atropos@gnn.com) > \/ AOL Internet Feedback/Response/Information Team Manager, LISTSERV Manager > Tel. 703/453-4000 x4255 FAX 703/453-4102 Pager 800/759-8888 PIN 128-5338 > WWW: http://www.cais.com/atropos/ "The spam stops here." > > OK, Davis, 'Fess up - whom did you tee off, besides those people who don't like responsible postmasters? -HWM From list-managers-owner Sun Feb 4 23:53:31 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id XAA29815 for list-managers-outgoing; Sun, 4 Feb 1996 23:44:49 -0800 (PST) Received: from j51.com (j51.com [199.224.7.51]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id XAA29810 for ; Sun, 4 Feb 1996 23:44:45 -0800 (PST) Received: from j51.com..com (pm11.j51.com [199.224.7.235]) by j51.com (8.6.12/8.6.9) with SMTP id HAA11275 for ; Mon, 5 Feb 1996 07:44:33 GMT Message-Id: <2.2.32.19960205074213.006db654@j51.com> X-Sender: genesis@j51.com X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 05 Feb 1996 02:42:13 -0500 To: list-managers@GreatCircle.COM From: Project Genesis Subject: Speaking of spams... Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Did I mention that Project Genesis is an organization specializing in religious education? The message below explains why all of our public lists are moderated. I value privacy and have grave doubts about things like the Exon amendment (which may make Internet providers liable), but I also think that we need to ensure that the Internet not become one big red-light district. Spams like this are a step in the wrong direction. It hit several of our religion-oriented lists. Ken >Sender: kristina@free.org [User Unknown - I told her to go away.] >Subject: LIVE NUDE VIDEOCONFERENCING! > >Hi, >My name is Kristina. I'm a nude model and I'd >love to take my clothes off and entertain you. >You can watch me live and in color on your >computer. We can type back and forth and I'll >be happy to perform your erotic fantasy. If >this sounds like fun, visit the website and >download the software. The address is >http://www.[I don't plan to help them].com or you can get the >software from the BBS at 815-[ditto]. I'll >turn the camera on in my studio and wait to >hear from you. I think you'll like what I have >to show you. This isn't a movie...you make a >request and I'll probably fulfill it for you. >Look for my picture on the Website. Hope to >see you soon! > >Love, >Kristina From list-managers-owner Mon Feb 5 01:23:29 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id BAA03012 for list-managers-outgoing; Mon, 5 Feb 1996 01:22:17 -0800 (PST) Received: from peg.apc.org (peg.apc.org [192.131.13.1]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id BAA03007 for ; Mon, 5 Feb 1996 01:22:09 -0800 (PST) Received: from guest1.peg.apc.org (t47.dialup.peg.apc.org [192.203.176.175]) by peg.apc.org (8.6.9/Revision: 1.10 ) with SMTP id UAA20192 for ; Mon, 5 Feb 1996 20:20:13 +1000 Date: Mon, 5 Feb 1996 20:20:13 +1000 Message-Id: <199602051020.UAA20192@peg.apc.org> X-Sender: janderson@peg.apc.org X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: list-managers@GreatCircle.COM From: janderson@peg.apc.org (Jeff Anderson) Subject: Re: Pattern matching for SPAM Sender: list-managers-owner@GreatCircle.COM Precedence: bulk It would require a bit of programming, temp storage and increased bandwidth, but echoing messages from all lists continually hit by spamming to a database that searchs for duplicates, addressing them to the list owner and bouncing the non duplicates back to the respective lists would soon stop the problem. The spammer would have to alter each message and send to each list from a different address. Most spammers would quickly find something else to do. The delay wouldn't be that great and one site could act as a filter more a great many lists. It will eventually come to something of that ilk. It will have to. Jeff Anderson From list-managers-owner Mon Feb 5 02:08:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id CAA04555 for list-managers-outgoing; Mon, 5 Feb 1996 02:01:49 -0800 (PST) Received: from tango.rahul.net (tango.rahul.net [192.160.13.5]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id CAA04550 for ; Mon, 5 Feb 1996 02:01:44 -0800 (PST) Received: from bolero.rahul.net by tango.rahul.net with SMTP id AA02388 (5.67b8/IDA-1.5 for ); Mon, 5 Feb 1996 02:00:49 -0800 Received: by bolero.rahul.net id AA00622 (5.67b8/IDA-1.5 for list-managers@GreatCircle.COM); Mon, 5 Feb 1996 02:00:48 -0800 Message-Id: <199602051000.AA00622@bolero.rahul.net> To: list-managers@GreatCircle.COM Subject: Re: Pattern matching for SPAM In-Reply-To: <199602051020.UAA20192@peg.apc.org> Date: Mon, 05 Feb 96 02:00:47 -0800 From: Michelle Dick Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Jeff wrote: > do. The delay wouldn't be that great and one site could act as a filter more > a great many lists. It will eventually come to something of that ilk. It > will have to. I doubt it. I'm actually not that concerned about SPAM and mailing lists, at least, not for my lists. It's easy enough to make the lists such that subscribers only are permitted posting privileges. Only those lists where the owner doesn't consider that an appropriate option are really at risk for spam. Now, it may come to pass that we'll see spam preceeded by mass subscription to enable posting privileges, but if it does, I'll just implement an appropriate posting delay for new subscriptions (dead easy with SmartList and similarly so with majordomo assuming one has access to appropriate files and cron). I also divert all messages longer than 3KB for review before posting (nearly all legitimate message to my list are short -- I hand approve the longer ones). This limit is very good for catching urban legend posts (though my list info has a rather strident warning to subscribers not to post such things -- and, indeed, it's been many many months since someone has tried). The mailing list software available now is very powerful; I think handling spam is one of the easier tasks in running a list these days and it's only getting better. Unlike newsgroup software, mailing list software is more advanced than the spammers. It's been a long time since spam has made it to my list. My list (still predominantly unmoderated) is much less noisy now at 2500+ subscribers than it was in the early days of a few hundred. Michelle From list-managers-owner Mon Feb 5 03:53:24 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id DAA07740 for list-managers-outgoing; Mon, 5 Feb 1996 03:38:38 -0800 (PST) Received: from felix.dircon.co.uk (felix.dircon.co.uk [193.128.224.10]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id DAA07724 for ; Mon, 5 Feb 1996 03:38:25 -0800 (PST) Received: by felix.dircon.co.uk id AA24397 (5.67b/IDA-1.5 for ); Mon, 5 Feb 1996 11:37:32 GMT Received: from diversity.org.uk(193.128.226.199) by amnesiac via smap (V1.3) id smac24339; Mon Feb 5 11:37:17 1996 From: Nigel Whitfield Subject: Re: Pattern matching for SPAM Organization: Digital Diversity Date: Mon, 5 Feb 1996 10:37:41 GMT Message-Id: References: Apparently-To: Sender: list-managers-owner@GreatCircle.COM Precedence: bulk In article , Brock Rozen wrote: >The lists I manage are all moderated and there are a few I manage which >allow posting by the readers (one is a list that relays news from >various sources, another is a discussion list; all are moderated). Truly, it >does not take much time to moderate lists and remove spams. When I started my first list, I decided that it would accept posts only from members, largely because it deals with sexuality. That was the main reason for writing my own list processor, and it frankly doesn't take too much effort handle addresses that aren't authorised - feed them into a script and then add the address to the auth database. Most of the time, this will deal with anything that comes up, and even with 450 members and up to 60 messages a day, I usually only have a couple of genuine posts with mangled headers that need to be released from the queue. (Fortunately, I don't think I've had any attempts to spam uk-motss yet). In the long term, seeing the problems that people have with spam, I don't think I'd run a list without this sort of address checking. So, I've now re-written the list's front-end to do the checking more efficiently. Of course, some spam will come from list members; the main tactic I use to prevent anything like that is simply a line limit; the lists I run are discussion lists. Sometimes things do get a bit verbose, but messages are often quite short. The list holds messages more than 150 lines long for my attention (which also stops people sending back digests). Again, it's a little more work, but not much in day to day operation. The updated script that does all this is more or less tested (it'll also bounce messages with uuencoded, binhex or certain MIME types); give me a few weeks and maybe I'll have something that people can drop in as a filter for other software. Nigel. -- Nigel Whitfield nigel@diversity.org.uk Digital Diversity nigel@stonewall.demon.co.uk and uk-motss ***** All demon.co.uk sites are independently run internet hosts ***** From list-managers-owner Mon Feb 5 05:08:25 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id EAA09967 for list-managers-outgoing; Mon, 5 Feb 1996 04:54:58 -0800 (PST) Received: from dub-img-3.compuserve.com (dub-img-3.compuserve.com [198.4.9.3]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id EAA09962 for ; Mon, 5 Feb 1996 04:54:54 -0800 (PST) Received: by dub-img-3.compuserve.com (8.6.10/5.950515) id FAA29041; Mon, 5 Feb 1996 05:49:24 -0500 Date: 05 Feb 96 05:45:45 EST From: To: Subject: Re[2]: Pattern matching for SPAM Message-ID: <960205104545_702420.204300_BHD25-1@CompuServe.COM> Sender: list-managers-owner@GreatCircle.COM Precedence: bulk |two spams over the course of a month or two, it's not worth our time! |The lists I manage are all moderated and there are a few I manage which |allow posting by the readers (one is a list that relays news from |various sources, another is a discussion list; all are moderated). Truly, it |does not take much time to moderate lists and remove spams. Likewise, a list of mine was targetted twic in a couple of weeks by the magazine scam - but second time it didn't get anywhere, since I switched the list to being open to postings only from subscribed members. There's no moderation, but this simple step has cut out this scam, and I'd guess a fair number in the future. It's easy for a spammer to pick up posting addresses from BITNET new-list - it's more work to deal with the various subscription engines out there and get onto them. That I guess will come, and some magic cookie scheme - or worse, manual checking - may be required. Until then, the switch from open subbing, open posting to open subbing, subscriber-only posting has bought some time. cheers jey =========================================================================== Jeffrey R Burrows http://ourworld.compuserve.com/homepages/jey ------------------------------------------------------------------------ "Robert Frost, the distinguished New England poet, used to define a liberal as someone who refused to take his own side in an argument." "Dreaming of JFK", The Economist, 17 March 1984 ------------------------------------------------------------------------- From list-managers-owner Mon Feb 5 07:08:53 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id GAA13147 for list-managers-outgoing; Mon, 5 Feb 1996 06:59:15 -0800 (PST) Received: from mail06.mail.aol.com (mail06.mail.aol.com [152.163.172.108]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id GAA13142 for ; Mon, 5 Feb 1996 06:59:11 -0800 (PST) From: PMDAtropos@aol.com Received: by mail06.mail.aol.com (8.6.12/8.6.12) id JAA10903; Mon, 5 Feb 1996 09:58:16 -0500 Date: Mon, 5 Feb 1996 09:58:16 -0500 Message-ID: <960205095815_136227044@mail06.mail.aol.com> To: list-managers@greatcircle.com, spam-l@searn.sunet.se Subject: Bombed again. Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Please pass this on to any majordomo list owners: This past weekend, you may have received a subscription request to your list(s) from "ListMaster@aol.com". These subscription requests were forged. If you would be kind enough to remove ListMaster from your lists, it would be greatly appreciated. ListMaster@aol.com has no need to be on any mailing lists, so feel free to add it to any filters you have. Thanks in advance. -- __ David B. O'Donnell (atropos@aol.net, PMDAtropos@aol.com, Atropos@gnn.com) \/ AOL Internet Feedback/Response/Information Team Manager, LISTSERV Manager Tel. 703/453-4000 x4255 FAX 703/453-4102 Pager 800/759-8888 PIN 128-5338 WWW: http://www.cais.com/atropos/ "The spam stops here." From list-managers-owner Mon Feb 5 07:54:14 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id HAA14836 for list-managers-outgoing; Mon, 5 Feb 1996 07:48:25 -0800 (PST) Received: from emout06.mail.aol.com (emout06.mail.aol.com [198.81.10.43]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id HAA14822 for ; Mon, 5 Feb 1996 07:48:21 -0800 (PST) From: PMDAtropos@aol.com Received: by emout06.mail.aol.com (8.6.12/8.6.12) id KAA23808 for list-managers@greatcircle.com; Mon, 5 Feb 1996 10:47:18 -0500 Date: Mon, 5 Feb 1996 10:47:18 -0500 Message-ID: <960205104717_313037911@emout06.mail.aol.com> To: list-managers@greatcircle.com Subject: Re: They did it again. Sender: list-managers-owner@GreatCircle.COM Precedence: bulk In a message dated 96-02-05 02:01:53 EST, henrym@sacto.mp.usbr.gov (Henry W. Miller) writes: >'Fess up - whom did you tee off, besides those people who don't >like responsible postmasters? It's hard to say, unfortunately. It could be one of many ex-AOL users who I've terminated for abusing the net, it could be someone who just hates AOL, it could be one of the several mass junk mailers who have been targeting AOL users... or any number of people :-/ --David From list-managers-owner Mon Feb 5 08:08:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id HAA15527 for list-managers-outgoing; Mon, 5 Feb 1996 07:57:32 -0800 (PST) Received: from CRPL.CEDAR-RAPIDS.LIB.IA.US (crpl.cedar-rapids.lib.ia.us [198.134.138.1]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id HAA15519 for ; Mon, 5 Feb 1996 07:57:27 -0800 (PST) Date: Mon, 5 Feb 1996 9:55:14 -0600 (CST) From: TERRY OWEN To: List-Managers@GreatCircle.COM Message-Id: <960205095514.9c38@CRPL.CEDAR-RAPIDS.LIB.IA.US> Subject: RE: List-Managers-Digest V5 #24 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk With all this talk of spams hitting the mailing lists represented here, I just thought I'd mention that the listserv at psuvm.psu.edu (where my fanzine list resides) faithfully dumps these in with my error messages from the list. All I have to do is delete them. Since I'm considering starting a new list with a commercial host who uses Majordomo it seems that this is something I'd have to consider. Is there a mailing service provider who uses listserv software? Or something similar? Terry Owen BrionyLodge@crpl.cedar-rapids.lib.ia.us From list-managers-owner Mon Feb 5 08:38:31 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id IAA17494 for list-managers-outgoing; Mon, 5 Feb 1996 08:30:19 -0800 (PST) Received: from torii.triple-i.com (torii.triple-i.com [192.94.150.1]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id IAA17489 for ; Mon, 5 Feb 1996 08:30:15 -0800 (PST) Received: from siesta (siesta+.triple-i.com [192.94.150.7]) by torii.triple-i.com (8.6.9/8.6.9) with SMTP id IAA25977; Mon, 5 Feb 1996 08:29:25 -0800 Received: from pak by siesta (4.1/SMI-4.1) id AA17200; Mon, 5 Feb 96 08:29:23 PST From: jeffw@triple-i.com (Jeff Wasilko) Message-Id: <9602051629.AA17200@siesta> Subject: Re: Pattern matching for SPAM To: BRIONYLODGE@CRPL.CEDAR-RAPIDS.LIB.IA.US (TERRY OWEN) Date: Mon, 5 Feb 1996 08:29:23 -0800 (PST) Cc: List-Managers@GreatCircle.COM In-Reply-To: <960205095514.9c38@CRPL.CEDAR-RAPIDS.LIB.IA.US> from "TERRY OWEN" at Feb 5, 96 09:55:14 am X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk TERRY OWEN writes: > > With all this talk of spams hitting the mailing lists represented here, I just > thought I'd mention that the listserv at psuvm.psu.edu (where my fanzine list > resides) faithfully dumps these in with my error messages from the list. All I > have to do is delete them. Since I'm considering starting a new list with a > commercial host who uses Majordomo it seems that this is something I'd have to > consider. Is there a mailing service provider who uses listserv software? Or > something similar? Majordomo caught the 2 Magazine spam posts that hit my 2 lists because they had an invalid "Approved:" header line. -Jeff From list-managers-owner Mon Feb 5 08:53:55 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id IAA18445 for list-managers-outgoing; Mon, 5 Feb 1996 08:52:32 -0800 (PST) Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id IAA18440 for ; Mon, 5 Feb 1996 08:52:29 -0800 (PST) Received: from lunch.engr.sgi.com by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id IAA04210; Mon, 5 Feb 1996 08:51:37 -0800 Received: by lunch.engr.sgi.com (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) id IAA23693; Mon, 5 Feb 1996 08:51:36 -0800 From: close@lunch.engr.sgi.com (Diane Barlow Close) Message-Id: <199602051651.IAA23693@lunch.engr.sgi.com> Subject: Re: majordomo and trapping spam versus Listserv. To: BRIONYLODGE@CRPL.CEDAR-RAPIDS.LIB.IA.US (TERRY OWEN) Date: Mon, 5 Feb 1996 08:51:35 -0800 (PST) Cc: List-Managers@GreatCircle.COM In-Reply-To: <960205095514.9c38@CRPL.CEDAR-RAPIDS.LIB.IA.US> from "TERRY OWEN" at Feb 05, 1996 09:55:14 AM X-Mailer: ELM [version 2.5 PL0a8s] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk TERRY OWEN wrote: > With all this talk of spams hitting the mailing lists represented here, I just > thought I'd mention that the listserv at psuvm.psu.edu (where my fanzine list > resides) faithfully dumps these in with my error messages from the list. All I > have to do is delete them. Since I'm considering starting a new list with a > commercial host who uses Majordomo it seems that this is something I'd have to > consider. Majordomo does the same thing. Right now all KK's spams are trapped due to "invalid approved header", but if he ever found a way around this (very doubtful, given majordomo's approval system), just set the "restrict-post" line and all spam is caught. KK faithfully sends his spams to my lists every week (and has for years now :-), and every week they're trapped and sent to me for deletion. Procmail even deletes them automatically for me now. :-) No spam has reached my majordomo-run lists for over two years now. -- Diane Close I'm at lunch all day. :-) If a Canadian Had Said It First (The Globe & Mail): "Cry havoc, and let loose the dogs of a peacekeeping mission!" From list-managers-owner Mon Feb 5 09:11:09 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id JAA19033 for list-managers-outgoing; Mon, 5 Feb 1996 09:00:38 -0800 (PST) Received: from VM.SE.LSOFT.COM (vm.se.lsoft.com.43.186.205.IN-ADDR.ARPA [205.186.43.254]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id JAA19023 for ; Mon, 5 Feb 1996 09:00:30 -0800 (PST) Message-Id: <199602051700.JAA19023@miles.greatcircle.com> Received: from VM.SE.LSOFT.COM by VM.SE.LSOFT.COM (IBM VM SMTP V2R3) with BSMTP id 7088; Mon, 05 Feb 96 11:59:35 EST Received: from VM.SE.LSOFT.COM (NJE origin ERIC@SEARN) by VM.SE.LSOFT.COM (LMail V1.2b/1.8b) with RFC822 id 1336; Mon, 5 Feb 1996 11:59:35 -0500 Date: Mon, 5 Feb 1996 11:57:53 EST From: Eric Thomas Subject: Re: majordomo and trapping spam versus Listserv. To: List-Managers@GreatCircle.COM In-Reply-To: Message of Mon, 5 Feb 1996 08:51:35 -0800 (PST) from list-managers-owner@GreatCircle.COM Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On Mon, 5 Feb 1996 08:51:35 -0800 (PST) Diane Barlow Close said: >TERRY OWEN wrote: With all >> this talk of spams hitting the mailing lists represented here, I just >> thought I'd mention that the listserv at psuvm.psu.edu (where my >> fanzine list resides) faithfully dumps these in with my error messages >> from the list. All I have to do is delete them. > >Majordomo does the same thing. No, it doesn't. Majordomo lets you configure your list so that people who aren't on the list can't post. LISTSERV's spam detector catches spams even when the list is totally open and anyone is allowed to post (and of course you can also restrict posting to subscribers, moderator, etc). Eric From list-managers-owner Mon Feb 5 10:39:26 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id KAA23194 for list-managers-outgoing; Mon, 5 Feb 1996 10:23:44 -0800 (PST) Received: from outsider.bolis.com (bolis.com [204.153.195.10]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id KAA23143 for ; Mon, 5 Feb 1996 10:23:29 -0800 (PST) Received: from hock.bolis.sf-bay.org (root@hock.bolis.com [199.165.142.10]) by outsider.bolis.com (8.7.3/8.7.3) with SMTP id KAA20385; Mon, 5 Feb 1996 10:18:04 -0800 Received: from amillar by hock.bolis.sf-bay.org with smtp (Smail3.1.28.1 #6) id m0tjVAD-000UpoC; Mon, 5 Feb 96 09:57 PST Message-Id: Comments: Authenticated sender is From: "Alan Millar" Organization: The Bolis Group To: Eric Thomas , List-Managers@GreatCircle.COM Date: Mon, 5 Feb 1996 10:00:12 -800 Subject: Re: majordomo and trapping spam versus Listserv. X-mailer: Pegasus Mail for Windows (v2.01) Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > >Majordomo does the same thing. > > No, it doesn't. Majordomo lets you configure your list so that people who > aren't on the list can't post. LISTSERV's spam detector catches spams > even when the list is totally open and anyone is allowed to post (and of > course you can also restrict posting to subscribers, moderator, etc). Majordomo has a number of things, including the recent "taboo" patches. Perhaps you can tell us *how* Listserv catches spams on a totally open list or what it looks for, for a fair comparison. - Alan ---- Alan Millar amillar@bolis.SF-Bay.org System Administrator http://www.bolis.com Batteries not included. From list-managers-owner Mon Feb 5 14:38:46 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id OAA07622 for list-managers-outgoing; Mon, 5 Feb 1996 14:33:39 -0800 (PST) Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id OAA07602 for ; Mon, 5 Feb 1996 14:33:32 -0800 (PST) Received: from lunch.engr.sgi.com by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id OAA26073; Mon, 5 Feb 1996 14:32:35 -0800 Received: by lunch.engr.sgi.com (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) id OAA05127; Mon, 5 Feb 1996 14:32:31 -0800 From: close@lunch.engr.sgi.com (Diane Barlow Close) Message-Id: <199602052232.OAA05127@lunch.engr.sgi.com> Subject: Re: majordomo and trapping spam versus Listserv. To: ERIC@VM.SE.LSOFT.COM (Eric Thomas) Date: Mon, 5 Feb 1996 14:32:29 -0800 (PST) Cc: List-Managers@GreatCircle.COM In-Reply-To: <199602051700.JAA19023@miles.greatcircle.com> from "Eric Thomas" at Feb 05, 1996 11:57:53 AM X-Mailer: ELM [version 2.5 PL0a8s] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Eric Thomas wrote: > No, it doesn't. Majordomo lets you configure your list so that people who > aren't on the list can't post. True. > LISTSERV's spam detector catches spams > even when the list is totally open and anyone is allowed to post (and of > [snip] Sounds exactly like Majordomo's new "taboo-headers" and "taboo-body". I set mine to catch /^Received: .*freeppp.com/i and any reference to magazines or other common "catch phrases" that KK likes to use. "Approved: moderator" is another good one. So yes, majordomo too can be configured to catch spam sent to an open list. Closing the list makes the job even easier imo. So how does "spam detector" differ from the "taboo catcher"? -- Diane Close I'm at lunch all day. :-) If a Canadian Had Said It First (The Globe & Mail): "Cry havoc, and let loose the dogs of a peacekeeping mission!" From list-managers-owner Mon Feb 5 15:15:41 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id PAA09273 for list-managers-outgoing; Mon, 5 Feb 1996 15:00:15 -0800 (PST) Received: from urth.acsu.buffalo.edu (urth.acsu.buffalo.edu [128.205.7.9]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id PAA09191 for ; Mon, 5 Feb 1996 15:00:01 -0800 (PST) Received: (from pjg@localhost [127.0.0.1]) by urth (8.7.2/8.7.1) with ESMTP id RAA04541; Mon, 5 Feb 1996 17:59:03 -0500 (EST) Message-Id: <199602052259.RAA04541@urth.acsu.buffalo.edu> To: close@lunch.engr.sgi.com (Diane Barlow Close) cc: List-Managers@GreatCircle.COM Subject: Re: majordomo and trapping spam versus Listserv. In-reply-to: A message of "Mon, 05 Feb 1996 14:32:29 PST." Date: Mon, 05 Feb 1996 17:59:01 -0500 From: Paul Graham Sender: list-managers-owner@GreatCircle.COM Precedence: bulk a large number of the listserv machines are interconnected (i suspect all the ones that host public lists) and share information. this lets them do things that independent systems can't. i understand that listproc can also share information with other listproc systems so it may be able to do clever things. it would be nice if the listserv notifications could be distributed elsewhere so that other systems that able to do dynamic exclusion updates could take advantage of them. -------- In reply to: So how does "spam detector" differ from the "taboo catcher"? --------------------- -- paul pjg@acsu.Buffalo.EDU |public keys at: pjg@ubvm | http://urth.acsu.Buffalo.EDU/~pjg/key.html if the above contains opinions they are mine unless marked otherwise. From list-managers-owner Mon Feb 5 15:23:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id OAA08771 for list-managers-outgoing; Mon, 5 Feb 1996 14:53:53 -0800 (PST) Received: from VM.SE.LSOFT.COM (vm.se.lsoft.com.43.186.205.IN-ADDR.ARPA [205.186.43.254]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id OAA08745 for ; Mon, 5 Feb 1996 14:53:27 -0800 (PST) Message-Id: <199602052253.OAA08745@miles.greatcircle.com> Received: from VM.SE.LSOFT.COM by VM.SE.LSOFT.COM (IBM VM SMTP V2R3) with BSMTP id 7298; Mon, 05 Feb 96 17:52:11 EST Received: from VM.SE.LSOFT.COM (NJE origin ERIC@SEARN) by VM.SE.LSOFT.COM (LMail V1.2b/1.8b) with RFC822 id 1755; Mon, 5 Feb 1996 17:52:11 -0500 Date: Mon, 5 Feb 1996 17:35:25 EST From: Eric Thomas Subject: Re: majordomo and trapping spam versus Listserv. To: List-Managers@GreatCircle.COM In-Reply-To: Message of Mon, 5 Feb 1996 14:32:29 -0800 (PST) from Diane Barlow Close Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On Mon, 5 Feb 1996 14:32:29 -0800 (PST) Diane Barlow Close said: >> LISTSERV's spam detector catches spams even when the list is totally >> open and anyone is allowed to post (and of [snip] > >Sounds exactly like Majordomo's new "taboo-headers" and "taboo-body". Sorry, but it's completely different. Keyword based filters may be very effective at catching recurring spams, like the magazine subscription club, but they are of limited usefulness with brand new spams, like the nude video conferencing one we got recently. Plus, if you filter too many keywords, you end up blocking perfectly legitimate postings. And filtering out entire domains just because one of the accounts was used for spamming, it's outright unfair to the other innocent users. LISTSERV's spam detector, which has been around for nearly a year, is not keyword based. It just detects messages that are posted to large number of lists in a short period of time, and blocks them. It doesn't matter whether the message contains the usual catch phrases, which I'm afraid to type here since my message might get filtered, even though it isn't a spam. In fact, the software isn't passing judgment on the *contents* of your message (and exposing you to lawsuits), it's just decreeing that any message posted to thousands of mailing lists is bound to be out of topic for a large fraction of these lists. The definition of "spam" is *not* "advertisement", but "message posted to a bunch of lists that have nothing to do with the subject matter". You can't build a spam filter with a pattern matching engine - all you can create is an advertisement filter, and not all advertisements are inappropriate. Conversely, not all spams are ads (aren't you tired of being invited to conferences in exotic resorts all over the world?), and it's easy to reword an ad so it doesn't sound like an ad any longer. Eric From list-managers-owner Mon Feb 5 15:53:42 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id PAA13361 for list-managers-outgoing; Mon, 5 Feb 1996 15:52:47 -0800 (PST) Received: from pathfinder.com (relay.pathfinder.com [204.71.242.18]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id PAA13341 for ; Mon, 5 Feb 1996 15:52:35 -0800 (PST) Received: from tigger.dev.pathfinder.com.pathfinder.com by pathfinder.com (8.6.12/SMI-SVR4) id SAA20664; Mon, 5 Feb 1996 18:51:37 -0500 Received: by tigger.dev.pathfinder.com.pathfinder.com (SMI-8.6/SMI-SVR4) id SAA01138; Mon, 5 Feb 1996 18:51:51 -0500 From: ahanes@pathfinder.com (Amanda Hanes (Pathfinder)) Message-Id: <199602052351.SAA01138@tigger.dev.pathfinder.com.pathfinder.com> Date: Mon, 5 Feb 1996 18:51:45 -0500 (EST) To: jrvb@info.cren.net Cc: list-managers@GreatCircle.COM Subject: serverd died: LISTPROC: Internal error, exit code 16 (fwd) X-Mailer: Ishmail 1.2-960123-sol24 MIME-Version: 1.0 Content-Type: text/plain Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >>>>> Forwarded message from server (listproc server daemon) Return-Path: Received: by pathfinder.com (8.6.12/SMI-SVR4) id SAA20526; Mon, 5 Feb 1996 18:48:12 -0500 Date: Mon, 5 Feb 1996 18:48:12 -0500 From: server (listproc server daemon) Message-Id: <199602052348.SAA20526@pathfinder.com> To: ahanes@pathfinder.com Subject: serverd died: LISTPROC: Internal error, exit code 16 Content-Type: text Content-Length: 1 << End forwarded message Any idea what caused this? Thanks in advance! Amanda Amanda S. Hanes System Engineer, Pathfinder Time Inc., New Media (x3585) From list-managers-owner Mon Feb 5 16:39:03 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id QAA15862 for list-managers-outgoing; Mon, 5 Feb 1996 16:25:16 -0800 (PST) Received: from hahp9k.harte-lyne.ca (hahp9k.harte-lyne.ca [205.206.207.101]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id QAA15857 for ; Mon, 5 Feb 1996 16:25:12 -0800 (PST) Received: from ham_hal_g02_u01 ([205.206.207.30]) by hahp9k.harte-lyne.ca with SMTP (1.39.111.2/16.2) id AA038246334; Mon, 5 Feb 1996 19:25:34 -0500 Message-Id: <3116A010.2981@harte-lyne.ca> Date: Mon, 05 Feb 1996 19:25:52 -0500 From: "James B. Byrne" Organization: Harte & Lyne Limited X-Mailer: Mozilla 2.0b6a (WinNT; I) Mime-Version: 1.0 To: Diane Barlow Close Cc: List-Managers@GreatCircle.COM Subject: Re: majordomo and trapping spam versus Listserv. References: <199602052232.OAA05127@lunch.engr.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk So, What is this Taboo List pach and where do I get it. -- James B. Byrne mailto:byrnejb@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca Hamilton, Ontario 905-561-1241 From list-managers-owner Mon Feb 5 16:53:50 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id QAA17259 for list-managers-outgoing; Mon, 5 Feb 1996 16:47:58 -0800 (PST) Received: from VM.SE.LSOFT.COM (vm.se.lsoft.com.43.186.205.IN-ADDR.ARPA [205.186.43.254]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id QAA17245 for ; Mon, 5 Feb 1996 16:47:48 -0800 (PST) Message-Id: <199602060047.QAA17245@miles.greatcircle.com> Received: from VM.SE.LSOFT.COM by VM.SE.LSOFT.COM (IBM VM SMTP V2R3) with BSMTP id 7377; Mon, 05 Feb 96 19:46:39 EST Received: from VM.SE.LSOFT.COM (NJE origin ERIC@SEARN) by VM.SE.LSOFT.COM (LMail V1.2b/1.8b) with RFC822 id 1912; Mon, 5 Feb 1996 19:46:39 -0500 Date: Mon, 5 Feb 1996 19:45:33 EST From: Eric Thomas Subject: Re: majordomo and trapping spam versus Listserv. To: Diane Barlow Close cc: List-Managers@GreatCircle.COM In-Reply-To: Message of Mon, 5 Feb 1996 16:23:28 -0800 (PST) from Diane Barlow Close Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On Mon, 5 Feb 1996 16:23:28 -0800 (PST) Diane Barlow Close said: >My husband (one of the "official" majordomo "enhancers") has hacked a >similar thing into our version of majordomo -- it simply catches things >sent "To:" too many places/addresses. Is that more like what you are >talking about with Listserv? No, only idiots send spams with "To:" fields listing hundreds of lists. You can't rely on the fact that all spammers are idiots; the Spam King and others certainly knew better :-) Eric From list-managers-owner Mon Feb 5 17:09:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id QAA16943 for list-managers-outgoing; Mon, 5 Feb 1996 16:42:49 -0800 (PST) Received: from sgi.sgi.com (SGI.COM [192.48.153.1]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id QAA16938 for ; Mon, 5 Feb 1996 16:42:45 -0800 (PST) Received: from sgihub.corp.sgi.com by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id QAA25453; Mon, 5 Feb 1996 16:41:31 -0800 Received: from lunch.engr.sgi.com by sgihub.corp.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id QAA17503; Mon, 5 Feb 1996 16:23:31 -0800 Received: by lunch.engr.sgi.com (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) id QAA09522; Mon, 5 Feb 1996 16:23:30 -0800 From: close@lunch.engr.sgi.com (Diane Barlow Close) Message-Id: <199602060023.QAA09522@lunch.engr.sgi.com> Subject: Re: majordomo and trapping spam versus Listserv. To: ERIC@VM.SE.LSOFT.COM (Eric Thomas) Date: Mon, 5 Feb 1996 16:23:28 -0800 (PST) Cc: List-Managers@GreatCircle.COM In-Reply-To: <199602052253.OAA08745@miles.greatcircle.com> from "Eric Thomas" at Feb 05, 1996 05:35:25 PM X-Mailer: ELM [version 2.5 PL0a8s] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Eric Thomas wrote: > LISTSERV's spam detector, which has been around for nearly a year, is not > keyword based. It just detects messages that are posted to large number > of lists in a short period of time, and blocks them. It doesn't matter My husband (one of the "official" majordomo "enhancers") has hacked a similar thing into our version of majordomo -- it simply catches things sent "To:" too many places/addresses. The vast majority of spams simply have an excessively long "To:" and "cc" line. Is that more like what you are talking about with Listserv? -- Diane Close I'm at lunch all day. :-) If a Canadian Had Said It First (The Globe & Mail): "Cry havoc, and let loose the dogs of a peacekeeping mission!" From list-managers-owner Mon Feb 5 17:38:41 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id RAA19704 for list-managers-outgoing; Mon, 5 Feb 1996 17:26:10 -0800 (PST) Received: from presence.lglobal.com (presence.lglobal.com [204.50.121.2]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id RAA19699 for ; Mon, 5 Feb 1996 17:26:06 -0800 (PST) Received: from presence.lglobal.com (jesse@presence.lglobal.com [204.50.121.2]) by presence.lglobal.com (8.6.12/8.6.12) with SMTP id UAA12575 for ; Mon, 5 Feb 1996 20:38:05 -0500 Date: Mon, 5 Feb 1996 20:38:05 -0500 (EST) From: Jesse Hirsh To: List-Managers@GreatCircle.COM Subject: mail program for windozeNT In-Reply-To: <199602052259.RAA04541@urth.acsu.buffalo.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk does anyone know of a mailer for windozeNT? From list-managers-owner Mon Feb 5 20:08:26 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id UAA26201 for list-managers-outgoing; Mon, 5 Feb 1996 20:03:34 -0800 (PST) Received: from info.cren.net (info.cren.net [198.76.81.4]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id UAA26196 for ; Mon, 5 Feb 1996 20:03:31 -0800 (PST) Received: (jrvb@localhost) by info.cren.net (8.6.12/8.6.4 (CREN)) id XAA13193; Mon, 5 Feb 1996 23:02:35 -0500 Date: Mon, 5 Feb 1996 23:02:34 -0500 (EST) From: James Robert von Behren X-Sender: jrvb@info To: Amanda Hanes cc: list-managers@GreatCircle.COM Subject: Re: serverd died: LISTPROC: Internal error, exit code 16 (fwd) In-Reply-To: <199602052351.SAA01138@tigger.dev.pathfinder.com.pathfinder.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Amanda - I believe that exit code 16 means that the server ran out of system resources. (most likely processes.) Probably the best thing to do would be to reboot your machine, to clean up the system. -Rob On Mon, 5 Feb 1996, Amanda Hanes wrote: > >>>>> Forwarded message from server (listproc server daemon) > > Return-Path: > Received: by pathfinder.com (8.6.12/SMI-SVR4) > id SAA20526; Mon, 5 Feb 1996 18:48:12 -0500 > Date: Mon, 5 Feb 1996 18:48:12 -0500 > From: server (listproc server daemon) > Message-Id: <199602052348.SAA20526@pathfinder.com> > To: ahanes@pathfinder.com > Subject: serverd died: LISTPROC: Internal error, exit code 16 > Content-Type: text > Content-Length: 1 > > > > << End forwarded message > > Any idea what caused this? > > Thanks in advance! > > Amanda > > > Amanda S. Hanes > System Engineer, Pathfinder > Time Inc., New Media (x3585) > ----------------------------------------------------------------------------- J. Rob von Behren CREN Programmer/Analyst Phone: (202) 331-5363 Fax: (202) 293-2853 ----------------------------------------------------------------------------- From list-managers-owner Tue Feb 6 07:09:56 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id HAA16821 for list-managers-outgoing; Tue, 6 Feb 1996 07:06:01 -0800 (PST) Received: from netcomsv.netcom.com (uucp12.netcom.com [163.179.3.12]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id HAA16816 for ; Tue, 6 Feb 1996 07:05:57 -0800 (PST) Received: from duke.sagarmatha.com by netcomsv.netcom.com with UUCP (8.6.12/SMI-4.1) id GAA24758; Tue, 6 Feb 1996 06:40:15 -0800 Received: by duke (Smail3.1.28.1 #64) id m0tjnpt-000gmAC; Tue, 6 Feb 96 05:53 PST Message-Id: From: james@sagarmatha.com (James C. Armstrong) Subject: Have any of you seen this before To: list-managers@greatcircle.com Date: Tue, 6 Feb 1996 05:53:33 -0800 (PST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I recently started to see some spew back from microsoft.com for one of my mailing lists; it looks like it is being returned to the original "From " line. The message is intact, and there is no error message information. Here's a copy of one of the headers: From microsoft.com!-d0-99.127 Mon Feb 5 23:04:05 1996 Return-Path: Received: by duke (Smail3.1.28.1 #64) id m0tjedQ-000gm9C; Mon, 5 Feb 96 23:04 EST Sender: microsoft.com!-d0-99.127 Received: from tide03.microsoft.com by netcomsv.netcom.com with ESMTP (8.6.12/SMI-4.1) id TAA21135; Mon, 5 Feb 1996 19:33:40 -0800 Received: by tide03.microsoft.com; id TAA29070; Mon, 5 Feb 1996 19:44:31 -0800 Received: from uucp12.netcom.com(163.179.3.12) by tide03.microsoft.com via smap (g3.0.3) id xma029026; Mon, 5 Feb 96 19:44:15 -0800 Received: from duke.sagarmatha.com by netcomsv.netcom.com with UUCP (8.6.12/SMI-4.1) id SAA07773; Mon, 5 Feb 1996 18:57:48 -0800 Received: by duke (Smail3.1.28.1 #64) id m0tjdR2-000gmDC; Mon, 5 Feb 96 21:47 EST Sender: owner-rangers-list@sagarmatha.com Received: by duke (Smail3.1.28.1 #64) id m0tjdQq-000gm9C; Mon, 5 Feb 96 21:47 EST Received: from Black.Cerritos.edu by netcomsv.netcom.com with ESMTP (8.6.12/SMI-4.1) id RAA06895; Mon, 5 Feb 1996 17:20:34 -0800 Received: from Cerritos.edu by Cerritos.edu (PMDF V5.0-5 #11610) id <01I0V1K6UJJO9KQ5Q3@Cerritos.edu> for rangers-list@sagarmatha.com; Mon, 05 Feb 1996 17:21:07 -0800 (PST) Date: Mon, 05 Feb 1996 17:21:07 -0800 (PST) From: CAMPBELL BRIAN Subject: Re: Mc Coist and the U.S.A To: rangers-list@sagarmatha.com Message-id: <01I0V1K6UJJQ9KQ5Q3@Cerritos.edu> X-VMS-To: IN%"rangers-list@sagarmatha.com" MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Sender: owner-rangers-list@sagarmatha.com Precedence: list Reply-To: rangers-list@sagarmatha.com Status: RO The message was sent to my machine, where majordomo expanded it and forwarded it to the rangers-list. There are two users @microsoft.com on this list. The message apparently goes all the way to that site, where it gets sent back, for no apparent reason... Have any of you experienced this on your lists? -- James C. Armstrong, Jr. | I told my love, I told my love, james@sagarmatha.com | I told her all my heart, | Trembling, cold, in ghastly fears-- | Ah, she doth depart. From list-managers-owner Tue Feb 6 07:38:42 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id HAA18596 for list-managers-outgoing; Tue, 6 Feb 1996 07:37:41 -0800 (PST) Received: from ttown.apci.com (ttown.apci.com [204.27.156.3]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id HAA18591 for ; Tue, 6 Feb 1996 07:37:37 -0800 (PST) Received: (from zukrp@localhost) by ttown.apci.com (8.6.12/8.6.12) id KAA02789; Tue, 6 Feb 1996 10:37:02 -0500 Date: Tue, 6 Feb 1996 10:37:02 -0500 (EST) From: Roland Zuk To: list-managers@greatcircle.com Subject: Re: Have any of you seen this before In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On Tue, 6 Feb 1996, James C. Armstrong wrote: > The message was sent to my machine, where majordomo expanded it and > forwarded it to the rangers-list. There are two users @microsoft.com > on this list. The message apparently goes all the way to that > site, where it gets sent back, for no apparent reason... > > Have any of you experienced this on your lists? Yes, I started getting the same thing a day or two ago, also from mail routed through the tide03.microsoft.com machine. I sent some test mails to a list subscriber @microsoft and found that mail without a Reply-To: in the header does not bounce, but mail with a reply-to header (as my list has), gets mirrored back to my majordomo server and ends up in duplicate postings to my list. I've notified my subscribers at microsoft.com and dropped them from the list pending resolution. Regards, Roland Admin, merkur-l merkur-l-owner@npl.com From list-managers-owner Tue Feb 6 18:53:38 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id SAA19207 for list-managers-outgoing; Tue, 6 Feb 1996 18:41:07 -0800 (PST) Received: from thud.cs.utk.edu (THUD.CS.UTK.EDU [128.169.94.228]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id SAA19202 for ; Tue, 6 Feb 1996 18:41:03 -0800 (PST) Received: from LOCALHOST.cs.utk.edu by thud.cs.utk.edu with SMTP (cf v2.11c-UTK) id VAA13860; Tue, 6 Feb 1996 21:39:59 -0500 Message-Id: <199602070239.VAA13860@thud.cs.utk.edu> X-URI: http://www.cs.utk.edu/~moore/ From: Keith Moore To: james@sagarmatha.com (James C. Armstrong) cc: list-managers@greatcircle.com, moore@cs.utk.edu Subject: Re: Have any of you seen this before In-reply-to: Your message of "Tue, 06 Feb 1996 05:53:33 PST." Date: Tue, 06 Feb 1996 21:39:58 -0500 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > I recently started to see some spew back from microsoft.com for > one of my mailing lists; it looks like it is being returned to > the original "From " line. The message is intact, and there is > no error message information. > Have any of you experienced this on your lists? Yes, I've seen them too. They're being sent to the envelope return address (not the header From address) of one of my lists. I sent mail to postmaster@microsoft.com about them as well as to the microsoft.com people on my lists. One of them said the problem was that their server was down last night (obviously they've never heard of queue and retry later) and that this was a nondelivery report. Since the returned message was indistinguishable from an ordinary message, I'm referring them to RFC's 1891-1894 -- the new internet standards track protocols for {non}delivery notifications. Keith -------- Take the pledge! "I will not limit my speech to satisfy the whims of Congress." From list-managers-owner Wed Feb 7 10:54:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id KAA19717 for list-managers-outgoing; Wed, 7 Feb 1996 10:38:51 -0800 (PST) Received: from lepomis.psych.upenn.edu (LEPOMIS.PSYCH.UPENN.EDU [130.91.68.34]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id KAA19686 for ; Wed, 7 Feb 1996 10:38:38 -0800 (PST) Received: by lepomis.psych.upenn.edu (AIX 3.2/UCB 5.64/4.03) id AA30095; Wed, 7 Feb 1996 13:35:07 -0500 Date: Wed, 7 Feb 1996 13:35:07 -0500 From: rowe@lepomis.psych.upenn.edu (Mickey Rowe) Message-Id: <9602071835.AA30095@lepomis.psych.upenn.edu> To: List-Managers@GreatCircle.COM Subject: Class assignments revisited... Sender: list-managers-owner@GreatCircle.COM Precedence: bulk For those of you that weren't here: Last Fall one of my lists was "assaulted" by a couple of classes -- instructors apparently gave students the assignment of subscribing to and unsubscribing from a list. Neither they nor previous instructors have ever given me specifics about how their assignments were spelled out to the students, but given the number of people involved I presume that my list was at best one of a small number of options given to the students during these assignments. Whether you've heard that before or not: I'm now getting assaulted by two more classes. Last night I got around 100 messages all as a result of mistakes made by the students of one of these two classes. The other one (in shades of last Fall's nightmares) is now bouncing all mail because there's a missing quotation mark in the machine's aliases file. All of the people from the offending sites are now on "vacation" from my lists, and I've attempted to contact them all to explain why, so I think I've performed all of the damage control that I can at this point (oh yeah, my MLM has been instructed to ignore all mail from either of the two sites). What I'd like to know is: what can we do to advertise to potential instructors that they shouldn't create such assignments? I suspect that some of you have also been hit without realizing it -- one of the two sites creating my current headache has been a low level irritant for a week or two. I finally reached the conclusion that it was a class assignment when I saw "eng314" as part of the alias problem I mentioned above. If their administrator hadn't biffed the creation of that alias, I might never have come across any such firm evidence (asking the students is generally like sending mail to /dev/null). In any case, I've checked out the website of the institution and found a faculty person that I'm guessing is the instructor because he refers to an "internet class" as though he expects its students to be reading his page -- and when I tried to send e-mail to him it bounced back to me because of the same alias problem. That's typically the sort of thing I run into when trying to make my class-exercise related problems go away. If anyone has any idea what I (or we) can do to prevent this sort of nonsense I'd really like to know. Certain times of the year this problem will be much more time-consuming than dealing with spams for some of us... On an unrelated note, I only get the digest version of this list, and a few times in the last couple of weeks I've received partial headers with no included messages. Is anybody aware of that problem? Thanks for at least giving me an outlet to share my pain! -- Mickey Rowe (rowe@lepomis.psych.upenn.edu) From list-managers-owner Wed Feb 7 12:13:29 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id LAA24278 for list-managers-outgoing; Wed, 7 Feb 1996 11:42:37 -0800 (PST) Received: from hamjudo.com (router.hamjudo.com [152.160.58.254]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id LAA24189 for ; Wed, 7 Feb 1996 11:41:45 -0800 (PST) Received: by hamjudo.com (Smail3.1.29.1 #3) id m0tkFnq-000J8oC; Wed, 7 Feb 96 14:45 EST Date: Wed, 7 Feb 1996 14:45:17 -0500 (EST) From: Paul Haas To: Mickey Rowe cc: List-Managers@GreatCircle.COM Subject: Re: Class assignments revisited... In-Reply-To: <9602071835.AA30095@lepomis.psych.upenn.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On Wed, 7 Feb 1996, Mickey Rowe wrote: > That's typically the sort of > thing I run into when trying to make my class-exercise related > problems go away. If anyone has any idea what I (or we) can do to > prevent this sort of nonsense I'd really like to know. If "we" provide a list or lists specifically for class-exercises, then we can give those folks a place to go. I created an email address for demonstrating my computer skills. It has worked great for getting me jobs, and it also works well for "Intro to the Internet" assignments and demonstrations. It is not a list, only a system that answers all of it's email, so it doesn't fill the list homework need. The listed address for my "hottub on the Internet" is hottub@hamjudo.com. The hot tub responds with its current temperature and a few other worthless pieces of information. It is sufficiently strange that people try it once and tell their friends to try it, but sufficiently boring that they don't try it repeatedly unless they are debugging an email problem. Instructors could tell students to send "help" to their nearest mailing list manager, but I guess the hottub is marginally more interesting. It's email gets forwarded to hottub@hogwild.hamjudo.com. I moved the hottub interface to that machine, because it had more serial ports. The move greatly cut down on postmaster email on the main machine, so I've learned to put email demo systems on separate hosts. I'm sure a virtual host would be sufficient. I glance at that machines postmaster email about once a week. It's fairly low maintenance. Someone, the "we" in my first paragraph, can set up a dedicated mail list server for mailing list practice. It would be a fine system for low key advertising, targeted at people new to the Internet. -- Paul Haas paulh@hamjudo.com http://www.hamjudo.com VP of Technology at The Internet Factory, Inc. http://www.netfactory.com From list-managers-owner Wed Feb 7 13:31:05 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id NAA29168 for list-managers-outgoing; Wed, 7 Feb 1996 13:09:32 -0800 (PST) Received: from ns.draper.com (ns.draper.com [140.102.2.1]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id NAA29155 for ; Wed, 7 Feb 1996 13:09:23 -0800 (PST) Received: from surname.draper.com by ns.draper.com id aa28021; 7 Feb 96 16:08 EST Received: from egbsun1.draper.com by surname.draper.com id aa03492; 7 Feb 96 16:08 EST Received: from egbsun21 by egbsun1 (8.6.8/sendmail-8.6.8) id QAA20987; Wed, 7 Feb 1996 16:06:57 -0500 Received: by egbsun21 (8.6.8/sendmail-8.6.8) id QAA09892; Wed, 7 Feb 1996 16:05:27 -0500 Date: Wed, 7 Feb 1996 16:05:27 -0500 Message-Id: <199602072105.QAA09892@egbsun21> To: List-Managers@greatcircle.com cc: Bruce Mackenzie From: Bruce A Mackenzie Reply-To: Bruce A Mackenzie Subject: Suggest practice lists for testing new config. files Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Paul Haas wrote: >>set up a dedicated mail list server for mailing list practice. I would like to suggest that EVERY majordomo (or listserve ?) site have a special list for testing new configuration files and letting new list administrators (like myself) practice. The list could be called: test-list@___.com There would be a standard password, and no permanent subscribers. Before a list-administrator changes a config file, she would subscribe to the test-list, download the config file to it, and send a few test messages. ...just be careful to leave the password unchanged for the next person. For example, I have had problems with majordomo replacing the domain name in the From and Reply_To fields, and testing that only subscribers may post messages, etc. Currently, I take one of our less used lists, unsubscribe everyone, load the new config file, and test it. Incidentally, I do not have an account on the host machine, so all this is via e-mail to majordomo. If someone can get this suggestion into the majordomo & listserve installation documentation (or if it already is), please send me a note privately. -Thanks. ---Bruce A. Mackenzie BMackenzie@draper.com From list-managers-owner Wed Feb 7 14:26:27 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id OAA02588 for list-managers-outgoing; Wed, 7 Feb 1996 14:10:51 -0800 (PST) Received: from village.ios.com (village.ios.com [198.4.75.49]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id OAA02581 for ; Wed, 7 Feb 1996 14:10:35 -0800 (PST) Received: (from gsp@localhost) by village.ios.com (8.6.11/8.6.9) id RAA01903; Wed, 7 Feb 1996 17:02:46 -0500 Date: Wed, 7 Feb 1996 17:02:44 -0500 (EST) From: Daniel Pfarrer To: Spam Prevention Discussion List cc: List Managers Mailing List Subject: MONEY Daily: How to keep the spam off your e-mail plate (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Here's an interesting article I found in my mailbox today. $**************************************************************************= $ * Daniel Pfarrer (DP108) SBA: daniel.pfarrer@sbaonline.gov = * * CEO & System Administrator CompuServe: 71324.212@compuserve.com = * * of GSP Services, Inc. Sys Admin: admin@gsp.com = * * Located in Washington, DC, USA Business: dpfarrer@gsp.com = * * For more info, e-mail info@gsp.com gsp@village.ios.com = * * "Balance the Budget!" WWW: http://village.ios.com/~gsp/ = * $**************************************************************************= $ ---------- Forwarded message ---------- Date: Tue, 6 Feb 1996 20:11:13 EST From: MONEY Daily To: MONEY Daily summary of news affecting your finances Subject: MONEY Daily: How to keep the spam off your e-mail plate Wednesday, February 7, 1996 How to keep the spam off your e-mail plate by Wilson Smith Bulk e-mail -- unaffectionately known on the=20 Internet as "spam" -- has been shunned, scorned and=20 reviled by anyone unlucky enough to find his e-mail=20 box overflowing with trashy ads. Now the spammers=20 are trying to present themselves as responsible=20 direct marketers, and are actively pitching their=20 services to small businesses and entrepreneurs. But=20 for millions of Internet users, they remain an=20 annoyance -- and we describe below how to avoid=20 eating what they serve. First appearing as unwanted postings on Internet=20 news groups, spam has migrated into broader=20 Internet communications, namely e-mail. With its=20 roots in the crudest and most transparent=20 matchbook-cover-style pitches and get-rich-quick=20 schemes, spam's tawdry reputation means it has a=20 long way to go before it's as accepted and welcome=20 as a Neiman-Marcus or L.L. Bean catalog. But some=20 in the industry claim they are trying. Promo Enterprises in Philadelphia=20 , for one, is a=20 high-profile, up-front company that says=20 "responsible bulk e-mail" has a place in the online=20 world. Its Web site brags not only about the low=20 cost, the high response rate, and the speedy=20 delivery, but also that the responsible direct=20 marketer can sleep a little easier knowing it's=20 also "environmentally friendly. Unlike postal mail=20 and broadcast faxing, no paper is used." Given such compassion for nature's precious=20 resources, what is it about spam that so irritates=20 people? A recent Internet Company report on so- called Postage-Due Marketing=20 points out that in more traditional direct- marketing and advertising, the cost of the=20 advertising is borne solely by the advertiser. In=20 the case of bulk e-mail, however, the cost is=20 shared by both advertiser and consumer. "Some pay=20 hourly charges for information and some pay per=20 message," writes report author Robert Raisich. "But=20 each Internet subscriber pays in some way for the=20 information they receive." "To fully appreciate why Postage-Due Marketing=20 raises the ire of the global Internet community,"=20 he continues, "ask yourself whether you would=20 accept a collect call from a telemarketer or an=20 advertising circular that arrived postage due. Or,=20 if you spent an entire evening consumed with calls=20 from telemarketers while you waited for an=20 important call." However annoying to recipients, spam's appeal to=20 advertisers is undeniable. It offers unprecedented=20 access to an immense Internet audience at=20 exceedingly low cost. If you want to reach half a=20 million people with up to 40 lines of advertising=20 text, Promo Enterprises will charge you $700, a --=20 get this! -- 14,000% savings off the equivalent=20 postal mailing rate of $100,000. Or, if you're on a=20 tight budget, it costs a mere $79 to have a two- line description of your Web site included in a=20 weekly mailing of Web addresses. What sorts of advertisers are using bulk e-mailers=20 like Promo Enterprises to reach out and touch=20 everyone? A recent survey found a tone reminiscent=20 of spam's early days. Some samples: * "E n e r g y !!! Give yourself the potential=20 for the energy you need to fulfill your goals. Find=20 out why over a Quarter Million people believe Super=20 Blue Green(tm) Algae to be a PERFECT FOOD. Hidden=20 within the miracle of this algae lies..." * "STS - GROUND FLOOR in the best pre-paid=20 calling card company. We offer 5 different ways to=20 increase your income and TOTALLY ELIMINATE YOUR=20 LONG DISTANCE PHONE BILLS...." * "A-LIST(tm). This is a very different=20 program, so pay close attention. You can make as=20 much as $160 your first month and $330 residual=20 income every month thereafter with only 6 people=20 total in your network, i.e., you sponsor two who=20 sponsor two each...." So what's changed? The thing that distinguishes a=20 setup like Promo Enterprises from its precursors is=20 this: rather than duck-and-run after flinging their=20 messages into the ether, these bulk e-mailers have=20 created businesses which they hope will be around=20 for the long haul. To prove it, they honor requests=20 to remove your name and address from their mailing=20 lists. Promo simply asks you to send a message to=20 remove@cyber-promo.com. What should you do if you find yourself plagued by=20 spam from an outfit that doesn't tell you how to=20 get off their list? If you're using a commercial online service like=20 America Online, CompuServe, Microsoft Network, or=20 Prodigy, you can forward a copy of the message to=20 your postmaster asking that unsolicited mail from=20 the outfit be stopped. Postmaster@aol.com, for=20 instance, replies to complaints about bulk e-mail=20 with detailed instructions on how to get off the=20 list. In addition, the net-abuse-faq posted to the=20 Internet newsgroup news.admin.net-abuse.misc=20 (devoted to the=20 discussion of various forms of Internet abuse)=20 suggests that "you can always complain about=20 unsolicited e-mail to both the bozo that sent it to=20 you and the bozo's postmaster. To write to a=20 postmaster, just substitute 'postmaster' for the=20 perp's username in their address (e.g., change=20 bozo@otherwise.lovely.com to=20 postmaster@otherwise.lovely.com). Make sure you are=20 brief and polite with postmasters, include a copy=20 of the e-mail you received, and leave the subject- line intact (in case the postmaster wants to set up=20 an auto-responder)."=20 Finally, where do these guys get their gigantic=20 lists of e-mail addresses in the first place?=20 Answer: all over -- newsgroup posts, chat rooms,=20 Internet directories, bulletin boards, and mailing=20 lists (MONEY Daily, for the record, has done its=20 best to ensure the security of its Internet mailing=20 list by disabling the command that would normally=20 generate a list of subscribers).=20 E-mail's relatively new-found popularity means that=20 the rules haven=B9t been agreed upon or formalized.=20 This will ultimately have to change, much the way=20 the flow of junk faxes slowed as laws were passed=20 to control unsolicited fax advertisements. For now,=20 the only way to keep an e-mail address truly safe=20 is 1) not to disclose it anywhere and 2) never use=20 it. In other words, if you're going to interact=20 online, expect to taste a little spam. For further web-formation, visit: Blacklist of Internet Advertisers news.admin.net-abuse.misc Postage-Due Marketing, an Internet Company White=20 Paper by Robert Raisch =20 Marketwatch for Tuesday, February 6, 1996 Dow Jones Industrial Average: up 52.02 to 5459.61 New York Stock Exchange Advances: 1390 Declines: 938 Volume: 469 million shares NASDAQ Composite: up 5.74 to 1089.08 S&P 500 Index: up 4.90 to 646.33 30-year Treasury bond yield: down 1 basis point to=20 6.13% London gold (afternoon fix): down $2.50 to $412.30 ------------------ SHARE YOUR OPINION ------------------ Check out discussions of topics in the Daily on=20 MONEY Online's bulletin board: http://www.pathfinder.com/boards/0003/ In addition, comments may be sent to Kevin McKean=20 or to Doug Dundas=20 . =20 ------------------------ SUBSCRIPTION INFORMATION ------------------------ TO ADD YOUR NAME TO THE MAILING LIST for Money=20 Daily, use any browser to reach the latest edition=20 on the Web at http://pathfinder.com/money/moneydaily/latest.html and click on the subscribe hotlink. Alternatively,=20 you may send an e-mail to this address: listproc@pathfinder.com It doesn't matter what the subject field of the=20 message says, but the body of the message should say=20 only: subscribe moneydaily Your Name For example, subscribe moneydaily Judy Doe The mailing program will automatically add your e-mail=20 address to the list. TO REMOVE YOUR NAME FROM THE MAILING LIST, point your=20 browser to http://pathfinder.com/money/moneydaily/unsubscribe.html Or you can send an e-mail to listproc@pathfinder.com. It=20 doesn't matter what the subject field of the message says, but=20 the body of the message should say only: unsubscribe moneydaily The mailing program will automatically remove your=20 e-mail address from the list. Thanks for signing up for the Money Daily! From list-managers-owner Wed Feb 7 20:24:07 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id TAA23649 for list-managers-outgoing; Wed, 7 Feb 1996 19:43:24 -0800 (PST) Received: from bottom.MTS.Net (top.mts.net [205.200.16.65]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id TAA23631; Wed, 7 Feb 1996 19:43:18 -0800 (PST) Received: from [204.112.33.145] (DialPort06.TKM.MB.CA [204.112.33.145]) by bottom.MTS.Net (8.7/8.7) with SMTP id TAA26056; Wed, 7 Feb 1996 19:50:41 -0600 Date: Wed, 7 Feb 1996 19:50:41 -0600 Message-Id: <199602080150.TAA26056@bottom.MTS.Net> X-Sender: cory@mailhub.mts.net Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: list-managers@GreatCircle.COM From: cory@MTS.Net (Cory Lewis) Subject: seeking sport list managers Cc: majordomo-users@GreatCircle.COM Sender: list-managers-owner@GreatCircle.COM Precedence: bulk At my request my service provider has just created several closed lists related to basketball, ice hockey, international football (soccer), and baseball. Now I am seeking a few people with sufficient knowledge of, and experience managing, mail lists to manage these lists. I am certain the requirements of this role exceed my abilities. The only compensation offered is membership in the closed list or lists managed. These are majordomo lists. If you may be interested in serving as the manager of one or more of these lists please contact me through my private address of cory@mts.net Due to probable formating problems please do not forward an entire resume. However a brief description of your knowledge and experience relating to managing mail lists, a personal history including your interest in the relevant sport, and two character references would be helpful. Thank you for your attention to this inquiry. Cory Lewis cory@mts.net From list-managers-owner Wed Feb 7 20:38:38 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id UAA26909 for list-managers-outgoing; Wed, 7 Feb 1996 20:36:25 -0800 (PST) Received: from schoneal.com (wildride.schoneal.com [206.81.38.2]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id UAA26896 for ; Wed, 7 Feb 1996 20:36:20 -0800 (PST) Received: (from meo@localhost) by schoneal.com (8.6.11/8.6.11) id WAA03967; Wed, 7 Feb 1996 22:36:28 -0600 Message-Id: <199602080436.WAA03967@schoneal.com> Subject: Re: Class assignments revisited... To: rowe@lepomis.psych.upenn.edu (Mickey Rowe) Date: Wed, 7 Feb 1996 22:36:28 -0600 (CST) Cc: List-Managers@GreatCircle.COM In-Reply-To: From: meo@schoneal.com (Miles O'Neal) Reply-To: meo@schoneal.com (Miles O'Neal) Organization: Schober O'Neal, Inc / Net Ads X-WWW-URL: http://www.schoneal.com/~meo/ X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Mickey Rowe said... | |What I'd like to know is: what can we do to advertise to potential |instructors that they shouldn't create such assignments? Surely there are journals and/or societies we can write to, explaining the problem. Meanwhile, perhaps we can start hitting the offending schools, and explaining *as a group* why this is not a good idea. Very politely showing them how it feels. Also, if they don't respond *immediately* with an apology and calling it off, we can call as well as email their departments, and move up the food chain as necessary. We really need a good analogy. "It's like telling a bumch of people the prof doesn't know to stop by and use the prof's flower beds a s a bathroom." Something to make the point. -Miles From list-managers-owner Wed Feb 7 20:53:52 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id UAA27062 for list-managers-outgoing; Wed, 7 Feb 1996 20:38:43 -0800 (PST) Received: from schoneal.com (wildride.schoneal.com [206.81.38.2]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id UAA27044 for ; Wed, 7 Feb 1996 20:38:36 -0800 (PST) Received: (from meo@localhost) by schoneal.com (8.6.11/8.6.11) id WAA04006; Wed, 7 Feb 1996 22:38:29 -0600 Message-Id: <199602080438.WAA04006@schoneal.com> Subject: Re: Class assignments revisited... To: paulh@hamjudo.com (Paul Haas) Date: Wed, 7 Feb 1996 22:38:29 -0600 (CST) Cc: rowe@lepomis.psych.upenn.edu, List-Managers@GreatCircle.COM In-Reply-To: from "Paul Haas" at Feb 7, 96 02:45:17 pm From: meo@schoneal.com (Miles O'Neal) Reply-To: meo@schoneal.com (Miles O'Neal) Organization: Schober O'Neal, Inc / Net Ads X-WWW-URL: http://www.schoneal.com/~meo/ X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk As part of the long term solutrion, suggest that profs get their CS people to set up lists for them, and keep the whole thing inhouse. Then once they understand the basics, they can decide for themselves whether they want to actually participate in any real world lists. From list-managers-owner Fri Feb 9 10:14:51 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id KAA20956 for list-managers-outgoing; Fri, 9 Feb 1996 10:00:31 -0800 (PST) Received: from kitsune.swcp.com (swcp.com [198.59.115.2]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id KAA20951 for ; Fri, 9 Feb 1996 10:00:27 -0800 (PST) Received: (from lazlo@localhost) by kitsune.swcp.com (8.6.9/8.6.9) id KAA01455 for list-managers@greatcircle.com; Fri, 9 Feb 1996 10:59:41 -0700 From: Lazlo Nibble Message-Id: <199602091759.KAA01455@kitsune.swcp.com> Subject: pobox.com? To: list-managers@greatcircle.com (lm) Date: Fri, 9 Feb 1996 10:59:41 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Can anyone here suggest a commerical provider that's a good place to host mailing lists from? I don't need (or want to pay for) a conventional internet access account on a machine -- I just need a site that can host lists, preferably with majordomo, for a reasonable price. -- ::: Lazlo (lazlo@swcp.com; http://www.swcp.com/lazlo) From list-managers-owner Fri Feb 9 17:39:07 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id RAA14862 for list-managers-outgoing; Fri, 9 Feb 1996 17:32:51 -0800 (PST) Received: from tango.rahul.net (tango.rahul.net [192.160.13.5]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id RAA14828 for ; Fri, 9 Feb 1996 17:32:43 -0800 (PST) Received: from bolero.rahul.net by tango.rahul.net with SMTP id AA18725 (5.67b8/IDA-1.5 for ); Fri, 9 Feb 1996 17:31:55 -0800 Received: from jive.rahul.net by bolero.rahul.net with SMTP id AA29398 (5.67b8/IDA-1.5 for ); Fri, 9 Feb 1996 17:31:54 -0800 From: Steve Portigal Received: by jive.rahul.net (5.67b8/jive-a2i-1.0) id AA16407; Fri, 9 Feb 1996 17:31:50 -0800 Message-Id: <199602100131.AA16407@jive.rahul.net> Subject: Yet another forged subscription To: list-managers@greatcircle.com Date: Fri, 9 Feb 1996 17:31:50 -0800 (PST) Organization: GVO - Interface Design Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >From jlagator@grove.ufl.edu Thu Feb 8 22:37:40 1996 Return-Path: Received: from leonardo.lls.se by tempest.cis.uoguelph.ca (NX5.67d/NX3.0M) id AA05499; Thu, 8 Feb 96 22:37:40 -0500 Received: from a (sefl.satelnet.org [204.157.227.55]) by leonardo.lls.se (8.6.11/iko.1.0) with SMTP id EAA27583 for undercover-request@tempest.cis.uoguelph.ca; Fri, 9 Feb 1996 04:33:03 +0100 Date: Fri, 9 Feb 1996 04:33:03 +0100 From: jlagator@grove.ufl.edu Message-Id: <199602090333.EAA27583@leonardo.lls.se> Apparently-To: undercover-request@tempest.cis.uoguelph.ca Status: R subscribe From list-managers-owner Fri Feb 9 20:54:04 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id UAA20519 for list-managers-outgoing; Fri, 9 Feb 1996 20:39:58 -0800 (PST) Received: from netcom14.netcom.com (netcom14.netcom.com [192.100.81.126]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id UAA20514 for ; Fri, 9 Feb 1996 20:39:54 -0800 (PST) Received: from [192.0.2.1] by netcom14.netcom.com (8.6.12/Netcom) id UAA26173; Fri, 9 Feb 1996 20:38:14 -0800 X-Sender: outings@netcom3.netcom.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 9 Feb 1996 21:40:49 -0700 To: list-managers@greatcircle.com From: outings@netcom.com (Steve Outing) Subject: More forged subscriptions Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Here's another batch of forged subscriptions that just came into my lists tonight. (sigh) senate house heymtv kuppe That last one is interesting (assuming that I'm right and it's a forgery). bvsd is Boulder Valley School District in Boulder, Colorado, where I happen to live. A clue to identity of our mysterious pranksters, perhaps? ---------------------------------------------------------------------------- Steve Outing Planetary News LLC outings@netcom.com Boulder, Colorado, USA owner-online-newspapers@marketplace.com voice: 303-543-7810 owner-online-news@marketplace.com fax/voice: 303-543-8550 Consulting services for the newspaper new media industry ---Read my Stop The Presses! column: http://www.mediainfo.com/ep/stop.htm--- From list-managers-owner Fri Feb 9 23:23:59 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id XAA28368 for list-managers-outgoing; Fri, 9 Feb 1996 23:12:16 -0800 (PST) Received: from vger.tripcom.com (vger.tripcom.com [198.5.220.33]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id XAA28347 for ; Fri, 9 Feb 1996 23:12:11 -0800 (PST) Received: (from adam@localhost) by vger.tripcom.com id BAA16968 for list-managers@greatcircle.com; Sat, 10 Feb 1996 01:11:25 -0600 From: Adam Horwitz Message-Id: <199602100711.BAA16968@vger.tripcom.com> Subject: Subscription from "your_email_address" To: list-managers@greatcircle.com Date: Sat, 10 Feb 1996 01:11:22 -0600 (CST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Here's a subscription problem I haven't seen discussed... I hope it brightens your day. Forwarded message: > From Majordomo-Owner@Tripcom.com Sat Feb 10 00:49:05 1996 > Date: Sat, 10 Feb 1996 00:49:04 -0600 > Message-Id: <199602100649.AAA16313@vger.tripcom.com> > To: triplets-digest-approval > From: Majordomo@Tripcom.com > Subject: SUBSCRIBE triplets-digest > Reply-To: Majordomo@Tripcom.com > > -- > > your_email_address@ornl.gov has been added to triplets-digest. > No action is required on your part. -- Adam Horwitz (708) 778-9531 Tripcom Systems Inc. adam@tripcom.com From list-managers-owner Sat Feb 10 04:24:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id EAA11054 for list-managers-outgoing; Sat, 10 Feb 1996 04:20:39 -0800 (PST) Received: from mycroft.GreatCircle.COM (mycroft.greatcircle.com [198.102.244.35]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id EAA11049 for ; Sat, 10 Feb 1996 04:20:36 -0800 (PST) Received: by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-960123) id EAA02567; Sat, 10 Feb 1996 04:17:01 -0800 Received: from relay-4.mail.demon.net(158.152.1.108) by mycroft via smap (V1.3mjr) id sma002564; Sat Feb 10 04:16:30 1996 Received: from post.demon.co.uk ([158.152.1.72]) by relay-4.mail.demon.net id at16585; 10 Feb 96 12:17 GMT Received: from bclimser.demon.co.uk ([158.152.80.60]) by relay-3.mail.demon.net id aa10479; 10 Feb 96 12:07 GMT From: Sanwar Ali Organization: BCL Immigration Services To: list-managers@greatcircle.com Date: Sat, 10 Feb 1996 11:47:53 +0000 Subject: Recommendations for Web-Site - Archive for New List Reply-to: sanwar@bclimser.demon.co.uk X-mailer: Pegasus Mail for Windows (v2.23) Message-ID: <823954029.10479.0@bclimser.demon.co.uk> Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Hi I am setting up a new list. I have found a server for the list. However, I would also like to have a Web-Site for the list and for other material. Has anybody got recommendations for: 1. A reasonably priced Web Site; I probably dont need more than 1 MB at the moment but it will probably increase rapidly over the year. 2. Excellent access World-Wide. I have heard horror stories of delays in access or no access at all. 3. My list will be on pobox. I wonder how people have found their Web space services. Any help would be much appreciated. BTW, ignore the http add at the bottom of my sig! All the best. -- Sanwar Ali Managing Partner BCL Immigration Services Acorn House 74-94 Cherry Orchard Road Croydon, Surrey CR0 6BA, UK. Telephone: +44 181 680 9621 or +44 181 681 8339 Fax: +44 181 667 0378 e-mail: sanwar@bclimser.demon.co.uk, sanwar@pobox.com WWW: http://www.algroup.co.uk/wpb/bcl From list-managers-owner Sat Feb 10 18:00:01 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id RAA09481 for list-managers-outgoing; Sat, 10 Feb 1996 17:47:59 -0800 (PST) Received: from earth.usa.net (earth.usa.net [192.156.196.1]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id RAA09461 for ; Sat, 10 Feb 1996 17:47:52 -0800 (PST) Received: (from jdebruyn@localhost) by earth.usa.net (8.6.10/8.6.10) id SAA15149 for list-managers@GreatCircle.COM; Sat, 10 Feb 1996 18:47:09 -0700 From: John Debruyn Reply-To: John Debruyn Message-Id: <199602110147.SAA15149@earth.usa.net> Subject: How large can a list get To: list-managers@GreatCircle.COM Date: Sat, 10 Feb 1996 18:47:09 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Hi: I started with majordomo back with version 1.2 something, which was really a wonderful improvement over the manual list set up I began with where the owner edited the list manually. Following this list has been a great help. I am working with a new set of lists where they may evolve into several thousand subscribers. I would like to know how large (long) a list is currently being supported by Majordomo. The Webcom site which got out of the server business was unable to maintain a list that got up to about 2,000 subscribers. I am hoping that was an abberation. Thanks, John -- John DeBruyn, Denver, Colorado, The Mile High City, USA (jdebruyn@usa.net) -- John DeBruyn, Denver, Colorado, The Mile High City, USA (jdebruyn@usa.net) From list-managers-owner Sat Feb 10 21:39:37 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id VAA17330 for list-managers-outgoing; Sat, 10 Feb 1996 21:26:13 -0800 (PST) Received: from sol.wvs.com (sol.wvs.com [204.247.80.10]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id VAA17325 for ; Sat, 10 Feb 1996 21:26:09 -0800 (PST) Received: by sol.wvs.com (5.x/SMI-SVR4) id AA16641; Sat, 10 Feb 1996 21:24:09 -0800 Received: (from news@localhost) by zorch.sf-bay.org (8.6.11/8.6.9) id UAA14152 for list-managers@greatcircle.com; Sat, 10 Feb 1996 20:26:07 -0800 Newsgroups: zorch.lists.list-managers Path: zorch.sf-bay.org!scott From: scott@zorch.sf-bay.org (Scott Hazen Mueller) Subject: Stand-alone subsub filter? Reply-To: scott@zorch.sf-bay.org Organization: At Home; Salida, CA Message-Id: X-Nntp-Posting-Host: localhost.sf-bay.org Date: Sun, 11 Feb 1996 04:26:04 GMT Apparently-To: list-managers@greatcircle.com Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Does anyone have a stand-alone (i.e. not part of a package) filter that checks that submissions are from subscribers? My lists got Krazy Kevined today, and I want to prevent a repeat. Thanks, \scott From list-managers-owner Sun Feb 11 04:39:31 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id EAA03640 for list-managers-outgoing; Sun, 11 Feb 1996 04:31:05 -0800 (PST) Received: from merlion.singnet.com.sg (merlion.singnet.com.sg [165.21.1.10]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id EAA03635 for ; Sun, 11 Feb 1996 04:30:56 -0800 (PST) Received: (from edmonds@localhost) by merlion.singnet.com.sg (8.6.12/8.6.11) id UAA06212; Sun, 11 Feb 1996 20:30:08 +0800 Date: Sun, 11 Feb 1996 20:30:07 +0800 (SST) From: Edmonds Subject: Pobox com To: List-Managers@GreatCircle.COM In-Reply-To: <199602110900.BAA25476@miles.greatcircle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk 'lo all, I have a list, BloodQuill, on pobox.com and I found them to be excellant if you don't have access to a server or want to be very technoid over things. It cost me $50 US for the year, with no limit on memebrship - though they did stay if it did get subjectively speaking too much, which would be a hundred plus messages a day I'd guess, they'd have to reajust the price. It's majordomo and there's a web interface which I find handy for doing admin things all at once instead of through commands in emails. Enough tweaking of options, closed, private, limits etc, and all in all simple enough. I rang Pobox in the middle of the night (time zones) once and the kind of groggy guy on the other side was helpful after he woke up . Hope that helps, be happy to answer any other questions. They were the only commercial list providor I cam across when I set it up, Decmeber 1995. Now I'm about to set up my own server offering mailing lists and stuff, and I'm pretty sure if you did a search you'd be able to find some other places. Still, pobox seem fairly stable and nice. Dale Edmonds whale@pobox.com http://www.pobox.com/~whale (mail redirection thing. Very useful) From list-managers-owner Sun Feb 11 10:58:13 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id KAA11538 for list-managers-outgoing; Sun, 11 Feb 1996 10:47:08 -0800 (PST) Received: from chardonnay.niagara.com (chardonnay.niagara.com [204.97.192.2]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id KAA11533 for ; Sun, 11 Feb 1996 10:47:05 -0800 (PST) Received: from [204.97.192.121] by chardonnay.niagara.com via SMTP (950911.SGI.8.6.12.PATCH825/931108.SGI.ANONFTP) for id NAA14967; Sun, 11 Feb 1996 13:46:16 -0500 Date: Sun, 11 Feb 1996 13:46:16 -0500 X-Sender: selene@chardonnay.niagara.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: List-Managers@GreatCircle.COM From: selene@niagara.com (Rowan Shirkie) Subject: Bad news -- E-cards from Heineken Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Some misguided person sent my entire mailing list an "e-card" from the Heineken World Wide Web server in the Netherlands. A silly .gif file with a message. The Heineken site seems set up so you that you cannot contact the webmaster or anyone at Heineken -- but visitors can fling messages/graphics files to any e-mail address. (Most of the postcard sites I've seen send a simple text notice that you follow up (or not) by visiting the WW site to see the message.) I did try to contact "postmaster@Heineken.nl" and "Heineke3@www.Heineken.com" saying that this was a BAD IDEA and was creating another set of net pests. Anyone here have a similar list experience? Or have any other suggestions on how to deal with this? If this technique proliferates, blocking originating addresses one-by-one in Majordomo seems futile. >Date: Sat, 10 Feb 1996 23:52:26 GMT >From: Heineke3@www.Heineken.com >Mime-Version: 1.0 >Subject: E-card from Gilbert.v.Houten@inter.nl.net [SNIP] > >This card was send to you by Gilbert.v.Houten@inter.nl.net. > >The card has been generated by the Heineken World Wide Web server. >(http://www.Heineken.nl/) > > >Content-Type: image/gif; name="e-card-59578.gif" >Content-Disposition: inline; filename="e-card-59578.gif" >Content-MD5: P6ADyMwIpzm5+dnsDZCOsg== ============================ Rowan Shirkie-Selene Communications [ selene@niagara.com | VOX: + 905.687.9805 | s-mail: 12 - 111 Fourth Avenue, Suite 200 | St. Catharines, ON, Canada L2S 3P5 ] From list-managers-owner Sun Feb 11 12:13:21 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id LAA12973 for list-managers-outgoing; Sun, 11 Feb 1996 11:58:10 -0800 (PST) Received: from outsider.bolis.com (bolis.com [204.153.195.10]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id LAA12968; Sun, 11 Feb 1996 11:58:01 -0800 (PST) Received: from hock.bolis.sf-bay.org (root@hock.bolis.com [199.165.142.10]) by outsider.bolis.com (8.7.3/8.7.3) with SMTP id LAA04365; Sun, 11 Feb 1996 11:51:30 -0800 Received: from amillar by hock.bolis.sf-bay.org with smtp (Smail3.1.28.1 #6) id m0tlhfE-000UpoC; Sun, 11 Feb 96 11:42 PST Message-Id: Comments: Authenticated sender is From: "Alan Millar" Organization: The Bolis Group To: John Debruyn , list-managers@GreatCircle.COM Date: Sun, 11 Feb 1996 11:45:03 -800 Subject: Re: How large can a list get CC: majordomo-users@GreatCircle.COM X-mailer: Pegasus Mail for Windows (v2.01) Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On 10 Feb 96 at 18:47, John Debruyn wrote: > I am working with a new set of lists where they may evolve into several > thousand subscribers. I would like to know how large (long) a list is > currently being supported by Majordomo. The Webcom site which got out > of the server business was unable to maintain a list that got up to about > 2,000 subscribers. I am hoping that was an abberation. This conversation perhaps should move to "majordomo-users", although the performance issues overlap with other list mgmt software. The maximum size of a Majordomo list depends on machine load. That comes from two factors: how much work it is for Majordomo to add and remove people from the list, and how much work it is for your mail transport to deliver the messages. In all the cases I've heard discussed, the first part (subscriptions) aren't usually the problem; it's usually delivery that's the problem. Majordomo doesn't actually deliver messages; sendmail (or whatever you have for a mailer) does. So the performance issues for Majordomo lists are the same for manually-administered lists or any that depend on the system mailer. There are a number of ways to deal with this: - Go to a daily digest. One message a day instead of dozens. - Get the latest sendmail. Connection caching and related new features help performance. - Sort your list by domain. This can help take advantage of any optimizations in the mailer. - Queue your messages instead of delivering immediately. It may not speed up delivery, but it helps system load. - Break your list into smaller chunks which can be processed independently. I know of some large lists that are administered by hand because of the need to split them, but there are a number of things you can do to automate it. (ObSendmail: "smail" can set a maximum number of addresses per message; I can't find a corresponding setting in sendmail. Anyone know?) - Use bulk_mailer. It splits the list into chunks and sorts by domain. - Use more than one machine. I run Majordomo proper one one machine and do actual delivery on another. Some people split their lists across multiple delivery machines. All that having been said, I don't have any 2000-member lists myself. Anyone else care to comment on actual use? - Alan ---- Alan Millar amillar@bolis.SF-Bay.org System Administrator http://www.bolis.com Batteries not included. From list-managers-owner Sun Feb 11 12:57:48 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id MAA14004 for list-managers-outgoing; Sun, 11 Feb 1996 12:39:47 -0800 (PST) Received: from VM.SE.LSOFT.COM (vm.se.lsoft.com [205.186.43.254]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id MAA13999 for ; Sun, 11 Feb 1996 12:39:41 -0800 (PST) Message-Id: <199602112039.MAA13999@miles.greatcircle.com> Received: from VM.SE.LSOFT.COM by VM.SE.LSOFT.COM (IBM VM SMTP V2R3) with BSMTP id 9695; Sun, 11 Feb 96 15:38:53 EST Received: from VM.SE.LSOFT.COM (NJE origin ERIC@SEARN) by VM.SE.LSOFT.COM (LMail V1.2b/1.8b) with RFC822 id 6546; Sun, 11 Feb 1996 15:38:53 -0500 Date: Sun, 11 Feb 1996 15:27:54 EST From: Eric Thomas Subject: Re: How large can a list get To: list-managers@GreatCircle.COM cc: majordomo-users@GreatCircle.COM In-Reply-To: Message of Sun, 11 Feb 1996 11:45:03 -800 from list-managers-owner@GreatCircle.COM Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On Sun, 11 Feb 1996 11:45:03 -800 Alan Millar said: >The maximum size of a Majordomo list depends on machine load. That comes >from two factors: how much work it is for Majordomo to add and remove >people from the list, and how much work it is for your mail transport to >deliver the messages. > >In all the cases I've heard discussed, the first part (subscriptions) >aren't usually the problem; it's usually delivery that's the problem. This isn't necessarily true. Try the following experiment: 1. Create a dummy list with 1,000 subscribers (dummy addresses are fine), and, while your system is otherwise idle, send 10 SIGNOFF requests from addresses near the middle of the list. This will measure the impact on Majordomo of 1% of the subscribers deciding to leave the list shortly after a posting (large lists are very often announcement lists, so users may not know what the contents will be until they get their first posting). Incidentally, 1% is a very conservative estimate. 2. Create a dummy list with 10,000 subscribers and submit 100 SIGNOFF requests. 3. Create a dummy list with 100,000 subscribers and send 1,000 SIGNOFF requests. For test #3, you will want to save any open editor window, notify users, etc. Your system may or may not survive the experiment :-) Eric From list-managers-owner Sun Feb 11 13:39:11 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id NAA14748 for list-managers-outgoing; Sun, 11 Feb 1996 13:32:38 -0800 (PST) Received: from ruby.ora.com (ruby.ora.com [198.112.208.25]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id NAA14743 for ; Sun, 11 Feb 1996 13:32:34 -0800 (PST) Received: (from jerry@localhost) by ruby.ora.com (8.6.12/8.6.11) id NAA15809; Sun, 11 Feb 1996 13:31:53 -0800 Message-Id: <199602112131.NAA15809@ruby.ora.com> From: Jerry Peek Date: Sun, 11 Feb 1996 13:31:53 EST In-Reply-To: selene@niagara.com (Rowan Shirkie) "Bad news -- E-cards from Heineken" (Feb 11, 13:46) X-Mailer: Mail User's Shell (7.2.0 10/31/90) To: List-Managers@GreatCircle.COM Subject: Re: Bad news -- E-cards from Heineken Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On Feb 11, 13:46, Rowan Shirkie wrote: } Some misguided person sent my entire mailing list an "e-card" from the } Heineken World Wide Web server in the Netherlands. A silly .gif file with a } message. ... } If this technique proliferates, blocking } originating addresses one-by-one in Majordomo seems futile. Has anyone set up Majordomo or other MLMs to route messages with certain MIME contents to the list owner for approval? For instance, this message has really suspicious headers (in this case, in a body part): } >Content-Type: image/gif; name="e-card-59578.gif" } >Content-Disposition: inline; filename="e-card-59578.gif" You could also search for big chunks of text without much whitespace -- like base64 or uuencoded text. --Jerry Peek, jerry@ora.com From list-managers-owner Mon Feb 12 15:09:56 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id PAA06179 for list-managers-outgoing; Mon, 12 Feb 1996 15:04:23 -0800 (PST) Received: from lepomis.psych.upenn.edu (LEPOMIS.PSYCH.UPENN.EDU [130.91.68.34]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id PAA06174 for ; Mon, 12 Feb 1996 15:04:18 -0800 (PST) Received: by lepomis.psych.upenn.edu (AIX 3.2/UCB 5.64/4.03) id AA22898; Mon, 12 Feb 1996 18:00:58 -0500 Date: Mon, 12 Feb 1996 18:00:58 -0500 From: rowe@lepomis.psych.upenn.edu (Mickey Rowe) Message-Id: <9602122300.AA22898@lepomis.psych.upenn.edu> To: list-managers@greatcircle.com Subject: scooby.pubnix.org Sender: list-managers-owner@GreatCircle.COM Precedence: bulk WRT my previous message about the spammer who created his own list by acquiring my list's subscribers: I've now been in contact with the postmaster at scooby.pubnix.com and he's assured me that he's removing merc@scooby's privileges on that machine. If merc@scooby.pubnix.org is on any of your mailing lists, you should remove him. -- Mickey Rowe (rowe@lepomis.psych.upenn.edu) From list-managers-owner Tue Feb 13 10:10:51 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id JAA14988 for list-managers-outgoing; Tue, 13 Feb 1996 09:31:58 -0800 (PST) Received: from hal.nes.com (hal.nes.com [205.153.28.50]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id JAA14983 for ; Tue, 13 Feb 1996 09:31:55 -0800 (PST) Received: by hal.nes.com with VINES-ISMTP; Tue, 13 Feb 96 12:31:10 EST Date: Tue, 13 Feb 96 12:31:12 EST Message-ID: X-Priority: 3 (Normal) To: From: (Philip Kubat) Subject: Auto replys Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I have question in reguard how mailing list should or do handle reply/returned mail. We are changing our domain and I would like to set up a autoreply for the old domain. I do not want to flood mail-list that many of my users are on with useless mail. Is there "proper" way to handle this? Thanks!! Philip Kubat New England Systems 60 First Avenue Waltham, MA 02154 617-672-8466 From list-managers-owner Tue Feb 13 12:44:18 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id MAA18803 for list-managers-outgoing; Tue, 13 Feb 1996 12:33:57 -0800 (PST) Received: from natashya.eden.com (natashya.eden.com [199.171.21.14]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id MAA18797 for ; Tue, 13 Feb 1996 12:33:52 -0800 (PST) Received: from matrix.eden.com (lwb@matrix.eden.com [199.171.21.1]) by natashya.eden.com (8.7.3.1/8.7.1.1) with ESMTP id OAA15589 for ; Tue, 13 Feb 1996 14:33:09 -0600 (CST) From: Lance Bledsoe Received: (from lwb@localhost) by matrix.eden.com (8.7.1/8.7.1.1) id OAA21514 for list-managers@GreatCircle.COM; Tue, 13 Feb 1996 14:33:09 -0600 (CST) Message-Id: <199602132033.OAA21514@matrix.eden.com> Subject: Majordomo List Server Site Needed... To: list-managers@GreatCircle.COM Date: Tue, 13 Feb 1996 14:33:08 -0600 (CST) X-Mailer: ELM [version 2.5 PL0a8] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Hi, I'm looking for a low cost (free would be nice) site to host several small email lists mostly having to do with photography. I anticipate that there would be no more than 20-50 people on each list with realatively low traffic. Please let me know if you can help me... Thanks, Lance Bledsoe -- Lance Bledsoe, President Avalon Enterprises, Inc. / Bledsoe Photographic, Inc. 9004 Jolly Hollow Drive, Austin, TX 78750 USA, Phone: 512-257-2900 Email: lwb@Eden.com URL: http://www.Eden.com/~lwb From list-managers-owner Tue Feb 13 17:39:24 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id RAA26973 for list-managers-outgoing; Tue, 13 Feb 1996 17:30:27 -0800 (PST) Received: from emout08.mail.aol.com (emout08.mx.aol.com [198.81.11.23]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id RAA26968 for ; Tue, 13 Feb 1996 17:30:24 -0800 (PST) From: PMDAtropos@aol.com Received: by emout08.mail.aol.com (8.6.12/8.6.12) id UAA05944; Tue, 13 Feb 1996 20:29:31 -0500 Date: Tue, 13 Feb 1996 20:29:31 -0500 Message-ID: <960213202929_321312655@emout08.mail.aol.com> To: lstown-l@searn.sunet.se, list-managers@greatcircle.com Subject: Hardware/software problem on one AOL mail gateway, 12 Feb 1996 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I wanted to alert list owners who may have noticed a suddent, dramatic "no such user" response last night during normal list delivery to AOL: due to a combination of sudden catastrophic disk failure and programmer oversight, one of our mail gateway machines falsely identified all AOL users to which it was routing mail as not existing. The problem existed for at least four hours last night on one of our sixteen inbound gateways, so there's a reasonable chance that one of your lists may have been affected. I've been advised that the software problem has been fixed and that it should now properly handle any future hardware failures. Please accept my apologies on behalf of America Online for any inconvenience this may have caused. -- __ David B. O'Donnell (atropos@aol.net, PMDAtropos@aol.com, Atropos@gnn.com) \/ AOL Internet Feedback/Response/Information Team Manager, LISTSERV Manager Tel. 703/453-4000 x4255 FAX 703/453-4102 Pager 800/759-8888 PIN 128-5338 WWW: http://www.cais.com/atropos/ "The spam stops here." From list-managers-owner Wed Feb 14 00:54:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id AAA08530 for list-managers-outgoing; Wed, 14 Feb 1996 00:33:32 -0800 (PST) Received: from wilma.cs.utk.edu (WILMA.CS.UTK.EDU [128.169.94.141]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id AAA08525 for ; Wed, 14 Feb 1996 00:33:27 -0800 (PST) Received: from LOCALHOST by wilma.cs.utk.edu with SMTP (cf v2.11c-UTK) id DAA03365; Wed, 14 Feb 1996 03:32:43 -0500 Message-Id: <199602140832.DAA03365@wilma.cs.utk.edu> X-URI: http://www.cs.utk.edu/~moore/ From: Keith Moore To: pkubat@nes.com (Philip Kubat) cc: list-managers@greatcircle.com, moore@cs.utk.edu Subject: Re: Auto replys In-reply-to: Your message of "Tue, 13 Feb 1996 12:31:12 EST." Date: Wed, 14 Feb 1996 03:32:37 -0500 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > We are changing our domain and I would like to set up a autoreply for the > old domain. I do not want to flood mail-list that many of my users are on > with useless mail. >Is there "proper" way to handle this? a) send the mail to the envelope return address (SMTP MAIL FROM or the address in the Return-Path header, or the address in the From_ line at the top of the message...NOT the address in the From: or Reply-To: header) b) keep some state about who you send auto-replies to, and don't send repeated auto-replies to the same address within, say, 15 days. Keith Moore -------- Take the pledge! "I do not limit my speech to satisfy the whims of Congress." From list-managers-owner Wed Feb 14 01:54:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id BAA11612 for list-managers-outgoing; Wed, 14 Feb 1996 01:53:07 -0800 (PST) Received: from cs.umass.edu (freya.cs.umass.edu [128.119.40.195]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id BAA11598 for ; Wed, 14 Feb 1996 01:52:57 -0800 (PST) From: lmccarth@cs.umass.edu Received: from opine.cs.umass.edu by cs.umass.edu (5.65/Ultrix3.0-C) id AA19616; Wed, 14 Feb 1996 04:52:15 -0500 Received: (from lmccarth@localhost) by opine.cs.umass.edu (8.6.11/8.6.9) id EAA18269 for List-Managers@GreatCircle.COM; Wed, 14 Feb 1996 04:52:14 -0500 Message-Id: <199602140952.EAA18269@opine.cs.umass.edu> Subject: Bouncing subscriber addresses on web page To: List-Managers@GreatCircle.COM Date: Wed, 14 Feb 1996 04:52:13 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Personal introduction: I manage a list with 150+ subscribers using Majordomo, but approving subscriptions manually. The list deals with cryptographic programming. Being pretty new to the list management biz, I've been developing my own set of little coping techniques etc., and appreciating the wisdom of others. I had a simple idea about dealing with subscribers whose addresses bounce list mail. Since the WWW is a widely accessible out-of-email-band means of communication on the net, I decided to put up a web page with all the addresses I've had to remove from the list due to bouncing mail. Next to each address I include the precise reason that address was bouncing mail, at least according to the mailer-daemon(s). It's easily updated with some cutting-and- pasting from the bounce messages I get. This is still a pretty new experiment for me. I announced the page on my list, but I haven't had any feedback so far from the subscribers. I am wondering what more experienced list managers think about this idea. Has this approach been tried much before ? Are there any non-obvious problems or benefits I should consider ? In case you care, the bounce list is at http://www.cs.umass.edu/~lmccarth/coderpunks/bounce.html (BTW, I read the digest version of list-managers, so you should cc: me directly if you want a relatively prompt response from me.) Lewis -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMSGwqmf7YYibNzjpAQFQpQP/VccDq0dz+Evf21V843kfW7kvE5kramva fDj3aZzQWdaHMehirt3gGfT+HHucDgDU2Sz812qrkIsyftS2RBsmGr6NHRLeWlUI tIp0UXF5hFoaFOQjdIVaTpFLDwIpPQJqvpCx3rAi2PnyX9zI1O3xeJoXZ0nFyv0u tcDD51gChpQ= =+FWX -----END PGP SIGNATURE----- From list-managers-owner Wed Feb 14 07:54:53 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id HAA25707 for list-managers-outgoing; Wed, 14 Feb 1996 07:40:20 -0800 (PST) Received: from mhub1.tc.umn.edu (mhub1.tc.umn.edu [128.101.131.51]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id HAA25699 for ; Wed, 14 Feb 1996 07:40:15 -0800 (PST) Received: from maroon.tc.umn.edu by mhub1.tc.umn.edu; Wed, 14 Feb 96 09:39:34 -0600 Received: from dialup-2-153.gw.umn.edu by maroon.tc.umn.edu; Wed, 14 Feb 96 09:39:31 -0600 Date: Wed, 14 Feb 96 09:41:56 CST From: "Fred H Olson WB0YQM" Message-Id: <89440.fholson@maroon.tc.umn.edu> X-Mailer: Minuet1.0_Beta_19 Reply-To: Fred H Olson X-POPMail-Charset: English To: List-Managers@GreatCircle.COM Cc: listmgr@mtn.org Subject: Mail deliver error messages Sender: list-managers-owner@GreatCircle.COM Precedence: bulk The main list I manage is moving to an MLM at a different site and to our own domain so I'm rethinking how to set things up to facilitate managing it (and other lists)... Mail deliver error messages are one of the biggest pains of list management. Particularly when they are mixed in with one's personal / general / other mail... Has anyone got an easy way to segregate them easily? Part of the problem is that there is no standard format. Writing something smart enough to parse and summarize them is difficult because of this. (Some violate the programming design rule that you have to know how to do the task manually in a well defined way before you can write software to do it.... Never found an error message that was unintelligible? If so you're lucky.) As a first step I'd just like to get them in their own folder automatically (one folder per list) Anyone have a procmail routine to do just this? Do you have to rout them thru a sendmail alias to get something unique added to the header to sort on? Other ways of doing it? BTW Is there a standard name / acronym for mail deliver error messages? If not, how about MDEM's ? ^ ^ ^ ^ ************** NOTE to local list getting a copy of this. This message is being sent to the list List-Managers@GreatCircle.COM which is moderately to quite active (Active enough that I subscribe digest mode). Regretably a lot of discussion is about SPAM's but lots of other topics come up. Subscribers are managing lists using all flavors of MLM's (Mailing List Management software). Subs to: Majordomo@GreatCircle.COM with first line in body: Subscribe List-managers (Note no name at end) ************** -- ################################################################# I MOURN the assault on the First Amendment and protest the passage of the Communications "Decency" Amendment to the Telecom Bill" 2/9/96 See: URL: http://www.eff.org/blueribbon.html and URL: http://www.eff.org/pub/Alerts/blackpage_0296.alert ################################################################# ADDRESS CHANGE ADDRESS CHANGE ADDRESS CHANGE 1/25/96 Use this address: fholson@tc.umn.edu DO NOT USE THIS ADDRESS: fholson@uci.com Fred H. Olson (612)588-9532 Amateur radio: WB0YQM 1221 Russell Av N, Minneapolis,MN 55411 List manager of Cohousing-L (which will be moving soon) & Nbhd-tc From list-managers-owner Wed Feb 14 09:09:43 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id IAA27697 for list-managers-outgoing; Wed, 14 Feb 1996 08:49:15 -0800 (PST) Received: from rubble.west.ora.com (rubble.west.ora.com [198.112.209.191]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id IAA27692 for ; Wed, 14 Feb 1996 08:49:09 -0800 (PST) Received: by rubble.west.ora.com (4.1/SMI-4.1+JP-2.5) id AA01750; Wed, 14 Feb 96 08:49:24 PST From: Jerry Peek X-Mailer: MH 6.8.3 To: lmccarth@cs.umass.edu Cc: List-Managers@GreatCircle.COM Subject: Re: Bouncing subscriber addresses on web page References: <199602140952.EAA18269@opine.cs.umass.edu> In-Reply-To: Message from (lmccarth@cs.umass.edu ) of "Wed, 14 Feb 1996 04:52:13 -0500." Date: Wed, 14 Feb 1996 08:49:20 -0800 Message-Id: <1749.824316560@rubble.west.ora.com> Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On 14 February, lmccarth@cs.umass.edu wrote: > Since the WWW is a widely accessible out-of-email-band means of > communication on the net, I decided to put up a web page with all the > addresses I've had to remove from the list due to bouncing mail. Next to each > address I include the precise reason that address was bouncing mail, at least > according to the mailer-daemon(s). Neat idea. I see two problems with it, though: - One is privacy. Some people don't want their email addresses advertised. This might be too picky, though... - Another is that, in a lot of cases, subscribers won't miss the mail from the mailing list... so even if they know about the Web page, they may not think to check it to see if they're on it. What we use is a system that tries to notify people when we've nuked them from a list. There are two steps: 1) When we nuke them, we send a complete copy of the bounce to their old address and tell them we're removing them. Lots of times, this bounces... but not always. 2) We have a cron job that tries to notify each nuked address, twice a week for a month, that they've been removed from the list. The message also tells them how to resubscribe... and how to cancel the notification messages if they start to receive them (if their problems are fixed). The message also tells postmasters how to cancel the notifications if they want to. We send this mail from "nobody", with Precedence: junk, so that we don't see bounces. It's amazing to me how many people have their mail problems fixed within a month -- and cancel the notifications, and often resubscribe too. Our system is sort of a hack, and wrapped up in some other custom stuff we do, so I'd rather not send it out. But the idea seems to work, and we've gotten very few complaints from postmasters or users about it. For us and our subscribers, I think it's been a win because it doesn't depend on the subscriber to realize that they aren't getting the mail anymore... the system tries to reach them. -- Jerry Peek, jerry@ora.com, http://www.ora.com/staff/jerry/ O'Reilly & Associates, Inc.; 101 Morris St.; Sebastopol, CA 95472 USA Phone: (800)998-9938, +1 707-829-0515; FAX +1 707-829-0104 All about ORA: WEB: http://www.ora.com/ EMAIL: info@online.ora.com From list-managers-owner Wed Feb 14 10:27:16 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id KAA00653 for list-managers-outgoing; Wed, 14 Feb 1996 10:05:32 -0800 (PST) Received: from pony-express.ims.advantis.com (pony-express.ims.advantis.com [165.87.194.144]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id KAA00646 for ; Wed, 14 Feb 1996 10:05:25 -0800 (PST) Received: (from Unknown UID 5@localhost) by pony-express.ims.advantis.com (8.6.9/95.10.11) id NAA156769; Wed, 14 Feb 1996 13:06:06 -0500 Received: from epizootic.sch.advantis.com(164.120.113.166) by pony-express.ims.advantis.com via smap (V1.3) id sma157279; Wed Feb 14 13:06:01 1996 Received: (from ctalman@localhost) by ims.advantis.com (8.6.9/8.6.9) id MAA24582; Wed, 14 Feb 1996 12:07:21 -0600 Date: Wed, 14 Feb 1996 12:07:21 -0600 Message-Id: <199602141807.MAA24582@ims.advantis.com> From: Cathy Talman To: lmccarth@cs.umass.edu Cc: List-Managers@GreatCircle.COM Subject: Bouncing subscriber addresses on web page In-Reply-To: <199602140952.EAA18269@opine.cs.umass.edu> References: <199602140952.EAA18269@opine.cs.umass.edu> Sender: list-managers-owner@GreatCircle.COM Precedence: bulk lmccarth@cs.umass.edu writes: > -----BEGIN PGP SIGNED MESSAGE----- > > Personal introduction: I manage a list with 150+ subscribers using > Majordomo, but approving subscriptions manually. The list deals with > cryptographic programming. > > Being pretty new to the list management biz, I've been developing my own set > of little coping techniques etc., and appreciating the wisdom of others. I > had a simple idea about dealing with subscribers whose addresses bounce list > mail. > > Since the WWW is a widely accessible out-of-email-band means of > communication on the net, I decided to put up a web page with all the > addresses I've had to remove from the list due to bouncing mail. Next to each > address I include the precise reason that address was bouncing mail, at least > according to the mailer-daemon(s). It's easily updated with some cutting-and- > pasting from the bounce messages I get. > > This is still a pretty new experiment for me. I announced the page on my > list, but I haven't had any feedback so far from the subscribers. I am > wondering what more experienced list managers think about this idea. Has this > approach been tried much before ? Are there any non-obvious problems or > benefits I should consider ? > > In case you care, the bounce list is at > http://www.cs.umass.edu/~lmccarth/coderpunks/bounce.html > > (BTW, I read the digest version of list-managers, so you should cc: me > directly if you want a relatively prompt response from me.) > > Lewis Lewis, In the couple of lists that I have run, I have had at least two or three on each list who have wanted to remain on the list but have their e-mail addresses remain confidential. I didn't ask why, but they came forward with reason, which in each instance seemed very valid. As long as your members are aware ahead of time you do this, then fair is fair. -- cathy cathy talman ctalman@ims.advantis.com From list-managers-owner Thu Feb 15 14:01:18 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id NAA21314 for list-managers-outgoing; Thu, 15 Feb 1996 13:49:19 -0800 (PST) Received: from kitsune.swcp.com (swcp.com [198.59.115.2]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id NAA21301 for ; Thu, 15 Feb 1996 13:49:16 -0800 (PST) Received: (from lazlo@localhost) by kitsune.swcp.com (8.6.9/8.6.9) id OAA02744 for list-managers@greatcircle.com; Thu, 15 Feb 1996 14:47:53 -0700 From: Lazlo Nibble Message-Id: <199602152147.OAA02744@kitsune.swcp.com> Subject: Mail deliver error messages To: list-managers@greatcircle.com (lm) Date: Thu, 15 Feb 1996 14:47:52 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > Mail deliver error messages are one of the biggest pains of list > management. Particularly when they are mixed in with one's personal / > general / other mail... Has anyone got an easy way to segregate them > easily? Using procmail (my lists are currently SmartList lists), "^TOowner@" and "^X-Diagnostic:" rules catch *all* admin mail directed to my account. When my lists ran under majordomo it was similarly simple to filter admin messages. -- ::: Lazlo (lazlo@swcp.com; http://www.swcp.com/lazlo) From list-managers-owner Thu Feb 15 14:43:00 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id OAA24165 for list-managers-outgoing; Thu, 15 Feb 1996 14:36:38 -0800 (PST) Received: from server.postmodern.com (server.postmodern.com [199.172.54.54]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id OAA24155 for ; Thu, 15 Feb 1996 14:36:32 -0800 (PST) Received: from 199.172.54.51 (derrida.postmodern.com [199.172.54.51]) by server.postmodern.com (8.6.10/8.6.10-mcb-951019) with SMTP id OAA03765; Thu, 15 Feb 1996 14:35:46 -0800 Message-ID: <3123B530.1B37@postmodern.com> Date: Thu, 15 Feb 1996 14:35:28 -0800 From: "Michael C. Berch" Reply-To: mcb@postmodern.com Organization: INFOBAHN Magazine / Postmodern Communications, Inc. X-Mailer: Mozilla 2.0 (Macintosh; I; 68K) MIME-Version: 1.0 To: list-managers@greatcircle.com Subject: And the winners are... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk My two nominations for Clueless Morons of the Internet, February 15 edition: 1. Portal (portal.com). After receiving a *third* copy of the William R. Strack "Value Dent" e-mail spam from strack@strack.ip.portal.com, I forwarded the message to postmaster@portal.com. Result? It bounced, with the message "Your message is too long" with a return address of "Postmaster-so filter works" . (It was all of about 200 lines, including headers & my forwarding comments, not exactly a uuencoded UNIX kernel.) So I located the domain contact with "whois", and forwarded it to him, with an explanation that bouncing postmaster mail is a really bad idea ... and you've guessed the result, of course -- it bounced with "Your message is too long." I called the guy up on the phone and left a voice mail -- no response so far. !@#$%^. 2. MCIMail (mcimail.com). (OK, these guys have already earned the lifetime Clueless Moron award, but I guess they're trying for emeritus status.) On one of my lists, a message was sent by someone whose From: line was From: "m." (The mailbox was a real address; I've just substituted a sample one.) MCIMail *rejected* it, with the message "Sender field too short". Never mind that the full-name in double quotes is optional and that the mailbox spec in <> is perfectly legal. So I complained, and the response was that "they are trying to make their Internet gateway software more compliant with RFC822." Uh huh. They've only had 12 years or so (I think MCImail was started in 1984); perhaps they'll get it right by 2000. The message also said that the name field in a From: line had to have a minimum of 2 alphanumerics ... apparently "Al" is OK, but "m." isn't. Morons. And these are the people that are spending $MM on InternetMCI/NetworkMCI advertising? -- Michael C. Berch mcb@postmodern.com From list-managers-owner Thu Feb 15 22:10:16 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id VAA05963 for list-managers-outgoing; Thu, 15 Feb 1996 21:56:31 -0800 (PST) Received: from cais.cais.com (cais.com [199.0.216.4]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id VAA05958 for ; Thu, 15 Feb 1996 21:56:27 -0800 (PST) Received: from [199.0.216.124] (pinpoint.cais.com [199.0.216.124]) by cais.cais.com (8.6.10/8.6.5) with SMTP id AAA27876 for ; Fri, 16 Feb 1996 00:54:32 -0500 Date: Fri, 16 Feb 96 00:48:41 EDT From: "Hugh Barnes" Message-Id: <19328.hbarnes@pinPoint.com> X-Minuet-Version: Minuet1.0_Beta_16 Reply-To: X-POPMail-Charset: English To: list-managers@GreatCircle.COM Subject: Problems with X.400 Addresses Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I am experiencing two different types of error messages with providers failure to deliver messages received from X.400 networks. The more common one is Type 1. My provider is not familiar with these types of error messages. Any assistance will be greatly appreciated. Hugh ---------------------- Error Message Type 1 ------------------------------- Confirming-MTS-Message-ID: Not-Delivered-To: mhs!fswa/S=T.CONWAY/OU1=S27L02A/RECIPNUM=1/MTA-BASIC@attmail.com due to code 01 "Invalid Address Specification"; arrived Fri Feb 2 09:23:24 GMT 1996; Supplementary-Info "DG 78043: (X400) Routing loop detected" --------------------- Error Message Type 2 ------------------------------ This report relates to your message: Re: send Data... of Mon, 22 Jan 1996 09:52:16 +0100 Your message was not delivered to Bjorn.Haugen/WestSoftAS@CCMAIL.telemax.no for the following reason: Unknown Address ***** The following information is directed towards the local administrator ***** and is not intended for the end user * * DR generated in /PRMD=CCMAIL/ADMD=TELEMAX/C=NO/ * at Mon, 22 Jan 1996 09:55:21 +0100 * * Converted to RFC 822 at gw.telepost.no * at Mon, 22 Jan 1996 10:00:27 +0100 * * Delivery Report Contents: * * Subject-Submission-Identifier: [/PRMD=internet/ADMD=telemax/C=no/;<199601220850.DAA08648@cais.cais] * Content-Identifier: Re: send Data... * Content-Type: p2 * Subject-Intermediate-Trace-Information: /PRMD=CCMAIL/ADMD=TELEMAX/C=NO/arrival Mon, 22 Jan 1996 09:52:16 +0100 action Relayed * Subject-Intermediate-Trace-Information: /PRMD=CCMAIL/ADMD=TELEMAX/C=NO/arrival Mon, 22 Jan 1996 09:52:33 +0100 action Relayed * Subject-Intermediate-Trace-Information: /PRMD=CCMAIL/ADMD=TELEMAX/C=NO/arrival Mon, 22 Jan 1996 09:50:01 +0100 action Relayed * Subject-Intermediate-Trace-Information: /PRMD=CCMAIL/ADMD=TELEMAX/C=NO/arrival Mon, 22 Jan 1996 09:50:04 +0100 action Relayed * Recipient-Info: Bjorn.Haugen/WestSoftAS@CCMAIL.telemax.no, * /G=Bjorn/S=Haugen$/WestSoftAS/PRMD=CCMAIL/ADMD=telemax/C=no/; * FAILURE reason Transfer-Failure (0); * diagnostic Unrecognised-ORName (0); * last trace Mon, 22 Jan 1996 09:50:04 +0100; ****** End of administration information The Original Message is not available Hugh Barnes pinPoint Corporation 5055 Chesterfield Rd., Suite 1000 Arlington, VA 22206 Voice: 703-379-8111 Fax: 703-379-3834 E-mail: hbarnes@pinpoint.com From list-managers-owner Fri Feb 16 00:40:22 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id AAA10183 for list-managers-outgoing; Fri, 16 Feb 1996 00:33:41 -0800 (PST) Received: from server.postmodern.com (server.postmodern.com [199.172.54.54]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id AAA10178 for ; Fri, 16 Feb 1996 00:33:37 -0800 (PST) Received: from 199.172.54.51 (derrida.postmodern.com [199.172.54.51]) by server.postmodern.com (8.6.10/8.6.10-mcb-951019) with SMTP id AAA05152; Fri, 16 Feb 1996 00:32:51 -0800 Message-ID: <31244122.48CE@postmodern.com> Date: Fri, 16 Feb 1996 00:32:34 -0800 From: "Michael C. Berch" Reply-To: mcb@postmodern.com Organization: INFOBAHN Magazine / Postmodern Communications, Inc. X-Mailer: Mozilla 2.0 (Macintosh; I; 68K) MIME-Version: 1.0 To: list-managers@GreatCircle.COM Subject: Re: Problems with X.400 Addresses References: <19328.hbarnes@pinPoint.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Hugh Barnes wrote: > I am experiencing two different types of error messages with providers > failure to deliver messages received from X.400 networks. The more common > one is Type 1. My provider is not familiar with these types of error > messages. Any assistance will be greatly appreciated. > > Hugh > > ---------------------- Error Message Type 1 ------------------------------- > Confirming-MTS-Message-ID: > Not-Delivered-To: mhs!fswa/S=T.CONWAY/OU1=S27L02A/RECIPNUM=1/MTA-BASIC@attmail.com due to code 01 "Invalid Address Specification"; > arrived Fri Feb 2 09:23:24 GMT 1996; > Supplementary-Info "DG 78043: (X400) Routing loop detected" This means there is an internal network error on the far end (in this case, it indicates that attmail.com is screwed up, which is not great surprise). Neither you nor your list recipient is likely to be able to fix this. I do bounce people from high-volume lists when something like this comes up; I leave them on my low-volume lists since it is usually cured in a while. > --------------------- Error Message Type 2 ------------------------------ > This report relates to your message: Re: send Data... > of Mon, 22 Jan 1996 09:52:16 +0100 >[lots of lines, then:] > Your message was not delivered to > * FAILURE reason Transfer-Failure (0); > * diagnostic Unrecognised-ORName (0); This basically translates to "User unknown". As with SMTP mail, it is possible that the report is erroneous, but it usually means the user/mailbox has gone away. -- Michael C. Berch mcb@postmodern.com From list-managers-owner Fri Feb 16 11:55:44 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id LAA07697 for list-managers-outgoing; Fri, 16 Feb 1996 11:44:18 -0800 (PST) Received: from skyhawk.ecc.engr.uky.edu (skyhawk.ecc.engr.uky.edu [128.163.144.19]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id LAA07684 for ; Fri, 16 Feb 1996 11:44:13 -0800 (PST) Received: (from morgan@localhost) by skyhawk.ecc.engr.uky.edu (8.6.10/8.6.10) id OAA10721 for list-managers@greatcircle.com; Fri, 16 Feb 1996 14:44:00 -0500 Date: Fri, 16 Feb 1996 14:44:00 -0500 From: Wes Morgan Message-Id: <199602161944.OAA10721@skyhawk.ecc.engr.uky.edu> To: list-managers@greatcircle.com Subject: Re: E-cards from Heineken Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >Some misguided person sent my entire mailing list an "e-card" from the >Heineken World Wide Web server in the Netherlands. A silly .gif file with a >message. > >The Heineken site seems set up so you that you cannot contact the webmaster >or anyone at Heineken -- but visitors can fling messages/graphics files to >any e-mail address. (Most of the postcard sites I've seen send a simple >text notice that you follow up (or not) by visiting the WW site to see the >message.) I left a comment (via the Web page) that "the ecard facility is causing problems and should be disabled." I received a rather polite letter from one of the admins of heineken.nl, inquiring after my comments. I clued him in on the particulars (untraceable email, hitting mailing lists) and the potential (hundreds of ecards flooding individuals, et cetera). In today's email, he assured me that they are discussing the impact of their facility on the rest of the Net, and that he will be back in touch with me soon. --Wes From list-managers-owner Fri Feb 16 20:10:30 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id TAA29078 for list-managers-outgoing; Fri, 16 Feb 1996 19:19:46 -0800 (PST) Received: from lepomis.psych.upenn.edu (LEPOMIS.PSYCH.UPENN.EDU [130.91.68.34]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id OAA04658 for ; Mon, 12 Feb 1996 14:26:18 -0800 (PST) Received: by lepomis.psych.upenn.edu (AIX 3.2/UCB 5.64/4.03) id AA39274; Mon, 12 Feb 1996 17:22:56 -0500 Date: Mon, 12 Feb 1996 17:22:56 -0500 From: rowe@lepomis.psych.upenn.edu (Mickey Rowe) Message-Id: <9602122222.AA39274@lepomis.psych.upenn.edu> To: List-Managers@GreatCircle.COM Subject: Spammers get more sophisticated... Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Before I get into the subject of this message, I need to revisit the topic I brought up last week. I'm the guy that complained about computer science classes being given an assignment in which the students have to subscribe to and unsubscribe from one (or a few) particular mailing list(s). In that message I also mentioned that as a subscriber to the digest version of list-managers, I've received a few partial headers with no message bodies. Naturally the message that I sent came back to me in that form, so my only access to public responses is via the archives. I may take up that discussion again later in the week after I've perused the responses -- excuse my delay. But for now... I'd like to know how unique I am in having been hit by merc@scooby.pubnix.org with a spam about "Progress Scholarships". This individual (or group) subscribed to my list, got a copy of the then current subscribers and unsubscribed within two days. Three days later I got the spam which was mailed to: progress@scooby.pubnix.org probably just an alias, definitely something that I did not ask to be a part of. I haven't yet researched it, but based upon their interactions with my MLM I presume that everybody on my list received this spam. Naturally the content of the spam is irrelevant to the discussions the list is supposed to entertain. In any case, I recommend that you set your MLM's to ignore mail merc@scooby... (if not the entire machine). And brace yourselves for a type of spam we've probably all been dreading. -- Mickey Rowe (rowe@lepomis.psych.upenn.edu) From list-managers-owner Sat Feb 17 06:10:36 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id GAA26011 for list-managers-outgoing; Sat, 17 Feb 1996 06:05:48 -0800 (PST) Received: from SYSWRK.UCIS.Dal.Ca (syswrk.UCIS.Dal.Ca [129.173.2.108]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id GAA26005 for ; Sat, 17 Feb 1996 06:05:43 -0800 (PST) Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.3-13 #6307) id <01I1BDWFAINK0009QA@SYSWRK.UCIS.DAL.CA>; Sat, 17 Feb 1996 10:03:53 -0400 Received: from biome.bio.dfo.ca ("port 3210"@biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.3-13 #6307) id <01I1BDW729KG00LZ6Y@AC.DAL.CA>; Sat, 17 Feb 1996 10:03:46 -0400 Received: by biome.bio.dfo.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:List-Managers@GreatCircle.COM id AA07310; Sat, 17 Feb 96 10:00:05 -0400 Date: Sat, 17 Feb 1996 10:00:05 -0400 (AST) From: bill@biome.bio.dfo.ca (Bill Silvert) Subject: Horror Story - is there a defense? To: List-Managers@GreatCircle.COM (List Managers) Message-id: <9602171400.AA07310@biome.bio.dfo.ca> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL23] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Yesterday I had a near disaster on one of the discussion lists I run, and the events really worried me, so I am posting this as a warning and as a request for advice on how to avoid this in the future. A subscriber sent several hundred copies of the same submission to the list, apparently through no fault of his own. His mailer, Microsoft Mail V3.0, ran amuck and was spitting out copies at the rate of several times per minute, and continued doing this until the machine was actually shut down. The post was perfectly legit and would have made it to the list, except that the day before I had a Vines mailer that started bouncing "Mailbox Full" full messages to the list and had started moderating it to block these. By the time I got to work my own mailbox was full of approval requests. I shot off an Email message to the submitter, and then as they continued to pour in I telephoned him. He had no idea what was happening, since Microsoft Mail informed him that the messages could not be delivered, so if I hadn't called him this could have continued indefinitely. Fortunately he was very conscientious and immediately got the systems administrators working on this. They called Microsoft and were told that this was a known bug, one that would be fixed in the next release, and that the only fix was to shut down the system for a few hours, which they did. If they hadn't, I guess that hundreds, perhpas thousands, of postings would have gone out, and if I hadn't been moderating the list, would have been sent to all subscribers. The cause? The subscriber decided that in his alias file (I don't know the details of how Microsoft Mail works) to change the name of the list from Theoretical Ecology to Ecologi'a Theore'tica (obviously he lives in an 8-bit environment), and Microsoft Mail translated this to Ecolog!a Theor"tica (I may have the accent in the wrong place, but you get the idea), and this appeared in the To: header. I can't fault him for doing this, but I have nightmares of other subscribers doing this sort of thing, and the consequences could be disastrous. That one double quote had other serious consequences too. I approved one copy of the message, which went out with the line `To: Ecolog!a Theor"tica ' in it, and it seems that almost half of the subscriber sites bounced it because of the unbalanced double quote. Since there are several hundred subscribers, this meant a lot of bounce messages. I don't know much about mail headers, but what if someone submitted a perfectly legitimate message with a Subject line like `Subject: Applications of x" = -kx to ecological systems' where x" is standard math for second derivative. Would that bounce too? What a blessing that I was moderating the list the day that this happened! In general, none of our lists are moderated, so does anyone have any ideas on how to avoid this in the future? By the way, this is a Majordomo list, but it seems to me that it could happen to any list. -- Bill Silvert, Habitat Ecology Section, Bedford Institute of Oceanography, P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2, Tel. (902)426-1577 HED runs a WWW server at URL=http://hed.bio.dfo.ca From list-managers-owner Sat Feb 17 09:25:29 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id JAA04413 for list-managers-outgoing; Sat, 17 Feb 1996 09:20:26 -0800 (PST) Received: from ruby.ora.com (ruby.ora.com [198.112.208.25]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id JAA04408 for ; Sat, 17 Feb 1996 09:20:22 -0800 (PST) Received: (from jerry@localhost) by ruby.ora.com (8.6.12/8.6.11) id JAA17652; Sat, 17 Feb 1996 09:18:53 -0800 Message-Id: <199602171718.JAA17652@ruby.ora.com> From: Jerry Peek Date: Sat, 17 Feb 1996 09:18:53 EST In-Reply-To: "Horror Story - is there a defense?" (bill@biome.bio.dfo.ca (Bill Silvert), Feb 17, 10:00) <9602171400.AA07310@biome.bio.dfo.ca> X-Mailer: Mail User's Shell (7.2.0 10/31/90) To: bill@biome.bio.dfo.ca (Bill Silvert), List-Managers@GreatCircle.COM (List Managers) Subject: Re: Horror Story - is there a defense? Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Listproc 6.0 (and probably later versions) do a few things to stop your problem of duplicate messages going to a list: - it keeps the last 500 (I think) Message-IDs sent to each list, and also sent to listproc itself (administrative requests). If a new message comes in with the same Message-ID as a previous message, listproc routes the message to the list owner or system manager. But some systems give the same Message-ID to more than one message (yes, this is wrong) and listproc rejects those too... I deal with that on a user-by-user basis; we have one user with that problem. - it computes a checksum of each message body sent to a list. When a new message comes in, it compares the checksum to the last 500 checksums; if there's a match, the message goes to the list owner. By default, listproc uses the sum(1) utility, which sometimes gives the same checksum for different message bodies. I hacked listproc to use the MD5 algorithm; we haven't had any problems since. You could probably add code like that to your Majordomo. The checksum would probably be enough. I haven't kept up on the lasest Majordomo features; there are probably others like this in Majordomo already. --Jerry, jerry@ora.com From list-managers-owner Sat Feb 17 10:40:31 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id KAA06347 for list-managers-outgoing; Sat, 17 Feb 1996 10:40:02 -0800 (PST) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.5]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id KAA06341 for ; Sat, 17 Feb 1996 10:39:54 -0800 (PST) Received: from ppp-66-76.dialup.winternet.com (ppp-66-76.dialup.winternet.com [204.246.66.76]) by icicle.winternet.com (8.7.3/8.7.2) with SMTP id MAA19887 for ; Sat, 17 Feb 1996 12:38:25 -0600 (CST) Message-Id: <199602171838.MAA19887@icicle.winternet.com> Comments: Authenticated sender is From: haverber@winternet.com To: List-Managers@GreatCircle.Com Date: Sat, 17 Feb 1996 12:38:02 +0000 Subject: Anonymous subscribers X-mailer: Pegasus Mail for Windows (v2.01) Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I just got my list up yesterday, and I'm still real new at this...so if I'm asking something innapropriate to the list or something in a faq I haven't glanced at yet, feel free to point out my errors. One of the users on my mailing list would like to have their EMail address not show up when they post. Is there any way I can diddle with .procmailrc or a majordomo command that will let me hide the FROM: address for (a) selected users or (b) everyone if I can't do (a)? From list-managers-owner Sat Feb 17 11:10:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id KAA06968 for list-managers-outgoing; Sat, 17 Feb 1996 10:59:15 -0800 (PST) Received: from CU.NIH.GOV (cu.nih.gov [128.231.64.112]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id KAA06963 for ; Sat, 17 Feb 1996 10:59:11 -0800 (PST) Message-Id: <199602171859.KAA06963@miles.greatcircle.com> To: jerry@ora.com, bill@biome.bio.dfo.ca, List-Managers@GreatCircle.COM From: "Roger Fajman" Date: Sat, 17 Feb 1996 13:54:48 EST Subject: Re: Horror Story - is there a defense? Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > - it computes a checksum of each message body sent to a list. > When a new message comes in, it compares the checksum to the last 500 > checksums; if there's a match, the message goes to the list owner. > By default, listproc uses the sum(1) utility, which sometimes gives > the same checksum for different message bodies. I hacked listproc > to use the MD5 algorithm; we haven't had any problems since. LISTSERV does something like this too, except that it returns the message to the sender. It seems to work well. From list-managers-owner Sat Feb 17 12:40:41 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id MAA10286 for list-managers-outgoing; Sat, 17 Feb 1996 12:33:33 -0800 (PST) Received: from SYSWRK.UCIS.Dal.Ca (syswrk.UCIS.Dal.Ca [129.173.2.108]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id MAA10281 for ; Sat, 17 Feb 1996 12:33:29 -0800 (PST) Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.3-13 #6307) id <01I1BN15P0DC000AW7@SYSWRK.UCIS.DAL.CA>; Sat, 17 Feb 1996 14:25:01 -0400 Received: from biome.bio.dfo.ca ("port 3275"@biome.BIO.dfo.ca) by AC.DAL.CA (PMDF V4.3-13 #6307) id <01I1BN0FYRVK00LXZU@AC.DAL.CA>; Sat, 17 Feb 1996 14:24:44 -0400 Received: by biome.bio.dfo.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:List-Managers@GreatCircle.COM id AA08520; Sat, 17 Feb 96 14:20:47 -0400 Date: Sat, 17 Feb 1996 14:20:47 -0400 (AST) From: bill@biome.bio.dfo.ca (Bill Silvert) Subject: Re: Horror Story - is there a defense? In-reply-to: <199602171718.JAA17652@ruby.ora.com> from "Jerry Peek" at Feb 17, 96 09:18:53 am To: List-Managers@GreatCircle.COM (List Managers) Message-id: <9602171820.AA08520@biome.bio.dfo.ca> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL23] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Jerry Peek writes: >- it keeps the last 500 (I think) Message-IDs sent to each list, and > also sent to listproc itself (administrative requests). If a new > message comes in with the same Message-ID as a previous message, > listproc routes the message to the list owner or system manager. > ... >- it computes a checksum of each message body sent to a list. In this case the headers were different for each message, with different times and message ID's. The actual time at which the message was submitted was the same of course, but all the other times for transfer between machines were different. This was not an SMTP problem after all, this was a problem with the queueing in Microsoft Mail I guess. Bill Silvert (bill@hed.bio.ns.ca) From list-managers-owner Sat Feb 17 21:40:30 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id VAA23464 for list-managers-outgoing; Sat, 17 Feb 1996 21:25:40 -0800 (PST) Received: from sacusr.mp.usbr.gov (sacusr.mp.usbr.gov [140.214.12.2]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id VAA23459 for ; Sat, 17 Feb 1996 21:25:35 -0800 (PST) Received: by sacto.mp.usbr.gov (MX V4.2 VAX) id 22; Sat, 17 Feb 1996 21:24:03 PST Date: Sat, 17 Feb 1996 21:24:00 PST From: "Henry W. Miller" To: jerry@ora.com CC: list-managers@greatcircle.com, henrym@sacto.mp.usbr.gov Message-ID: <0099E106.B8133762.22@sacto.mp.usbr.gov> Subject: Re: Horror Story - is there a defense? Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > From: MX%"jerry@ora.com" 17-FEB-1996 09:28:05.11 > Subj: Re: Horror Story - is there a defense? > Listproc 6.0 (and probably later versions) do a few things to stop > your problem of duplicate messages going to a list: > > - it keeps the last 500 (I think) Message-IDs sent to each list, and > also sent to listproc itself (administrative requests). If a new > message comes in with the same Message-ID as a previous message, > listproc routes the message to the list owner or system manager. > But some systems give the same Message-ID to more than one message > (yes, this is wrong) and listproc rejects those too... I deal with > that on a user-by-user basis; we have one user with that problem. > > - it computes a checksum of each message body sent to a list. > When a new message comes in, it compares the checksum to the last 500 > checksums; if there's a match, the message goes to the list owner. > By default, listproc uses the sum(1) utility, which sometimes gives > the same checksum for different message bodies. I hacked listproc > to use the MD5 algorithm; we haven't had any problems since. > > You could probably add code like that to your Majordomo. The checksum > would probably be enough. I haven't kept up on the lasest Majordomo > features; there are probably others like this in Majordomo already. > > --Jerry, jerry@ora.com This would assume, of course, that the rogue mailer kept generating the same message-id for each message. If not, then there would still be trouble... -HWM From list-managers-owner Sat Feb 17 22:25:45 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id WAA24908 for list-managers-outgoing; Sat, 17 Feb 1996 22:12:31 -0800 (PST) Received: from sgigate.sgi.com (sgigate.SGI.COM [204.94.209.1]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id WAA24903 for ; Sat, 17 Feb 1996 22:12:27 -0800 (PST) Received: from lunch.engr.sgi.com by sgigate.sgi.com via ESMTP (950911.SGI.8.6.12.PATCH825/940406.SGI) id WAA04553; Sat, 17 Feb 1996 22:11:06 -0800 Received: by lunch.engr.sgi.com (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) id WAA21630; Sat, 17 Feb 1996 22:11:05 -0800 From: close@lunch.engr.sgi.com (Diane Barlow Close) Message-Id: <199602180611.WAA21630@lunch.engr.sgi.com> Subject: Re: Horror Story - is there a defense? To: henrym@sacto.mp.usbr.gov (Henry W. Miller) Date: Sat, 17 Feb 1996 22:09:09 -0800 (PST) Cc: list-managers@greatcircle.com In-Reply-To: <0099E106.B8133762.22@sacto.mp.usbr.gov> from "Henry W. Miller" at Feb 17, 1996 09:24:00 PM X-Mailer: ELM [version 2.5 PL0a8s] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Henry W. Miller wrote: > This would assume, of course, that the rogue mailer kept > generating the same message-id for each message. If not, then there > would still be trouble... You could always strip out the headers and do a body checksum... -- Diane Close I'm at lunch all day. :-) If a Canadian Had Said It First (The Globe & Mail): "The price of freedom is eternal vigilance plus GST." From list-managers-owner Sat Feb 17 22:40:40 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id WAA25640 for list-managers-outgoing; Sat, 17 Feb 1996 22:34:08 -0800 (PST) Received: from sacusr.mp.usbr.gov (sacusr.mp.usbr.gov [140.214.12.2]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id WAA25635 for ; Sat, 17 Feb 1996 22:34:04 -0800 (PST) Received: by sacto.mp.usbr.gov (MX V4.2 VAX) id 16; Sat, 17 Feb 1996 22:32:29 PST Date: Sat, 17 Feb 1996 22:32:26 PST From: "Henry W. Miller" To: close@lunch.engr.sgi.com CC: list-managers@greatcircle.com, henrym@sacto.mp.usbr.gov Message-ID: <0099E110.47B2DC52.16@sacto.mp.usbr.gov> Subject: Re: Horror Story - is there a defense? Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > From: MX%"close@lunch.engr.sgi.com" 17-FEB-1996 22:12:17.59 > Subj: Re: Horror Story - is there a defense? > Henry W. Miller wrote: > > This would assume, of course, that the rogue mailer kept > > generating the same message-id for each message. If not, then there > > would still be trouble... > > You could always strip out the headers and do a body checksum... > -- > Diane Close > I'm at lunch all day. :-) > If a Canadian Had Said It First (The Globe & Mail): > "The price of freedom is eternal vigilance plus GST." Diane, Aye, good point. Hey, it's Saturday, where is "Krazy Kevin"? Busted, I hope... -HWM From list-managers-owner Sun Feb 18 02:43:46 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id CAA04466 for list-managers-outgoing; Sun, 18 Feb 1996 02:31:12 -0800 (PST) Received: from cs.umass.edu (freya.cs.umass.edu [128.119.40.195]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id CAA04452 for ; Sun, 18 Feb 1996 02:31:04 -0800 (PST) From: lmccarth@cs.umass.edu Received: from thor.cs.umass.edu by cs.umass.edu (5.65/Ultrix3.0-C) id AA03214; Sun, 18 Feb 1996 05:29:43 -0500 Received: (from lmccarth@localhost) by thor.cs.umass.edu (8.6.12/8.6.9) id FAA25615 for List-Managers@GreatCircle.COM; Sun, 18 Feb 1996 05:29:41 -0500 Message-Id: <199602181029.FAA25615@thor.cs.umass.edu> Subject: Re: Anonymous subscribers To: List-Managers@GreatCircle.COM Date: Sun, 18 Feb 1996 05:29:41 -0500 (EST) In-Reply-To: <199602180900.BAA00500@miles.greatcircle.com> from "list-managers-digest-owner@GreatCircle.COM" at Feb 18, 96 01:00:24 am X-Mailer: ELM [version 2.4 PL25] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk haverber@winternet.com writes: > One of the users on my mailing list would like to have their EMail > address not show up when they post. Is there any way I can diddle > with .procmailrc or a majordomo command that will let me hide the > FROM: address for (a) selected users or (b) everyone if I can't do > (a)? I suggest that your user read http://www.stack.urc.tue.nl/~galactus/remailers/alpha.html and set up a pseudonymous email address. You won't need to do anything differently, and s/he won't need to trust you to keep the secret (nothing personal). -Lewis From list-managers-owner Sun Feb 18 10:55:50 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id KAA18539 for list-managers-outgoing; Sun, 18 Feb 1996 10:47:52 -0800 (PST) Received: from aix.wingra.com (aix.wingra.com [192.101.144.86]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id KAA18506 for ; Sun, 18 Feb 1996 10:47:40 -0800 (PST) Received: from I (root@localhost) by aix.wingra.com (8.7.3/8.7.3) with SMTP id MAA49352 for ; Sun, 18 Feb 1996 12:46:21 -0600 Received: from aix.wingra.com by wingra.com id <"9602181846.AA44474"@aix.wingra.com>; Sun, 18 Feb 1996 12:46:20 -0600 Received: from wingra.com by aix.wingra.com id AA44474; Sun, 18 Feb 1996 12:46:19 -0600 Hop-Count: 1 Date: Sun, 18 Feb 1996 12:46:19 -0600 From: Harlan Harris Subject: Re: Horror Story - is there a defense? To: List-Managers@greatcircle.com Message-ID: <"9602181846.AA44474"@aix.wingra.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: list-managers-owner@GreatCircle.COM Precedence: bulk As people have pointed out, some of the commercial MLMs do Message-ID and checksum storage to prevent these problems. Someone mentioned Listproc, but from their message it sounds like they meant the old 6.0c version. The commercial version, 7.X, correctly stores the checksums of the body of the message, stripping the headers, exactly as suggested. I'm pretty certain that that would have elegantly prevented your situation. >That one double quote had other serious consequences too. I approved one >copy of the message, which went out with the line >`To: Ecolog!a Theor"tica ' >in it, and it seems that almost half of the subscriber sites bounced it >because of the unbalanced double quote. That's right. That's not a legal RFC822 To: line. Ideally, your mail system should have bounced it too. I think the correct line would have looked like: To: "Ecolog!a Theor\"tica" <...> (but I'm not completely certain about the backslash to escape the quote...) >Since there are several hundred >subscribers, this meant a lot of bounce messages. I don't know much >about mail headers, but what if someone submitted a perfectly legitimate >message with a Subject line like >`Subject: Applications of x" = -kx to ecological systems' >where x" is standard math for second derivative. Would that bounce too? Nope. The Subject line is not processed by an SMTP MTA. >In general, none of our lists are moderated, so does anyone >have any ideas on how to avoid this in the future? By the way, this is a >Majordomo list, but it seems to me that it could happen to any list. Well, I'd continue to urge people who need more control or more performance than what SmartList or MajorDomo provide to consider purchasing Listproc. I was pretty happy with it when I had the opportunity to use it, and have been fairly unhappy with the inflexibility of Majordomo (which I run now, at a different site). But we're running less than 10 lists (rather than 200) with something like 1000 times fewer recipients, so it's not worth the money to us... -Harlan -- Harlan Harris Missive/AIX Wingra Technologies, Inc. The Simple Solution to Email Integration harris@wingra.com http://www.wingra.com/ +1 608 238 4454 +1 608 238 8986 (fax) From list-managers-owner Sun Feb 18 11:10:34 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id LAA19675 for list-managers-outgoing; Sun, 18 Feb 1996 11:08:15 -0800 (PST) Received: from netcom10.netcom.com (netcom10.netcom.com [192.100.81.120]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id LAA19670 for ; Sun, 18 Feb 1996 11:08:12 -0800 (PST) Received: by netcom10.netcom.com (8.6.12/Netcom) id LAA22168; Sun, 18 Feb 1996 11:05:51 -0800 Date: Sun, 18 Feb 1996 11:05:51 -0800 (PST) From: James Cook Subject: Lsoft's Listserv VS. Listproc??? To: Harlan Harris cc: List-Managers@greatcircle.com In-Reply-To: <"9602181846.AA44474"@aix.wingra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On Sun, 18 Feb 1996, Harlan Harris wrote: > > Well, I'd continue to urge people who need more control or more performance > than what SmartList or MajorDomo provide to consider purchasing Listproc. > How would the commercial "Listserv" by Lsoft compare with the Listproc product? I'm planning service over SCO Unix OpenServer 5.... Thank you. James Cook From list-managers-owner Sun Feb 18 11:40:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id LAA20949 for list-managers-outgoing; Sun, 18 Feb 1996 11:30:04 -0800 (PST) Received: from CU.NIH.GOV (cu.nih.gov [128.231.64.112]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id LAA20944 for ; Sun, 18 Feb 1996 11:30:00 -0800 (PST) Message-Id: <199602181930.LAA20944@miles.greatcircle.com> To: jcook@netcom.com cc: List-Managers@greatcircle.com From: "Roger Fajman" Date: Sun, 18 Feb 1996 14:26:46 EST Subject: Re: Lsoft's Listserv VS. Listproc??? Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > > Well, I'd continue to urge people who need more control or more performance > > than what SmartList or MajorDomo provide to consider purchasing Listproc. > > > > How would the commercial "Listserv" by Lsoft compare with the Listproc > product? You might have a look at their respective WWW pages: www.cren.net for Listproc www.lfsoft.com for LISTSERV From list-managers-owner Sun Feb 18 12:10:35 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id LAA21969 for list-managers-outgoing; Sun, 18 Feb 1996 11:57:30 -0800 (PST) Received: from netcom10.netcom.com (netcom10.netcom.com [192.100.81.120]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id LAA21964 for ; Sun, 18 Feb 1996 11:57:26 -0800 (PST) Received: by netcom10.netcom.com (8.6.12/Netcom) id LAA25768; Sun, 18 Feb 1996 11:55:05 -0800 Date: Sun, 18 Feb 1996 11:55:04 -0800 (PST) From: James Cook Subject: Re: Lsoft's Listserv VS. Listproc??? To: Roger Fajman cc: List-Managers@greatcircle.com In-Reply-To: <199602181930.LAA20944@miles.greatcircle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On Sun, 18 Feb 1996, Roger Fajman wrote: > > How would the commercial "Listserv" by Lsoft compare with the Listproc > > product? > > You might have a look at their respective WWW pages: > > www.cren.net for Listproc > www.lfsoft.com for LISTSERV > I respect the bandwidth aspect of this suggestion. I have reviewed the basic literature, and hoped for actual user feedback, which is often richer and more pragmatic than promotional/online material. Thanks. James Cook From list-managers-owner Sun Feb 18 12:40:32 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id MAA24047 for list-managers-outgoing; Sun, 18 Feb 1996 12:35:24 -0800 (PST) Received: from CU.NIH.GOV (cu.nih.gov [128.231.64.112]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id MAA24035 for ; Sun, 18 Feb 1996 12:35:19 -0800 (PST) Message-Id: <199602182035.MAA24035@miles.greatcircle.com> To: List-Managers@greatcircle.com From: "Roger Fajman" Date: Sun, 18 Feb 1996 15:25:44 EST Subject: Re: Lsoft's Listserv VS. Listproc??? Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > You might have a look at their respective WWW pages: > > www.cren.net for Listproc > www.lfsoft.com for LISTSERV Oops. Of course that should be www.lsoft.com. From list-managers-owner Sun Feb 18 12:55:31 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id MAA24397 for list-managers-outgoing; Sun, 18 Feb 1996 12:45:50 -0800 (PST) Received: from CU.NIH.GOV (cu.nih.gov [128.231.64.112]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id MAA24390 for ; Sun, 18 Feb 1996 12:45:46 -0800 (PST) Message-Id: <199602182045.MAA24390@miles.greatcircle.com> To: jcook@netcom.com cc: List-Managers@greatcircle.com From: "Roger Fajman" Date: Sun, 18 Feb 1996 15:41:06 EST Subject: Re: Lsoft's Listserv VS. Listproc??? Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > I respect the bandwidth aspect of this suggestion. I have reviewed the > basic literature, and hoped for actual user feedback, which is often > richer and more pragmatic than promotional/online material. We use LISTSERV here and are just switching to the Unix version from the VM version. I can't say that I did an extensive evaluation of Listproc. Instead I decided to stick with what our users already were used to. Here's some differences that I can think of (1) Listproc 7.0 is cheaper than LISTSERV, especially if you are already a CREN member as we are. CREN members get one copy free. (2) LISTSERV is available for several platforms: Unix, NT, Win95, and VM. (3) LISTSERV servers cooperate with each other for building a global list of LISTSERV lists, for distributing messages, and for filtering spam. With the Unix version we'll miss the automatic file distribution and data base features of VM LISTSERV. L-Soft has promised these, but is quite late in delivering them. But Listproc doesn't have those features at all, as far as I know. Here's a wish list for LISTSERV compiled from my own ideas and from messages on the LSTSRV-L and LSTOWN-L lists. LISTSERV Wish List February 18, 1996 (1) A simple command to change the address of a subscriber (e.g., CHANGE listname old-addr new-addr). Wildcards should be allowed for userids. List owners could use it on their own list. LISTSERV postmasters could use it on all lists on a server. The advantage over subscribing and unsubscribing is that users settings would be preserved. The advantage over issuing a GET and editing the list of subscribers is that it's safer and would work on multiple lists. (2) Statistics on usage of lists for list owners and LISTSERV postmasters. Statistics should be kept on number of subscribers, number and size of posts, and number of bounces redirected to the list owner. Reports should be available daily, weekly, and monthly. There are various uses for this, such as to identify unused lists, identifying lists that are generating an excessive number of bounces, and to justify the existence of the LISTSERV. (3) Statistics on the usage of files in a file list, to be used primarily for identifying unused files. (4) Statistics on the usage of list archives by the data base function. (5) Messages sent to all-request should contain the list name so that bounces can be identified with the list whose owner they are for. (6) The ability to control the spam filter on a per subscriber basis, primarily for use with netnews gateways. (7) When a message is sent to two or more lists on the same server, users subscribed to more than one of the lists should receive only one copy of the message. (8) Security violations should be clearly noted in the log. (9) Control of defaults on a per server basis, by the LISTSERV maintainer. (10) A way in addition to using Resent- headers for a moderator to send edited messages back to the list so that they appear with the original poster's email address. (11) MIME digests. (12) Support for Delivery Status Notifications. This should allow for more automated processing of bounces. (13) LISTSERV messages in MIME format for messages to list owners, postmasters, and in response to commands. (14) Output from the QUERY command that is more amenable to machine processing. (15) QUERY support for topics. (16) Automatically delete notebook files older than a specified number of months. (17) Support for the TCP/IP Message Send Protocol in non-VM versions. From list-managers-owner Mon Feb 19 06:12:10 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id FAA22658 for list-managers-outgoing; Mon, 19 Feb 1996 05:59:08 -0800 (PST) Received: from rubble.west.ora.com (rubble.west.ora.com [198.112.209.191]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id FAA22646 for ; Mon, 19 Feb 1996 05:59:03 -0800 (PST) Received: by rubble.west.ora.com (4.1/SMI-4.1+JP-2.5) id AA02495; Mon, 19 Feb 96 05:58:47 PST From: Jerry Peek X-Mailer: MH 6.8.3 To: list-managers@greatcircle.com Subject: Re: Horror Story - is there a defense? References: <0099E106.B8133762.22@sacto.mp.usbr.gov> <199602180611.WAA21630@lunch.engr.sgi.com> Date: Mon, 19 Feb 1996 05:58:45 -0800 Message-Id: <2494.824738325@rubble.west.ora.com> Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On 17 February, "Henry W. Miller" wrote: > > From: MX%"jerry@ora.com" 17-FEB-1996 09:28:05.11 > > Listproc 6.0 (and probably later versions) do a few things to stop > > your problem of duplicate messages going to a list: > > > > - it keeps the last 500 (I think) Message-IDs sent to each list, and > > also sent to listproc itself (administrative requests). ... > > > > - it computes a checksum of each message body sent to a list. > > When a new message comes in, it compares the checksum to the last 500 > > checksums ... > > This would assume, of course, that the rogue mailer kept > generating the same message-id for each message. If not, then there > would still be trouble... On 17 February, close@lunch.engr.sgi.com (Diane Barlow Close) wrote: > You could always strip out the headers and do a body checksum... Sorry if I wasn't clear. That's what listproc does when it computes that checksum I mentioned. (I think it also strips trailing whitespace from each line of the body before it calculates the checksum... in case some gateway/etc. has added whitespace to the original message body.) --Jerry, jerry@ora.com From list-managers-owner Tue Feb 20 09:57:40 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id JAA00316 for list-managers-outgoing; Tue, 20 Feb 1996 09:54:30 -0800 (PST) Received: from cs.bu.edu (CS.BU.EDU [128.197.13.2]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id JAA00309 for ; Tue, 20 Feb 1996 09:54:23 -0800 (PST) Received: from csa.bu.edu by cs.bu.edu (8.6.10/Spike-2.1) id MAA02383; Tue, 20 Feb 1996 12:50:39 -0500 From: tasos@cs.bu.edu (Anastasios Kotsikonas) Received: by csa.bu.edu (8.6.10/Spike-2.1) id MAA27686; Tue, 20 Feb 1996 12:50:18 -0500 Message-Id: <199602201750.MAA27686@csa.bu.edu> Subject: Re: Horror Story - is there a defense? To: jerry@ora.com (Jerry Peek) Date: Tue, 20 Feb 1996 12:50:17 -0500 (EST) Cc: list-managers@GreatCircle.COM In-Reply-To: <2494.824738325@rubble.west.ora.com> from "Jerry Peek" at Feb 19, 96 05:58:45 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > Sorry if I wasn't clear. That's what listproc does when it computes > that checksum I mentioned. (I think it also strips trailing whitespace > from each line of the body before it calculates the checksum... in case > some gateway/etc. has added whitespace to the original message body.) it actually strips ALL white spaces from the body.... the commercial version, however, rolls in the From: address into the stripped body as well and then computes the checksum -- therefore a user can re-send his/her message from a different account if listproc bounces his/her original posting ("... you are not subscribed ..."); also, someone else can bounce the same message to the list (in that case Sender: or Resent-From: is rolled in, not From:)... tasos > --Jerry, jerry@ora.com > From list-managers-owner Tue Feb 20 11:15:11 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id KAA05686 for list-managers-outgoing; Tue, 20 Feb 1996 10:59:26 -0800 (PST) Received: from mycroft.GreatCircle.COM (mycroft.greatcircle.com [198.102.244.35]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id KAA05555 for ; Tue, 20 Feb 1996 10:59:04 -0800 (PST) Received: by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-960123) id KAA10790; Tue, 20 Feb 1996 10:03:30 -0800 Received: from unknown(128.197.13.2) by mycroft via smap (V1.3mjr) id sma010779; Tue Feb 20 10:02:34 1996 Received: from csa.bu.edu by cs.bu.edu (8.6.10/Spike-2.1) id NAA02895; Tue, 20 Feb 1996 13:03:24 -0500 From: tasos@cs.bu.edu (Anastasios Kotsikonas) Received: by csa.bu.edu (8.6.10/Spike-2.1) id NAA28560; Tue, 20 Feb 1996 13:03:06 -0500 Message-Id: <199602201803.NAA28560@csa.bu.edu> Subject: Re: Horror Story - is there a defense? To: harris@aix.wingra.com (Harlan Harris) Date: Tue, 20 Feb 1996 13:03:06 -0500 (EST) Cc: List-Managers@GreatCircle.COM In-Reply-To: <"9602181846.AA44474"@aix.wingra.com> from "Harlan Harris" at Feb 18, 96 12:46:19 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > > As people have pointed out, some of the commercial MLMs do Message-ID and > checksum storage to prevent these problems. Someone mentioned Listproc, > but from their message it sounds like they meant the old 6.0c version. > The commercial version, 7.X, correctly stores the checksums of the body > of the message, stripping the headers, exactly as suggested. I'm pretty > certain that that would have elegantly prevented your situation. As I mentioned in my previous post, *ALL* listproc versions stip headers and white spaces before computing the checksum... tasos From list-managers-owner Tue Feb 20 11:43:52 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id KAA05792 for list-managers-outgoing; Tue, 20 Feb 1996 10:59:45 -0800 (PST) Received: from mycroft.GreatCircle.COM (mycroft.greatcircle.com [198.102.244.35]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id KAA05704 for ; Tue, 20 Feb 1996 10:59:26 -0800 (PST) Received: by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-960123) id JAA10721; Tue, 20 Feb 1996 09:57:26 -0800 Received: from unknown(128.197.13.2) by mycroft via smap (V1.3mjr) id sma010707; Tue Feb 20 09:56:38 1996 Received: from csa.bu.edu by cs.bu.edu (8.6.10/Spike-2.1) id MAA02705; Tue, 20 Feb 1996 12:57:27 -0500 From: tasos@cs.bu.edu (Anastasios Kotsikonas) Received: by csa.bu.edu (8.6.10/Spike-2.1) id MAA28115; Tue, 20 Feb 1996 12:57:10 -0500 Message-Id: <199602201757.MAA28115@csa.bu.edu> Subject: Re: Lsoft's Listserv VS. Listproc??? To: RAF@CU.NIH.GOV (Roger Fajman) Date: Tue, 20 Feb 1996 12:57:09 -0500 (EST) Cc: jcook@netcom.com, List-Managers@GreatCircle.COM In-Reply-To: <199602182045.MAA24390@miles.greatcircle.com> from "Roger Fajman" at Feb 18, 96 03:41:06 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > (3) LISTSERV servers cooperate with each other for building a global > list of LISTSERV lists, for distributing messages, and for filtering > spam. so do listproc servers, except for spamming at this point. > With the Unix version we'll miss the automatic file distribution and > data base features of VM LISTSERV. L-Soft has promised these, but is > quite late in delivering them. But Listproc doesn't have those > features at all, as far as I know. it does in 7.1 and subsequent... > Here's a wish list for LISTSERV compiled from my own ideas and from > messages on the LSTSRV-L and LSTOWN-L lists. > > LISTSERV Wish List > February 18, 1996 > > (1) A simple command to change the address of a subscriber (e.g., > CHANGE listname old-addr new-addr). Wildcards should be allowed > for userids. List owners could use it on their own list. > LISTSERV postmasters could use it on all lists on a server. The > advantage over subscribing and unsubscribing is that users > settings would be preserved. The advantage over issuing a GET > and editing the list of subscribers is that it's safer and would > work on multiple lists. listproc supports changing of addresses on the fly, if the list owners allow that. > (2) Statistics on usage of lists for list owners and LISTSERV > postmasters. Statistics should be kept on number of subscribers, > number and size of posts, and number of bounces redirected to the > list owner. Reports should be available daily, weekly, and > monthly. There are various uses for this, such as to identify > unused lists, identifying lists that are generating an excessive > number of bounces, and to justify the existence of the LISTSERV. listproc supports something like this for accounting purposes -- it provides hooks to external programs and passes on information... > (9) Control of defaults on a per server basis, by the LISTSERV > maintainer. listproc supports default subscriber settings, set by the owners... > (11) MIME digests. listproc 8.0 sends MIME digests... tasos From list-managers-owner Tue Feb 20 15:45:14 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id PAA18573 for list-managers-outgoing; Tue, 20 Feb 1996 15:41:36 -0800 (PST) Received: from linden.fortnet.org (linden.fortnet.org [199.45.144.10]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id PAA18560 for ; Tue, 20 Feb 1996 15:41:32 -0800 (PST) Received: (from phredo@localhost) by linden.fortnet.org (8.7.2/8.7.2) id QAA10240; Tue, 20 Feb 1996 16:42:27 -0700 (MST) Date: Tue, 20 Feb 1996 16:42:27 -0600 (MDT) From: "Blaine E. Thompson" Subject: List For Sale To: "Blaine E. Thompson" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I have a ex-listserv based list that runs in Turkey that has migrated to Listproc. Since I do not know that much about LIstproc, I wish to give up this list to a capable list-owner with proficient konwledge of Listproc. The list centers around classic and sport automobiles and is quite low volume...perhaps 10-20 posts/month. If interested, please e-mail me. Thanks!! Blaine (phredo@fortnet.org) From list-managers-owner Wed Feb 21 21:05:14 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id UAA06043 for list-managers-outgoing; Wed, 21 Feb 1996 20:51:55 -0800 (PST) Received: from digital.netvoyage.net (digital.netvoyage.net [205.162.154.10]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id UAA06038 for ; Wed, 21 Feb 1996 20:51:52 -0800 (PST) Received: from digital.netvoyage.net (digital.netvoyage.net [205.162.154.10]) by digital.netvoyage.net (8.6.11/8.6.9) with SMTP id UAA19518 for ; Wed, 21 Feb 1996 20:50:13 -0800 Date: Wed, 21 Feb 1996 20:50:10 -0800 (PST) From: Brock Rozen To: List Managers Subject: AOL Message-ID: X-URL: http://www.netvoyage.net/~brozen MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Is AOL bouncing everybody an user unknowns again? Or is it just me? THanks, ------------------------------------------------------------------------- | Brock Rozen | brozen@netvoyage.net | http://www.netvoyage.net/~brozen | | Check out my Auto-Reply System -- Send me mail with subject SEND HELP | ------------------------------------------------------------------------- From list-managers-owner Wed Feb 21 22:00:04 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id VAA09342 for list-managers-outgoing; Wed, 21 Feb 1996 21:57:01 -0800 (PST) Received: from netcom17.netcom.com (netcom17.netcom.com [192.100.81.130]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id VAA09337 for ; Wed, 21 Feb 1996 21:56:56 -0800 (PST) Received: by netcom17.netcom.com (8.6.12/Netcom) id VAA29579; Wed, 21 Feb 1996 21:54:14 -0800 Date: Wed, 21 Feb 1996 21:54:13 -0800 (PST) From: James Cook Subject: Listservs, line-capacity, selection? cc: List Managers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk When planning to administer a possibly large array of listservs, and selecting among various firms offering to provide 56k frame relay, ISDN variations, and T-1 options, how would experienced administrators here suggest comparing alternative sources in terms of actual speed of throughput, consistency of performance, etc.. Many firms, including Netcom and others, have marketing people who strongly suggest their CIR's, latency, and other factors underlying throughput of mail is better than others...given their MAE WEST and MCI and other structures. Is there a good method or checklist for choosing among these options and verifying their actual vs. claimed throughput/CIR performance BEFORE investing the thousands in set up in equipment? What technical measurements, if any, might you undertake on your own before selecting your next expansion via frame relay or other providers? Thank you. James Cook From list-managers-owner Wed Feb 21 23:44:18 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id XAA13670 for list-managers-outgoing; Wed, 21 Feb 1996 23:32:20 -0800 (PST) Received: from tango.rahul.net (tango.rahul.net [192.160.13.5]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id XAA13656 for ; Wed, 21 Feb 1996 23:32:14 -0800 (PST) Received: from bolero.rahul.net by tango.rahul.net with SMTP id AA25541 (5.67b8/IDA-1.5 for ); Wed, 21 Feb 1996 23:30:23 -0800 Received: from jive.rahul.net by bolero.rahul.net with SMTP id AA25476 (5.67b8/IDA-1.5); Wed, 21 Feb 1996 23:30:22 -0800 From: Steve Portigal Received: by jive.rahul.net (5.67b8/jive-a2i-1.0) id AA10155; Wed, 21 Feb 1996 23:30:18 -0800 Message-Id: <199602220730.AA10155@jive.rahul.net> Subject: Re: AOL To: brozen@netvoyage.net (Brock Rozen) Date: Wed, 21 Feb 1996 23:30:18 -0800 (PST) Cc: list-managers@greatcircle.com In-Reply-To: from "Brock Rozen" at Feb 21, 96 08:50:10 pm Organization: GVO - Interface Design Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Brock Rozen spake: > > Is AOL bouncing everybody an user unknowns again? Or is it just me? I haven't got any problems tonight. My 100 AOL recipients got their digest no problem. -- | steve portigal G V O | user interface dude | culturally aware interface design From list-managers-owner Thu Feb 22 10:26:19 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id KAA01941 for list-managers-outgoing; Thu, 22 Feb 1996 10:06:12 -0800 (PST) Received: from mycroft.GreatCircle.COM (mycroft.greatcircle.com [198.102.244.35]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id KAA01578 for ; Thu, 22 Feb 1996 10:05:11 -0800 (PST) Received: by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-960123) id CAA20351; Thu, 22 Feb 1996 02:31:44 -0800 Received: from sacusr.mp.usbr.gov(140.214.12.2) by mycroft via smap (V1.3mjr) id sma020343; Thu Feb 22 02:30:48 1996 Received: by sacto.mp.usbr.gov (MX V4.2 VAX) id 2; Thu, 22 Feb 1996 02:30:59 PST Date: Thu, 22 Feb 1996 02:30:56 PST From: "Henry W. Miller" To: brozen@netvoyage.net CC: list-managers@greatcircle.com, henrym@sacto.mp.usbr.gov Message-ID: <0099E456.423B9162.2@sacto.mp.usbr.gov> Subject: RE: AOL Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > From: MX%"brozen@netvoyage.net" 21-FEB-1996 22:27:20.06 > Subj: AOL > Is AOL bouncing everybody an user unknowns again? Or is it just me? > > THanks, > > > ------------------------------------------------------------------------- > | Brock Rozen | brozen@netvoyage.net | http://www.netvoyage.net/~brozen | > | Check out my Auto-Reply System -- Send me mail with subject SEND HELP | > ------------------------------------------------------------------------- > Brock, I've seen no problems here - I have a major list and about 1/6 of the membership I would say are on AOL. I've seen no bounces from AOL at all in fact for several days. -HWM From list-managers-owner Thu Feb 22 11:20:00 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id LAA04945 for list-managers-outgoing; Thu, 22 Feb 1996 11:08:49 -0800 (PST) Received: from red-05-imc.itg.microsoft.com (abash1.microsoft.com [131.107.3.23]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id LAA04932 for ; Thu, 22 Feb 1996 11:08:43 -0800 (PST) Received: by red-05-imc.itg.microsoft.com with Microsoft Exchange (IMC 4.3.736) id <01BB0115.9B80EF80@red-05-imc.itg.microsoft.com>; Thu, 22 Feb 1996 11:04:59 -0800 Message-ID: From: Brian Fleming To: "list-managers@greatcircle.com" , "lstsrv-l@listserv.net" , "lstown-l@listserv.net" Subject: Bill Gates ListServ Spam (another!) Date: Thu, 22 Feb 1996 10:09:55 -0800 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.3.736 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk My apologies if this has already made the rounds on these lists, but it was suggested that I forward this here... Thank you. Brian Fleming brianf@microsoft.com >---------- >From: Brian Fleming Sent: Monday, February 19, 1996 1:55 PM > >Any subscriptions to listservs in the last 2 weeks from billg@microsoft.com >are fake. > >Feel free to contact me with questions--I haven't had a chance to look >through the mail yet, but it began arriving about 30 minutes ago. > >---- Brian From list-managers-owner Sun Feb 25 14:22:38 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id OAA00123 for list-managers-outgoing; Sun, 25 Feb 1996 14:00:41 -0800 (PST) Received: from sys2.bloodstockwww.com (sys2.bloodstockwww.com [206.24.34.70]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id OAA15736 for ; Wed, 21 Feb 1996 14:21:56 -0800 (PST) Received: (from billy@localhost) by sys2.bloodstockwww.com (8.7.1/8.7.1) id RAA27443 for list-managers@greatcircle.com; Wed, 21 Feb 1996 17:22:52 -0500 (EST) Date: Wed, 21 Feb 1996 17:22:52 -0500 (EST) From: Bill Antoniadis Message-Id: <199602212222.RAA27443@sys2.bloodstockwww.com> To: list-managers@greatcircle.com Subject: Help w/ Majordomo Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Hi, I have set up a moderated mailing list using Majordomo but when somebody sends e-mail to that list with the approved password, the Subject header is chopped off (along with the password). Am I doing something wrong? Has anyone experienced this? Any help would be greatly appreciated! Billy billy@bris.com From list-managers-owner Mon Feb 26 08:17:59 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id IAA27571 for list-managers-outgoing; Mon, 26 Feb 1996 08:05:14 -0800 (PST) Received: from vorlon.mit.edu (VORLON.MIT.EDU [18.238.0.139]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with ESMTP id IAA27559 for ; Mon, 26 Feb 1996 08:05:10 -0800 (PST) Received: (from jered@localhost) by vorlon.mit.edu (8.7.3/8.7.3) id LAA23444; Mon, 26 Feb 1996 11:03:47 -0500 Message-Id: <199602261603.LAA23444@vorlon.mit.edu> X-Mailer: exmh version 1.6.5 12/11/95 To: list-managers@greatcircle.com Subject: Majordomo mailing loops? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Feb 1996 11:03:46 EST From: Jered Floyd Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Last night I awoke to my machine making quite a bit of noise. It was doing something to the disk every 2 seconds or so, and had been doing so for many hours. After I logged in, I discovered that sendmail was syslogging every two seconds, moreover the messages it was syslogging were: Feb 26 06:50:21 vorlon sendmail[20756]: GAA20755: to="|/home/majordom/majordomo -1.93/wrapper majordomo", delay=00:00:02, xdelay=00:00:02, mailer=prog, stat=Sent Feb 26 06:50:22 vorlon sendmail[20767]: GAA20767: from=Majordomo-Owner, size=163, class=0, pri=30163,nrcpts=1, msgid=<199602261150.GAA20767@vorlon.mit.edu>, relay=majordom@localhost Apparently, a none-too-clueful subscriber who thought he or she understood SMTP tried and failed to forge a good subscribe message to some mailing list. He or she did, however, succeed in having majordomo receive mail from its own address. Majordomo will reply to that mail, sending a message to itself. Wash, rinse, repeat as necessary. This is arguably a bad thing. However, I don't know what an appropriate solution is. Having majordomo not reply to itself is a start, but it's nearly as easy to get it in a fight with another majordomo, or some other autoreply software. Has anyone else been bitten by this? Does anyone have suggestions on how to avoid 25 MB syslog files in the future? Thanks. --Jered jered@mit.edu From list-managers-owner Tue Feb 27 11:03:39 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id KAA23259 for list-managers-outgoing; Tue, 27 Feb 1996 10:42:45 -0800 (PST) Received: from kajen.com (mother.kajen.com [194.16.18.1]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id KAA23250 for ; Tue, 27 Feb 1996 10:42:29 -0800 (PST) Received: from dennis (patrik@dennis.kajen.com [194.16.18.106]) by kajen.com (8.6.12/8.6.12) with SMTP id TAA11771 for ; Tue, 27 Feb 1996 19:40:47 +0100 Message-ID: <31335011.4E808256@kajen.com> Date: Tue, 27 Feb 1996 19:40:17 +0100 From: Patrik Berglund Organization: Kajplats 305 X-Mailer: Mozilla 2.0 (X11; I; Linux 1.3.64 i586) MIME-Version: 1.0 To: List-Managers@GreatCircle.COM Subject: Re: List-Managers-Digest V5 #39 References: <199602260900.BAA15290@miles.greatcircle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > From: Bill Antoniadis > Date: Wed, 21 Feb 1996 17:22:52 -0500 (EST) > Subject: Help w/ Majordomo > > Hi, I have set up a moderated mailing list using Majordomo but when > somebody sends e-mail to that list with the approved password, the Subject > header is chopped off (along with the password). Am I doing something > wrong? Has anyone experienced this? Any help would be greatly appreciated! > > Billy > > billy@bris.com I had the same problem with one of the lists we host. I solved it by making it an open list, and specifying the list-managers email address with the "restrict_post" keyword in the configuration file for the list. -- | Patrik Berglund patrik@kajen.com | Kajplats 305 | http://www.kajen.com/~patrik/ | N. Neptunig. 5 |------------------------------------------| S-211 18 MALMO | System administrator, customer support | SWEDEN `------------------------------------------' Security is when everything is settled. When nothing can happen to you. Security is the denial of life. -Germaine Greer From list-managers-owner Tue Feb 27 11:32:59 1996 Received: (majordom@localhost) by miles.greatcircle.com (8.7.1-lists/Lists-951222-1) id LAA24464 for list-managers-outgoing; Tue, 27 Feb 1996 11:30:40 -0800 (PST) Received: from tango.rahul.net (tango.rahul.net [192.160.13.5]) by miles.greatcircle.com (8.7.1/Miles-951221-1) with SMTP id LAA24459 for ; Tue, 27 Feb 1996 11:30:34 -0800 (PST) Received: from bolero.rahul.net by tango.rahul.net with SMTP id AA24536 (5.67b8/IDA-1.5 for ); Tue, 27 Feb 1996 11:29:12 -0800 Received: from jive.rahul.net by bolero.rahul.net with SMTP id AA04850 (5.67b8/IDA-1.5 for ); Tue, 27 Feb 1996 11:29:11 -0800 From: Steve Portigal Received: by jive.rahul.net (5.67b8/jive-a2i-1.0) id AA24964; Tue, 27 Feb 1996 11:29:05 -0800 Message-Id: <199602271929.AA24964@jive.rahul.net> Subject: pobox redux To: List-Managers@GreatCircle.COM Date: Tue, 27 Feb 1996 11:29:05 -0800 (PST) Organization: GVO - Interface Design Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Stupidly, I ignored the pobox discussion here recently. Now I find my list has to move and I "discovered" pobox, realizing that I had seen a thread on it here. What's the feelinghere about their service, reliabity, pricing? It seems GREAT to me, I want to start there right away, actually, but I'd like to hear from others. Steve -- | steve portigal G V O | user interface dude | culturally aware interface design