From list-managers-owner Thu Mar 2 05:31:44 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id FAA02432 for list-managers-outgoing; Thu, 2 Mar 1995 05:23:00 -0800 Received: from netcom21.netcom.com (netcom21.netcom.com [192.100.81.135]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id FAA02427 for ; Thu, 2 Mar 1995 05:22:56 -0800 Received: from [192.187.167.52] by netcom21.netcom.com (8.6.9/Netcom) id FAA29013; Thu, 2 Mar 1995 05:19:53 -0800 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: Level Seven Design X-PGP-KeyID-Fprnt: 4AAF00E5 - 30D81F3484E6A83F 6EC8D7F0CAB3D265 X-PGP-KeyLocation: ftp.netcom.com:/pub/dd/ddt/crypto/ddtPGPkey.txt Date: Thu, 2 Mar 1995 05:22:37 -0800 To: nruggles@panix.com (Neil Ruggles) From: Dave Del Torto Subject: Re: How should public relations pros work with mailing lists Cc: list-managers@greatcircle.com Sender: list-managers-owner@GreatCircle.COM Precedence: bulk At 9:10 AM 2/27/95, Neil Ruggles wrote: >>Pricing info should only be posted by persons without a conflict of >>interest and only in clearly labelled, easily deleted forms. > >Dave, third parties who post supposedly unbiased pricing info or favorable >reviews of a vendor may or may not be associated with the vendors. It can >be pretty hard to tell the difference between a serious fan of a given >product and a paid professional promoter. Especially since the promoter >gets paid to be clever. Neil, I've not yet encountered anyone who was a decoy advertiser for a company on any list, and almost always, any infomation provided in the course of a discussion is balanced and includes pros & cons. The only "product advertising" I've seen on lists is spamming by unethical weasels. You must be confusing the Internet I work on with some ideal of an Internet that tolerates the same sort of crass commercialism that the TV networks allow (fake "consumer advocate panels," "infomercials," etc.). Furthermore, if you'll allow me to play Angel's Advocate a moment longer, when people mention commercial products on a list, I expect them to explicitly state that they don't have any financial interest in the company - I always do myself when I mention anything. If they don't state as much, and they endore a product, then they're not being "clever," they're practicing "fraud." Not only that, they're practicing fraud in a medium where thay can be easily traced, which is the inverse of clever. >Here is a quote I picked today (2/27) off a journalism list I subscribe to: > >>BTW, those of you on this list might be interested to know that when I gave >>a speech recently on Internet marketing, one of the attendees told me >>privately that "We have gotten a lot of business off the Net. We have >>chosen about five of our most passionate, positive end-users to lurk for us >>and respond positively to messages about us. We pay them for this." These >>users are not revealing their financial arrangement with the vendor as they >>post their positive comments/recommendations. That's plain unethical. You should inform them of this privately and see what their response is. The "lurkers" who do this for them probably practice forms of fraud or other criminal activities in other parts of their lives, and there's no way to protect against this without establishing a "police force" on the net, something I'm loathe to do. Ethics is a system of beliefs and practices which everyone should agree to support or no-one will benefit from them. >I'm curious whether you would rather have a vendor "sneak" their promotions >into your list by having a third party say good things about them, or have >the promotions clearly identified as as such? You don't offer me much of a choice here, so my answer is "neither one." I still don't see how a vendor could "sneak" promotions onto a list if I didn't allow promotions on the list, without either violating the rules of the list they agreed to when they became a subscriber (they'd get one shot off and be dropped), or by practicing fraud as described above (they might eventually be visited by the real Police if discovered). If people on a list mention something in passing while discussing a topic ("yeah, and these random number generator chips from OBFUSCO, Inc. are perfect for those elliptical curve crypto functions") I'd expect them to follow basic netiquette and mention that they had no financial interest in OBFUSCO, Inc. FYI, I've had discussions at conferences with folks from the FBI's Computer Crime squad who'd like to meet your business aquiaintenances and discuss their methods with them in a poorly-lit room. Their days pulling that sort of fraud are numbered. I have no problem with one or two lines of header information (it can be filtered or switched off pretty easily, and it's no business of mine what you paint on your car as much as it might offend me to look at it in traffic), but I think that lists of an academic nature, which is what I'd be managing, are clearly NOT the place for commercial promotion. Again, there are other ways for such commercial interests to have a place on the net that people _choose_ to visit (URLs, Gopher and FTP sites, etc.). With all the manifold ways to flog products electronically, can't public relations and marketing people be more creative than "putting up billboards in classrooms?" Or must they shove their pap in our faces no matter where we go? I speak of others here, of course: I'm sure this doesn't apply to a thoughtful person like yourself, who's at least asking about the Right Thing from a list-manager's perspective. dave From list-managers-owner Fri Mar 3 10:59:23 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA04331 for list-managers-outgoing; Fri, 3 Mar 1995 10:53:09 -0800 Received: from bbfm.di.com (bbfm.di.com [204.74.64.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id KAA04326 for ; Fri, 3 Mar 1995 10:53:06 -0800 Received: by bbfm.di.com (8.6.9/TD-1.12) id KAA11993 for List-Managers@GreatCircle.COM on Fri, 3 Mar 1995 10:52:00 -0800 From: Todd Day Message-Id: <199503031852.KAA11993@bbfm.di.com> Subject: What to do when list gets too big? To: List-Managers@GreatCircle.COM Date: Fri, 3 Mar 1995 10:52:00 -0800 (PST) In-Reply-To: <199503030900.BAA29889@miles.greatcircle.com> from "list-managers-digest-owner@GreatCircle.COM" at Mar 3, 95 01:00:13 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2152 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk You might remember from previous posts that I run the Talon/Eclipse/Laser list. This list is going on five years now, and is starting to get a bit out of control. I have something like 500 people on it (pretty small compared to some of your guys' lists, but getting large for me). I've gotten complaints from some of the old timers that the quality of the list is decreasing due to the large amount of newbie questions and rehashed issues. I do make an effort to delete a large number of simple requests and redirect the sender to net resources that can answer their questions (we have a large archive plus a nice little web site). However, I feel if I delete too much of these types of posts, these beginners might feel a little left out of the discussion, so I let some sneak by. This wasn't a problem in the past, but the list is growing pretty rapidly now, enough to significantly impact the true S/N of the list. Another problem is that in '95, there is a new model of the car. The changes from this model to '90-'94 aren't really that significant, but a lot of questions have popped up that '90-'94 people aren't really interesting in answering again. Anyway, I have the following suggestions/questions for improving my list and I want to hear from other list managers that have gone through similar problems. 1) Split the list into sub-topics. pros: perceived S/N should increase keeps the old timers happy newbies can get their own sub-topic cons: I won't be able to heavily edit, due to load more of the typical admin problems (bounces, subscriptions, etc) 2) Stop the "live" feed. You may remember that I allow a digest and non-digest (live) version of the list. A lot of the increased load is due to the people on the live feed replying way too often. pros: S/N should increase, due to less posting cons: a *lot* of people really like the live feed I could solve the problem of heavy editing by threating to unsubscribe anyone posting any of my pet peeves, like too much attribution and long .sigs. So, what have you done with your list when the load gets too heavy and the old timers start grumbling? -todd- From list-managers-owner Fri Mar 3 18:34:02 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id SAA10416 for list-managers-outgoing; Fri, 3 Mar 1995 18:07:37 -0800 Received: from calon.calon.com (calon.calon.com [199.4.94.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id KAA07815 for ; Thu, 2 Mar 1995 10:24:34 -0800 Message-Id: <199503021824.KAA07815@miles.greatcircle.com> Subject: Help with Moderated List To: list-managers@greatcircle.com Date: Thu, 2 Mar 1995 10:20:14 -0800 (PST) From: "Dave Lampson" X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 848 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Greetings, and apologies in advance for a newbie question. I have set up a moderated mailing list, defined a distribution list, created an info file, editted the config file, and most things seem to be working fine, except that I can't get anything distributed. Subscribing and retrieving info works, but when I try and approve a post for distribution, it just keeps bouncing back to me. I have tried putting the "Approved:" line in both the header of the message (I use elm) and as the first line in the body of a message, and I've sent it to "list" and not to "list-request", but they just keep getting bounced back for approval. I'm stumped, but surely I'm missing something obvious. I've been through the documentation thoroughly, and can't see any problem with the procedure I'm using. Any suggestions? Thanks, Dave lampson@calon.com From list-managers-owner Sat Mar 4 13:59:11 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA13208 for list-managers-outgoing; Sat, 4 Mar 1995 13:32:05 -0800 Received: from tta.com (tta.com [198.65.128.193]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id NAA13201 for ; Sat, 4 Mar 1995 13:32:01 -0800 Received: (from stan@localhost) by tta.com (8.6.9/8.6.9) id PAA04051; Sat, 4 Mar 1995 15:11:08 -0600 From: stan@tta.com (Stan Hanks) Message-Id: <199503042111.PAA04051@tta.com> Subject: Re: What to do when list gets too big? To: List-Managers@GreatCircle.COM Date: Sat, 4 Mar 1995 15:11:08 -0600 (CST) Cc: today@di.com In-Reply-To: from "Todd Day" at Mar 3, 95 10:52:00 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 4669 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > You might remember from previous posts that I run the Talon/Eclipse/Laser > list. This list is going on five years now, and is starting to get a bit > out of control. I have something like 500 people on it (pretty small > compared to some of your guys' lists, but getting large for me). I run Porschephiles, and we're at over 1300 after about 5 years. I hit most of the problems you're talking about around two years ago, and have whole 'nother pile facing me as this thing pushes towards 2000 and above... > I've gotten complaints from some of the old timers ... This is the nature of "old timers" -- they like it "like it used to be". My solution was so to get some of them involved in helping out with various aspects of list management (more on that later), and to, with deep regret and sense of loss, let some of them go their way. > Another problem is that in '95, there is a new model of the car Uh-huh. I'm supporting the same issue, in spades. Ownership on my list ranges across 45 model years, 7 major models with various sub-variants, plus the factory specials and racing cars... It's a lot harder to do just a single model in my opinion, because you *DO* have so much tighter focus. Look at the MR-2 list (for which I also run the digest) -- they have the Mk-I, Mk-II, and turbo/supercharged splits. Somehow, it works out... > 1) Split the list I thought about that, and decided not to. The issue: how do you handle distribution across topic lines?? The heading says "911" but it's really also "autocross" and "PCA events". Making sure that no one misses info that they want is a *BIG* deal -- some sort of semanticly driven infobot is what's called for. Then you have to ask yourself if it was possible to have one of them, would it be worth the extra overhead or would you just distribute a massive feed anyway and let people run their own infobots to pull out the stuff they really wanted? My stated policy is that the list won't split until I find a good clean solution for this problem. > 2) Stop the "live" feed. I wouldn't do that. I've seen too many "I'm in the middle of doing X, and need to know Y -- HELP!" messages over the years. I've also noted with some interest that a message-at-a-time feed is much easier for some of the mail readers on some of the Major On Line Services to deal with -- if you send out a digest, then everyone has to download everything, where with the right user agent, you can just tag the messages that look interesting and download them only. > I could solve the problem of heavy editing by threating to unsubscribe anyone > posting any of my pet peeves, like too much attribution and long .sigs. Automation is a BIG step forward. I put up three different filter packs: 1) trap anything that looks like subscribe/unsubscribe, or very very short messages that *could* be the above, and route to the list admin. 2) fully block messages containing certain key words and phrases This also can be used to block certain individuals from posting 3) trap anything that contains certain other key words and phrases for approval before release into the main mail reflector. I've had to yell at people for being boneheads more than a few times, but have only had to fully sanction someone ONCE. It was not pleasant. I would hope not to have to do it again. There's also a useful trick I picked up from another list I subscribe to. Getting old timers involved in doing certain things is very good -- let everyone know that Old Joe is going to answer questions about Tires and Old Bill is going to answer questions about Oil, and have them maintain FAQs. When someone asks a newbie question, everyone knows that Joe or Bill or Brad or Mark or someone is more or less the "designated hitter" for that one. They send out a private e-mail, everyone is happy. IF they discover something new or think it merits a PUBLIC response, they can do that too. The *BIG* problem is that once you clear the 1000 subscriber point, it starts to get a netnews "feel" to it -- these topics pop up that develop a life of their own like radar detectors, good cop/bad cop, speeding, etc. and you can't shut them down (unless you have a filter capability). The other big problem is resources. I had to modify a bulk mailer program that I picked up somewhere over the years to handle my message load. From a 486/25 running BSDI, I send -- on average -- 58,000 mail messages *A DAY*. Do that counting on sendmail to handle it all, and it chokes. MajorDomo turns greenish just thinking about it. Clearly a faster system would help but only masks the real issue: it's alot of work to push that much mail. Stan Hanks From list-managers-owner Sun Mar 5 12:07:41 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA00710 for list-managers-outgoing; Sun, 5 Mar 1995 11:39:15 -0800 Received: from mycroft.GreatCircle.COM (mycroft.greatcircle.com [198.102.244.35]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA00698 for ; Sun, 5 Mar 1995 11:39:12 -0800 Received: from qvarsx.er.usgs.GOV by mycroft.GreatCircle.COM (8.6.10/SMI-4.1/Brent-950108) id JAA25530; Sun, 5 Mar 1995 09:33:43 -0800 Received: from macdgs1.er.usgs.gov (macdgs1.er.usgs.gov [130.11.52.62]) by qvarsx.er.usgs.GOV (EMAIL 1.2) with SMTP id RAA08831 for ; Sun, 5 Mar 1995 17:34:48 GMT Received: by macdgs1.er.usgs.gov (5.4R2.01/200.1.1.4) id AA13532; Sun, 5 Mar 1995 12:40:00 -0500 Date: Sun, 5 Mar 1995 12:40:00 -0500 From: rjohnson@macdgs1.er.usgs.GOV (Robert F. Johnstone) Message-Id: <9503051740.AA13532@macdgs1.er.usgs.gov> To: List-Managers@greatcircle.com Sender: list-managers-owner@GreatCircle.COM Precedence: bulk lists From list-managers-owner Sun Mar 5 17:08:16 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id RAA07199 for list-managers-outgoing; Sun, 5 Mar 1995 17:01:33 -0800 Received: from gw2.att.com (gw2.att.com [192.20.239.134]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id WAA14604 for ; Fri, 3 Mar 1995 22:47:33 -0800 Received: from anuxv.UUCP by ig1.att.att.com id AA12196; Fri, 3 Mar 95 15:13:28 EST Message-Id: <9503032013.AA12196@ig1.att.att.com> To: list-managers@greatcircle.com From: merchant@anuxv.att.com (s.merchant) Original-To: list-managers@greatcircle.com Date: 3 Mar 1995 14:53 EST Subject: re: What to do when list gets too big? Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Todd Day asks: >So, what have you done with your list when the load gets too heavy and the >old timers start grumbling? Establish guidelines for postings, that are included in the "welcome" message and reposted periodically (and perhaps excerpts also mailed to frequent offenders). Here are my set of proposed guidelines for my ballroom list that I posted to the list, soliciting opinions, modifications, etc. By and large the guidelines were very well received. I also got some good suggestions for a few modifications, which are not yet incorporated into the version I'm attaching here; these included things like: - Check the FAQ if you are a new member before posting - Make the subject line descriptive Feel free to edit and use for your list if you'd like. The advantage of guidelines that are somewhat formally adopted is that you have at least a somewhat objective set of rules to point to. Furthermore, "enforcement" can be by "peer pressure"--any member of the group can send e-mail to the offender attaching the guidelines, and pointing out the violation, and that removes some of the burden from the list administrator. Unless you have a very divisive and argumentative group (which does not seem to be the case), it is unlikely that you will break out into a "rules war." Shahrukh Merchant merchant@anuxv.att.com ================================================================ [Excerpts from my mail to members of the ballroom list] THE PROBLEM =========== As many of you have noticed, the traffic on the ballroom mailing list has got to the point that it is reducing the effectiveness of the list. There are two problems with this: 1. The more important one is it drives people away from the list who don't have the time or inclination (or high-bandwidth user interfaces) to handle the volume. Based on the increasing subscription rate, there should be 500 or more members on the list. In fact, the list membership is just at around 250, which is _less than_ its high of 300+ several months ago. I see a direct correlation between the volume and unsubscription rate--many people actually send me e-mail telling me that that's why they unsubscribed. Consequently, I think we all lose out by the reduction in the number of participants (which is _not_ compensated for by the increased participation of those remaining...). In a sense, the list is victim of its own "success," if you measure success by volume of postings (though I prefer to measure it in terms of the number of subscribers and the quality of the postings). 2. Unlike a Usenet newsgroup, a mailing list--even an automated one-- requires a certain amount of personal administration, and it has become burdensome. (To give you an idea, I get about 200 messages _per day_ related to the ballroom list; there are always 2-4 addresses generating bounced mail on any day, and _each_ generates a message for _each_ message to the list.) POSSIBLE OPTIONS ================ There are a few: 1. Start up the moderated ballroom list to supplement the unmoderated one. This would address problem #1 above, but would actually exacerbate #2. 2. Make "ballroom" a moderated-only list. This would be effective, but I think many of us would miss the open forum of an unmoderated list. It would also considerably reduce the transparency of the rec.arts.dance (which would remain unmoderated) <--> ballroom list gateway. 3. Establish voluntary guidelines for mailings to the ballroom list that would reduce the volume through some common-sense suggestions without, one hopes, introducing an atmosphere of restrictiveness or censorship. I would like to try option 3 as it seems the least disruptive. Besides, many people have voiced the sentiment that there is a lot of "noise" and trivia on the list anyway, so perhaps there would be some other side benefits to these guidelines. [Some stuff deleted] PROPOSED GUIDELINES (FINALLY) ============================= [Each guideline is followed by an "editorial" on why I believe it is appropriate.] 1. RELEVANCE OF SUBJECT: Only submit articles that are related to ballroom or swing dancing or a directly related subject. There seems to be a school of thought that the list is for discussion on any subject whatsoever, as long as it is between ballroom dancers, or as long as it stemmed from a subject that originally did pertain to ballroom dancing. From day one, that has never been my intention in setting up the list--even when it was on athena.mit.edu, the description of the purpose of the list clearly stated, I think, its primary purpose. In a previous era, when the volume was low, these digressions did little harm and, one could argue, even added a certain amount of congeniality. While I certainly do not intend to imply that discussions should be limited to technical ones by any means--opinions, questions, philosophy, social dynamics, music, etc., are all fine--it should bear *some* relevance to the purpose of the list (ballroom/swing dancing). 2. BROAD INTEREST: Don't send personal replies to the entire list. The list has deliberately been configured so that replies by default do NOT go to the whole list. If you choose to override the default, please make sure that it is warranted, i.e., ask yourself if you are including information that would be of interest to the list _in general_. Even some information of general interest can be sent only to the requester, if the requester promises to post a summary (see #3). 3. ETIQUETTE WHEN ASKING QUESTIONS: Request that answers be sent directly to you, and offer to post summaries of responses. Questions are fine--the access to a large number of people who might answer them (though not necessarily consistenly :-)) is one of the biggest assets we have in the list. However, they also have the potential for generating a lot of list traffic with bits and pieces of answers. A good way to "get the best of both worlds," and also for those who ask for the information and presumably benefit from it to "return the favour" to the list, is to offer to post a summary or compilation of the information back to the list. E.g., "Where can I go ballroom dancing in Albuquerque, New Mexico? Please send e-mail responses directly to me, and I will post a summary of responses back to the list, combined with my own observations and experiences when I return. I have checked the Dancers' Archive, but couldn't find what I wanted--I will also add the new information to the Dancers' Archive file and send the update to Eileen." [Now *there's* a socially reponsible posting!] Not only does this reduce piecemeal traffic, but your compilation may make an excellent article for inclusion in the Dancers' Archives, or FAQ, or even so that other interested people can store all the pertinent information in one mail message. 4. AVOID TRIVIA: Please refrain from trivial responses (usually characterized by being 1-2 lines long). This is not to encourage you to be verbose if you can make a point concisely, but most 1-2 line responses of late have seemed rather trivial. When one is asking several hundred people to go through your message (and the dozens of lines of quoted material that typically accompanies these trivial messages), would it not behoove one to put at least a little thought into the content? Examples of trivial messages (unless accompanied by some further elaboration): "Me [sic] too!" "I'm not sure if I would agree with that." "Ha, Ha!" "I was wondering that too." These are probably appropriate if sent *just* to the original poster, but it really does little more than clutter up mailboxes if sent to the whole list. (Many _questions_ ARE 1-2 lines long and appropriately so--this guideline is not intended to apply to questions.) 5. SILENCE MAY BE GOLDEN: There is nothing wrong with a silent list. OK, that's not an absolute for ALL lists. For example, for a startup list, some continuous traffic may be desirable just so that the list achieves critical mass of membership and volume, and does not die from inactivity. It is quite safe to say that the ballroom list is in no immediate danger of suffering this fate. On the contrary, there has been an exodus of people who complain about the volume of traffic, and the entire list suffers from the loss of their participation. 6. PROLIFIC POSTERS: Don't feel that you need to respond to _every_ message on which you have an opinion. A lot of good information comes from some of the most frequent contributors, and it is not atypical that the majority of people on the list are "lurkers," and are quite happy to remain so. But sometimes one sees an abundance of messages from the same person that fall into the "trivial" category (see #4) and it is then especially annoying. One solution, if you really must add your two bits' worth to _everything_, is to assemble these responses into a file, and post it once a week. Even if you feel that you are making worthwhile and well-considered statements with every posting, try not to dominate the list with your own postings. 7. FLAMES (DON'T): Don't send flames* to the list. [*Attacks, usually personal, typically going back and forth several times between the same two people, ad nauseum.] Just send it to the person you want to insult.:-) OK, so that removes most of the "satisfaction" one gets from flaming someone in public. Disagreements and controversy are fine and even healthy. But when these degenerate into personal attacks and nitpicking, then after the first round of disagreements has been aired, nothing new of value to the list membership is usually provided, and it is only egos that are being aired, and list members' patience that are being tried. Some people like to flame-bait. Don't fall for it! 8. CONSIDERATION: Be aware of and considerate towards the _readers_. Consider that when one posts an article, one is ostensibly doing it either (i) for the benefit of the _other_ members of the list, or (ii) to gain benefit from the other members of the list. In either case, it seems that one should be considerate towards all these other people. There are many little things you can do--here is just one example: + Don't quote the entire article when mailing a follow-up note. It is rarely needed since most people have seen the original. If you must, do take the minute or two extra time to edit out all but the most pertinent part of the original article. If your own contribution is smaller than what you're quoting, you're probably quoting too much [also see Item 4: Avoid Trivia]. If your mailer does not make it easy to do this, don't subject everyone else to its limitations. Learn how to save the file, edit it separately and read it back into your reply. Some people still have 2400 baud connections to their on-line services and this can make a _big_ difference! From list-managers-owner Wed Mar 8 16:36:00 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id QAA09235 for list-managers-outgoing; Wed, 8 Mar 1995 16:23:35 -0800 Received: from wilma.cs.utk.edu (WILMA.CS.UTK.EDU [128.169.94.141]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id VAA26896 for ; Tue, 7 Mar 1995 21:09:27 -0800 Received: from LOCALHOST by wilma.cs.utk.edu with SMTP (cf v2.11c-UTK) id AAA01304; Wed, 8 Mar 1995 00:03:49 -0500 Message-Id: <199503080503.AAA01304@wilma.cs.utk.edu> X-URI: http://www.cs.utk.edu/~moore/ To: list-managers@greatcircle.com cc: moore@cs.utk.edu From: Keith Moore Subject: suspicious looking subscribe message points to 800 fax gateways Date: Wed, 08 Mar 1995 00:03:41 -0500 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I recieved the following subscribe message addressed to info-mime-request@cs.utk.edu. This looks suspiciously like an attempt to flood that 800 number with junk faxes (probably from lots of lists) and bill lots of calls to it. I telephoned that number and it turns out to be a doctor's office in Queens, NY. It's not even attached to a fax machine, and sure enough, they are getting lots of calls with a high-pitched beep. So you might want to check your lists and see if this same address is subscribed... Also, since the subscription itself came from a listproc, maybe the attacker was using that to cover his/her tracks? Keith Moore ------- Forwarded Message Delivery-Date: Tue, 07 Mar 1995 22:56:54 -0500 X-Folder: postmaster Return-Path: Received: from tequesta.gate.net by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id WAA11357; Tue, 7 Mar 1995 22:56:49 -0500 From: Received: from epinet.com (listproc@router.epinet.com [199.227.49.1]) by tequesta.gate.net (8.6.9/8.6.9) with SMTP id WAA31834 for info-mime-REQUEST@cs.utk.edu; Tue, 7 Mar 1995 22:56:52 -0500 Date: Tue, 7 Mar 1995 22:56:52 -0500 Message-Id: <199503080356.WAA31834@tequesta.gate.net> Apparently-To: info-mime-REQUEST@cs.utk.edu subscribe ------- End of Forwarded Message From list-managers-owner Thu Mar 9 18:50:43 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id SAA05103 for list-managers-outgoing; Thu, 9 Mar 1995 18:45:58 -0800 Received: from unicorn.swi.com.sg (unicorn.swi.com.sg [202.0.71.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id RAA10922 for ; Wed, 8 Mar 1995 17:27:11 -0800 Received: (from mathias@localhost) by unicorn.swi.com.sg (8.6.10/8.6.6) id JAA06097; Thu, 9 Mar 1995 09:19:56 +0800 Message-Id: <199503090119.JAA06097@unicorn.swi.com.sg> Subject: Re: suspicious looking subscribe message points to 800 fax gateways To: moore@cs.utk.edu (Keith Moore) Date: Thu, 9 Mar 1995 09:19:56 +0800 (SST) Cc: list-managers@GreatCircle.COM, moore@cs.utk.edu In-Reply-To: <199503080503.AAA01304@wilma.cs.utk.edu> from "Keith Moore" at Mar 8, 95 00:03:41 am From: Mathias.Koerber@swi.com.sg (Mathias Koerber) Reply-To: Mathias.Koerber@swi.com.sg Organization: SW International Systems Pte Ltd Disclaimer: My company pays me to work, not speak for them. So there ! X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2060 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk According to Keith Moore | I recieved the following subscribe message addressed to | info-mime-request@cs.utk.edu. This looks suspiciously like an attempt | to flood that 800 number with junk faxes (probably from lots of lists) | and bill lots of calls to it. | | I telephoned that number and it turns out to be a doctor's office in | Queens, NY. It's not even attached to a fax machine, and sure enough, | they are getting lots of calls with a high-pitched beep. | | So you might want to check your lists and see if this same address is | subscribed... Also, since the subscription itself came from a listproc, | maybe the attacker was using that to cover his/her tracks? Mayve the guys at tpc.int could be asked to weed out fax requests from mailing lists to prvent this kind of misuse. And then snd a msg to the list maintainer... chers | | Keith Moore | | ------- Forwarded Message | | Delivery-Date: Tue, 07 Mar 1995 22:56:54 -0500 | X-Folder: postmaster | Return-Path: | Received: from tequesta.gate.net by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) | id WAA11357; Tue, 7 Mar 1995 22:56:49 -0500 | From: | Received: from epinet.com (listproc@router.epinet.com [199.227.49.1]) by tequesta.gate.net (8.6.9/8.6.9) with SMTP id WAA31834 for info-mime-REQUEST@cs.utk.edu; Tue, 7 Mar 1995 22:56:52 -0500 | Date: Tue, 7 Mar 1995 22:56:52 -0500 | Message-Id: <199503080356.WAA31834@tequesta.gate.net> | Apparently-To: info-mime-REQUEST@cs.utk.edu | | subscribe | | ------- End of Forwarded Message | | -- Mathias Koerber Tel: +65 / 7780066 x 29 SW International Systems Pte Ltd Fax: +65 / 7779401 14 Science Park Drive #04-01 email: Mathias.Koerber@swi.com.sg The Maxwell, Singapore Science Park S'pore 0511 MK * Eifersucht ist eine Leidenschaft, die mit Eifer sucht, was Leiden schafft * From list-managers-owner Thu Mar 9 19:21:54 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA06086 for list-managers-outgoing; Thu, 9 Mar 1995 19:11:14 -0800 Received: from ns.ge.com (ns.ge.com [192.35.39.24]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id TAA06055 for ; Thu, 9 Mar 1995 19:11:06 -0800 Received: from [158.254.10.56] (xcrsnyder.ge_xc.dialup.net [158.254.10.56]) by ns.ge.com (8.6.10/8.6.10) with SMTP id WAA18991 for ; Thu, 9 Mar 1995 22:08:37 -0500 X-Sender: snyderra@dunx1.ocs.drexel.edu Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 9 Mar 1995 22:08:42 -0500 To: list-managers@GreatCircle.COM From: snyderra@post.drexel.edu (Bob Snyder) Subject: Re: suspicious looking subscribe message points to 800 fax gateways Sender: list-managers-owner@GreatCircle.COM Precedence: bulk At 9:19 AM 3/9/95, Mathias Koerber wrote: >Mayve the guys at tpc.int could be asked to weed out fax requests from >mailing lists to prvent this kind of misuse. And then snd a msg to >the list maintainer... Except that: a) tpc.int is a group of people who have volunteered their systems to deliver faxes/pages to local phone numbers, and certainly not under any central control. b) There are legitimate reasons to want to have faxes delivered from a list. I have users where I work that require this. Intelligent fax senders should keep track of unsuccessful calls, and stop sending to a number where you get pickups without a fax machine. I doubt this will be a regular occurance (especially given that many areas aren't covered by tpc.int). If it concerns you, prevent tpc.int address from subscribing without prior approval. Bob -- Bob Snyder N2KGO MIME, PGP, RIPEM mail accepted snyderra@post.drexel.edu PGP & RIPEM keys on key servers When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl. From list-managers-owner Thu Mar 9 20:20:26 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id UAA09399 for list-managers-outgoing; Thu, 9 Mar 1995 20:14:38 -0800 Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id UAA09394 for ; Thu, 9 Mar 1995 20:14:34 -0800 Received: from surt.ifi.uio.no (1232@surt.ifi.uio.no [129.240.76.2]) by ifi.uio.no with ESMTP (8.6.10/ifi2.4) id for ; Fri, 10 Mar 1995 05:12:11 +0100 From: Kjetil Torgrim Homme Received: (from kjetilho@localhost) by surt.ifi.uio.no ; Fri, 10 Mar 1995 05:12:11 +0100 Date: Fri, 10 Mar 1995 05:12:11 +0100 Message-Id: <199503100412.28570.surt.ifi.uio.no@ifi.uio.no> To: list-managers@GreatCircle.COM In-reply-to: (snyderra@post.drexel.edu) Subject: Re: suspicious looking subscribe message points to 800 fax gateways Sender: list-managers-owner@GreatCircle.COM Precedence: bulk [Bob Snyder] | a) tpc.int is a group of people who have volunteered their systems | to deliver faxes/pages to local phone numbers, and certainly not | under any central control. So why don't they block numbers which cost money? Aren't they easily recognizable? Not that this has anything to do with list management :-) Kjetil T. From list-managers-owner Thu Mar 9 21:50:29 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id VAA13613 for list-managers-outgoing; Thu, 9 Mar 1995 21:22:18 -0800 Received: from LAGAVULIN.PDL.CS.CMU.EDU (LAGAVULIN.PDL.CS.CMU.EDU [128.2.198.241]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id VAA13600 for ; Thu, 9 Mar 1995 21:22:13 -0800 Message-Id: <199503100522.VAA13600@miles.greatcircle.com> Received: from LOCALHOST by LAGAVULIN.PDL.CS.CMU.EDU id aa23223; 10 Mar 95 0:19 EST To: Kjetil Torgrim Homme cc: list-managers@greatcircle.com X-Copyright: Copyright 1995, Christopher G. Demetriou. All rights reserved. X-Notice: Duplication and redistribution prohibited without consent of the author. Subject: Re: suspicious looking subscribe message points to 800 fax gateways In-reply-to: Your message of "Fri, 10 Mar 1995 05:12:11 +0100." <199503100412.28570.surt.ifi.uio.no@ifi.uio.no> Date: Fri, 10 Mar 1995 00:19:47 -0500 From: Chris G Demetriou Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > So why don't they block numbers which cost money? Aren't they easily > recognizable? _every_ phone call costs _someone_ something, and every fax costs the receiver something. (obviously, the folks behind tpc.int aren't calling numbers that are toll calls for them...) the point is, how do you determine which requests are "legitimate"? there are many legit. uses for faxing an 800 number, or for subscribing one's fax machine to a mailing list. Mailing list managers have a responsibility to make sure that their mailing lists aren't abused in this manner. It isn't even very hard to do... chris From list-managers-owner Thu Mar 9 21:54:44 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id VAA13656 for list-managers-outgoing; Thu, 9 Mar 1995 21:22:51 -0800 Received: from wilma.cs.utk.edu (WILMA.CS.UTK.EDU [128.169.94.141]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id VAA13649 for ; Thu, 9 Mar 1995 21:22:47 -0800 Received: from LOCALHOST by wilma.cs.utk.edu with SMTP (cf v2.11c-UTK) id AAA04926; Fri, 10 Mar 1995 00:17:04 -0500 Message-Id: <199503100517.AAA04926@wilma.cs.utk.edu> X-URI: http://www.cs.utk.edu/~moore/ From: Keith Moore To: Kjetil Torgrim Homme cc: list-managers@greatcircle.com, moore@cs.utk.edu Subject: Re: suspicious looking subscribe message points to 800 fax gateways In-reply-to: Your message of "Fri, 10 Mar 1995 05:12:11 +0100." <199503100412.28570.surt.ifi.uio.no@ifi.uio.no> Date: Fri, 10 Mar 1995 00:16:57 -0500 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >| a) tpc.int is a group of people who have volunteered their systems >| to deliver faxes/pages to local phone numbers, and certainly not >| under any central control. > > So why don't they block numbers which cost money? Aren't they easily > recognizable? Calls to numbers with the U.S. 800 area code are billed to the called party. That's why the subscribe request looked suspicious. Lots of places have 800 numbers for their fax machines so that their customers can send them faxes for free. But it doesn't make much sense to have the info-mime mailing list faxed to your 800 number (where you have to pay for the call) when you could probably get them for free using a different number. (It makes even less sense if there's no fax machine at that number...) At any rate, the people who manage the TPC.INT domain have since blocked faxes from the Internet to that particular 800 number. I only mentioned it on list-managers because I had reason to believe that the same number was being subscribed to other lists also, and I wanted to stop or limit the abuse as quickly as possible. Keith From list-managers-owner Fri Mar 10 19:22:30 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id SAA01285 for list-managers-outgoing; Fri, 10 Mar 1995 18:53:49 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id SAA01280 for ; Fri, 10 Mar 1995 18:53:47 -0800 Received: (frugal@localhost) by shell1.best.com (8.6.10/8.6.5) id SAA20784; Fri, 10 Mar 1995 18:51:14 -0800 Date: Fri, 10 Mar 1995 18:51:14 -0800 (PST) From: Linda Henneman To: list-managers@GreatCircle.COM Subject: List Moderation and Profanity In-Reply-To: <199503101618.KAA03184@crasher1.ttgcitn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Pardon me if this road has been trod down many times before but, as someone who is planning to launch a fully-moderated list very soon, I was wondering how people decide what to let through when confronted w/something that contains vulgar language? Of course, defining what is vulgar or not varies from person to person, but does anyone have any guidelines or can share w/me what they do/have done? I know from other moderated lists I'm on that certain messages don't get posted to the list because they're off the topic or repetitious or for rather benign reasons like that. So, I don't really think it's a first amendment issue. They can say what they like elsewhere maybe, but just not on my list. Sort of like the newspaper won't print certain things even if you do have a paid subscription to it. I've also seen that when someone is vulgar they draw many flames on (and probably off) the list so it's not something other people welcome. I'd like to spare my subscribers the exposure but am not really into being "big brother" and heavy w/the censoring, either. TIA for any info. Linda From list-managers-owner Sat Mar 11 04:20:21 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id DAA15068 for list-managers-outgoing; Sat, 11 Mar 1995 03:53:37 -0800 Received: from europe.std.com (europe.std.com [192.74.137.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id DAA15063 for ; Sat, 11 Mar 1995 03:53:34 -0800 Received: from world.std.com by europe.std.com (8.6.8.1/Spike-8-1.0) id GAA12378; Sat, 11 Mar 1995 06:51:14 -0500 Received: by world.std.com (5.65c/Spike-2.0) id AA17842; Sat, 11 Mar 1995 06:51:19 -0500 Date: Sat, 11 Mar 1995 06:51:19 +0001 (EST) From: Sharon Shea Subject: Re: List Moderation and Profanity To: Linda Henneman Cc: list-managers@GreatCircle.COM In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > Pardon me if this road has been trod down many times before but, as > someone who is planning to launch a fully-moderated list very soon, I was > wondering how people decide what to let through when confronted > w/something that contains vulgar language? Of course, defining what is > vulgar or not varies from person to person, but does anyone have any > guidelines or can share w/me what they do/have done? > I found that vulgar language did a lot of damage to my 'unmoderated' list. I asked politely, then deleted the offender. I let any comment on any issue go by - except personal attacks and vulgar language. I explained that it was like inviting people to a party at my house - I sure hoped they had a good time, but being genuinely offensive was out of order. I stuck with this and I'm glad I did. I got some 'fascist pig' and 'freedom of speech' comments, but I didn't buy it. -Sharon From list-managers-owner Sat Mar 11 10:20:24 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id JAA19453 for list-managers-outgoing; Sat, 11 Mar 1995 09:57:20 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id JAA19448 for ; Sat, 11 Mar 1995 09:57:17 -0800 Received: from [204.156.141.133] (agoodloe.vip.best.com [204.156.141.133]) by shell1.best.com (8.6.10/8.6.5) with SMTP id JAA03584 for ; Sat, 11 Mar 1995 09:54:39 -0800 Date: Sat, 11 Mar 1995 09:54:39 -0800 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: list-managers@greatcircle.com From: agoodloe@best.com (Amy Goodloe) Subject: Re: List Moderation and Profanity Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >> Pardon me if this road has been trod down many times before but, as >> someone who is planning to launch a fully-moderated list very soon, I was >> wondering how people decide what to let through when confronted >> w/something that contains vulgar language? Of course, defining what is >> vulgar or not varies from person to person, but does anyone have any >> guidelines or can share w/me what they do/have done? >> >I found that vulgar language did a lot of damage to my 'unmoderated' list. >I asked politely, then deleted the offender. I let any comment on any >issue go by - except personal attacks and vulgar language. I explained that >it was like inviting people to a party at my house - I sure hoped they >had a good time, but being genuinely offensive was out of order. I have a similar concern. There is someone who is subscribed to one of my lists who is clearl NOT welcome on the list; the list policies state as much and he has been told privately twice. The problem is that I can't seem to unsubscribe him, as his address does not appear to be listed in the majordomo listmember file. I've tried searching for as many variations as possible, but I can't seem to figure out HOW he's getting list mail -- b/c it must be under a name that IS on the list; otherwise he wouldn't be "allowed" by majordomo to post to it. I've gotten notes from a few subscribers telling me about what this guy has done on other lists, and I'm quite sure he knows he isn't welcome on this list and has deliberately made it tough to track down his subscribed address. Any ideas on how I CAN track it down, or on what to do? The list is currently not moderated, but I suppose if all else fails I *could* just make it moderated... Thanks, --Amy agoodloe@best.com From list-managers-owner Sat Mar 11 11:20:27 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA21016 for list-managers-outgoing; Sat, 11 Mar 1995 11:12:21 -0800 Received: from netcomsv.netcom.com (uumail3.netcom.com [163.179.3.53]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA21011 for ; Sat, 11 Mar 1995 11:12:19 -0800 Received: from znyx.com by netcomsv.netcom.com with SMTP (8.6.9/SMI-4.1) id LAA10678; Sat, 11 Mar 1995 11:09:15 -0800 Received: from alan.znyx.com by znyx.com (5.65/1.35) id AA03079; Sat, 11 Mar 95 11:14:43 -0800 Date: Sat, 11 Mar 95 11:14:43 -0800 Message-Id: <9503111914.AA03079@znyx.com> X-Sender: alan@znyx.com 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: alan@znyx.com (Alan Deikman) Subject: Re: List Moderation and Profanity Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Sharon Wrote: >Linda Wrote: >> I was >> wondering how people decide what to let through when confronted >> w/something that contains vulgar language? Of course, defining what is >> vulgar or not varies from person to person, but does anyone have any >> guidelines or can share w/me what they do/have done? I really don't think you need guidelines. If you have to get down to that level you have already lost the war. A subscriber who is so out of touch, lacking of perspective, or just plain too stoopid to understand basic good manners over e-mail doesn't need to be on your list. "I don't know what obscenity is, but I sure know it when I see it." If that's good enough for the Supreme Court justice who said it (I think it was Reinquist?) I should be good enough for an Internet mailing list manager. >I found that vulgar language did a lot of damage to my 'unmoderated' list. >I asked politely, then deleted the offender. I let any comment on any >issue go by - except personal attacks and vulgar language. I explained that >it was like inviting people to a party at my house - I sure hoped they >had a good time, but being genuinely offensive was out of order. Good call, sharon, that's exactly the way I think of my list. Let them go to USENET if they think peeing in the house plants is funny. Point out to them (if you care to) that at least 50% of the reason that you have a private mailing list instead of a USENET news group is to avoid such antics. >I stuck with this and I'm glad I did. I got some 'fascist pig' and >'freedom of speech' comments, but I didn't buy it. You toltarian despot, you. Just out of curiosity (and if you happen to know) did the name caller(s) ever generate a posting that you thought was a worthwhile contribution? Or did anything that caused you to respect them? Another question for both Sharon and Linda: what are the mailing lists you run? My list (the pci-sig) so far has posted over 400 messages without anything remotely objectionable. Is there some category of list that is more prone to this kind of problem than another? Reagrds, -------------------------------- Alan Deikman, ZNYX Corporation alan@znyx.com From list-managers-owner Sat Mar 11 12:20:35 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA21751 for list-managers-outgoing; Sat, 11 Mar 1995 12:18:34 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id MAA21746 for ; Sat, 11 Mar 1995 12:18:32 -0800 Received: from [204.156.141.133] (agoodloe.vip.best.com [204.156.141.133]) by shell1.best.com (8.6.10/8.6.5) with SMTP id MAA09212; Sat, 11 Mar 1995 12:15:44 -0801 Date: Sat, 11 Mar 1995 12:15:44 -0801 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: alan@znyx.com (Alan Deikman), list-managers@GreatCircle.COM From: agoodloe@best.com (Amy Goodloe) Subject: Re: List Moderation and Profanity Sender: list-managers-owner@GreatCircle.COM Precedence: bulk At 11:14 AM 3/11/95, Alan Deikman wrote: >Another question for both Sharon and Linda: what are the mailing lists >you run? My list (the pci-sig) so far has posted over 400 messages without >anything remotely objectionable. Is there some category of list that is >more prone to this kind of problem than another? I can answer that one: any list with the words woman, women, gay, lesbian, queer, dyke or feminist in the titles are OPEN SEASON for idiots -- and all seven of my lists have at least ONE of those words in their titles... --Amy From list-managers-owner Sat Mar 11 13:20:28 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA22092 for list-managers-outgoing; Sat, 11 Mar 1995 13:06:50 -0800 Received: from netcomsv.netcom.com (uumail2.netcom.com [163.179.3.52]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id NAA22087 for ; Sat, 11 Mar 1995 13:06:47 -0800 Received: from znyx.com by netcomsv.netcom.com with SMTP (8.6.9/SMI-4.1) id NAA28222; Sat, 11 Mar 1995 13:03:42 -0800 Received: from alan.znyx.com by znyx.com (5.65/1.35) id AA03292; Sat, 11 Mar 95 13:09:12 -0800 Date: Sat, 11 Mar 95 13:09:12 -0800 Message-Id: <9503112109.AA03292@znyx.com> X-Sender: alan@znyx.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: list-managers@GreatCircle.COM, agoodloe@best.com (Amy Goodloe) From: alan@znyx.com (Alan Deikman) Subject: Re: List Moderation and Profanity Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Amy Goodloe: >I can answer that one: any list with the words woman, women, gay, lesbian, >queer, dyke or feminist in the titles are OPEN SEASON for idiots -- and all >seven of my lists have at least ONE of those words in their titles... Aw, gee wizz. I guess, contrary to my expectation, that the PCI bus doesn't after all stimulate the most primal urges instincts of human kind. I can see where your lists would have problems in this area. You are dealing with sexual topics, and all the maggots will crawl out from their respective rocks to have their say, to be noticed for once in their lives, particularly by the opposite sex. I'll bet even odds that 99.9% of your offenders are males, who have problems with women, right? And most of the other .1% are still males using a female e-mail moniker. You might say that the maggots are simply part of the soil you have chosen to work, Amy. But that's what makes it interesting, no? I'll stick to circuits and wave-forms, thank you. Regards, -------------------------------- Alan Deikman, ZNYX Corporation alan@znyx.com From list-managers-owner Sat Mar 11 13:50:26 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA22305 for list-managers-outgoing; Sat, 11 Mar 1995 13:28:54 -0800 Received: from relay2.UU.NET (relay2.UU.NET [192.48.96.7]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id NAA22300 for ; Sat, 11 Mar 1995 13:28:51 -0800 Received: from world.std.com by relay2.UU.NET with SMTP id QQygqn15166; Sat, 11 Mar 1995 16:24:00 -0500 Received: by world.std.com (5.65c/Spike-2.0) id AA02481; Sat, 11 Mar 1995 16:22:51 -0500 Date: Sat, 11 Mar 1995 16:22:50 +0001 (EST) From: Sharon Shea Subject: Re: List Moderation and Profanity To: Amy Goodloe Cc: Alan Deikman , list-managers@GreatCircle.COM In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > > I can answer that one: any list with the words woman, women, gay, lesbian, > queer, dyke or feminist in the titles are OPEN SEASON for idiots -- and all > seven of my lists have at least ONE of those words in their titles... > Yup...my list is 'women'...;-) From list-managers-owner Sat Mar 11 14:50:24 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA23500 for list-managers-outgoing; Sat, 11 Mar 1995 14:23:24 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id OAA23495 for ; Sat, 11 Mar 1995 14:23:22 -0800 Received: from [204.156.141.133] (agoodloe.vip.best.com [204.156.141.133]) by shell1.best.com (8.6.10/8.6.5) with SMTP id OAA15104 for ; Sat, 11 Mar 1995 14:20:47 -0801 Date: Sat, 11 Mar 1995 14:20:47 -0801 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: list-managers@greatcircle.com From: agoodloe@best.com (Amy Goodloe) Subject: Re: List Moderation and Profanity Sender: list-managers-owner@GreatCircle.COM Precedence: bulk bill@biome.bio.dfo.ca (Bill Silvert) writes: >Have you checked the headers on the mail carefully? The address of the >poster normally appears there, although it may not show up when you >display the message through some mailers. Yes. I use Eudora, and can choose to see full headers -- which gives me no more info other than what I already know: his email address. >Are you sure that non-members cannot post? MJ can be configured this >way, but it is not the default. Ok, say my list is called fun-list@here.com. In the config file, under restricted post, I should just type: fun-list right? to make majordomo check the poster's address against who's in the fun-list subscriber list?? That's what I've done, but please let me know if that isn't right!! --Amy From list-managers-owner Sat Mar 11 14:53:34 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA23953 for list-managers-outgoing; Sat, 11 Mar 1995 14:40:53 -0800 Received: from europe.std.com (europe.std.com [192.74.137.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id OAA23948 for ; Sat, 11 Mar 1995 14:40:50 -0800 Received: from world.std.com by europe.std.com (8.6.8.1/Spike-8-1.0) id RAA10862; Sat, 11 Mar 1995 17:38:35 -0500 Received: by world.std.com (5.65c/Spike-2.0) id AA08100; Sat, 11 Mar 1995 17:38:35 -0500 Date: Sat, 11 Mar 1995 17:38:35 +0001 (EST) From: Sharon Shea Subject: Re: List Moderation and Profanity To: Alan Deikman Cc: list-managers@GreatCircle.COM, Amy Goodloe In-Reply-To: <9503112109.AA03292@znyx.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > > I can see where your lists would have problems in this area. You are > dealing with sexual topics, and all the maggots will crawl out from their > respective rocks to have their say, to be noticed for once in their lives, particularly by the opposite sex. I'll bet even odds that 99.9% of > your offenders are males, who have problems with women, right? And most > of the other .1% are still males using a female e-mail moniker. Yup, some are men. And there is a problem with men using women's email. But I've found some women to be particularly hostile and vulgar - toward women! - as well. And women who masquerade as men get themselves into hot water also. Administrate an email list - and you'll meet them all. BTW, I have seen some amazingly harsh exchanges on very 'professional' lists. You're on target that there's lot of 'sexual attention' nonsense out there, but I've run into more than a few who have a real problem with anyone they feel is an 'authority figure.' I had one fellow(?) rip me up all over the internet as being 'single-handedly responsible for the demise of feminism and free speach'. Ah, yeah, sure. He just 'arrived' on the list - I don't think he'd ever seen a message from me since I rarely get into the discussions. Just decided to hang me up for being in charge, I suspect. Tracking this fellow determined that he 'arrived' by email to pounce on people routinely. (Turns out those who knew him personaly said he was a very quite, very low-life sort offline. Got his kicks by online attacks.) -Sharon From list-managers-owner Sat Mar 11 19:20:24 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA28849 for list-managers-outgoing; Sat, 11 Mar 1995 19:12:04 -0800 Received: from gagme.wwa.com (gagme.wwa.com [198.49.174.33]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id TAA28843 for ; Sat, 11 Mar 1995 19:11:58 -0800 Received: by gagme.wwa.com (Smail3.1.28.1 #8) id m0rne6k-000FCZC; Sat, 11 Mar 95 21:14 CST Message-Id: From: dattier@wwa.com (David W. Tamkin) Subject: Re: List Moderation and Profanity To: sshea@world.std.com (Sharon Shea) Date: Sat, 11 Mar 1995 21:14:17 -0600 (CST) Cc: alan@znyx.com, list-managers@GreatCircle.COM, agoodloe@best.com In-Reply-To: from "Sharon Shea" at Mar 11, 95 05:38:35 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 750 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Sharon Shea wrote, | I had one fellow(?) rip me up all over the internet as being | 'single-handedly responsible for the demise of feminism and free speach'. | Ah, yeah, sure. He just 'arrived' on the list - I don't think he'd ever | seen a message from me since I rarely get into the discussions. Just | decided to hang me up for being in charge, I suspect. The lists I've run have never had problems with profanity, but on two of the three I've been attacked just because a jerk decided that all list managers perforce have the same stuck-up power made that the jerk would have if he or she (yes, "or she") ran a list. The higher visibility makes the list adminis- trator the easiest target around for flamage over things that never happened. From list-managers-owner Sat Mar 11 19:24:56 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA28672 for list-managers-outgoing; Sat, 11 Mar 1995 19:06:02 -0800 Received: from netcomsv.netcom.com (uumail2.netcom.com [163.179.3.52]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id TAA28666 for ; Sat, 11 Mar 1995 19:05:58 -0800 Received: from znyx.com by netcomsv.netcom.com with SMTP (8.6.9/SMI-4.1) id TAA18347; Sat, 11 Mar 1995 19:01:38 -0800 Received: from alan.znyx.com by znyx.com (5.65/1.35) id AA03964; Sat, 11 Mar 95 19:07:12 -0800 Date: Sat, 11 Mar 95 19:07:12 -0800 Message-Id: <9503120307.AA03964@znyx.com> X-Sender: alan@znyx.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Sharon Shea From: alan@znyx.com (Alan Deikman) Subject: Re: List Moderation and Profanity Cc: list-managers@GreatCircle.COM, Amy Goodloe Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Sharon, >Yup, some are men. And there is a problem with men using women's email. >But I've found some women to be particularly hostile and vulgar - toward >women! - as well. And women who masquerade as men get themselves into hot >water also. Administrate an email list - and you'll meet them all. I guess I would have lost my bet. Most of the complaints I see about hostility seem to be about "the boys." From what you are telling me it seems that the insulating attributes of Internet e-mail (real or perceived) would allow women to be more agressive than they would normally be inclined to in a physical situation. You can see similar types of behavior in automobile traffic. Something happens to people when they get behind the wheel. The same person who would politely usher you into the elevator in front of them will go fully ballistic if they think you've encroached on "their" lane. Even if there were no safety issue involved. >I had one fellow(?) rip me up all over the internet as being >'single-handedly responsible for the demise of feminism and free speach'. Wow. Gives you a real sense of power, doesn't it? >Tracking this fellow determined that he 'arrived' by email to pounce on >people routinely. (Turns out those who knew him personaly said he was a >very quite, very low-life sort offline. Got his kicks by online attacks.) Hmm. Fortunately, most such types don't have enough physical courage to show up on your doorstep, or stalk you. I have never heard of this happening, but there was a recent case of a USENET poster posting a violent rape/pornographic story with a real person named by name as the victim. I know if I were her, I would be really upset, and worried that if this guy was thinking such things would he or another guy be inspired to implement them? This is scary. I wonder if anyone besides myself would see a value in keeping and accessing a private list of such individuals. I would be willing to maintain and disperse this data-base for known list managers. I would take contributions that would help track these guys and help keep them from becoming a problem. The point would not be to "blacklist" anyone but to keep an impartial record for use by list managers, particularly if they might have to get the authorities involved. Amy, Sharon, Linda, would you participate? Regards, -------------------------------- Alan Deikman, ZNYX Corporation alan@znyx.com From list-managers-owner Sat Mar 11 20:50:30 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id UAA00375 for list-managers-outgoing; Sat, 11 Mar 1995 20:32:57 -0800 Received: from UUCP-GW.CC.UH.EDU (UUCP-GW.CC.UH.EDU [129.7.1.11]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id UAA00370 for ; Sat, 11 Mar 1995 20:32:53 -0800 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA28993 (5.67a/IDA-1.5 for greatcircle.com!list-managers); Sat, 11 Mar 1995 22:08:36 -0600 Received: by bonkers.taronga.com (smail2.5p) id AA01233; 11 Mar 95 22:07:10 CST (Sat) Received: (from arielle@localhost) by bonkers.taronga.com (8.6.8/8.6.6) id WAA01230 for list-managers@greatcircle.com; Sat, 11 Mar 1995 22:07:10 -0600 From: Stephanie da Silva Message-Id: <199503120407.WAA01230@bonkers.taronga.com> Subject: Re: List Moderation and Profanity To: list-managers@greatcircle.com Date: Sat, 11 Mar 1995 22:07:10 -0600 (CST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 529 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > The point would not be to "blacklist" anyone > but to keep an impartial record for use by list managers, particularly > if they might have to get the authorities involved. Amy, Sharon, Linda, > would you participate? I don't really think this is necessary. On the subject of profanity, it doesn't bother me if it's not abusive. Though it hasn't really been a problem on my list. I can't say that, as nothing's been much of a problem on my list because it's moderated. Guess that's why I go to the trouble of moderating. From list-managers-owner Sat Mar 11 20:52:29 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id UAA00318 for list-managers-outgoing; Sat, 11 Mar 1995 20:26:52 -0800 Received: from usis.com (usis.com [199.171.178.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id UAA00313 for ; Sat, 11 Mar 1995 20:26:47 -0800 Received: from siberia.usis.com (siberia.usis.com [199.171.178.71]) by usis.com (8.6.5/8.6.5) with SMTP id WAA06658 for ; Sat, 11 Mar 1995 22:20:37 -0600 Message-Id: <199503120420.WAA06658@usis.com> From: "Kimberly Long" Organization: usis To: list-managers@GreatCircle.COM Date: Sat, 11 Mar 1995 22:21:11 +0000 Subject: Re: List Moderation and Profanity Reply-to: siberia@usis.com Priority: normal X-mailer: Pegasus Mail/Windows (v1.22) Sender: list-managers-owner@GreatCircle.COM Precedence: bulk alan@znyx.com (Alan Deikman) wrote in part: > I wonder if anyone besides myself would see a value in keeping and > accessing a private list of such individuals. I would be willing to > maintain and disperse this data-base for known list managers. I would > take contributions that would help track these guys and help keep them > from becoming a problem. The point would not be to "blacklist" anyone > but to keep an impartial record for use by list managers, particularly > if they might have to get the authorities involved. Amy, Sharon, Linda, > would you participate? I don't know. This makes me uncomfortable. First of all, anyone that is actively involved in the internet will eventually figure out the "hard-core" trouble makers. The net may be appear to be a big place, but in my experience, it really isn't. Keeping an "impartial record" seems too power-trippy to me as well as ineffective. There is nothing to keep a crazed person from closing one net account down and within 5 minutes getting another. It seems to me that we should be dealing with the mechanics of the problem, i.e., how to keep a closed list closed. I cannot understand why anyone would not want to keep their list open to non-subscriber postings. Is there something I am missing? Namaste' Kimberly Long siberia@usis.com If a man does not keep pace with his companions, perhaps it is because he hears a different drummer. Let him step to the music he hears, however measured or far away. )O( ~~Thoreau From list-managers-owner Sun Mar 12 00:20:21 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id XAA02833 for list-managers-outgoing; Sat, 11 Mar 1995 23:52:40 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id XAA02827 for ; Sat, 11 Mar 1995 23:52:38 -0800 Received: from [204.156.141.133] (agoodloe.vip.best.com [204.156.141.133]) by shell1.best.com (8.6.10/8.6.5) with SMTP id XAA12484; Sat, 11 Mar 1995 23:50:01 -0800 Date: Sat, 11 Mar 1995 23:50:01 -0800 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: siberia@usis.com, list-managers@GreatCircle.COM From: agoodloe@best.com (Amy Goodloe) Subject: Re: List Moderation and Profanity Sender: list-managers-owner@GreatCircle.COM Precedence: bulk At 10:21 PM 3/11/95, Kimberly Long wrote: >I cannot understand why anyone would not want to keep their list open >to non-subscriber postings. Is there something I am missing? I can't understand why anyone WOULD want their lists open to non-subscriber postings (is that what you meant?) I can't believe its the default in the current version of majordomo to have lists open to random posts -- that seems rather, well, dumb. But I also can't understand why it isn't harder for outsiders to figure out the outgoing mail alias (I mean listname-outgoing IS fairly obvious...) --amy From list-managers-owner Sun Mar 12 01:50:24 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id BAA04430 for list-managers-outgoing; Sun, 12 Mar 1995 01:42:07 -0800 Received: from LAGAVULIN.PDL.CS.CMU.EDU (LAGAVULIN.PDL.CS.CMU.EDU [128.2.198.241]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id BAA04425 for ; Sun, 12 Mar 1995 01:42:05 -0800 Message-Id: <199503120942.BAA04425@miles.greatcircle.com> Received: from localhost by LAGAVULIN.PDL.CS.CMU.EDU id aa09347; 12 Mar 95 4:39 EST To: Sharon Shea cc: Alan Deikman , list-managers@greatcircle.com, Amy Goodloe X-Copyright: Copyright 1995, Christopher G. Demetriou. All rights reserved. X-Notice: Duplication and redistribution prohibited without consent of the author. Subject: Re: List Moderation and Profanity In-reply-to: Your message of "Sat, 11 Mar 1995 17:38:35 +0001." Date: Sun, 12 Mar 1995 04:39:17 -0500 From: Chris G Demetriou Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > Yup, some are men. And there is a problem with men using women's email. > But I've found some women to be particularly hostile and vulgar - toward > women! - as well. And women who masquerade as men get themselves into hot > water also. Administrate an email list - and you'll meet them all. Thankfully, i don't run lists where the posters' gender and assumed gender don't come up often... 8-) > BTW, I have seen some amazingly harsh exchanges on very 'professional' lists. Yeah. i think this is especially likely if one or more of the people on the list who have reason to send mail to it often are either immature in their reactions to people's posts or brief to the point of insulting the people they're responding to... Since majordomo's written perl, it's really easy (a few lines of perl, at most; see below) to add keyword matches to "resend" so that abusive mail is filtered out and bounced to the list owner. In general, i'm not of the opinion that the words "fuck" and "asshole" are appropriate for technical, computer-oriented lists, and i have no qualms about bouncing messages containing them. 8-) the chunk of perl to do it looks like: if (defined($opt_s) && ! defined($approved) && ( /\bfuck\b/i || /\basshole\b/i )) { &bounce("Keyword match"); } and we (actually, the guy who now runs the majordomo that serves our lists) added it right after the "admin-request recognition heuristics" section in "resend". Obviously, if your list gets a lot of traffic with those two words in it, you'll need to change it so it's a better heuristic for abuse, but that should give you the idea... later, chris From list-managers-owner Sun Mar 12 02:20:53 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id CAA04937 for list-managers-outgoing; Sun, 12 Mar 1995 02:15:17 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id CAA04932 for ; Sun, 12 Mar 1995 02:15:14 -0800 Received: (frugal@localhost) by shell1.best.com (8.6.10/8.6.5) id CAA05340; Sun, 12 Mar 1995 02:12:37 -0800 Date: Sun, 12 Mar 1995 02:12:36 -0800 (PST) From: Linda Henneman To: Alan Deikman cc: list-managers@GreatCircle.COM Subject: Re: List Moderation and Profanity In-Reply-To: <9503111914.AA03079@znyx.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Alan, thanks for the info. I haven't even launched my list yet so haven't gotten any posts, but was just trying to plan how to head off trouble if it reared its ugly head. My list, BTW, is called "FRUGAL-L" and is about frugal living geared toward urban renters. Shouldn't think that would attract a lot of jerks attired in asbestos suits but, who knows. . .? Linda Henneman (frugal@best.com) On Sat, 11 Mar 1995, Alan Deikman wrote: > Another question for both Sharon and Linda: what are the mailing lists > you run? My list (the pci-sig) so far has posted over 400 messages without > anything remotely objectionable. Is there some category of list that is > more prone to this kind of problem than another? > > Reagrds, > > > > -------------------------------- > Alan Deikman, ZNYX Corporation > alan@znyx.com > From list-managers-owner Sun Mar 12 02:22:34 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id CAA04855 for list-managers-outgoing; Sun, 12 Mar 1995 02:08:39 -0800 Received: from LAGAVULIN.PDL.CS.CMU.EDU (LAGAVULIN.PDL.CS.CMU.EDU [128.2.198.241]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id CAA04850 for ; Sun, 12 Mar 1995 02:08:35 -0800 Message-Id: <199503121008.CAA04850@miles.greatcircle.com> Received: from localhost by LAGAVULIN.PDL.CS.CMU.EDU id aa09403; 12 Mar 95 5:05 EST To: Amy Goodloe cc: siberia@usis.com, list-managers@greatcircle.com X-Copyright: Copyright 1995, Christopher G. Demetriou. All rights reserved. X-Notice: Duplication and redistribution prohibited without consent of the author. Subject: Re: List Moderation and Profanity In-reply-to: Your message of "Sat, 11 Mar 1995 23:50:01 PST." Date: Sun, 12 Mar 1995 05:05:39 -0500 From: Chris G Demetriou Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > >I cannot understand why anyone would not want to keep their list open > >to non-subscriber postings. Is there something I am missing? > > I can't understand why anyone WOULD want their lists open to non-subscriber > postings (is that what you meant?) I can't believe its the default in the > current version of majordomo to have lists open to random posts -- that > seems rather, well, dumb. For most lists, it causes no harm (great) to allow people to send to the list without subscribing. the only real problems with it (that i can think of 8-) are: (1) SPAM!, (2) idiots being jerks, and (3) newbies asking stupid questions without being informed of the FAQ, or whatever. Usually (2) can be taken care of with reasonable pointers to FAQs wherever the mailing lists are advertised. On the other hand, there are benefits to having "open-posting" lists: (1) allows people who have a quick question that isn't easily answered by list archives or a FAQ to ask it, and not get completely swamped by (for the) irrelevant mail. (This is especially true for high-volume lists.) (2) allows people who have a "floating" e-mail address to use the list reasonably... (for instance, i send most of my mail from here (lagavulin), but often from other machines, and most of the mailing lists i'm subscribed to are subscribed to my berkeley.edu addresses... 8-) If you restrict postings to people who are subscribed, this becomes harder to deal with properly. all of the lists i run (22, or so, at last count) are "open posting." (Interesting, _not_ all are open subscription, but even the one that isn't is open to all posters...) > But I also can't understand why it isn't harder > for outsiders to figure out the outgoing mail alias (I mean > listname-outgoing IS fairly obvious...) Especially since it may be in the mail headers of your outgoing mail! e.g.: Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id XAA02833 for list-managers-outgoing; Sat, 11 Mar 1995 23:52:40 -0800 in the message that i'm replying to. I think the big stroke of luck is that (with a few exceptions) the people most likely to abuse mailing lists are also those least likely to actually know what the headers are telling them. 8-) In any case: The presence in the headers can be dealt with (at worst by hacking sendmail; i dunno what all the relevant options are). The "-outgoing" name is just a convention; you can set it up to use whatever you'd like (assuming your admin is amenable). To keep outsiders from finding the new outgoing address, you could disable EXPNs. Or, if that's not reasonable and you (or they) are willing to hack the sendmail.cf on your machine, you can get the incoming list archive to get pointed to someplace where the outgoing list name is not obvious. (I don't know how standard this is, but) we point the incoming mail to a special mail delivery rule, with sendmail, and have it figure out the right outgoing name and use that. It's not drop-dead-simple to get the security (in terms of subscription, finding out who's on the list, posting to the list, etc.) that a "sensitive" list requires, but it's definitely not too hard... It's definitely worth noting that if you're running a "sensitive" list, and you're really concerned about its traffic being monitored or its users being discovered, it's probably a bad idea to be running it on a "shared" machine, e.g. a machine owned by a big shell-account provider. Given that you or a trusted individual would be running the machine, there should be no problem arranging for all the sendmail hacks necessary to make the mailing list secure. 8-) chris From list-managers-owner Sun Mar 12 05:50:20 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id FAA07626 for list-managers-outgoing; Sun, 12 Mar 1995 05:49:05 -0800 Received: from usis.com (usis.com [199.171.178.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id FAA07621 for ; Sun, 12 Mar 1995 05:49:02 -0800 Received: from siberia.usis.com (siberia.usis.com [199.171.178.71]) by usis.com (8.6.5/8.6.5) with SMTP id HAA20563; Sun, 12 Mar 1995 07:42:47 -0600 Message-Id: <199503121342.HAA20563@usis.com> From: "Kimberly Long" Organization: usis To: agoodloe@best.com (Amy Goodloe) Date: Sun, 12 Mar 1995 07:43:18 +0000 Subject: Re: List Moderation and Profanity Reply-to: siberia@usis.com CC: list-managers@GreatCircle.COM Priority: normal X-mailer: Pegasus Mail/Windows (v1.22) Sender: list-managers-owner@GreatCircle.COM Precedence: bulk agoodloe@best.com (Amy Goodloe) wrote in part: > At 10:21 PM 3/11/95, Kimberly Long wrote: > > >I cannot understand why anyone would not want to keep their list open > >to non-subscriber postings. Is there something I am missing? > > I can't understand why anyone WOULD want their lists open to non-subscriber > postings (is that what you meant?) Erp! You are correct, that is what I meant. Thanks for recognizing my train of thought which can be rather difficult at times (even for me). ;-) Namaste' Kimberly Long siberia@usis.com If a man does not keep pace with his companions, perhaps it is because he hears a different drummer. Let him step to the music he hears, however measured or far away. )O( ~~Thoreau From list-managers-owner Sun Mar 12 07:20:21 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA08914 for list-managers-outgoing; Sun, 12 Mar 1995 07:07:32 -0800 Received: from europe.std.com (europe.std.com [192.74.137.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id HAA08909 for ; Sun, 12 Mar 1995 07:07:30 -0800 Received: from world.std.com by europe.std.com (8.6.11/Spike-8-1.0) id KAA14942; Sun, 12 Mar 1995 10:01:41 -0500 Received: by world.std.com (5.65c/Spike-2.0) id AA11581; Sun, 12 Mar 1995 10:01:38 -0500 Date: Sun, 12 Mar 1995 10:01:37 +0001 (EST) From: Sharon Shea Subject: Re: List Moderation and Profanity To: "David W. Tamkin" Cc: alan@znyx.com, list-managers@GreatCircle.COM, agoodloe@best.com In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > > three I've been attacked just because a jerk decided that all list managers > perforce have the same stuck-up power made that the jerk would have if he or > she (yes, "or she") ran a list. The higher visibility makes the list adminis- > trator the easiest target around for flamage over things that never happened. > I think there are two issues. List managers will indeed occasionally get blasted just because they are 'available' (on the net) and 'in charge' (of a list). Either men or women cause problems here. These people have been on the list awhile, but develop a sense of entitlement. The other sorts are more often men, who go 'hunting' to cause trouble on lists. I am surely no man-hostile person (refuse to bounce them off my list) but this is what I've experienced. I have found men helpful in dealing with 'problem men' - 'problem women' are another matter. -Sharon From list-managers-owner Sun Mar 12 07:21:54 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id GAA08689 for list-managers-outgoing; Sun, 12 Mar 1995 06:52:30 -0800 Received: from europe.std.com (europe.std.com [192.74.137.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id GAA08684 for ; Sun, 12 Mar 1995 06:52:27 -0800 Received: from world.std.com by europe.std.com (8.6.11/Spike-8-1.0) id JAA14316; Sun, 12 Mar 1995 09:47:11 -0500 Received: by world.std.com (5.65c/Spike-2.0) id AA07122; Sun, 12 Mar 1995 09:47:08 -0500 Date: Sun, 12 Mar 1995 09:47:08 +0001 (EST) From: Sharon Shea Subject: Re: List Moderation and Profanity To: Alan Deikman Cc: list-managers@GreatCircle.COM, Amy Goodloe In-Reply-To: <9503120307.AA03964@znyx.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > > I guess I would have lost my bet. Most of the complaints I see about > hostility seem to be about "the boys." From what you are telling me > it seems that the insulating attributes of Internet e-mail (real or > perceived) would allow women to be more agressive than they would > normally be inclined to in a physical situation. > I think that net-wide, most are 'boys.' They will show up all sorts of places they aren't welcome with their attitude. But women will get nasty with a group that they already know. (Keep in mind this is anecdotal! I havent' done a study on this - yet.) > > Hmm. Fortunately, most such types don't have enough physical courage > to show up on your doorstep, or stalk you. I have never heard of this > happening, but there was a recent case of a USENET poster posting a > violent rape/pornographic story with a real person named by name as > the victim. I know if I were her, I would be really upset, and worried > that if this guy was thinking such things would he or another guy > be inspired to implement them? This is scary. Actually, I have had to call the authorities. Someone who was thoroughly hostile on the net did make a local population of women nervous. As you mentioned, he wasn't probably physically dangerous in person, but he had such an aggresive, sexually hostile email manner, that those he had contacted personally on my list did request police protection. I did call for them. > > I wonder if anyone besides myself would see a value in keeping and > accessing a private list of such individuals. I would be willing to > maintain and disperse this data-base for known list managers. I would > take contributions that would help track these guys and help keep them > from becoming a problem. The point would not be to "blacklist" anyone > but to keep an impartial record for use by list managers, particularly > if they might have to get the authorities involved. Amy, Sharon, Linda, > would you participate? > Yes. I would be real, real cautious about it. But there have been a couple of totally hostile types that it would be good to know about if they are giving lists trouble. Perhaps it might be a 'low-profile' way to deal with these people. It might be less problem (but indeed more effective) to send a message like 'gee, we see you give lists trouble routinely' than calling out the cops. I think these sorts do what they do because they are sure there is no one 'net-watching' them. -Sharon From list-managers-owner Sun Mar 12 10:50:20 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA10464 for list-managers-outgoing; Sun, 12 Mar 1995 10:33:00 -0800 Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id KAA10459 for ; Sun, 12 Mar 1995 10:32:56 -0800 Received: from surt.ifi.uio.no (1232@surt.ifi.uio.no [129.240.76.2]) by ifi.uio.no with ESMTP (8.6.10/ifi2.4) id for ; Sun, 12 Mar 1995 19:30:40 +0100 From: Kjetil Torgrim Homme Received: (from kjetilho@localhost) by surt.ifi.uio.no ; Sun, 12 Mar 1995 19:30:39 +0100 Date: Sun, 12 Mar 1995 19:30:39 +0100 Message-Id: <199503121830.6778.surt.ifi.uio.no@ifi.uio.no> To: list-managers@GreatCircle.COM In-reply-to: <199503120420.WAA06658@usis.com> (siberia@usis.com) Subject: Re: List Moderation and Profanity Sender: list-managers-owner@GreatCircle.COM Precedence: bulk One reason to keep the list open to non-subscribers is gateways. The sysadmins here urge people to use the Usenet mirrors rather than subscribing ourselves (they are pretty responsive about creating new ones as they are needed). The mirrors are one-way, so I'd have to send mail to say linux-kernel@vger.rutgers.edu rather than post to fa.linux.kernel. However, it would be easy to extend Majordomo and other packages to keep a separate list of approved posters. It might even be a subset of the subscribers in some cases! A new command, "participate", perhaps? "subscribe" should implicitly mean "participate", of course. Since the list of participants is only used for checking, it doesn't matter whether addresses in it grow stale, so it should mean little or no extra hassle for the list manager. Kjetil T. PS. Please remember to use the majordomo list for majordomo-specific issues in response to this. From list-managers-owner Sun Mar 12 10:53:14 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA10473 for list-managers-outgoing; Sun, 12 Mar 1995 10:33:28 -0800 Received: from netcomsv.netcom.com (uumail3.netcom.com [163.179.3.53]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id KAA10468 for ; Sun, 12 Mar 1995 10:33:26 -0800 Received: from znyx.com by netcomsv.netcom.com with SMTP (8.6.9/SMI-4.1) id KAA13913; Sun, 12 Mar 1995 10:30:23 -0800 Received: from alan.znyx.com by znyx.com (5.65/1.35) id AA08156; Sun, 12 Mar 95 10:36:06 -0800 Date: Sun, 12 Mar 95 10:36:06 -0800 Message-Id: <9503121836.AA08156@znyx.com> X-Sender: alan@znyx.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Chris G Demetriou From: alan@znyx.com (Alan Deikman) Subject: Abuse problem is not treatable by Software Cc: list-managers@greatcircle.com Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >In general, i'm >not of the opinion that the words "fuck" and "asshole" are appropriate >for technical, computer-oriented lists, and i have no qualms about >bouncing messages containing them. 8-) > >the chunk of perl to do it looks like: The problem, Chris, with these types of solutions is that they invite further attack and do nothing, really, to solve the problem. Your post, and mine, would be bounced by the perl script you suggested, even though there is nothing objectionable in either. I have seen a lot of net.abusers that would take great delight in discovering ways to get around it with a vengance (being challenged) by posting such things as "XYZ is a phuqehead and an anushole..." You get the idea. The only real solution is to get these p-heads and a-holes off your list as quickly as possible. The trick is identifying them. Regards, -------------------------------- Alan Deikman, ZNYX Corporation alan@znyx.com From list-managers-owner Sun Mar 12 11:20:26 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA10920 for list-managers-outgoing; Sun, 12 Mar 1995 11:14:00 -0800 Received: from netcomsv.netcom.com (uumail2.netcom.com [163.179.3.52]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA10915 for ; Sun, 12 Mar 1995 11:13:57 -0800 Received: from znyx.com by netcomsv.netcom.com with SMTP (8.6.9/SMI-4.1) id LAA00668; Sun, 12 Mar 1995 11:10:53 -0800 Received: from alan.znyx.com by znyx.com (5.65/1.35) id AA08237; Sun, 12 Mar 95 11:16:41 -0800 Date: Sun, 12 Mar 95 11:16:41 -0800 Message-Id: <9503121916.AA08237@znyx.com> X-Sender: alan@znyx.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Sharon Shea From: alan@znyx.com (Alan Deikman) Subject: Proposed Trouble Data Base Cc: list-managers@greatcircle.com Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >> Amy, Sharon, Linda, would you participate? Amy wrote: >I'm not so sure it would be useful to me, b/c the people likely to be >giving me trouble wouldn't be the same kind giving others trouble -- the >reasons and just about everything else would be different. But I WOULD >appreciate it if someone would develop a better way of keeping unwanted >people OFF my lists, without me having to resort to making them moderated The trick to keeping them off your list is principally identifying them. Policy is up to a list manager, yourself. Sharon wrote: >Yes. I would be real, real cautious about it. Absolutely positively. Caution is what my suggestion is all about, and low profile is definitely the way to go. What I am suggesting is that several list-managers who know each other get together to share information by private e-mail. The last thing you want is this information to be known to the net in general. Kimberly wrote: >I don't know. This makes me uncomfortable. First of all, anyone >that is actively involved in the internet will eventually figure out >the "hard-core" trouble makers. The net may be appear to be a big >place, but in my experience, it really isn't. I think I know what you mean, but I saw an article in the SJ murky news this morning that listed the on-line services that provide over four million individuals access to the Internet. Stephanie's directory of lists is available to all of them. It isn't the ones that you know that are the problem, its the ones you don't know. >Keeping an "impartial record" seems too power-trippy to me as well as >ineffective. Maybe it is power-trippy. So what? I just know that I was considering opening some new lists and decided not to because I can't afford to have any controversy associated with my company's name just now. I very rarely post to USENET for the same reason. The way that I would envision this working is as follows: List Manager X sees some questionable postings from a given address. A note to the source doesn't help. E-mail to data base, "what do you have on Cranston Snord, foo@bar.com?" It turns out he was booted off of Y and Z's list. Now X knows Y and knows she would not do any such thing capriciously, but at least he knows now that there is a problem, which is 90% of the way to solving it. What to do is up to X, as always. I would also want such a data base to cross-reference aliases. That way you could find out that Cranston is also known as Farley Flamer, or that bar.com seems to have an awful lot of problem email coming from it lately. All of this is really no more than the Better Business Bureau does. X, Y, and Z, when they have a problem, copy the offending posting and send it in for future reference. Suppose Z has to finally call the authorites to have a chat with the much-wronged Mr. Snord. They will pay a lot more attention to Z if he has a history. True? Well, it's not a perfect scheme, and now that I have written some of it down it seems like a lot more work than I at first thought. But worth it if the resulting data base becomes really useful. Anyway, if as many as four list managers want to participate I would be willing to start the data base, although I think I would want to pass it to someone else later this year. Please note: I will be out of the office starting now through the end of the week to attend UniForum (come see our Fast Ethernet PCI Adpater) in Dallas. I will only be able to respond to e-mail after next weekend. Regards, and thanks for your comments, -------------------------------- Alan Deikman, ZNYX Corporation alan@znyx.com From list-managers-owner Sun Mar 12 11:50:25 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA11001 for list-managers-outgoing; Sun, 12 Mar 1995 11:22:28 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA10995 for ; Sun, 12 Mar 1995 11:22:25 -0800 Received: from [204.156.141.133] (agoodloe.vip.best.com [204.156.141.133]) by shell1.best.com (8.6.10/8.6.5) with SMTP id LAA04726; Sun, 12 Mar 1995 11:19:36 -0800 Date: Sun, 12 Mar 1995 11:19:36 -0800 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Kjetil Torgrim Homme From: agoodloe@best.com (Amy Goodloe) Subject: Re: List Moderation and Profanity Cc: list-managers@greatcircle.com Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Kjetil Torgrim Homme writes: >One reason to keep the list open to non-subscribers is gateways. The >sysadmins here urge people to use the Usenet mirrors rather than >subscribing ourselves (they are pretty responsive about creating new >ones as they are needed). The mirrors are one-way, so I'd have to send >mail to say linux-kernel@vger.rutgers.edu rather than post to >fa.linux.kernel. All this talk about gateways makes me wonder if my lists aren't maybe being gatewayed, WITHOUT my knowledge or permission. The object of all my lists is NOT size, but creating a comfortable environment for certain groups of people to engage in certain kinds of conversations. I don't want them gatewayed for all the world to read -- is there a way to avoid this? or to spot a "gatewayed" address? I've changed my majordomo settings to restricted-post by list members only (I had thought my sysadmin had done that already, but he apparently didn't set ANYTHING as I'd requested and left if all in default mode) -- so we'll see if this guy comes back to the one list. --amy agoodloe@best.com From list-managers-owner Sun Mar 12 12:50:20 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA11922 for list-managers-outgoing; Sun, 12 Mar 1995 12:25:08 -0800 Received: from wilma.cs.utk.edu (WILMA.CS.UTK.EDU [128.169.94.141]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id MAA11917 for ; Sun, 12 Mar 1995 12:25:05 -0800 Received: from LOCALHOST by wilma.cs.utk.edu with SMTP (cf v2.11c-UTK) id PAA26973; Sun, 12 Mar 1995 15:18:36 -0500 Message-Id: <199503122018.PAA26973@wilma.cs.utk.edu> X-URI: http://www.cs.utk.edu/~moore/ From: Keith Moore To: alan@znyx.com (Alan Deikman) cc: Chris G Demetriou , list-managers@greatcircle.com, moore@cs.utk.edu Subject: Re: Abuse problem is not treatable by Software In-reply-to: Your message of "Sun, 12 Mar 1995 10:36:06 PST." <9503121836.AA08156@znyx.com> Date: Sun, 12 Mar 1995 15:18:28 -0500 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > >In general, i'm > >not of the opinion that the words "fuck" and "asshole" are appropriate > >for technical, computer-oriented lists, and i have no qualms about > >bouncing messages containing them. 8-) > > > >the chunk of perl to do it looks like: > > The problem, Chris, with these types of solutions is that they invite > further attack and do nothing, really, to solve the problem. Actually, I've found it quite effective to filter messages. But instead of rejecting such postings, I filter the copies of the messages that go to the people who complain about such things. So instead of seeing "fucking" they see "fardling", and everybody else sees what the sender intended. Our standard filter to do this job is called "tipper". It's just a sed script. Personal attacks are another thing entirely, but I wouldn't put up with these on my lists, regardless of whether four-letter words were used or not. Keith From list-managers-owner Sun Mar 12 12:52:20 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA11980 for list-managers-outgoing; Sun, 12 Mar 1995 12:30:22 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id MAA11975 for ; Sun, 12 Mar 1995 12:30:19 -0800 Received: (frugal@localhost) by shell1.best.com (8.6.10/8.6.5) id MAA20938; Sun, 12 Mar 1995 12:27:40 -0800 Date: Sun, 12 Mar 1995 12:27:40 -0800 (PST) From: Linda Henneman To: Alan Deikman cc: Sharon Shea , list-managers@GreatCircle.COM Subject: Re: Proposed Trouble Data Base In-Reply-To: <9503121916.AA08237@znyx.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Alan, I don't feel comfortable keeping a list, either. I worry about people on it finding out and perhaps trying to bring some legal action for libel against the person who keeps the database plus people who give input. Even if their claims have no merit, you still have to pay to get an attorney and defend yourself. I'm reminded of when I did volunteer work for a tenants' rights organization and we discussed keeping a list of landlords that people had had bad experiences w/so people could call and check it out before renting w/someone and it couldn't be set up for the above reason. Plus, mean-spirited people could give false information so people who don't deserve to have negative things said about them could end up having that happen. This may be comparing applies and oranges somewhat as there's not a business reputation at stake generally in the case of the "sicko" list abusers, but IMHO it still applies. I'd like to say a great big *thank you* to everyone who's responded to my original post about profanity on lists--had no idea it would generate such feedback! It's been very, very helpful and made me feel very comfortable to be firm in my resolve not to allow what I feel is inappropriate material on my list. Best wishes to my comrades in the world of list managing! Linda Henneman (frugal@best.com) On Sun, 12 Mar 1995, Alan Deikman wrote: > >> Amy, Sharon, Linda, would you participate? From list-managers-owner Sun Mar 12 14:20:30 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA12710 for list-managers-outgoing; Sun, 12 Mar 1995 13:56:06 -0800 Received: from cs.umb.edu (cs.umb.edu [158.121.104.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id NAA12705 for ; Sun, 12 Mar 1995 13:56:03 -0800 Received: from terminus.cs.umb.edu by cs.umb.edu with SMTP id AA00292 (5.65c/IDA-1.4.4 for ); Sun, 12 Mar 1995 16:53:45 -0500 Message-Id: <199503122153.AA00292@cs.umb.edu> To: "Dave Lampson" Cc: list-managers@greatcircle.com Subject: Re: Help with Moderated List In-Reply-To: Your message of "Thu, 02 Mar 1995 10:20:14 PST." <199503021824.KAA07815@miles.greatcircle.com> Date: Sun, 12 Mar 1995 16:53:27 -0500 From: "John P. Rouillard" Sender: list-managers-owner@GreatCircle.COM Precedence: bulk In message <199503021824.KAA07815@miles.greatcircle.com>, "Dave Lampson" writes: >I have set up a moderated mailing list, defined a distribution list, >created an info file, editted the config file, and most things seem to be >working fine, except that I can't get anything distributed. Subscribing >and retrieving info works, but when I try and approve a post for >distribution, it just keeps bouncing back to me. > >I have tried putting the "Approved:" line in both the header of the >message (I use elm) and as the first line in the body of a message, and >I've sent it to "list" and not to "list-request", but they just keep >getting bounced back for approval. I'm stumped, but surely I'm missing >something obvious. I've been through the documentation thoroughly, and >can't see any problem with the procedure I'm using. Any suggestions? When troubleshooting this type of problem do two things: add an archive program to the list alias so you can see the message that is given to resend use approve to generate a message compare your approved message against approve's approved message and see what needs to be done. This assumes that approve puts our a correct message. -- John From list-managers-owner Sun Mar 12 14:50:23 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA13067 for list-managers-outgoing; Sun, 12 Mar 1995 14:27:29 -0800 Received: from rex.cs.tulane.edu (rex.cs.tulane.edu [129.81.132.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id OAA13050 for ; Sun, 12 Mar 1995 14:27:22 -0800 Received: by rex.cs.tulane.edu; Sun, 12 Mar 1995 16:25:05 -0600 >Received: by mintir.new-orleans.la.us (1.65/waf) via UUCP; Sun, 12 Mar 95 15:44:36 CST for list-managers@greatcircle.com To: list-managers@greatcircle.com Subject: opening lists to non-subscribers... From: elendil@mintir.new-orleans.la.us (Edward J. Branley) Message-ID: Date: Sun, 12 Mar 95 15:40:08 CST In-Reply-To: Organization: Minas Tirith BBS (Public Access Usenet for New Orleans) Content-Type: text Content-Length: 1655 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk rex!best.com!agoodloe (Amy Goodloe) writes: > At 10:21 PM 3/11/95, Kimberly Long wrote: > > >I cannot understand why anyone would not want to keep their list open > >to non-subscriber postings. Is there something I am missing? > > I can't understand why anyone WOULD want their lists open to non-subscriber > postings (is that what you meant?) I can't believe its the default in the > current version of majordomo to have lists open to random posts -- that > seems rather, well, dumb. But I also can't understand why it isn't harder > for outsiders to figure out the outgoing mail alias (I mean > listname-outgoing IS fairly obvious...) > This will vary from list to list. I keep my New Orleans list open to non-subscribers so folks can ask for info about the city without joining. I suppose some folks regard asking questions of a list membership without joining as being a bit rude, in the same way some people find messages that say things like "please e-mail me, I don't read this group regularly" rude on USENET. The default on my mail software was also to allow anyone to post, so majordomo is not unique in this regard. Now, I can see any list dealing with women's issues, gay or straight, as being a target for jerks. I'm sure that the authors of most list software didn't consider this when developing the programs. Nor did they factor in the increased number of "e-mail spams" we've been seeing lately. Cheers, Ed. |Edward J. Branley elendil@mintir.new-orleans.la.us| |Seashell Software +1.504.455.5087 (voice)| |3508 North Woodlawn Ave, Metairie, LA 70006 +1.504.455.8665 (bbs)| From list-managers-owner Sun Mar 12 15:20:22 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id PAA13566 for list-managers-outgoing; Sun, 12 Mar 1995 15:11:44 -0800 Received: from usis.com (usis.com [199.171.178.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id PAA13561 for ; Sun, 12 Mar 1995 15:11:41 -0800 Received: from siberia.usis.com (siberia.usis.com [199.171.178.71]) by usis.com (8.6.5/8.6.5) with SMTP id RAA10085 for ; Sun, 12 Mar 1995 17:05:33 -0600 Message-Id: <199503122305.RAA10085@usis.com> From: "Kimberly Long" Organization: usis To: list-managers@GreatCircle.COM Date: Sun, 12 Mar 1995 17:05:56 +0000 Subject: Re: opening lists to non-subscribers... Reply-to: siberia@usis.com Priority: normal X-mailer: Pegasus Mail/Windows (v1.22) Sender: list-managers-owner@GreatCircle.COM Precedence: bulk elendil@mintir.new-orleans.la.us (Edward J. Branley) wrote in part: > >[...] > > This will vary from list to list. I keep my New Orleans list open to > non-subscribers so folks can ask for info about the city without joining. > I suppose some folks regard asking questions of a list membership without > joining as being a bit rude, in the same way some people find messages that say > things like "please e-mail me, I don't read this group regularly" rude on > USENET. The default on my mail software was also to allow anyone to post, so > majordomo is not unique in this regard. > [...] I hope I am not being perceived as argumentative by furthering this discussion. I am simply am trying to understand all thoughts on this issue. :-) In regards to your example, wouldn't your regular subscribers get tired of seeing repeated requests: "send me info about New Orleans" from people that are not subscribers to the list? I would suspect that you have developed a (I always want to put "an" in front of FAQ, it just sounds better) FAQ for your list. Wouldn't your subscribers be better served by a deflection of repeated requests? You could even set up an infobot to automatically reply to what would appear to be a rather common question thereby improving your S/N ratio on your list. Just thinking outloud.... :-) Namaste' Kimberly Long siberia@usis.com If a man does not keep pace with his companions, perhaps it is because he hears a different drummer. Let him step to the music he hears, however measured or far away. )O( ~~Thoreau From list-managers-owner Sun Mar 12 15:22:43 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id PAA13586 for list-managers-outgoing; Sun, 12 Mar 1995 15:14:25 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id PAA13581 for ; Sun, 12 Mar 1995 15:14:22 -0800 Received: from [204.156.141.133] (agoodloe.vip.best.com [204.156.141.133]) by shell1.best.com (8.6.10/8.6.5) with SMTP id PAA03091; Sun, 12 Mar 1995 15:11:29 -0800 Date: Sun, 12 Mar 1995 15:11:29 -0800 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: "John P. Rouillard" , "Dave Lampson" From: agoodloe@best.com (Amy Goodloe) Subject: Re: Help with Moderated List Cc: list-managers@GreatCircle.COM Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >In message <199503021824.KAA07815@miles.greatcircle.com>, >"Dave Lampson" writes: >>I have set up a moderated mailing list, defined a distribution list, >>created an info file, editted the config file, and most things seem to be >>working fine, except that I can't get anything distributed. Subscribing >>and retrieving info works, but when I try and approve a post for >>distribution, it just keeps bouncing back to me. >> >>I have tried putting the "Approved:" line in both the header of the >>message (I use elm) and as the first line in the body of a message, and >>I've sent it to "list" and not to "list-request", but they just keep >>getting bounced back for approval. I'm stumped, but surely I'm missing >>something obvious. I've been through the documentation thoroughly, and >>can't see any problem with the procedure I'm using. Any suggestions? What does the BOUNCED line say? Does it say: ADMIN REQUEST? It could be that you have your list set up to filter out administrative requests, which means that majordomo will bounce any message with the words subscribe, unsubscribe, help, info, lists or several others in the first five lines. While I find this sometimes useful as a feature, it's often a PITA, esp. if you're running a help list where people routinely use those words in their posts. Or does the bounced line say: INVALID APPROVAL or something like that? I approve messages by adding the following THREE lines at the beginning of the message to be approved: ----------------------------- Approved: passwd From: fill in sender Subject: fill in subject Paste message here. Address message to listname@site.com. ------------------------------ For what it's worth, I find the approval process often quite tricky, and have even seen some of my messages go right to the list WITH the approval lines (and passwords) still in them... Sorry not to be of much more help. --amy From list-managers-owner Sun Mar 12 15:50:21 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id PAA13959 for list-managers-outgoing; Sun, 12 Mar 1995 15:35:17 -0800 Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id PAA13954 for ; Sun, 12 Mar 1995 15:35:14 -0800 From: pshuang@MIT.EDU Received: from CARTOON.MIT.EDU by MIT.EDU with SMTP id AB10176; Sun, 12 Mar 95 18:32:54 EST Received: by cartoon.MIT.EDU (5.57/4.7) id AA16579; Sun, 12 Mar 95 18:32:54 -0500 Date: Sun, 12 Mar 95 18:32:54 -0500 Message-Id: <9503122332.AA16579@cartoon.MIT.EDU> To: List-Managers@GreatCircle.COM In-Reply-To: list-managers-digest-owner@GreatCircle.COM's message of Sun, 12 Mar 1995 01:00:12 -0800 <199503120900.BAA03400@miles.greatcircle.com> Subject: Unwelcome subscribers (was: List Moderation and Profanity) Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > From: agoodloe@best.com (Amy Goodloe) > Date: Sat, 11 Mar 1995 09:54:39 -0800 > > [....] > > I have a similar concern. There is someone who is subscribed to one > of my lists who is clearl NOT welcome on the list; the list policies > state as much and he has been told privately twice. [....] I used to run a mailing list for people who wished to conduct discussions about Greek Letter organizations (both social and non-social fraternities and sororities) with less flamage than could be found on various Usenet newsgroups (e.g., soc.college), a topic which can also "draw maggots out of the woodwork". (I'm sure another such maggot-drawing topic would be religion.) At one point, someone who was fair well-known in those Usenet newsgroups for taking one side of long flaming effectively content-free threads wanted to subscribe to the mailing list. After some discussion amongst ourselves, the other list owner and I decided to let him subscribe, after explicitly letting him know he needs to be on "good behavior". Although he WAS on pretty good behavior ON THE MAILING LIST, many other subscribers immediately engaged in ad hominem attacks, flooded the mailing list itself with protests despite requests from myself and the other list owner to send such protests to us, and in general made mayhem. One of the reasons the other list owner and I decided to discontinue the list was precisely our disgust at this kind of reaction. There wasn't much question that we could have denied him a subscription; however, we felt that he was being more reasonable than many others on the mailing list and therefore did not deserve to get kicked off. Quoted below is the policy about such problem subscribers from a different mailing list I help maintain, which sets an explicit policy for removal and appeal. Other list maintainers/owners may wish to adapt such a policy for their own mailing lists; alternatively, you may decide that you would rather not set such a policy in stone. > ******** Policy concerning removal from the lists > > The administrators reserve the right to remove individuals from the > lists under extraordinary circumstances. It is difficult to > anticipate every reason why someone might be removed from the > lists; in general, behavior which is substantially disruptive to > the list and which is known by the perpetrator to be inappropriate > may lead to removal. > > An individual who is removed from the lists will be notified of the > removal by the administrators. If he or she wishes to appeal the > removal, a poll will be taken of the current membership of the > faq-maintainers list. If 10% or more of the current membership > supports reinstatement, the individual will be returned to the lists. -- Yours in Leadership, Friendship, and Service, Ping Huang (INTERNET: pshuang@mit.edu), probably speaking for himself From list-managers-owner Sun Mar 12 18:20:28 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id RAA15770 for list-managers-outgoing; Sun, 12 Mar 1995 17:58:57 -0800 Received: from rex.cs.tulane.edu (rex.cs.tulane.edu [129.81.132.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id RAA15765 for ; Sun, 12 Mar 1995 17:58:54 -0800 Received: by rex.cs.tulane.edu; Sun, 12 Mar 1995 19:56:37 -0600 >Received: by mintir.new-orleans.la.us (1.65/waf) via UUCP; Sun, 12 Mar 95 19:32:22 CST for list-managers@greatcircle.com To: list-managers@greatcircle.com Subject: messages from non-subscribers From: elendil@mintir.new-orleans.la.us (Edward J. Branley) Message-ID: Date: Sun, 12 Mar 95 19:21:28 CST In-Reply-To: <199503122305.RAA10085@usis.com> Organization: Minas Tirith BBS (Public Access Usenet for New Orleans) Content-Type: text Content-Length: 2390 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk "Kimberly Long" writes: > I hope I am not being perceived as argumentative by furthering this > discussion. I am simply am trying to understand all thoughts on this > issue. :-) > > In regards to your example, wouldn't your regular subscribers get > tired of seeing repeated requests: "send me info about New Orleans" > from people that are not subscribers to the list? I would suspect > that you have developed a (I always want to put "an" in front of FAQ, > it just sounds better) FAQ for your list. Wouldn't your subscribers > be better served by a deflection of repeated requests? You could > even set up an infobot to automatically reply to what would appear to > be a rather common question thereby improving your S/N ratio on your > list. I do indeed have a FAQ for the list, so I use the reply to the non-subscriber to let them know where that is. That in itself is a service to many on the list, since so many newbies don't read the "welcome" message that they receive when they subscribe. They are either unaware of how to get the FAQ or they've forgotten. Most of the requests tend to be more specific than "send me info about New Orleans," so I try to turn a negative (repeated questions) into a positive (fodder for discussion among regulars). For example, Jane Non-subscriber sends a message that reads something like: "I'm coming to town on such-and-such a date. What are some good places to eat?" I'll post some suggestions, and, if I'm feeling particularly devilish, I'll make one or two of those suggestions someplace that will spark controversy amongst the regulars. A discussion on the relative merits of the restaurants ensues. Jane gets her answer, and the regulars chat. Everyone's happy. I suppose if the off-list requests became more frequent than they are now, I might consider a policy change. Fortunately, the incidence of spamming on my list has been light, and the off-list requests have been fairly intelligent questions (e.g., restaurant recommendations, requests from folks doing research on specifics, etc.) > > Just thinking outloud.... :-) > So long as nobody hears you... :-) Cheers, Ed. |Edward J. Branley elendil@mintir.new-orleans.la.us| |Seashell Software +1.504.455.5087 (voice)| |3508 North Woodlawn Ave, Metairie, LA 70006 +1.504.455.8665 (bbs)| From list-managers-owner Sun Mar 12 19:51:44 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA17456 for list-managers-outgoing; Sun, 12 Mar 1995 19:30:04 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id XAA02820 for ; Sat, 11 Mar 1995 23:52:35 -0800 Received: from [204.156.141.133] (agoodloe.vip.best.com [204.156.141.133]) by shell1.best.com (8.6.10/8.6.5) with SMTP id XAA12461; Sat, 11 Mar 1995 23:49:55 -0801 Date: Sat, 11 Mar 1995 23:49:55 -0801 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: alan@znyx.com (Alan Deikman) From: agoodloe@best.com (Amy Goodloe) Subject: Re: List Moderation and Profanity Cc: list-managers@greatcircle.com Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >I wonder if anyone besides myself would see a value in keeping and >accessing a private list of such individuals. I would be willing to >maintain and disperse this data-base for known list managers. I would >take contributions that would help track these guys and help keep them >from becoming a problem. The point would not be to "blacklist" anyone >but to keep an impartial record for use by list managers, particularly >if they might have to get the authorities involved. Amy, Sharon, Linda, >would you participate? I'm not so sure it would be useful to me, b/c the people likely to be giving me trouble wouldn't be the same kind giving others trouble -- the reasons and just about everything else would be different. But I WOULD appreciate it if someone would develop a better way of keeping unwanted people OFF my lists, without me having to resort to making them moderated (I run 7 lists; they ALREADY take up too much time -- moderation would be HELL). I suppose I should just be more choosy in my approval of subscribe requests process... --amy From list-managers-owner Sun Mar 12 19:54:57 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA17458 for list-managers-outgoing; Sun, 12 Mar 1995 19:30:08 -0800 Received: from LAGAVULIN.PDL.CS.CMU.EDU (LAGAVULIN.PDL.CS.CMU.EDU [128.2.198.241]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id BAA04138 for ; Sun, 12 Mar 1995 01:26:15 -0800 Message-Id: <199503120926.BAA04138@miles.greatcircle.com> Received: from localhost by LAGAVULIN.PDL.CS.CMU.EDU id aa09321; 12 Mar 95 4:23 EST To: Amy Goodloe cc: list-managers@greatcircle.com X-Copyright: Copyright 1995, Christopher G. Demetriou. All rights reserved. X-Notice: Duplication and redistribution prohibited without consent of the author. Subject: Re: List Moderation and Profanity In-reply-to: Your message of "Sat, 11 Mar 1995 09:54:39 PST." Date: Sun, 12 Mar 1995 04:23:11 -0500 From: Chris G Demetriou Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > I have a similar concern. There is someone who is subscribed to one of my > lists who is clearl NOT welcome on the list; the list policies state as > much and he has been told privately twice. The problem is that I can't > seem to unsubscribe him, as his address does not appear to be listed in the > majordomo listmember file. I've tried searching for as many variations as > possible, but I can't seem to figure out HOW he's getting list mail -- b/c > it must be under a name that IS on the list; otherwise he wouldn't be > "allowed" by majordomo to post to it. Well, assuming that the restriction that he must be on the list to post to it is actually in effect have you tried logging all incoming mail for the list (i.e. dumping it into a log file via a sendmail alias), and comparing all of the addresses in that (e.g. From, Sender, etc.) against those in the 'bad posts' and the subscription list? If you only look at the mail after majordomo has resent it, some of the "jucier" headers may have been clobbered. chris From list-managers-owner Sun Mar 12 19:58:43 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA17436 for list-managers-outgoing; Sun, 12 Mar 1995 19:29:59 -0800 Received: from netcomsv.netcom.com (uumail2.netcom.com [163.179.3.52]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA21116 for ; Sat, 11 Mar 1995 11:21:51 -0800 Received: from znyx.com by netcomsv.netcom.com with SMTP (8.6.9/SMI-4.1) id LAA13369; Sat, 11 Mar 1995 11:18:47 -0800 Received: from alan.znyx.com by znyx.com (5.65/1.35) id AA03094; Sat, 11 Mar 95 11:24:14 -0800 Date: Sat, 11 Mar 95 11:24:14 -0800 Message-Id: <9503111924.AA03094@znyx.com> X-Sender: alan@znyx.com 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: alan@znyx.com (Alan Deikman) Subject: Re: List Moderation and Profanity Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >I have a similar concern. There is someone who is subscribed to one of my >lists who is clearl NOT welcome on the list; the list policies state as >much and he has been told privately twice. The problem is that I can't >seem to unsubscribe him, as his address does not appear to be listed in the >majordomo listmember file. I've tried searching for as many variations as >possible, but I can't seem to figure out HOW he's getting list mail -- b/c >it must be under a name that IS on the list; otherwise he wouldn't be >"allowed" by majordomo to post to it. >I've gotten notes from a few subscribers telling me about what this guy has >done on other lists, and I'm quite sure he knows he isn't welcome on this >list and has deliberately made it tough to track down his subscribed >address. Any ideas on how I CAN track it down, or on what to do? The list >is currently not moderated, but I suppose if all else fails I *could* just >make it moderated... > Yow. What a nightmare. I can think of several techniques for gate crashers. The most trivial, and the one you are probably looking for, is to get an alias in one domain or another. There are a lot of systems on the Internet where you can get an account fairly easily, often for free. Also likely is a collaborator on your list that happens to be in good standing is sending him copies of postings. The worst case is if he has su access to a system that handles a lot of Internet mail, including acting as a gateway for *your* system. There are all sorts of games a hacker can play with "catching" mail, corrupting it, and re-sending it, making it impossible to trace. If he is doing this, you may have a case to take to the police. This kind of hacking is against the law and its possible the owner of the system he is using is not even aware of it. Good luck, -------------------------------- Alan Deikman, ZNYX Corporation alan@znyx.com From list-managers-owner Sun Mar 12 22:50:37 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id WAA22542 for list-managers-outgoing; Sun, 12 Mar 1995 22:33:43 -0800 Received: from UUCP-GW.CC.UH.EDU (UUCP-GW.CC.UH.EDU [129.7.1.11]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id WAA22537 for ; Sun, 12 Mar 1995 22:33:37 -0800 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA10955 (5.67a/IDA-1.5 for greatcircle.com!list-managers); Mon, 13 Mar 1995 00:04:07 -0600 Received: by bonkers.taronga.com (smail2.5p) id AA27370; 12 Mar 95 23:43:42 CST (Sun) Received: (from arielle@localhost) by bonkers.taronga.com (8.6.8/8.6.6) id XAA27367 for list-managers@greatcircle.com; Sun, 12 Mar 1995 23:43:41 -0600 From: Stephanie da Silva Message-Id: <199503130543.XAA27367@bonkers.taronga.com> Subject: Re: Failed LISTSERV@wsyd.com access? what happened from your end(fwd) To: list-managers@greatcircle.com Date: Sun, 12 Mar 1995 23:43:40 -0600 (CST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1192 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I was a third party to this, it got cc'ed to me (I probably did send his listserv a request that bounced). But I thought it might be of interest to some list owners, to see if their lists were involved in this abuse. > From: Barry Kort > Message-Id: <199503121654.LAA24894@michael.musenet.org> > Subject: Re: Failed LISTSERV@wsyd.com access? what happened from your end, > To: james@wsyd.com (James Pallack) > Date: Sun, 12 Mar 1995 11:54:14 -0500 (EST) > > > > I was going though my LOGS and noticed that my system had received a > > LISTSERV request from you. But looks as if it BOUNCED the reply. But > > not sure if it bounced your request instead. > > I didn't request it. A notorious Internet hacker sent forged E-Mail > to hundreds of ListServs around the world to subscribe me and others > to hundreds of lists. The following addresses were victimized by > this attack: > > barry@musenet.org > dc@musenet.org > bkort@musenet.org > veralynn@aardvark.stu.rpi.edu > veralynn@dan.com > co215@cleveland.freenet.edu > > None of the above should be on any of your subscription lists. > > If you would like further information, please contact me. > From list-managers-owner Mon Mar 13 12:21:26 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id MAA08305 for list-managers-outgoing; Mon, 13 Mar 1995 12:07:28 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id MAA08300 for ; Mon, 13 Mar 1995 12:07:25 -0800 Received: from [204.156.141.133] (agoodloe.vip.best.com [204.156.141.133]) by shell1.best.com (8.6.10/8.6.5) with SMTP id MAA08834 for ; Mon, 13 Mar 1995 12:04:53 -0801 Date: Mon, 13 Mar 1995 12:04:53 -0801 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: list-managers@GreatCircle.COM From: agoodloe@best.com (Amy Goodloe) Subject: Subject: duplicated posts -- what causes them? Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I've been on lists that went through duplication periods, where every post came through twice, and now it's happening on one of my lists (all lists in question are majordomo run). What causes duplication and how does one fix it? I've checked the headers of some duplicated messages to see if they're coming to slightly diff. addresses, and that isn't it. Any advice would be appreciated. --Amy agoodloe@best.com From list-managers-owner Mon Mar 13 13:51:26 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA10927 for list-managers-outgoing; Mon, 13 Mar 1995 13:42:04 -0800 Received: from wilma.cs.utk.edu (WILMA.CS.UTK.EDU [128.169.94.141]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id NAA10922 for ; Mon, 13 Mar 1995 13:42:01 -0800 Received: from LOCALHOST by wilma.cs.utk.edu with SMTP (cf v2.11c-UTK) id QAA02539; Mon, 13 Mar 1995 16:36:25 -0500 Message-Id: <199503132136.QAA02539@wilma.cs.utk.edu> X-URI: http://www.cs.utk.edu/~moore/ From: Keith Moore To: agoodloe@best.com (Amy Goodloe) cc: list-managers@greatcircle.com, moore@cs.utk.edu Subject: Re: Subject: duplicated posts -- what causes them? In-reply-to: Your message of "Mon, 13 Mar 1995 12:04:53 -0801." Date: Mon, 13 Mar 1995 16:36:19 -0500 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > I've been on lists that went through duplication periods, where > every post came through twice, and now it's happening on one of my > lists (all lists in question are majordomo run). What causes > duplication and how does one fix it? I've checked the headers of > some duplicated messages to see if they're coming to slightly > diff. addresses, and that isn't it. I've seen several reasons for duplicate messages. 1. It is normal for an occasional message to be duplicated. For example, machine A completely transfers a message to machine B but never gets a response from B that B got the message. So machine A sends it again. It's rare that such a response gets lost (or that either machine A or B shuts down at just the right time), but it does happen. 2. Extraordinary circumstances can cause the above to happen more often that it should. For instance, some mailers won't return the response that "they got the message" until they've tried to send it to every one of the recipients of that message (or at least verify their addresses). For a long list, this can take so long that the sending mailer (machine A in the above example) assumes that machine B has crashed, so machine A re-sends the message. Because it's affected by network delays, the symptom can come and go with no apparent cause. 3. Some thoroughly broken mail gateways to LAN environments will, instead of bouncing a message to the sender, re-send a message to each of its recipients. (One of these just sent 600+ duplicate messages to one of my lists.) 4. The same thing can occur with gateways between mailing lists and Usenet newsgroups, if they aren't set up carefully. The newsgroup sends a message to the mailing list, which promptly sends it back to the newsgroup. If the message-id changes (some lists do this), Usenet will think it's a new article and send it back to the mailing list. You can usually tell where the duplication is coming from by comparing the Received headers of a few copies of such a message, and see where they diverge. (The dates on the Received headers of two copies of a duplicated message will be the same before the point of duplication, and different afterward.) Some list managers try to be smart and detect duplicated messages by recognizing any text and/or message-id that appears more than once. Sometimes this works very well; at other times it ends up rejecting perfectly valid messages that happen to contain parts of old messages. (In particular, Listproc 6.0 is notorious for doing this badly.) Keith From list-managers-owner Mon Mar 13 21:20:34 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id VAA20291 for list-managers-outgoing; Mon, 13 Mar 1995 21:00:49 -0800 Received: from ns.ge.com (ns.ge.com [192.35.39.24]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id VAA20286 for ; Mon, 13 Mar 1995 21:00:46 -0800 Received: from [158.254.10.56] (xcrsnyder.ge_xc.dialup.net [158.254.10.56]) by ns.ge.com (8.6.11/8.6.11) with SMTP id XAA27385 for ; Mon, 13 Mar 1995 23:58:25 -0500 X-Sender: snyderra@dunx1.ocs.drexel.edu Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 13 Mar 1995 23:58:33 -0500 To: list-managers@GreatCircle.COM From: snyderra@post.drexel.edu (Bob Snyder) Subject: Non-subscriber postings Sender: list-managers-owner@GreatCircle.COM Precedence: bulk At 11:50 PM 3/11/95, Amy Goodloe wrote: >I can't understand why anyone WOULD want their lists open to non-subscriber >postings (is that what you meant?) I can't believe its the default in the >current version of majordomo to have lists open to random posts -- that >seems rather, well, dumb. But I also can't understand why it isn't harder Well, one reason I can think of is that many hosts aren't configured to send mail as a domain address. For example, you may have the foo.com domain, with a.foo.com, b.foo.com, c.foo.com, and so on. Mail from the user could come from any of them. There are ways of coding around them, but preventing subscribers from posting is a tad anti-social without cause. Bob -- Bob Snyder N2KGO MIME, PGP, RIPEM mail accepted snyderra@post.drexel.edu PGP & RIPEM keys on key servers When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl. From list-managers-owner Tue Mar 14 02:50:28 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id CAA25547 for list-managers-outgoing; Tue, 14 Mar 1995 02:26:10 -0800 Received: from jazzie.com (p8.jazzie.com [192.147.229.18]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id CAA25542 for ; Tue, 14 Mar 1995 02:26:06 -0800 Received: by jazzie.com (Smail3.1.28.1 #63) id m0roTkW-000OWwC; Tue, 14 Mar 95 02:22 PST Message-Id: From: sds@jazzie.com (Sean Shapira) Subject: Re: Proposed Trouble Data Base To: alan@znyx.com (Alan Deikman) Date: Tue, 14 Mar 1995 02:22:48 -0800 (PST) Cc: sshea@world.std.com, list-managers@greatcircle.com In-Reply-To: <9503121916.AA08237@znyx.com> from "Alan Deikman" at Mar 12, 95 11:16:41 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1486 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Alan wrote: > The trick to keeping them off your list is principally > identifying them. Identity is a nebulous concept. I know people who maintain an electronic personae for their professional life completely separate from their personal persona. Which do you want to identify: the person, or the persona? List managers interested in mapping email personae to real- world people should check out the SLED (Stable, Large, Email Database) project. Mail to info@sled.com gets you a nice description of the service from their mailbot. (Obligatory disclaimer: I have no connection to SLED other than having taken advantage of their free service.) > What I am suggesting > is that several list-managers who know each other get together to > share information by private e-mail. The last thing you want is > this information to be known to the net in general. As others have done, I suggest extreme care with this approach. A public database open to inspection and correction (like the big credit databases) would be less vulnerable to criticism. Kimberly wrote: >The net may be appear to be a big >place, but in my experience, it really isn't. I have just one word in response: "Growth." FWIW, I believe the best approach to shaping list traffic is "out-of-band self-moderation". I would be happy to expand on this idea if there's interest.... -- Sean Shapira sds@jazzie.com (206) 443-2028 Jazzie Systems From list-managers-owner Tue Mar 14 04:50:33 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id EAA26752 for list-managers-outgoing; Tue, 14 Mar 1995 04:23:37 -0800 Received: from maroon.tc.umn.edu (maroon.tc.umn.edu [128.101.118.21]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id EAA26747 for ; Tue, 14 Mar 1995 04:23:33 -0800 Received: from dialup-3-242.gw.umn.edu by maroon.tc.umn.edu; Tue, 14 Mar 95 06:20:19 -0500 Date: Tue, 14 Mar 95 06:21:10 CST From: "Fred H Olson WB0YQM" Message-Id: <37487.fholson@maroon.tc.umn.edu> X-Minuet-Version: Minuet1.0_Beta_17A Reply-To: X-POPMail-Charset: English To: List-Managers@GreatCircle.COM Subject: List abusers database Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I would participate in such a database tho I have not had much problem. I do wonder if it's worth the effort. I would propose that the format be name, email address and url of sample objectionable posts from the abuser. It's hard to charge libel if you dont comment. One could even have a discalimer such as: "No implications is intended by names simply being mentioned in this archive; please use the author's words to draw any conclusions." Try to stick to the facts. Let the abuser speak for themselves. The effort to maintain it would be minimal if the database were a non linked searchable WWW archive of email messages (obscure URL shared among participating list managers only). The lack of good information to enforce accountability and appropriate 'peer pressure' lets a lot of anti social behavior thrive. It's sort of like people will write graffitti on bathroom walls that they wouldn't say in public. Fred -- Fred H. Olson fholson@uci.com (612)588-9532 Amateur radio: WB0YQM 1221 Russell Av N, Minneapolis,MN 55411 Sysop of COHOUSING-L listserv; COHOUSING URL's: mailto://listserv@uci.com (w/ msg: Info Cohousing-L) gopher://gopher.uci.com/ TC FREENET PUBLIC TEST PHASE: May 1, 1995 URL's: mailto://info@freenet.msp.mn.us http://freenet.msp.mn.us:8000/ From list-managers-owner Tue Mar 14 04:53:16 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id EAA26746 for list-managers-outgoing; Tue, 14 Mar 1995 04:23:32 -0800 Received: from maroon.tc.umn.edu (maroon.tc.umn.edu [128.101.118.21]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id EAA26741 for ; Tue, 14 Mar 1995 04:23:28 -0800 Received: from dialup-3-242.gw.umn.edu by maroon.tc.umn.edu; Tue, 14 Mar 95 06:20:07 -0500 Date: Tue, 14 Mar 95 06:20:58 CST From: "Fred H Olson WB0YQM" Message-Id: <37476.fholson@maroon.tc.umn.edu> X-Minuet-Version: Minuet1.0_Beta_17A Reply-To: X-POPMail-Charset: English To: List-Managers@GreatCircle.COM Subject: Re: Non-subscriber postings Sender: list-managers-owner@GreatCircle.COM Precedence: bulk My list requires subscription to post and tho there In order to post or execute most commands, the listserver requires that they be sent from an address of a subscriber. The reason for this requirement is to prevent distributing messages such as 1) error messages that are sent back to the list's address. 2) "spam" messages -- broadcast advertising and other inappropriate messages. 3) just inappropriate messages posted by nosubscribers I think this policy is worth it. Cohousing-L gets comments about it's high signal to noise ratio. Early on we had some error messages that got distributed, which caused us to adopt this policy. But there are times when I wonder if it is worth it because some messages are "rejected" because the list server sometimes finds a variation on a subscribers address and rejected a valid post. I repost these (and appropriatemessages from non-subscribers) manually with a little preface explaination. (I have a little file explaining this more - available on request.) snyderra@post.drexel.edu (Bob Snyder) said: > > but preventing subscribers from posting is a tad anti-social >without cause. True but their post does get posted manually (on my list) and I think the benefits are worth it. I've had no complaints. Fred -- Fred H. Olson fholson@uci.com (612)588-9532 Amateur radio: WB0YQM 1221 Russell Av N, Minneapolis,MN 55411 Sysop of COHOUSING-L listserv; COHOUSING URL's: mailto://listserv@uci.com (w/ msg: Info Cohousing-L) gopher://gopher.uci.com/ TC FREENET PUBLIC TEST PHASE: May 1, 1995 URL's: mailto://info@freenet.msp.mn.us http://freenet.msp.mn.us:8000/ From list-managers-owner Tue Mar 14 10:26:35 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id JAA00940 for list-managers-outgoing; Tue, 14 Mar 1995 09:55:29 -0800 Received: from xmission.xmission.com (xmission.xmission.com [198.60.22.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id JAA00935 for ; Tue, 14 Mar 1995 09:55:26 -0800 Received: from slc69.xmission.com (slc69.xmission.com [198.60.22.169]) by xmission.xmission.com (8.6.10/8.6.10) with SMTP id KAA27365 for ; Tue, 14 Mar 1995 10:53:05 -0700 Message-Id: <199503141753.KAA27365@xmission.xmission.com> From: "clements@xmission.com" Organization: xmission.com To: list-managers@GreatCircle.COM Date: Tue, 14 Mar 1995 10:43:36 +0000 Subject: New to the list Reply-to: clements@xmission.com Priority: normal X-mailer: Pegasus Mail/Windows (v1.22) Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Hello I am new to this list and am looking for some good sources for information on learning majordomo. I will be starting / managing a mailing list soon using majordomo as the mailer. Are there any sources on the network that have online documentation on majordomo. Maybe down the road I may be able to contribute to the group but being a novice I will probably be asking more questions than I am answering at this point. Thank you, jim ______________________________________________________________ Jim Clements email: clements@xmission.com Total Health Marketing ph. 801/553-8716 fax 801/553-1606 Nikken Independent Distributors http://www.xmission.com/~total/health.html From list-managers-owner Tue Mar 14 10:30:40 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA01159 for list-managers-outgoing; Tue, 14 Mar 1995 10:03:58 -0800 Received: from pinyon.enet.net (pinyon.enet.net [168.158.8.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id KAA01154 for ; Tue, 14 Mar 1995 10:03:55 -0800 Received: (from oceania@localhost) by pinyon.enet.net (8.6.9/8.6.9) id LAA05738 for list-managers@greatcircle.com; Tue, 14 Mar 1995 11:02:14 -0700 Date: Tue, 14 Mar 1995 11:02:14 -0700 From: Eric Klien Message-Id: <199503141802.LAA05738@pinyon.enet.net> To: list-managers@greatcircle.com Subject: Security Problems Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Hello, I am working on changing the code of majordomo by hand to solve some major security problems with it. The problems that I have are that 1) anyone can post to the list by sending e-mail to list-l-outgoing and 2) anyone can get a copy of the list by sending majordomo telnet client 25, expn listname-outgoing even if I disable the who command in majordomo. Can anyone give suggestions on solving the above problems? Someone suggested that I "have MajorDomo create a temporary copy of the list each time a message is sent from the list". How could I accomplish this? Eric Klien +---------------------------------------------------------------+ | Oceania: A New Country In Development -> welcome@oceania.org | +---------------------------------------------------------------+ From list-managers-owner Tue Mar 14 10:56:51 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA01909 for list-managers-outgoing; Tue, 14 Mar 1995 10:44:37 -0800 Received: from leibniz.math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id KAA01904 for ; Tue, 14 Mar 1995 10:44:33 -0800 Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.131.77]) by leibniz.math.psu.edu (8.6.10/8.6.9) with ESMTP id NAA18116; Tue, 14 Mar 1995 13:42:16 -0500 Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.6.10/8.6.9) with ESMTP id NAA18039; Tue, 14 Mar 1995 13:42:14 -0500 Message-Id: <199503141842.NAA18039@augusta.math.psu.edu> X-Mailer: exmh version 1.5.3 12/28/94 To: Eric Klien cc: list-managers@GreatCircle.COM Subject: Re: Security Problems In-reply-to: Your message of "Tue, 14 Mar 1995 11:02:14 MST." <199503141802.LAA05738@pinyon.enet.net> X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 14 Mar 1995 13:42:13 -0500 From: Dave Barr Sender: list-managers-owner@GreatCircle.COM Precedence: bulk In message <199503141802.LAA05738@pinyon.enet.net>, Eric Klien writes: >I am working on changing the code of majordomo by hand to solve some >major security problems with it. The problems that I have are that >1) anyone can post to the list by sending e-mail to list-l-outgoing >and 2) anyone can get a copy of the list by sending majordomo telnet >client 25, expn listname-outgoing even if I disable the who command >in majordomo. The Majordomo FAQ goes into great length to tell you how to solve this problem without any code changes. http://www.math.psu.edu/barr/majordomo-faq.html --Dave From list-managers-owner Tue Mar 14 11:29:36 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA02576 for list-managers-outgoing; Tue, 14 Mar 1995 11:10:52 -0800 Received: from pinyon.enet.net (pinyon.enet.net [168.158.8.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA02570 for ; Tue, 14 Mar 1995 11:10:49 -0800 Received: (from oceania@localhost) by pinyon.enet.net (8.6.9/8.6.9) id MAA06636; Tue, 14 Mar 1995 12:09:08 -0700 Date: Tue, 14 Mar 1995 12:09:08 -0700 From: Eric Klien Message-Id: <199503141909.MAA06636@pinyon.enet.net> To: list-managers@greatcircle.com, reb@serf.nsc.com Subject: Security Sender: list-managers-owner@GreatCircle.COM Precedence: bulk "Maybe you could incorporate PGP into the list." While I would love a feature that would only send a subscription list to the owner PGP encrypted, my problem with moderated lists is not related. With my current majordomo setup, anyone can post to my list even if they don't know either the owner's name or owner's password. Eric Klien +---------------------------------------------------------------+ | Oceania: A New Country In Development -> welcome@oceania.org | +---------------------------------------------------------------+ From list-managers-owner Tue Mar 14 11:33:56 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA02590 for list-managers-outgoing; Tue, 14 Mar 1995 11:11:02 -0800 Received: from pinyon.enet.net (pinyon.enet.net [168.158.8.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA02579 for ; Tue, 14 Mar 1995 11:10:57 -0800 Received: (from oceania@localhost) by pinyon.enet.net (8.6.9/8.6.9) id MAA06630; Tue, 14 Mar 1995 12:08:37 -0700 Date: Tue, 14 Mar 1995 12:08:37 -0700 From: Eric Klien Message-Id: <199503141908.MAA06630@pinyon.enet.net> To: barr@math.psu.edu, list-managers@greatcircle.com Subject: Security Sender: list-managers-owner@GreatCircle.COM Precedence: bulk "It's a directive which was used a lot by Brent but sort of fell into undocumentation. Look in the beginning of the 'resend' script for the explanation." I have looked there but I am no Perl expert. Could you tell me exactly what changes I would have to make in resend to solve the problem. Would I also have to make any change in the aliases file in /etc? Eric Klien +---------------------------------------------------------------+ | Oceania: A New Country In Development -> welcome@oceania.org | +---------------------------------------------------------------+ From list-managers-owner Tue Mar 14 12:11:03 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA02143 for list-managers-outgoing; Tue, 14 Mar 1995 10:53:41 -0800 Received: from pinyon.enet.net (pinyon.enet.net [168.158.8.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id KAA02138 for ; Tue, 14 Mar 1995 10:53:38 -0800 Received: (from oceania@localhost) by pinyon.enet.net (8.6.9/8.6.9) id LAA06355; Tue, 14 Mar 1995 11:51:19 -0700 Date: Tue, 14 Mar 1995 11:51:19 -0700 From: Eric Klien Message-Id: <199503141851.LAA06355@pinyon.enet.net> To: barr@math.psu.edu, list-managers@greatcircle.com Subject: Security Problems continued Sender: list-managers-owner@GreatCircle.COM Precedence: bulk " You can use the "@filename" directive in resend to move the command-line options of resend into a file readable only by the majordomo user/group. This will make it such that you can't find out the -outgoing address by connecting to your mailer and doing an EXPN or VRFY, or even locally by looking at the aliases file or NIS map." What is the "@filename" directive"? " Another more direct approach is to simply disable EXPN or VRFY altogether. See the documentation for your mailer on how to do this." Could someone be more specific about what needs to be done here? Eric From list-managers-owner Tue Mar 14 12:12:37 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA03648 for list-managers-outgoing; Tue, 14 Mar 1995 11:30:00 -0800 Received: from leibniz.math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA03639 for ; Tue, 14 Mar 1995 11:29:57 -0800 Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.131.77]) by leibniz.math.psu.edu (8.6.10/8.6.9) with ESMTP id OAA18773; Tue, 14 Mar 1995 14:27:45 -0500 Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.6.10/8.6.9) with ESMTP id OAA18273; Tue, 14 Mar 1995 14:27:43 -0500 Message-Id: <199503141927.OAA18273@augusta.math.psu.edu> X-Mailer: exmh version 1.5.3 12/28/94 To: Eric Klien cc: list-managers@greatcircle.com Subject: Re: Security In-reply-to: Your message of "Tue, 14 Mar 1995 12:08:37 MST." <199503141908.MAA06630@pinyon.enet.net> X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 14 Mar 1995 14:27:43 -0500 From: Dave Barr Sender: list-managers-owner@GreatCircle.COM Precedence: bulk In message <199503141908.MAA06630@pinyon.enet.net>, Eric Klien writes: >I have looked there but I am no Perl expert. Could you tell me >exactly what changes I would have to make in resend to solve the >problem. There is no changes to resend. From resend: # If the first argument is "@filename", read the real arguments # from "filename", and shove them onto the ARGV for later processing # by &Getopts() > Would I also have to make any change in the aliases file >in /etc? In your aliases, you'd specify '... wrapper resend @/path/to/filename' and put all the arguements to resend in /path/to/filename --Dave From list-managers-owner Tue Mar 14 12:20:17 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA00299 for list-managers-outgoing; Tue, 14 Mar 1995 11:41:59 -0800 Received: from pinyon.enet.net (pinyon.enet.net [168.158.8.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA00294 for ; Tue, 14 Mar 1995 11:41:57 -0800 Received: (from oceania@localhost) by pinyon.enet.net (8.6.9/8.6.9) id MAA07012; Tue, 14 Mar 1995 12:39:31 -0700 Date: Tue, 14 Mar 1995 12:39:31 -0700 From: Eric Klien Message-Id: <199503141939.MAA07012@pinyon.enet.net> To: barr@math.psu.edu, list-managers@greatcircle.com Subject: Security Sender: list-managers-owner@GreatCircle.COM Precedence: bulk According to Dave Barr: "There is no changes to resend." O.K. "In your aliases, you'd specify '... wrapper resend @/path/to/filename' and put all the arguements to resend in /path/to/filename" O.K. Here is my original aliases file: # Oceania-l Mailing List oceania-l-outgoing: :include:/home/oceandom/lists/oceania-l oceania-l: "|/home/oceandom/bin/wrapper resend -p Bulk -A -a /home/oceandom/lists/oceania-l.passwd -l oceania-l -f owner-oceania-l -h oceania.org -s oceania-l-outgoing" owner-oceania-l: oceania oceania-l-owner: owner-oceania-l oceania-l-request: "|/home/oceandom/bin/wrapper majordomo -l oceania-l" oceania-l-approval: oceania Would I change it to following? # Oceania-l Mailing List oceania-l-plugh: :include:/home/oceandom/lists/oceania-l oceania-l: "|/home/oceandom/bin/wrapper resend -p Bulk -A -a @/home/oceandom/lists/oceania-l.passwd -l oceania-l -f owner-oceania-l -h oceania.org -s oceania-l-plugh" owner-oceania-l: oceania oceania-l-owner: owner-oceania-l oceania-l-request: "|/home/oceandom/bin/wrapper majordomo -l oceania-l" oceania-l-approval: oceania Eric From list-managers-owner Tue Mar 14 12:20:43 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA02335 for list-managers-outgoing; Tue, 14 Mar 1995 11:02:28 -0800 Received: from well.sf.ca.us (well.sf.ca.us [198.93.4.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA02330 for ; Tue, 14 Mar 1995 11:02:26 -0800 Received: (from tpesce@localhost) by well.sf.ca.us (8.6.10/8.6.9) id LAA25020; Tue, 14 Mar 1995 11:00:10 -0800 From: Tim Pesce Message-Id: <199503141900.LAA25020@well.sf.ca.us> Subject: Re: Security Problems To: oceania@enet.net (Eric Klien) Date: Tue, 14 Mar 1995 11:00:07 -0800 (PST) Cc: list-managers@GreatCircle.COM In-Reply-To: <199503141802.LAA05738@pinyon.enet.net> from "Eric Klien" at Mar 14, 95 11:02:14 am Organization: Whole Earth 'Lectronic Link X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 1195 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > I am working on changing the code of majordomo by hand to solve some > major security problems with it. The problems that I have are that > 1) anyone can post to the list by sending e-mail to list-l-outgoing > and 2) anyone can get a copy of the list by sending majordomo telnet > client 25, expn listname-outgoing even if I disable the who command > in majordomo. > > Can anyone give suggestions on solving the above problems? Suggestion for problem #2: If you are using V8 sendmail as your MTA, it can be configured to disallow the SMTP expn operation. This is also useful in many contexts other than mailing lists and Majordomo. Take a look at the p (privacy) option, and especially the "noexpn" argument. Granted, this will need to be done systemwide, and if you aren't the sys. admin. for your site, you'll need to convince someone else of the validity of this solution. I think, however, the arguments in favor of enabling this behavior outweigh the arguments against it. Hope this helps! Tim -- Tim Pesce Whole Earth 'Lectronic Link (415) 332-4335 VOICE System Administrator 1750 Bridgeway Suite A200 (415) 332-4927 FAX tpesce@well.sf.ca.us Sausalito, CA 94965-1900 From list-managers-owner Tue Mar 14 12:26:47 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA02322 for list-managers-outgoing; Tue, 14 Mar 1995 11:01:45 -0800 Received: from leibniz.math.psu.edu (leibniz.math.psu.edu [146.186.130.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA02317 for ; Tue, 14 Mar 1995 11:01:41 -0800 Received: from augusta.math.psu.edu (barr@augusta.math.psu.edu [146.186.131.77]) by leibniz.math.psu.edu (8.6.10/8.6.9) with ESMTP id NAA18356; Tue, 14 Mar 1995 13:59:30 -0500 Received: from localhost (barr@localhost) by augusta.math.psu.edu (8.6.10/8.6.9) with ESMTP id NAA18121; Tue, 14 Mar 1995 13:59:29 -0500 Message-Id: <199503141859.NAA18121@augusta.math.psu.edu> X-Mailer: exmh version 1.5.3 12/28/94 To: Eric Klien cc: list-managers@greatcircle.com Subject: Re: Security Problems continued In-reply-to: Your message of "Tue, 14 Mar 1995 11:51:19 MST." <199503141851.LAA06355@pinyon.enet.net> X-Face: $+9-wYg.[->94HJ{go[7Q]E!K&hUg7ZhLyCMyq_FU*ca0GazE>^/2BKLcK0bP-'%;Nn?M+am,jlSP>1K$iz@ %'v'FEW{@](U&Ed/}>ju3Ctlr!XwJ27Q)7h2a%"`sz;j:/3EC[mXi@*X@HE1]'ddq$ZX"ePsMyTkeg >zdML.SVvX1W`adGIUD Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 14 Mar 1995 13:59:28 -0500 From: Dave Barr Sender: list-managers-owner@GreatCircle.COM Precedence: bulk In message <199503141851.LAA06355@pinyon.enet.net>, Eric Klien writes: >" You can use the "@filename" directive in resend to move the > >What is the "@filename" directive"? It's a directive which was used a lot by Brent but sort of fell into undocumentation. Look in the beginning of the 'resend' script for the explanation. >" Another more direct approach is to simply disable EXPN or VRFY > altogether. See the documentation for your mailer on how to do this." > >Could someone be more specific about what needs to be done here? No, not without knowing what mailer you use. With sendmail, it's just options to the configuration file (it's something like privacyflags). Look at the sendmail docs. --Dave From list-managers-owner Tue Mar 14 12:31:59 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA00221 for list-managers-outgoing; Tue, 14 Mar 1995 11:35:02 -0800 Received: from pinyon.enet.net (pinyon.enet.net [168.158.8.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA00216 for ; Tue, 14 Mar 1995 11:34:59 -0800 Received: (from oceania@localhost) by pinyon.enet.net (8.6.9/8.6.9) id MAA06953; Tue, 14 Mar 1995 12:33:05 -0700 Date: Tue, 14 Mar 1995 12:33:05 -0700 From: Eric Klien Message-Id: <199503141933.MAA06953@pinyon.enet.net> To: list-managers@greatcircle.com, paul%av2.vrx.vhi.com@vhipub.vhi.com Subject: Security Sender: list-managers-owner@GreatCircle.COM Precedence: bulk [Relevant message attached at end of this file.] O.K. Here is my original aliases file: # Oceania-l Mailing List oceania-l-outgoing: :include:/home/oceandom/lists/oceania-l oceania-l: "|/home/oceandom/bin/wrapper resend -p Bulk -A -a /home/oceandom/lists/oceania-l.passwd -l oceania-l -f owner-oceania-l -h oceania.org -s oceania-l-outgoing" owner-oceania-l: oceania oceania-l-owner: owner-oceania-l oceania-l-request: "|/home/oceandom/bin/wrapper majordomo -l oceania-l" oceania-l-approval: oceania Would I change it to following? # Oceania-l Mailing List oceania-l-plugh: :include:/home/oceandom/lists/oceania-l oceania-l: "|/home/oceandom/bin/wrapper resend -p Bulk -A -a /home/oceandom/lists/oceania-l.passwd -l oceania-l -f owner-oceania-l -h oceania.org -s oceania-l-outgoing" owner-oceania-l: oceania oceania-l-owner: owner-oceania-l oceania-l-request: "|/home/oceandom/bin/wrapper majordomo -l oceania-l" oceania-l-approval: oceania And how would I change resend? Eric Relevant message: "A suggestion would be to have an entry in the configuration file that specifies the suffix to append to the list name. For example, if the outgoing expansion list is aliased as -plugh, then the config file would have "plugh" as the outgoing suffix. Then resend will take the list name, append the dash and the suffix, and finally send it to that alias. Thus, 1) allowing removal of the destination alias in the list alias of the resend line, and 2) thereby creating a more secure method with minimal recoding. Here's a sample: config file contains suffix of "plugh" /etc/aliases: ctp-list: "| /usr/local/majordomo-1.93/wrapper resend -l ctp-list -h av2.vrx.vhi.com -f ctp-list-owner" ctp-list-approval: ctp-list-owner ctp-list-plugh: :include:/usr/local/majordomo-1.93/mail/lists/ctp-list ctp-list-owner: ctp ctp-list-request: majordomo owner-ctp-list: ctp-list-owner owner-ctp-list-outgoing: sample-owner" From list-managers-owner Tue Mar 14 13:45:20 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA02376 for list-managers-outgoing; Tue, 14 Mar 1995 13:13:21 -0800 Received: from pinyon.enet.net (pinyon.enet.net [168.158.8.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id NAA02371 for ; Tue, 14 Mar 1995 13:13:17 -0800 Received: (from oceania@localhost) by pinyon.enet.net (8.6.9/8.6.9) id OAA07810 for list-managers@greatcircle.com; Tue, 14 Mar 1995 14:11:22 -0700 Date: Tue, 14 Mar 1995 14:11:22 -0700 From: Eric Klien Message-Id: <199503142111.OAA07810@pinyon.enet.net> To: list-managers@greatcircle.com Subject: outgoing Sender: list-managers-owner@GreatCircle.COM Precedence: bulk While I attempt to figure out how to fix the security on my site, where can I find the file -outgoing so I can delete it and stop postings to my list? My list is under attack... Eric From list-managers-owner Tue Mar 14 15:03:23 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA02966 for list-managers-outgoing; Tue, 14 Mar 1995 13:39:50 -0800 Received: from pinyon.enet.net (pinyon.enet.net [168.158.8.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id NAA02961 for ; Tue, 14 Mar 1995 13:39:47 -0800 Received: (from oceania@localhost) by pinyon.enet.net (8.6.9/8.6.9) id OAA08050; Tue, 14 Mar 1995 14:37:46 -0700 Date: Tue, 14 Mar 1995 14:37:46 -0700 From: Eric Klien Message-Id: <199503142137.OAA08050@pinyon.enet.net> To: list-managers@greatcircle.com, mcb@postmodern.com Subject: Correct list Sender: list-managers-owner@GreatCircle.COM Precedence: bulk "Reminder -- the list-managers list is for discussion of general list-management policy and technical issues, not specific configuration/code level questions about particular packagers." Just for the record, I started off the threads by posting in both list-managers and in majordomo-workers. *ALL* my responses came out of list-managers. I'll redirect the remaining part of the threads directly to the authors since there is no traffic on majordomo-workers. I have almost solved my problem... Eric From list-managers-owner Tue Mar 14 15:03:57 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA02775 for list-managers-outgoing; Tue, 14 Mar 1995 13:29:25 -0800 Received: from taz.hyperreal.com (taz.hyperreal.com [204.62.130.120]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id NAA02770 for ; Tue, 14 Mar 1995 13:29:20 -0800 Received: by taz.hyperreal.com (8.6.10/8.6.5) id NAA29354; Tue, 14 Mar 1995 13:26:50 -0800 Date: Tue, 14 Mar 1995 13:26:49 -0800 (PST) From: Brian Behlendorf To: Eric Klien cc: list-managers@GreatCircle.COM Subject: Re: Security Problems In-Reply-To: <199503141802.LAA05738@pinyon.enet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On Tue, 14 Mar 1995, Eric Klien wrote: > I am working on changing the code of majordomo by hand to solve some > major security problems with it. The problems that I have are that > 1) anyone can post to the list by sending e-mail to list-l-outgoing > and 2) anyone can get a copy of the list by sending majordomo telnet > client 25, expn listname-outgoing even if I disable the who command > in majordomo. > > Can anyone give suggestions on solving the above problems? Yes, rename the outgoing alias to something other than list-outgoing. Brian From list-managers-owner Tue Mar 14 15:05:00 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA02646 for list-managers-outgoing; Tue, 14 Mar 1995 13:22:00 -0800 Received: from taz.hyperreal.com (taz.hyperreal.com [204.62.130.120]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id NAA02641 for ; Tue, 14 Mar 1995 13:21:57 -0800 Received: by taz.hyperreal.com (8.6.10/8.6.5) id NAA28844; Tue, 14 Mar 1995 13:19:20 -0800 Date: Tue, 14 Mar 1995 13:19:20 -0800 (PST) From: Brian Behlendorf To: Sean Shapira cc: Alan Deikman , sshea@world.std.com, list-managers@GreatCircle.COM Subject: Re: Proposed Trouble Data Base 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, 14 Mar 1995, Sean Shapira wrote: > FWIW, I believe the best approach to shaping list traffic is > "out-of-band self-moderation". I would be happy to expand on > this idea if there's interest.... Collaborative filtering is definitely the way to go in the future, but to do it right either requires modifying mail user agents (so that individual Seals of Approval can be combined and attached to the messages they reference transparently), or having people read mailing list mail through a web interface (more doable now, but web browsers are really poor when it comes to navigating threaded streams of data, like mailing lists). As you can see, I've thought a lot about this :) Brian From list-managers-owner Tue Mar 14 15:07:19 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id NAA02579 for list-managers-outgoing; Tue, 14 Mar 1995 13:19:37 -0800 Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id NAA02574 for ; Tue, 14 Mar 1995 13:19:34 -0800 Received: from postmodern.com by relay1.UU.NET with SMTP id QQyhbo29345; Tue, 14 Mar 1995 16:09:50 -0500 Received: by postmodern.com (5.0/SMI-SVR4/GCA-Makitso-941228-mcb1) id AA04077; Tue, 14 Mar 95 13:00:06 PST Message-Id: <9503142100.AA04077@postmodern.com> From: mcb@postmodern.com (Michael C. Berch) Date: Tue, 14 Mar 1995 13:00:05 -0800 In-Reply-To: <199503141900.LAA25020@well.sf.ca.us> X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: list-managers@greatcircle.com Subject: Re: Security Problems Cc: tpesce@well.sf.ca.us, oceania@enet.net, barr@math.psu.edu content-length: 853 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Reminder -- the list-managers list is for discussion of general list-management policy and technical issues, not specific configuration/code level questions about particular packagers. Please use the Majordomo-specific mailing lists for discussion of particular majordomo configuration issues, problems, code, etc. These lists are hosted at greatcircle.com and are majordomo-users for people who use Majordomo and have questions, need support, etc., and majordomo-workers for Majordomo developers and discussion of development issues. There is also a majordomo-announce list, and a majordomo-docs list for documentation workders. To subscribe, send the message subscribe to majordomo@greatcircle.com, where is the name of the list. -- Michael C. Berch List-Managers list manager mcb@greatcircle.com / mcb@postmodern.com From list-managers-owner Tue Mar 14 19:32:04 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA07731 for list-managers-outgoing; Tue, 14 Mar 1995 19:13:38 -0800 Received: from bbfm.di.com (bbfm.di.com [204.74.64.1]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id TAA07724 for ; Tue, 14 Mar 1995 19:13:35 -0800 Received: from tune.di.com by bbfm.di.com (8.6.9/TD-1.12) with SMTP id TAA11884 for on Tue, 14 Mar 1995 19:12:25 -0800 Message-Id: <199503150312.TAA11884@bbfm.di.com> X-Sender: today@di.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 14 Mar 1995 19:12:36 -0800 To: List-Managers@GreatCircle.COM From: today@di.com (Todd Day) Subject: Re: duplicated posts -- what causes them? Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >I've been on lists that went through duplication periods, where every post >came through twice, and now it's happening on one of my lists (all lists in >question are majordomo run). I went through the same problem. Turned out that my Linux system had a bad implementation of flock, and sendmail was relying on it. Since it would take longer than 15 minutes to empty the mail queue once a digest went out, sendmail would come along and try to deliver the mail again since the file wasn't properly locked. I recompiled sendmail with patches so it wouldn't rely on the broken Linux stuff, and that was the end of my double digest problem. Has your mailer system gone through any upgrades? Has your system software been upgraded lately? Either one of these might point to the same sort of bug, even if your platform isn't Linux. -todd- From list-managers-owner Wed Mar 15 02:32:07 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id CAA17608 for list-managers-outgoing; Wed, 15 Mar 1995 02:12:43 -0800 Received: from tango.rahul.net (tango.rahul.net [192.160.13.5]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id CAA17603 for ; Wed, 15 Mar 1995 02:12:37 -0800 Received: from bolero.rahul.net by tango.rahul.net with SMTP id AA19135 (5.67b8/IDA-1.5 for ); Wed, 15 Mar 1995 02:10:15 -0800 Received: by bolero.rahul.net id AA16137 (5.67b8/IDA-1.5 for list-managers@greatcircle.com); Wed, 15 Mar 1995 02:10:15 -0800 Message-Id: <199503151010.AA16137@bolero.rahul.net> To: list-managers@greatcircle.com Subject: Re: Correct list In-Reply-To: <199503142137.OAA08050@pinyon.enet.net> Date: Wed, 15 Mar 95 02:10:14 -0800 From: Michelle Dick Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Eric wrote: > Just for the record, I started off the threads by posting in > both list-managers and in majordomo-workers. *ALL* my responses > came out of list-managers. Irrelevant. My low fat vegetarian list does not permit posting of high-fat or non-vegetarian recipes. As I tell folks who plead with me for an exception because they posted a comment about having a good high-fat/non-veg recipe which garnered them several hundred private email requests for the recipe: tough. -- Michelle Dick artemis@rahul.net East Palo Alto, CA Owner, FATFREE Vegetarian Mailing List "A dead-end street is just a place to turn around." From list-managers-owner Wed Mar 15 12:13:55 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA28296 for list-managers-outgoing; Wed, 15 Mar 1995 11:40:01 -0800 Received: from SYSWRK.UCIS.Dal.Ca (syswrk.UCIS.Dal.Ca [129.173.2.108]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id LAA28284; Wed, 15 Mar 1995 11:39:43 -0800 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.3-13 #6307) id <01HO64N9Q9G0000KSG@SYSWRK.UCIS.DAL.CA>; Wed, 15 Mar 1995 15:33:45 -0400 Received: from biome.bio.dfo.ca by AC.DAL.CA (PMDF V4.3-13 #2545) id <01HO64MQAF3K00CYTS@AC.DAL.CA>; Wed, 15 Mar 1995 15:33:21 -0400 Received: by biome.bio.dfo.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:Majordomo-Users@GreatCircle.COM id AA17802; Wed, 15 Mar 95 15:27:06 -0400 Date: Wed, 15 Mar 1995 15:27:05 -0400 (AST) From: bill@biome.bio.dfo.ca (Bill Silvert) Subject: Re: General ettiquette guidelines In-reply-to: <199503151852.KAA00071@potrzebie.ee.pdx.edu> from "God in Training - Mike Butry" at Mar 15, 95 10:52:45 am To: surviver@ee.pdx.edu (God in Training - Mike Butry) Cc: List-Managers@GreatCircle.COM (List Managers), Majordomo-Users@GreatCircle.COM (Majordomo Users) Message-id: <9503151927.AA17802@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 Content-length: 1910 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk This was posted to the Majordomo-Users list, I'm copying it to the List-Managers list because (for a change) it is a general List issue. Although there is a need for general etiquette guidelines, this matter of putting other peoples' names on a list is a serious issue that stands out from the rest. I have had no end of problems from someone copying names from one list to another, and I often end up on lists that I don't want to be on. I feel very strongly that no one should be added to a mailing list by someone else, except when the person who does so has their permission and assumes full responsibility for maintenance of the list. This latter generally only applies to special-purpose lists like those used for committee mailings, where the secretary might add and delete names. Bill >Has anyone come up with some general guidelines on ettiquette that can be given >to new/novice list owners? I have one list owner that pre-loaded his list with >over 100 addresses, and now I, as majordomo-owner, am caught in the middle of >irrate subscribee's who were never asked to be on this list and the list owner. > >I don't want this to happen again, and would like to prevent other such social >fax paux (phopaws) from happening. So, if anyone has come up with such >guidelines, I would greatly appreciate a copy. If not, send me suggestions and >I'll compile a set of guidelines. My e-mail is surviver@ee..pdx.edu > >/////////////////////// O'boy - Dr. Sam Beckett //////////////////////////// >Mike Butry - System Administrator >Computer Action Team >CLAW - emeritus >surviver@ee.pdx.edu >\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ -- Bill Silvert, Habitat Ecology Div., Bedford Inst. Oceanography P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2 Personal InterNet Address: silvert@biome.bio.ns.ca HED runs a WWW server at URL=http://biome.bio.dfo.ca From list-managers-owner Wed Mar 15 14:39:17 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA01709 for list-managers-outgoing; Wed, 15 Mar 1995 14:21:24 -0800 Received: from and.com (and.com [199.182.35.35]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id OAA01704; Wed, 15 Mar 1995 14:21:20 -0800 Received: (from hahn@localhost) by and.com (8.6.8/8.6.6) id OAA28519; Wed, 15 Mar 1995 14:20:02 -0800 Date: Wed, 15 Mar 1995 14:20:02 -0800 From: Jonathan Hahn Message-Id: <199503152220.OAA28519@and.com> To: List-Managers@GreatCircle.COM, Majordomo-Users@GreatCircle.COM Subject: Re: General ettiquette guidelines Cc: staff@and.com Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I manage many lists in which users add themselves via a form on a web page. Anyone can add anyone else to a list, and I knew that some poeple would add others with out asking permission first. I handled this by modifying the mailing that goes out to new subscribers to say that if the person was added to the list without their knowledge, they should contact me. In the few instances in which this has happened, I have been able to give adequate information about the list addition so the "victim" could figure out who put them on. We keep copious records of all activity and never throw anything away. -jonathan hahn --- hahn@and.com http://and.com/hahn/ > From majordomo-users-owner@GreatCircle.COM Wed Mar 15 12:53:58 1995 > Date: Wed, 15 Mar 1995 15:27:05 -0400 (AST) > From: bill@biome.bio.dfo.ca (Bill Silvert) > Subject: Re: General ettiquette guidelines > In-reply-to: <199503151852.KAA00071@potrzebie.ee.pdx.edu> from > "God in Training - Mike Butry" at Mar 15, 95 10:52:45 am > To: surviver@ee.pdx.edu (God in Training - Mike Butry) > Cc: List-Managers@GreatCircle.COM (List Managers), > Majordomo-Users@GreatCircle.COM (Majordomo Users) > > This was posted to the Majordomo-Users list, I'm copying it to the > List-Managers list because (for a change) it is a general List issue. > > Although there is a need for general etiquette guidelines, this matter > of putting other peoples' names on a list is a serious issue that > stands out from the rest. I have had no end of problems from someone > copying names from one list to another, and I often end up on lists > that I don't want to be on. > > I feel very strongly that no one should be added to a mailing list by > someone else, except when the person who does so has their permission > and assumes full responsibility for maintenance of the list. This > latter generally only applies to special-purpose lists like those used > for committee mailings, where the secretary might add and delete names. > > Bill > > >Has anyone come up with some general guidelines on ettiquette that can be given > >to new/novice list owners? I have one list owner that pre-loaded his list with > >over 100 addresses, and now I, as majordomo-owner, am caught in the middle of > >irrate subscribee's who were never asked to be on this list and the list owner. > > > >I don't want this to happen again, and would like to prevent other such social > >fax paux (phopaws) from happening. So, if anyone has come up with such > >guidelines, I would greatly appreciate a copy. If not, send me suggestions and > >I'll compile a set of guidelines. My e-mail is surviver@ee..pdx.edu > > > >/////////////////////// O'boy - Dr. Sam Beckett //////////////////////////// > >Mike Butry - System Administrator > >Computer Action Team > >CLAW - emeritus > >surviver@ee.pdx.edu > >\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ > > -- > Bill Silvert, Habitat Ecology Div., Bedford Inst. Oceanography > P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2 > Personal InterNet Address: silvert@biome.bio.ns.ca > HED runs a WWW server at URL=http://biome.bio.dfo.ca From list-managers-owner Wed Mar 15 16:02:24 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id PAA03806 for list-managers-outgoing; Wed, 15 Mar 1995 15:51:57 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id PAA03801 for ; Wed, 15 Mar 1995 15:51:55 -0800 Received: from [204.156.141.133] (agoodloe.vip.best.com [204.156.141.133]) by shell1.best.com (8.6.10/8.6.5) with SMTP id PAA24158 for ; Wed, 15 Mar 1995 15:49:14 -0800 Date: Wed, 15 Mar 1995 15:49:14 -0800 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: list-managers@GreatCircle.COM From: agoodloe@best.com (Amy Goodloe) Subject: Digest posts showing approved header Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Ok, I run two list that come in regular and digest versions. List 1 is moderated, and requires that every post be "approved." Adding an approved header at the beginning of every message works just fine for the regular list, but the digest version ends up SHOWING the approved header in the message (thereby giving away my list password). Both the regular and digest config files are set to moderate= yes. List 2 is not moderated, but occasionally I have to "approve" an admin request. It then goes to the regular list fine, but appears in the digest WITH the approved header in it. Also, this list (reg and digest) is set to administrivia-= no, but admin requests STILL bounce. Help!!! --amy agoodloe@best.com From list-managers-owner Wed Mar 15 19:32:23 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA07178 for list-managers-outgoing; Wed, 15 Mar 1995 19:08:35 -0800 Received: from suntan.Tandem.com (suntan.tandem.com [192.216.221.8]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id JAA04565 for ; Mon, 13 Mar 1995 09:54:58 -0800 Received: from adm.loc3.tandem.com by suntan.Tandem.com (4.1/suntan5.940222) for list-managers@greatcircle.com id AA21443; Mon, 13 Mar 95 09:52:11 PST Received: from zorch.loc3.tandem.com by adm.loc3.tandem.com (4.1/6main.940209) id AA07820; Mon, 13 Mar 95 09:51:09 PST Received: by zorch.loc3.tandem.com (4.1/6leaf.940209) id AA19350; Mon, 13 Mar 95 09:52:10 PST Date: Mon, 13 Mar 95 09:52:10 PST From: scott@loc3.tandem.com (mueller_scott) Message-Id: <9503131752.AA19350@zorch.loc3.tandem.com> To: list-managers@greatcircle.com Subject: Re: Abuse problem is not treatable by Software X-Envelope-To: moore@cs.utk.edu Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >Actually, I've found it quite effective to filter messages. I think it would be a neat extension to list management software to allow extensible filtering. Existing filter in (for example) Majordomo catch "(un)subscribe", but it's absolutely amazing to me how many people cannot spell "subscribe" correctly. It would be useful to adapt the filtering without changing the code, and that sort of filter could be used as a "profanity" filter for those who care, without affecting those who don't. -- Scott Hazen Mueller, Tandem Computers +1 408 285 5762 scott@tandem.com Unix System/Network Administrator, Host-, Post-, News- and Web-Master From list-managers-owner Thu Mar 16 02:32:08 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id CAA14453 for list-managers-outgoing; Thu, 16 Mar 1995 02:23:49 -0800 Received: from flatboat.pop.net (slip-81.io.com [199.170.88.207]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id CAA14448 for ; Thu, 16 Mar 1995 02:23:41 -0800 Received: (from zeek@localhost) by flatboat.pop.net (8.6.9/8.6.9) id EAA01594; Thu, 16 Mar 1995 04:14:06 -0600 Message-Id: <199503161014.EAA01594@flatboat.pop.net> Subject: READMENOW To: POSTMASTER@compuserve.com, info@compuserve.com, root@compuserve.com, operator@compuserve.com, admin@compuserve.com Date: Thu, 16 Mar 1995 04:14:06 -0600 (CST) In-Reply-To: <950316095159_515664.456256_CHU29-18@CompuServe.COM> from "Electronic Postmaster" at Mar 16, 95 04:51:59 am From: zeek@sunshine.io.com Reply-To: zeek@sunshine.io.com X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2763 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk America Online, Please find and direct these forwards to /dev/null, I've no time to find them for you. This is my second request. The next will propogate throughout USENET. Thank you, -zeek > Re: ? EMDNRM - Mail Delivery Failure. No room in mailbox. 72241,1735 > RE: stand corrected re "MBV" flick > > Your message could not be delivered as addressed. > > --- Returned message --- > > Sender: mbv-owner@sunshine.io.com > Received: from is.NYU.EDU by arl-img-1.compuserve.com (8.6.10/5.941228sam) > id EAA26868; Thu, 16 Mar 1995 04:48:24 -0500 > Received: from sunshine.io.com by is.NYU.EDU (5.61/1.34) > id AA20819; Thu, 16 Mar 95 04:48:54 -0500 > Received: from batch1.csd.uwm.edu (root@batch1.csd.uwm.edu [129.89.70.230]) by sunshine.io.com (8.6.9/8.6.9) with ESMTP id DAA22732 for ; Thu, 16 Mar 1995 03:31:29 -0600 > Received: from alpha1.csd.uwm.edu (jenor@alpha1.csd.uwm.edu [129.89.169.1]) by batch1.csd.uwm.edu (8.6.10/8.6.8) with ESMTP id DAA21872 for ; Thu, 16 Mar 1995 03:47:05 -0600 > Received: (jenor@localhost) by alpha1.csd.uwm.edu (8.6.10/8.6.8) id DAA16774; Thu, 16 Mar 1995 03:47:05 -0600 > Date: Thu, 16 Mar 1995 03:47:05 -0600 (CST) > From: "Jeffrey with 2 f's Jeffrey" > To: "MBV@SUNSHINE.IO.COM" > Subject: RE: stand corrected re "MBV" flick > In-Reply-To: > Message-Id: > Mime-Version: 1.0 > Content-Type: TEXT/PLAIN; charset=US-ASCII > > On Wed, 15 Mar 1995, Andrew H. Otwell typed not wrote: > > > > > I think we may be getting into grindcore/thrash band names here, but how > > about those "FACES OF DEATH" movies? C'mon, John if you watched "Blood > > Sucking Freaks" you must have been tempted ti rent something from the "FOD" > > series. :-) > > Y'know, a fiend of mine (I meant "friend" honest) has seen those FOD > things--no thank you please--but now things are getting rather > ridiculous. There's a *children's* version of the _Faces of Death_ videos > now: it's called _Faces of Owies_ (ba dum shing!) > > --Jeff > > Jeffrey Norman "I've been praying a lot lately-- > University of Wisconsin-Milwaukee it's because I no longer have a TV." > Dept. of English & Comp. Lit. > e-mail: jenor@csd.uwm.edu --Mark Eitzel (American Music Club) > Kind regards, -zeek --- - -- -- --- -- - - -- - - -- - --- ---- ---- --- - - - - ---- --- --- S u n s h i n e N e t w o r k i n g S e r v i c e s 1 9 9 5 http://sunshine.io.com voice 512.479.0081 email sunshine@sunshine.io.com -- --- - - - - - - ---- - - --- - -- -- - - - ---- -- --- -- - - --- -- From list-managers-owner Thu Mar 16 11:02:04 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA21741 for list-managers-outgoing; Thu, 16 Mar 1995 10:59:00 -0800 Received: from flatboat.pop.net (slip-68.io.com [199.170.88.194]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id KAA21736 for ; Thu, 16 Mar 1995 10:58:55 -0800 Received: (from zeek@localhost) by flatboat.pop.net (8.6.9/8.6.9) id MAA00127 for list-managers@greatcircle.com; Thu, 16 Mar 1995 12:49:19 -0600 Message-Id: <199503161849.MAA00127@flatboat.pop.net> Subject: "America Online" typo To: list-managers@greatcircle.com Date: Thu, 16 Mar 1995 12:49:17 -0600 (CST) From: zeek@sunshine.io.com Reply-To: zeek@sunshine.io.com X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1136 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I Cc:ed a message to this list earlier this morning addressing an issue of bounced mail from compuserve, "America Online" was a typo. The message addressed the compuserve staff rather than the list-managers group. My apologies for the confusion, I Cc:ed for a witness. My gripe here is that compuserve (and perhaps others) is making no effort in controlling bounced mail from their origin. It is my understanding they offer free trial accounts in which people subscribe, place a .forward to @compuserve.com, and eventually abandon the account. The result is a few dozen bounced messages in my mail queue each day that I don't have time to trace. I feel it is not my responsibility to clean up this mess, but rather compuserve's to control their accounting more closely with these "free trials." Kind regards, -zeek --- - -- -- --- -- - - -- - - -- - --- ---- ---- --- - - - - ---- --- --- S u n s h i n e N e t w o r k i n g S e r v i c e s 1 9 9 5 http://sunshine.io.com voice 512.479.0081 email sunshine@sunshine.io.com -- --- - - - - - - ---- - - --- - -- -- - - - ---- -- --- -- - - --- -- From list-managers-owner Thu Mar 16 15:02:28 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id OAA24415 for list-managers-outgoing; Thu, 16 Mar 1995 14:47:21 -0800 Received: from netcom12.netcom.com (netcom12.netcom.com [192.100.81.124]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id OAA24410 for ; Thu, 16 Mar 1995 14:47:18 -0800 Received: by netcom12.netcom.com (8.6.10/Netcom) id OAA01172; Thu, 16 Mar 1995 14:41:04 -0800 Date: Thu, 16 Mar 1995 14:41:03 -0800 (PST) From: James Cook Subject: Re: List abusers database To: Fred H Olson WB0YQM cc: List-Managers@GreatCircle.COM In-Reply-To: <37487.fholson@maroon.tc.umn.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I'm not an attorney, but do believe that libel is often shown to exist based on the reasonable inference another person might take from some disclosure of information about a person, whether or not named. If it is reasonably possible to identify a person from some information communicated/ made public, and if a reasonable person might infer such effect from the manner of disclsoure as to subject to person to some form of ridicule or other "trouble", then a case for libel may lay. So, in this respect, it's possible that simply putting someone's name in a database publicly known as a reserve of data about "abusers" could be sufficient contextual info. to "libel" the guy..... or at least enable an attorney to argue that. James Cook On Tue, 14 Mar 1995, Fred H Olson WB0YQM wrote: > I would participate in such a database tho I have not had much problem. > I do wonder if it's worth the effort. > > I would propose that the format be name, email address and url of > sample objectionable posts from the abuser. It's hard to charge libel > if you dont comment. One could even have a discalimer such as: > "No implications is intended by names simply being mentioned in this > archive; please use the author's words to draw any conclusions." > > Try to stick to the facts. Let the abuser speak for themselves. > The effort to maintain it would be minimal if the database were a > non linked searchable WWW archive of email messages (obscure URL shared > among participating list managers only). > > The lack of good information to enforce accountability and appropriate > 'peer pressure' lets a lot of anti social behavior thrive. It's sort of > like people will write graffitti on bathroom walls that they wouldn't say > in public. > > Fred > > -- > Fred H. Olson fholson@uci.com (612)588-9532 Amateur radio: WB0YQM > 1221 Russell Av N, Minneapolis,MN 55411 Sysop of COHOUSING-L listserv; > COHOUSING URL's: mailto://listserv@uci.com (w/ msg: Info Cohousing-L) > gopher://gopher.uci.com/ TC FREENET PUBLIC TEST PHASE: May 1, 1995 > URL's: mailto://info@freenet.msp.mn.us http://freenet.msp.mn.us:8000/ > -- ______________________________________________________________________________ James Cook * Information Professionals List Internet: jcook@netcom.com * IPN / Information Professionals Network ============================================================================== From list-managers-owner Thu Mar 16 19:32:26 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA29544 for list-managers-outgoing; Thu, 16 Mar 1995 19:26:40 -0800 Received: from liverbird.liverpool.ac.uk (livbird.liv.ac.uk [138.253.31.12]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id TAA29539 for ; Thu, 16 Mar 1995 19:26:37 -0800 Received: from liverbird.liverpool.ac.uk by liverbird.liverpool.ac.uk via Local channel id <21032-0@liverbird.liverpool.ac.uk>; Fri, 17 Mar 1995 03:23:22 +0000 Subject: Re: Security Problems To: brian@hyperreal.com (Brian Behlendorf) Date: Fri, 17 Mar 1995 03:23:18 +0000 (GMT) Cc: oceania@enet.net, list-managers@GreatCircle.COM In-Reply-To: from "Brian Behlendorf" at Mar 14, 95 01:26:49 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1007 From: Alan Thew Message-ID: <"liverbird.li:210340:950317032324"@liverbird.liverpool.ac.uk> Sender: list-managers-owner@GreatCircle.COM Precedence: bulk In the last mail, Brian Behlendorf wrote: > > On Tue, 14 Mar 1995, Eric Klien wrote: > > I am working on changing the code of majordomo by hand to solve some > > major security problems with it. The problems that I have are that > > 1) anyone can post to the list by sending e-mail to list-l-outgoing > > and 2) anyone can get a copy of the list by sending majordomo telnet > > client 25, expn listname-outgoing even if I disable the who command > > in majordomo. > > > > Can anyone give suggestions on solving the above problems? > > Yes, rename the outgoing alias to something other than list-outgoing. > surely it's better to write the SMTP envelope with an address which if mailed either goes to /dev/null or better to a person/robot. That's how we run listproc (not how it was written though). This just seems like a general point. -- Alan Thew alan.thew@liv.ac.uk ...!uknet!liv!alan.thew Tel: +44 151 794-4497 University of Liverpool, Computing Services Fax: +44 151 794-4442 From list-managers-owner Fri Mar 17 09:39:12 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id JAA12938 for list-managers-outgoing; Fri, 17 Mar 1995 09:14:27 -0800 Received: from netcomsv.netcom.com (uumail1.netcom.com [163.179.3.50]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id JAA12928 for ; Fri, 17 Mar 1995 09:14:24 -0800 Received: from znyx.com by netcomsv.netcom.com with SMTP (8.6.9/SMI-4.1) id JAA10137; Fri, 17 Mar 1995 09:10:49 -0800 Received: from alan.znyx.com by znyx.com (5.65/1.35) id AA01289; Fri, 17 Mar 95 09:18:32 -0800 Date: Fri, 17 Mar 95 09:18:32 -0800 Message-Id: <9503171718.AA01289@znyx.com> X-Sender: alan@znyx.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: James Cook From: alan@znyx.com (Alan Deikman) Subject: Re: List abusers database Cc: List-Managers@GreatCircle.COM Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >I'm not an attorney, but do believe that libel is often shown to exist >based on the reasonable inference another person might take from some >disclosure of information about a person, whether or not named. If it is >reasonably possible to identify a person from some information >communicated/ made public, and if a reasonable person might infer such >effect from the manner of disclsoure as to subject to person to some form >of ridicule or other "trouble", then a case for libel may lay. So, in >this respect, it's possible that simply putting someone's name in a >database publicly known as a reserve of data about "abusers" could be >sufficient contextual info. to "libel" the guy..... or at least enable an >attorney to argue that. > >James Cook Issues of slander are defensible when supported by objective factual information, particularly if it is verifiable. If a data base documents that A) the plantiff said this, and B) other parties objected to that, and C) the list manager had taken the action to take that person off their private list (kick them out of the house, so to speak), and that information is accurate, and there were witnesses to all those facts, and there were no further annotations in the data base, then I don't see where an issue of slanderous libel would apply. IF someone was added to the data base without all those facts being in place, then definitely there would be grounds for damages. Of course, they could still sue, and someone would have to pay for the defense of that suit. Looking at this aspect really spports the "loser pays" legislation that is going through Congress right now. If I maintained the data base, it would be a *private* data base, no more subject to public scrutiny than a diary shared among friends. Accessers would also be contributors. Imagine, for example, a political group such as the KKK or Trial Lawyers Association keeping a list of politicians they don't like. Are they libel because they add a name to it that didn't deserve to be there? Given the feedback on the data base, however, and the workload that I now face, it seems a moot point, since I will not have the band width to devote to it. It was just an idea that didn't pan out, unless someone else wants to pick up the torch. Regards, -------------------------------- Alan Deikman, ZNYX Corporation alan@znyx.com From list-managers-owner Fri Mar 17 17:37:20 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id RAA07614 for list-managers-outgoing; Fri, 17 Mar 1995 17:34:16 -0800 Received: from netcom13.netcom.com (netcom13.netcom.com [192.100.81.125]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id RAA07608 for ; Fri, 17 Mar 1995 17:34:13 -0800 Received: by netcom13.netcom.com (8.6.10/Netcom) id RAA17198; Fri, 17 Mar 1995 17:30:27 -0800 Date: Fri, 17 Mar 1995 17:30:26 -0800 (PST) From: James Cook Subject: Re: List abusers database To: Alan Deikman cc: List-Managers@GreatCircle.COM In-Reply-To: <9503171718.AA01289@znyx.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk On Fri, 17 Mar 1995, Alan Deikman wrote: > Issues of slander are defensible when supported by objective factual > information, particularly if it is verifiable. If a data base documents > that A) the plantiff said this, and B) other parties objected to that, > and C) the list manager had taken the action to take that person off > their private list (kick them out of the house, so to speak), and that > information is accurate, and there were witnesses to all those facts, > and there were no further annotations in the data base, then I don't see > where an issue of slanderous libel would apply. Generally true... but the law of slander generally varies from state to state, territory to territory. So you'd need to know the rules where relevant. Also, the truth of a matter is not the sole issue to be shown to defend all libel or slander suits. There are other issues that can arise to defend. But I think it's enough for me to have offered what I have on this topic, which is probably wandering off "charter for the list." James Cook From list-managers-owner Sat Mar 18 20:07:21 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA23927 for list-managers-outgoing; Sat, 18 Mar 1995 19:43:09 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id TAA23922 for ; Sat, 18 Mar 1995 19:43:06 -0800 Received: (frugal@localhost) by shell1.best.com (8.6.11/8.6.5) id TAA02238; Sat, 18 Mar 1995 19:40:23 -0800 Date: Sat, 18 Mar 1995 19:40:23 -0800 (PST) From: Linda Henneman To: list-managers@GreatCircle.COM Subject: How to Manage List When Away, Etc. In-Reply-To: <9503032013.AA12196@ig1.att.att.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I'll hopefully be launching my very first majordomo mailing list (fully-moderated) next week and was just wondering what you other list managers do when you go out of town? Do you all have laptops and those little modems the size of a playing card and just log in while vacationing or on business trips, etc.? And how about, God forbid, if you become ill and perhaps even need hospitalization, surgery, or are otherwise incapacitated? Do you have a backup person who you trust your user id and password with to carry on in your stead? What kind of contingency plans do you have in place? Managing a list strikes me as similar to operating a one-person business in that you have to be available much of the time. However, w/a one-person business you can tell customers you won't be available or even let an answering machine do that. Do you ever announce to your list not to post anything to it or make any requests, especially if it's a fully-moderated one, if you know you might not be physically able to deal w/them for awhile? TIA for any pearls of wisdom you can toss my way. Linda Linda Henneman manager, frugal-l frugal@best.com From list-managers-owner Sun Mar 19 06:07:10 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id FAA00937 for list-managers-outgoing; Sun, 19 Mar 1995 05:41:13 -0800 Received: from oodis01.hill.af.mil (oodis01.hill.af.mil [192.12.100.3]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id FAA00932 for ; Sun, 19 Mar 1995 05:41:09 -0800 Received: by oodis01.hill.af.mil id AA20820; Sun, 19 Mar 95 06:39:01 -0700 Message-Id: <9503191339.AA20820@oodis01.hill.af.mil> Date: Sun, 19 Mar 95 06:39:00 -0700 From: kburton@oodis01.hill.af.mil (A Kelly Burton SSgt) To: list-managers@GreatCircle.COM Sender: list-managers-owner@GreatCircle.COM Precedence: bulk QUIT CANCEL UNSUBSRIBE From list-managers-owner Sun Mar 19 08:07:15 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id IAA02240 for list-managers-outgoing; Sun, 19 Mar 1995 08:04:19 -0800 Received: from hamp.hampshire.edu (newhamp.hampshire.edu [192.33.12.137]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id IAA02235 for ; Sun, 19 Mar 1995 08:04:15 -0800 Received: from [192.33.12.80] (mac80.hampshire.edu) by hamp.hampshire.edu (4.1/SMI-4.1) id AA03498; Sun, 19 Mar 95 11:05:12 EST Date: Sun, 19 Mar 95 11:05:09 EST Message-Id: <9503191605.AA03498@hamp.hampshire.edu> To: List-Managers@GreatCircle.COM From: mpmNS@hamp.hampshire.edu (Michelle Murrain) Subject: How to Manage List When Away, Etc. Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Linda Henneman writes: >I'll hopefully be launching my very first majordomo mailing list >(fully-moderated) next week and was just wondering what you other list >managers do when you go out of town? Do you all have laptops and those >little modems the size of a playing card and just log in while vacationing >or on business trips, etc.? Well, I've been managing 3 lists, two for about 3 years, one for 2 years, and I just hope that they don't implode or explode while I'm away. I don't have a laptop, and my trips are mostly under one week. (Besides, if I want a vacation, I want a *vacation*!) I make sure all piled up list business is done, send a note to my list letting folk know I'm away (so admin requests and the like that are not automatic will be delayed), and keep my fingers crossed. >And how about, God forbid, if you become ill and perhaps even need >hospitalization, surgery, or are otherwise incapacitated? Do you have a >backup person who you trust your user id and password with to carry on in >your stead? What kind of contingency plans do you have in place? Hmmm, I hadn't even thought of that one. Now that I think of it, it might behoove me to find someone (maybe who's on the list, perhaps) to volunteer to be a backup list manager. My lists are pretty low volume (two <7 messages/week, one is about 10/day these days), few subscribers (one <200, two <400), and I've only had one of them explode at all. The explosions, which thankfully are *rare* (like mail loops when net.idiots use vacation messages and forget to unsubscribe from the list) are the ones to worry about. If the list implodes and stops sending out messages for one reason or another (happens fairly often to me, like twice a year on my old system, less often now) it can wait till I get back. Michelle ---------------------------------------------------------------------- Michelle Murrain, Ph.D. email and finger: School of Natural Science mpmNS@hamp.hampshire.edu Hampshire College, mmurrain@family.hampshire.edu Amherst, MA 01002 (413) 582-5688 fax:(413) 582-5448 Home page URL -> http://www.hampshire.edu/Hampshire/ns/html/Murrain.html From list-managers-owner Mon Mar 20 02:08:12 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id BAA17071 for list-managers-outgoing; Mon, 20 Mar 1995 01:45:07 -0800 Received: from shell1.best.com (shell1.best.com [204.156.128.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id BAA17066 for ; Mon, 20 Mar 1995 01:45:04 -0800 Received: (frugal@localhost) by shell1.best.com (8.6.11/8.6.5) id BAA12443; Mon, 20 Mar 1995 01:42:25 -0800 Date: Mon, 20 Mar 1995 01:42:25 -0800 (PST) From: Linda Henneman To: Michelle Murrain cc: List-Managers@GreatCircle.COM Subject: Re: How to Manage List When Away, Etc. In-Reply-To: <9503191605.AA03498@hamp.hampshire.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Michelle, thanks for the info. I've thought, too, that I could just switch to unmoderated while on vacation, etc. so my majordomo could do the work and warn my subscribers beforehand. I learned via private e-mail that you don't have to give someone your login id and password, just the password to the majordomo in order for them to run it in your absence. Think I'll see if I can find someone who could provide me w/backup and I could do the same for them. I probably could just have them subscribe to the list and then they'd be alerted to any problems w/mail loops, etc. On one list I was on I got over twenty copies each of two different messages the owner posted to the list. He had to unsubscribe the entire almost 3,000 member list to stop it until the ISP fixed things! Linda (frugal@best.com) On Sun, 19 Mar 1995, Michelle Murrain wrote: > and I just hope that they don't implode or explode while I'm away. I don't > have a laptop, and my trips are mostly under one week. (Besides, if I want > a vacation, I want a *vacation*!) I make sure all piled up list business is > done, send a note to my list letting folk know I'm away (so admin requests > and the like that are not automatic will be delayed), and keep my fingers > crossed. > > Now that I think of it, it might behoove me to find someone (maybe who's on > the list, perhaps) to volunteer to be a backup list manager. My lists are > > > From list-managers-owner Mon Mar 20 11:07:58 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA27190 for list-managers-outgoing; Mon, 20 Mar 1995 10:54:05 -0800 Received: from FSM-1.PICA.ARMY.MIL (fsm-1.pica.army.mil [129.139.164.101]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id KAA27185 for ; Mon, 20 Mar 1995 10:54:02 -0800 Date: Mon, 20 Mar 95 13:54:17 EST From: Info-LabVIEW List Maintainer To: list-managers@greatcircle.com Subject: An RFC? question (maybe) Organization: Electric Armts Div, US Army ARDEC, Picatinny Arsenal, NJ Message-ID: <9503201354.aa18068@fsm-1.pica.army.mil> Sender: list-managers-owner@GreatCircle.COM Precedence: bulk A list I am subscribed to has recently experienced a problem which some of my lists have come across as well: that is, mail to a user bounces and gets returned to the list (ie, to the To: line, and not From: or Sender:). Needless to say, this usually only happens to people subscribed to the digest version, so a 20 or 30k file gets sent to everyone (including those subscribed to individual msgs) and, if the list maintainer isn't around, say over the weekend, the bounced digest gets included in the next digest and ... well, you get the idea. Any references to just how bounced mail should be handled? I did a keyword search at the Internic, but just don't have time to sort thru all the responses it got me (besides, I already know how to unsub the offenders:-}). Thanks much... Tom Coradeschi, Info-LabVIEW List Maintainer http://k-whiner.pica.army.mil/info-labview.html From list-managers-owner Tue Mar 21 06:07:26 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id FAA26925 for list-managers-outgoing; Tue, 21 Mar 1995 05:43:05 -0800 Received: from wilma.cs.utk.edu (WILMA.CS.UTK.EDU [128.169.94.141]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id FAA26920 for ; Tue, 21 Mar 1995 05:43:00 -0800 Received: from LOCALHOST by wilma.cs.utk.edu with SMTP (cf v2.11c-UTK) id IAA10702; Tue, 21 Mar 1995 08:37:17 -0500 Message-Id: <199503211337.IAA10702@wilma.cs.utk.edu> X-URI: http://www.cs.utk.edu/~moore/ From: Keith Moore To: Info-LabVIEW List Maintainer cc: list-managers@greatcircle.com, moore@cs.utk.edu Subject: Re: An RFC? question (maybe) In-reply-to: Your message of "Mon, 20 Mar 1995 13:54:17 EST." <9503201354.aa18068@fsm-1.pica.army.mil> Date: Tue, 21 Mar 1995 08:37:11 -0500 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk > A list I am subscribed to has recently experienced a problem which some of > my lists have come across as well: that is, mail to a user bounces and > gets returned to the list (ie, to the To: line, and not From: or > Sender:). Just to clear up a common misconception... Mail should ALWAYS be bounced to the "envelope return address". In SMTP this is the address in the MAIL FROM command, or if a message is not being transferred by SMTP, it is the address in the Return-Path header field. Mail should NEVER be bounced to an address in any header field other than Return-Path. So bouncing to the From, Sender, or Errors-To fields are all illegal, and mailers that do this are broken. (See RFC 821 and RFC 1123.) > Needless to say, this usually only happens to people subscribed to the > digest version, so a 20 or 30k file gets sent to everyone (including those > subscribed to individual msgs) and, if the list maintainer isn't around, > say over the weekend, the bounced digest gets included in the next digest > and ... well, you get the idea. > > Any references to just how bounced mail should be handled? I did a keyword > search at the Internic, but just don't have time to sort thru all the > responses it got me (besides, I already know how to unsub the offenders:-}). Make sure the offenders (and their postmasters) know why they're being unsubbed, so that they at least have the chance of fixing the problem. Any mailer that exhibits the behavior you described is so badly broken that you should consider deleting any list member who uses it. I recently deleted every user on every list I had that used one particular Internet gateway to Lotus Notes, for reasons very similar to those you cite. Mailers that bounce to the From or Sender header are bad enough -- a mailer that bounces to the To or CC header is inexcusable, and a sure invitation to disaster. Some mailing list manager programs try to notice when messages are bounced back to the list, with varying degrees of success. Sometimes they don't filter well enough, and sometimes they filter out perfectly valid messages. Bounce message formats change over time, so an MLM that is good at filtering today may not be so good tomorrow. (Bounce messages are being standardized by the IETF, so this situation may improve in a few years as the new standards start to be implemented.) For the specific case of a digest, you might consider having the From header field be the digest submission address, and the To: field being an unreplyable group address... From: foo-digest@j.random.host To: foo-digest-members:; ...but you'll still want some filtering because of all of the broken systems that bounce to the From header address. (Note that while it is reasonable for a digest list to set the From header, ordinary lists should leave the From header alone.) Keith Moore From list-managers-owner Fri Mar 24 03:07:32 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id CAA25478 for list-managers-outgoing; Fri, 24 Mar 1995 02:44:31 -0800 Received: from uclink.berkeley.edu (uclink.Berkeley.EDU [128.32.155.3]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id CAA25462 for ; Fri, 24 Mar 1995 02:44:25 -0800 Received: by uclink.berkeley.edu (8.6.10/1.33(web)-OV4) id CAA11942; Fri, 24 Mar 1995 02:42:05 -0800 Date: Fri, 24 Mar 1995 02:42:04 -0800 (PST) From: "Michael J. Osofsky" Subject: Newinfo To: Majordomo-L Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Newinfo Syntax? What is the syntax for the newinfo command? That is, where do I write the new information and do I need to delimit it with quotes or something else? mike From list-managers-owner Sat Mar 25 08:07:13 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA02444 for list-managers-outgoing; Sat, 25 Mar 1995 07:42:20 -0800 Received: from SYSWRK.UCIS.Dal.Ca (syswrk.UCIS.Dal.Ca [129.173.2.108]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id HAA02438 for ; Sat, 25 Mar 1995 07:42:17 -0800 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.3-13 #6307) id <01HOJVDSU4HC001SF4@SYSWRK.UCIS.DAL.CA>; Sat, 25 Mar 1995 11:39:53 -0400 Received: from biome.bio.dfo.ca by AC.DAL.CA (PMDF V4.3-13 #2545) id <01HOJVDG8BEO00LHOJ@AC.DAL.CA>; Sat, 25 Mar 1995 11:39:37 -0400 Received: by biome.bio.dfo.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:List-Managers@GreatCircle.COM id AA23442; Sat, 25 Mar 95 11:33:03 -0400 Date: Sat, 25 Mar 1995 11:33:03 -0400 (AST) From: bill@biome.bio.dfo.ca (Bill Silvert) Subject: What means "Mailbox not found"? To: List-Managers@GreatCircle.COM (List Managers) Message-id: <9503251533.AA23442@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 Content-length: 683 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I'm getting a lot of "Mailbox not found" bounces on one of my lists, mostly from NOAA sites in the US. I don't know whether this means that the addresses are invalid, in which case I'll delete them, or just a symptom of temporary network problems. Can someone clarify this, or tell me what other diagnostic information to look for? In general I get a lot of bounces from US government sites. Does anyone else have any insights about this? Bill Silvert -- Bill Silvert, Habitat Ecology Div., Bedford Inst. Oceanography P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2 Personal InterNet Address: silvert@biome.bio.ns.ca HED runs a WWW server at URL=http://biome.bio.dfo.ca From list-managers-owner Mon Mar 27 02:38:36 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id CAA05501 for list-managers-outgoing; Mon, 27 Mar 1995 02:12:29 -0800 Received: from perth.DIALix.oz.au (perth.DIALix.oz.au [192.203.228.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id CAA05496 for ; Mon, 27 Mar 1995 02:12:25 -0800 Received: from vector.UUCP (vectuucp@localhost) by perth.DIALix.oz.au (8.6.11/8.6.11/DIALix) with UUCP id SAA08993 for greatcircle.com!list-managers; Mon, 27 Mar 1995 18:10:03 +0800 Subject: A manual list manager !!?? To: list-managers@greatcircle.com Date: Mon, 27 Mar 1995 17:55:56 +0800 (WST) From: Gregory Smith X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1924 Message-ID: <9503271756.aa23813@vector.vector.dialix.oz.au> Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Hi all, I'm from a smallish software company and am looking to set up a mailing list for our users. First thing I did was grab Norm Aleks' MAILING LIST MANAGEMENT SOFTWARE FAQ. Now this has convinced me that a manually driven mailing list may be my answer because: 1. Our mailing list will be small - only 50 - 150 subscribers 2. The subscriber list will be pretty stable (1-2 changes per month) 3. I envisage fairly low message volume 4. The list will be moderated by me 5. I don't have a lot of time to learn an proper MLM But now I've decided to go manual - I need some help. The above document says that the best way to go manual is to "bounce" incoming mail to a list. Also it recommends using Bcc for the distribution list to ensure replys come back. So my first two questions are: 1. I can't understand how bouncing will work. Won't the reply address be set to the originator rather than the mailing list? 2. What's the difference between Bcc and just plain cc? >From what I can figure, the best way might be for the mailing list user to forward incoming mail to a distribution list. The original sender may be lost in the header, but we can encourage people to sign each posting. By using forward, all replys will come back properly (won't they?) I'm going to use elm and hope to kick off in the next couple of weeks so any hints or tips would be gratefully accepted. Please excuse my ignorance in (what must be) basic mail concepts. I've done lots of reading but can't seem to find out what it all means. Regards, |-----------------------------------------| | Gregory J Smith | | Vector International Pty Ltd ,-_|\ | | / \ | | Perth, Western Australia ----> *_,-._/ | | P: 619 242 3396 F: 619 242 3397 v | | * * The Makers of MacroView * * | |-----------------------------------------| From list-managers-owner Mon Mar 27 05:38:45 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id FAA09082 for list-managers-outgoing; Mon, 27 Mar 1995 05:32:49 -0800 Received: from FSM-1.PICA.ARMY.MIL (fsm-1.pica.army.mil [129.139.164.101]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id FAA09077 for ; Mon, 27 Mar 1995 05:32:45 -0800 Date: Mon, 27 Mar 95 8:33:06 EST From: Info-LabVIEW List Maintainer To: list-managers@greatcircle.com Subject: Re: What means "Mailbox not found"? Organization: Electric Armts Div, US Army ARDEC, Picatinny Arsenal, NJ Message-ID: <9503270833.aa04531@fsm-1.pica.army.mil> Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Bill Silvert wrote: >I'm getting a lot of "Mailbox not found" bounces on one of my lists, >mostly from NOAA sites in the US. I don't know whether this means that >the addresses are invalid, in which case I'll delete them, or just a >symptom of temporary network problems. Can someone clarify this, or >tell me what other diagnostic information to look for? It's difficult to say what causes this. Best bet is to forward one to postmaster@that.site with a note asking if they're aware of the problem. Or you can summarily delete them:-} >In general I get a lot of bounces from US government sites. Does anyone >else have any insights about this? Nope. I get most of my bounces from .com sites which generally appear to be public access providers. Tom Coradeschi, Info-LabVIEW List Maintainer http://k-whiner.pica.army.mil/info-labview.html From list-managers-owner Mon Mar 27 11:11:16 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA18592 for list-managers-outgoing; Mon, 27 Mar 1995 10:58:19 -0800 Received: from suntan.Tandem.com (suntan.tandem.com [192.216.221.8]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id KAA18587 for ; Mon, 27 Mar 1995 10:58:15 -0800 Received: from adm.loc3.tandem.com by suntan.Tandem.com (4.1/suntan5.950313) for list-managers@greatcircle.com id AA28869; Mon, 27 Mar 95 10:56:05 PST Received: from zorch.loc3.tandem.com by adm.loc3.tandem.com (4.1/6main.940209) id AA21436; Mon, 27 Mar 95 10:54:46 PST Received: by zorch.loc3.tandem.com (4.1/6leaf.940209) id AA09418; Mon, 27 Mar 95 10:56:03 PST Date: Mon, 27 Mar 95 10:56:03 PST From: scott@loc3.tandem.com (mueller_scott) Message-Id: <9503271856.AA09418@zorch.loc3.tandem.com> To: list-managers@greatcircle.com Subject: looking for someone to adopt a list Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I'm looking for someone to adopt a mailing list. The list is 'wireless', the charter is: This is an unmoderated mailing list for the discussion and technological advancement of Wireless local area networks for data. Mailings to this list may cover any of the technical aspects of Wireless LANs: RF Design Propagation and wave physics Applications Data communications Computer engineering ... The people who started it have since left the company, and none of the postmaster staff have the time or interest in running it. There are about 390 addresses on it (many dead) and about two dozen subsidiary exploders. Traffic is light. If you're interested, please reply to this message. -- Scott Hazen Mueller, Tandem Computers +1 408 285 5762 scott@tandem.com Unix System/Network Administrator, Host-, Post-, News- and Web-Master From list-managers-owner Tue Mar 28 11:59:43 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA28485 for list-managers-outgoing; Tue, 28 Mar 1995 11:23:44 -0800 Received: from suntan.Tandem.com (suntan.tandem.com [192.216.221.8]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id LAA28480 for ; Tue, 28 Mar 1995 11:23:42 -0800 Received: from adm.loc3.tandem.com by suntan.Tandem.com (4.1/suntan5.950313) for list-managers@greatcircle.com id AA12643; Tue, 28 Mar 95 11:21:35 PST Received: from zorch.loc3.tandem.com by adm.loc3.tandem.com (4.1/6main.940209) id AA02228; Tue, 28 Mar 95 11:20:15 PST Received: by zorch.loc3.tandem.com (4.1/6leaf.940209) id AA28317; Tue, 28 Mar 95 11:21:33 PST Date: Tue, 28 Mar 95 11:21:33 PST From: scott@loc3.tandem.com (mueller_scott) Message-Id: <9503281921.AA28317@zorch.loc3.tandem.com> To: list-managers@greatcircle.com Subject: list adopted, thanks! Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Thanks, list managers. \scott From list-managers-owner Tue Mar 28 19:37:15 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id TAA11409 for list-managers-outgoing; Tue, 28 Mar 1995 19:12:37 -0800 Received: from perth.DIALix.oz.au (perth.DIALix.oz.au [192.203.228.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id TAA11404 for ; Tue, 28 Mar 1995 19:12:25 -0800 Received: from vector.UUCP (vectuucp@localhost) by perth.DIALix.oz.au (8.6.11/8.6.11/DIALix) with UUCP id LAA12691 for greatcircle.com!list-managers; Wed, 29 Mar 1995 11:10:16 +0800 Subject: MAILING LIST MANAGEMENT SOFTWARE FAQ To: list-managers@greatcircle.com Date: Wed, 29 Mar 1995 09:41:58 +0800 (WST) From: Gregory Smith X-Mailer: ELM [version 2.4 PL21] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1395 Message-ID: <9503290942.aa28873@vector.vector.dialix.oz.au> Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Several people have asked me for sources of Norm Aleks' MAILING LIST MANAGEMENT SOFTWARE FAQ. The extract below gives some sources. -----------EXTRACT FROM MAILING LIST MANAGEMENT SOFTWARE FAQ------------- Subject: 4.00 Where to get the current version of this FAQ This FAQ is posted monthly on comp.mail.list-admin.software, comp.answers, and news.answers. It is then archived at news.answers archives including . In addition, the current version may be retrieved from these mail servers: Write "get doc mlm-software-faq" in the body of mail to ListProc@avs.com Write "get mlm-software faq" in the body of mail to LISTSERV@listserv.net Write "get file mlm-software-faq" in the body of mail to Majordomo@pop.psu.edu Write "archive get FAQ/mlm-software" in the subject or body of mail to SmartList-request@informatik.rwth-aachen.de ------------------------EXTRACT ENDS-------------------------------------- Hope this helps. |-----------------------------------------| | Gregory J Smith | | Vector International Pty Ltd ,-_|\ | | / \ | | Perth, Western Australia ----> *_,-._/ | | P: 619 242 3396 F: 619 242 3397 v | | * * The Makers of MacroView * * | |-----------------------------------------| From list-managers-owner Wed Mar 29 07:38:04 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA25724 for list-managers-outgoing; Wed, 29 Mar 1995 07:23:36 -0800 Received: from joyx.joensuu.fi (joyx.joensuu.fi [128.214.14.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id HAA25708 for ; Wed, 29 Mar 1995 07:22:57 -0800 Received: by joyx.joensuu.fi (5.57/Ultrix3.0-C) id AA28161; Wed, 29 Mar 95 18:17:13 +0300 Received: by cc.joensuu.fi (4.1/SMI-4.1) id AA03728; Wed, 29 Mar 95 18:22:00 +0300 Date: Wed, 29 Mar 1995 18:21:59 +0300 (EET DST) From: Marko Toivanen To: List-Managers@greatcircle.com Cc: Bill Silvert , Marko Toivanen Subject: Re: What means "Mailbox not found"? In-Reply-To: <199503260900.BAA13129@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 Sat, 25 Mar 1995 11:33:03 -0400 (AST) bill@biome.bio.dfo.ca (Bill Silvert) wrote: > I'm getting a lot of "Mailbox not found" bounces on one of my lists, > mostly from NOAA sites in the US. I don't know whether this means that > the addresses are invalid, in which case I'll delete them, or just a > symptom of temporary network problems. Can someone clarify this, or > tell me what other diagnostic information to look for? > > In general I get a lot of bounces from US government sites. Does anyone > else have any insights about this? I've found that occasionally "user unknown" bounces are due to local nameserver problems, not the the users really being unknown. Try the postmasters of the bouncing sites, they should be able to tell you what's happening. * * * * * * * * * * * * * * * * * * * * * * * * * Marko Toivanen * * * * * * * * * * co-moderator in FEYERABEND of mtoivane@cc.joensuu.fi * * * * * * majordomo@lists.village.virginia.edu http://www.joensuu.fi/~mtoivane/ * finger mtoivane@cc.joensuu.fi for info From list-managers-owner Wed Mar 29 11:37:48 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA04509 for list-managers-outgoing; Wed, 29 Mar 1995 11:29:20 -0800 Received: from gagme.wwa.com (gagme.wwa.com [198.49.174.33]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id LAA04502 for ; Wed, 29 Mar 1995 11:29:15 -0800 Received: by gagme.wwa.com (Smail3.1.28.1 #8) id m0ru3S9-000FFEC; Wed, 29 Mar 95 13:30 CST Message-Id: From: dattier@wwa.com (David W. Tamkin) Subject: Re: What means "Mailbox not found"? To: mtoivane@cc.joensuu.fi (Marko Toivanen) Date: Wed, 29 Mar 1995 13:30:53 -0600 (CST) Cc: List-Managers@greatcircle.com In-Reply-To: from "Marko Toivanen" at Mar 29, 95 06:21:59 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1151 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Marko Toivanen suggested to Bill Silvert, | I've found that occasionally "user unknown" bounces are due to local | nameserver problems, not the the users really being unknown. | | Try the postmasters of the bouncing sites, they should be able to tell | you what's happening. There was one time I tried that only to find that mail to postmaster was bounced with the same error as that for mail to the subscriber. (It was "unknown mailer error.") Then it vanished and her mail went through again. About a month later it resumed and kept up for three days running, so I un- subbed her. There's not much one can do when mail to postmaster isn't delivered either. But I still think that the winners in this category are the people who, when they notice their mail from the list has dried up and ask what happened, and you tell them why they were unsubbed and your explanation is delivered, get mad at you for not telling them. I've taken the pre-emptive measure of in- cluding, "and I couldn't tell you what was happening because if I can't send you email, I can't send you email that says `I can't send you email,'" when they ask me what happened. From list-managers-owner Thu Mar 30 00:20:22 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id AAA12166 for list-managers-outgoing; Thu, 30 Mar 1995 00:10:56 -0800 Received: from moon.earthlink.net (moon.earthlink.net [198.68.160.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id AAA12154 for ; Thu, 30 Mar 1995 00:10:52 -0800 Received: by moon.earthlink.net (/\==/\ Smail3.1.28.1 #28.2) id ; Thu, 30 Mar 95 00:02 PST Message-Id: Date: Wed, 29 Mar 1995 23:45:57 -0800 From: stp@earthlink.net (Stephen Porter) To: List-Managers@greatcircle.com (List-Managers@greatcircle.com) Subject: MajorDomo Question Sender: list-managers-owner@GreatCircle.COM Precedence: bulk To: ron@apollo.theta.com, stp@earthlink.net Cc: dhelrod@apollo.theta.com Subject: MajorDomo Question Date: Wed, 29 Mar 1995 16:17:58 -0800 From: "David H. Elrod" Do either of you know of a feature that would allow anyone NOT in some list post a message? This would be a "kill" feature to keep specific people from posting. Any ideas? dhelrod Stephen T. Porter / Los Angeles, CA stp@earthlink.net From list-managers-owner Thu Mar 30 00:50:22 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id AAA14638 for list-managers-outgoing; Thu, 30 Mar 1995 00:43:24 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id AAA14594 for ; Thu, 30 Mar 1995 00:43:13 -0800 Message-Id: <199503300840.BAA24373@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id BAA24373; Thu, 30 Mar 1995 01:40:36 -0700 From: stp@earthlink.net (Stephen Porter) Subject: MajorDomo Question To: List-Managers@GreatCircle.COM (List-Managers@greatcircle.com) Date: Wed, 29 Mar 1995 23:45:57 -0800 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk To: ron@apollo.theta.com, stp@earthlink.net Cc: dhelrod@apollo.theta.com Subject: MajorDomo Question Date: Wed, 29 Mar 1995 16:17:58 -0800 From: "David H. Elrod" Do either of you know of a feature that would allow anyone NOT in some list post a message? This would be a "kill" feature to keep specific people from posting. Any ideas? dhelrod Stephen T. Porter / Los Angeles, CA stp@earthlink.net From list-managers-owner Thu Mar 30 01:20:24 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id AAA15481 for list-managers-outgoing; Thu, 30 Mar 1995 00:58:38 -0800 Received: from gate.pschools.st-albert.ab.ca (gate.pschools.st-albert.ab.ca [199.185.209.2]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id AAA15470 for ; Thu, 30 Mar 1995 00:58:32 -0800 Message-Id: <199503300858.AAA15470@miles.greatcircle.com> Received: from pschools.st-albert.ab.ca by gate.pschools.st-albert.ab.ca; Thu, 30 Mar 95 01:54 MST X-Sender: stuartr@pschools.st-albert.ab.ca X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Length: 2752 Content-Type: text/plain; charset="us-ascii" To: list-managers@greatcircle.com Date: Thu, 30 Mar 95 01:54 MST From: stuartr@pschools.st-albert.ab.ca (Robin Stuart) Subject: UnixWare 1.1.3 & Majordomo 93 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I'm using UnixWare 1.1.3 and have the SDK 1.1 installed. I'm no expert in "C" and so I can'nt figure out the following error. Any ideas?? Thanks in advance! --------------------------------------------------------------------- Makefile: W_BIN=/home2/majordomo W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh W_MAJORDOMO_CF=$(W_BIN)/majordomo.cf # W_USER=daemon W_USER=majordom W_GROUP=majordom # W_CHOWN=${W_USER}.${W_GROUP} W_CHOWN=${W_USER} W_CHMOD=6755 WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" --------------------------------------------------------------------- # make wrapper cc -DBIN=\"/home2/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -DHOME=\"HOME=/home2/majordomo\" -DSHELL=\"SHELL=/bin/csh\" -DMAJORDOMO_CF= \"MAJORDOMO_CF=/home2/majordomo/majordomo.cf\" -o wrapper wrapper.c UX:acomp: WARNING: "wrapper.c", line 65: warning: improper pointer/integer combi nation: op "!=" ************************************************ Can anybody tell me whats going on with line 65? ************************************************ --------------------------------------------------------------------- /usr/ucblib/aliases: ####################### # Local aliases below # ####################### owner-owner: postmaster # Majordomo owner-majordomo: sysop majordomo: "|/home2/majordomo/wrapper majordomo" majordom: owner-majordomo Majordomo-Owner: owner-majordomo --------------------------------------------------------------------- # echo help | /usr/ucblib/sendmail -v majordomo majordomo... aliased to "|/home2/majordomo/wrapper majordomo" "|/home2/majordomo/wrapper majordomo"... Connecting to via prog... /home2/majordomo/wrapper: error: recompile with POSIX flags. "|/home2/majordomo/wrapper majordomo"... unknown mailer error 4 owner-majordomo... aliased to sysop Postmaster... aliased to sysop sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent I believe that this error is due to the wrapper compile error! --------------------------------------------------------- Robin Stuart The Gate Keeper! stuartr@pschools.st-albert.ab.ca [PC Eudora v1.4.4] St. Albert Protestant Schools (403)460-3712 "Opening up your mind to the world is called learning!" --------------------------------------------------------- From list-managers-owner Thu Mar 30 01:50:54 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id BAA19347 for list-managers-outgoing; Thu, 30 Mar 1995 01:43:08 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id BAA19335 for ; Thu, 30 Mar 1995 01:43:01 -0800 Message-Id: <199503300940.CAA24854@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id CAA24854; Thu, 30 Mar 1995 02:40:27 -0700 From: stp@earthlink.net (Stephen Porter) Subject: MajorDomo Question To: List-Managers@GreatCircle.COM (List-Managers@greatcircle.com) Date: Wed, 29 Mar 1995 23:45:57 -0800 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk To: ron@apollo.theta.com, stp@earthlink.net Cc: dhelrod@apollo.theta.com Subject: MajorDomo Question Date: Wed, 29 Mar 1995 16:17:58 -0800 From: "David H. Elrod" Do either of you know of a feature that would allow anyone NOT in some list post a message? This would be a "kill" feature to keep specific people from posting. Any ideas? dhelrod Stephen T. Porter / Los Angeles, CA stp@earthlink.net From list-managers-owner Thu Mar 30 01:53:46 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id BAA19377 for list-managers-outgoing; Thu, 30 Mar 1995 01:43:18 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id BAA19346 for ; Thu, 30 Mar 1995 01:43:08 -0800 Message-Id: <199503300940.CAA24893@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id CAA24893; Thu, 30 Mar 1995 02:40:34 -0700 From: stuartr@pschools.st-albert.ab.ca (Robin Stuart) Subject: UnixWare 1.1.3 & Majordomo 93 To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 95 01:54 MST Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I'm using UnixWare 1.1.3 and have the SDK 1.1 installed. I'm no expert in "C" and so I can'nt figure out the following error. Any ideas?? Thanks in advance! --------------------------------------------------------------------- Makefile: W_BIN=/home2/majordomo W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh W_MAJORDOMO_CF=$(W_BIN)/majordomo.cf # W_USER=daemon W_USER=majordom W_GROUP=majordom # W_CHOWN=${W_USER}.${W_GROUP} W_CHOWN=${W_USER} W_CHMOD=6755 WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" --------------------------------------------------------------------- # make wrapper cc -DBIN=\"/home2/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -DHOME=\"HOME=/home2/majordomo\" -DSHELL=\"SHELL=/bin/csh\" -DMAJORDOMO_CF= \"MAJORDOMO_CF=/home2/majordomo/majordomo.cf\" -o wrapper wrapper.c UX:acomp: WARNING: "wrapper.c", line 65: warning: improper pointer/integer combi nation: op "!=" ************************************************ Can anybody tell me whats going on with line 65? ************************************************ --------------------------------------------------------------------- /usr/ucblib/aliases: ####################### # Local aliases below # ####################### owner-owner: postmaster # Majordomo owner-majordomo: sysop majordomo: "|/home2/majordomo/wrapper majordomo" majordom: owner-majordomo Majordomo-Owner: owner-majordomo --------------------------------------------------------------------- # echo help | /usr/ucblib/sendmail -v majordomo majordomo... aliased to "|/home2/majordomo/wrapper majordomo" "|/home2/majordomo/wrapper majordomo"... Connecting to via prog... /home2/majordomo/wrapper: error: recompile with POSIX flags. "|/home2/majordomo/wrapper majordomo"... unknown mailer error 4 owner-majordomo... aliased to sysop Postmaster... aliased to sysop sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent I believe that this error is due to the wrapper compile error! --------------------------------------------------------- Robin Stuart The Gate Keeper! stuartr@pschools.st-albert.ab.ca [PC Eudora v1.4.4] St. Albert Protestant Schools (403)460-3712 "Opening up your mind to the world is called learning!" --------------------------------------------------------- From list-managers-owner Thu Mar 30 02:50:17 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id CAA20940 for list-managers-outgoing; Thu, 30 Mar 1995 02:43:14 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id CAA20929 for ; Thu, 30 Mar 1995 02:43:08 -0800 Message-Id: <199503301040.DAA25451@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id DAA25451; Thu, 30 Mar 1995 03:40:35 -0700 From: stp@earthlink.net (Stephen Porter) Subject: MajorDomo Question To: List-Managers@GreatCircle.COM (List-Managers@greatcircle.com) Date: Wed, 29 Mar 1995 23:45:57 -0800 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk To: ron@apollo.theta.com, stp@earthlink.net Cc: dhelrod@apollo.theta.com Subject: MajorDomo Question Date: Wed, 29 Mar 1995 16:17:58 -0800 From: "David H. Elrod" Do either of you know of a feature that would allow anyone NOT in some list post a message? This would be a "kill" feature to keep specific people from posting. Any ideas? dhelrod Stephen T. Porter / Los Angeles, CA stp@earthlink.net From list-managers-owner Thu Mar 30 02:52:08 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id CAA20941 for list-managers-outgoing; Thu, 30 Mar 1995 02:43:15 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id CAA20931 for ; Thu, 30 Mar 1995 02:43:10 -0800 Message-Id: <199503301040.DAA25460@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id DAA25460; Thu, 30 Mar 1995 03:40:36 -0700 From: stuartr@pschools.st-albert.ab.ca (Robin Stuart) Subject: UnixWare 1.1.3 & Majordomo 93 To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 95 01:54 MST Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I'm using UnixWare 1.1.3 and have the SDK 1.1 installed. I'm no expert in "C" and so I can'nt figure out the following error. Any ideas?? Thanks in advance! --------------------------------------------------------------------- Makefile: W_BIN=/home2/majordomo W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh W_MAJORDOMO_CF=$(W_BIN)/majordomo.cf # W_USER=daemon W_USER=majordom W_GROUP=majordom # W_CHOWN=${W_USER}.${W_GROUP} W_CHOWN=${W_USER} W_CHMOD=6755 WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" --------------------------------------------------------------------- # make wrapper cc -DBIN=\"/home2/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -DHOME=\"HOME=/home2/majordomo\" -DSHELL=\"SHELL=/bin/csh\" -DMAJORDOMO_CF= \"MAJORDOMO_CF=/home2/majordomo/majordomo.cf\" -o wrapper wrapper.c UX:acomp: WARNING: "wrapper.c", line 65: warning: improper pointer/integer combi nation: op "!=" ************************************************ Can anybody tell me whats going on with line 65? ************************************************ --------------------------------------------------------------------- /usr/ucblib/aliases: ####################### # Local aliases below # ####################### owner-owner: postmaster # Majordomo owner-majordomo: sysop majordomo: "|/home2/majordomo/wrapper majordomo" majordom: owner-majordomo Majordomo-Owner: owner-majordomo --------------------------------------------------------------------- # echo help | /usr/ucblib/sendmail -v majordomo majordomo... aliased to "|/home2/majordomo/wrapper majordomo" "|/home2/majordomo/wrapper majordomo"... Connecting to via prog... /home2/majordomo/wrapper: error: recompile with POSIX flags. "|/home2/majordomo/wrapper majordomo"... unknown mailer error 4 owner-majordomo... aliased to sysop Postmaster... aliased to sysop sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent I believe that this error is due to the wrapper compile error! --------------------------------------------------------- Robin Stuart The Gate Keeper! stuartr@pschools.st-albert.ab.ca [PC Eudora v1.4.4] St. Albert Protestant Schools (403)460-3712 "Opening up your mind to the world is called learning!" --------------------------------------------------------- From list-managers-owner Thu Mar 30 03:50:26 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id DAA21891 for list-managers-outgoing; Thu, 30 Mar 1995 03:43:15 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id DAA21884 for ; Thu, 30 Mar 1995 03:43:12 -0800 Message-Id: <199503301140.EAA26336@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id EAA26336; Thu, 30 Mar 1995 04:40:38 -0700 From: stp@earthlink.net (Stephen Porter) Subject: MajorDomo Question To: List-Managers@GreatCircle.COM (List-Managers@greatcircle.com) Date: Wed, 29 Mar 1995 23:45:57 -0800 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk To: ron@apollo.theta.com, stp@earthlink.net Cc: dhelrod@apollo.theta.com Subject: MajorDomo Question Date: Wed, 29 Mar 1995 16:17:58 -0800 From: "David H. Elrod" Do either of you know of a feature that would allow anyone NOT in some list post a message? This would be a "kill" feature to keep specific people from posting. Any ideas? dhelrod Stephen T. Porter / Los Angeles, CA stp@earthlink.net From list-managers-owner Thu Mar 30 03:52:43 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id DAA21896 for list-managers-outgoing; Thu, 30 Mar 1995 03:43:17 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id DAA21889 for ; Thu, 30 Mar 1995 03:43:13 -0800 Message-Id: <199503301140.EAA26348@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id EAA26348; Thu, 30 Mar 1995 04:40:40 -0700 From: stuartr@pschools.st-albert.ab.ca (Robin Stuart) Subject: UnixWare 1.1.3 & Majordomo 93 To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 95 01:54 MST Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I'm using UnixWare 1.1.3 and have the SDK 1.1 installed. I'm no expert in "C" and so I can'nt figure out the following error. Any ideas?? Thanks in advance! --------------------------------------------------------------------- Makefile: W_BIN=/home2/majordomo W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh W_MAJORDOMO_CF=$(W_BIN)/majordomo.cf # W_USER=daemon W_USER=majordom W_GROUP=majordom # W_CHOWN=${W_USER}.${W_GROUP} W_CHOWN=${W_USER} W_CHMOD=6755 WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" --------------------------------------------------------------------- # make wrapper cc -DBIN=\"/home2/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -DHOME=\"HOME=/home2/majordomo\" -DSHELL=\"SHELL=/bin/csh\" -DMAJORDOMO_CF= \"MAJORDOMO_CF=/home2/majordomo/majordomo.cf\" -o wrapper wrapper.c UX:acomp: WARNING: "wrapper.c", line 65: warning: improper pointer/integer combi nation: op "!=" ************************************************ Can anybody tell me whats going on with line 65? ************************************************ --------------------------------------------------------------------- /usr/ucblib/aliases: ####################### # Local aliases below # ####################### owner-owner: postmaster # Majordomo owner-majordomo: sysop majordomo: "|/home2/majordomo/wrapper majordomo" majordom: owner-majordomo Majordomo-Owner: owner-majordomo --------------------------------------------------------------------- # echo help | /usr/ucblib/sendmail -v majordomo majordomo... aliased to "|/home2/majordomo/wrapper majordomo" "|/home2/majordomo/wrapper majordomo"... Connecting to via prog... /home2/majordomo/wrapper: error: recompile with POSIX flags. "|/home2/majordomo/wrapper majordomo"... unknown mailer error 4 owner-majordomo... aliased to sysop Postmaster... aliased to sysop sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent I believe that this error is due to the wrapper compile error! --------------------------------------------------------- Robin Stuart The Gate Keeper! stuartr@pschools.st-albert.ab.ca [PC Eudora v1.4.4] St. Albert Protestant Schools (403)460-3712 "Opening up your mind to the world is called learning!" --------------------------------------------------------- From list-managers-owner Thu Mar 30 04:50:21 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id EAA22560 for list-managers-outgoing; Thu, 30 Mar 1995 04:43:10 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id EAA22553 for ; Thu, 30 Mar 1995 04:43:07 -0800 Message-Id: <199503301240.FAA27028@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id FAA27028; Thu, 30 Mar 1995 05:40:34 -0700 From: stp@earthlink.net (Stephen Porter) Subject: MajorDomo Question To: List-Managers@GreatCircle.COM (List-Managers@greatcircle.com) Date: Wed, 29 Mar 1995 23:45:57 -0800 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk To: ron@apollo.theta.com, stp@earthlink.net Cc: dhelrod@apollo.theta.com Subject: MajorDomo Question Date: Wed, 29 Mar 1995 16:17:58 -0800 From: "David H. Elrod" Do either of you know of a feature that would allow anyone NOT in some list post a message? This would be a "kill" feature to keep specific people from posting. Any ideas? dhelrod Stephen T. Porter / Los Angeles, CA stp@earthlink.net From list-managers-owner Thu Mar 30 04:51:59 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id EAA22566 for list-managers-outgoing; Thu, 30 Mar 1995 04:43:13 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id EAA22559 for ; Thu, 30 Mar 1995 04:43:09 -0800 Message-Id: <199503301240.FAA27040@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id FAA27040; Thu, 30 Mar 1995 05:40:36 -0700 From: stuartr@pschools.st-albert.ab.ca (Robin Stuart) Subject: UnixWare 1.1.3 & Majordomo 93 To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 95 01:54 MST Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I'm using UnixWare 1.1.3 and have the SDK 1.1 installed. I'm no expert in "C" and so I can'nt figure out the following error. Any ideas?? Thanks in advance! --------------------------------------------------------------------- Makefile: W_BIN=/home2/majordomo W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh W_MAJORDOMO_CF=$(W_BIN)/majordomo.cf # W_USER=daemon W_USER=majordom W_GROUP=majordom # W_CHOWN=${W_USER}.${W_GROUP} W_CHOWN=${W_USER} W_CHMOD=6755 WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" --------------------------------------------------------------------- # make wrapper cc -DBIN=\"/home2/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -DHOME=\"HOME=/home2/majordomo\" -DSHELL=\"SHELL=/bin/csh\" -DMAJORDOMO_CF= \"MAJORDOMO_CF=/home2/majordomo/majordomo.cf\" -o wrapper wrapper.c UX:acomp: WARNING: "wrapper.c", line 65: warning: improper pointer/integer combi nation: op "!=" ************************************************ Can anybody tell me whats going on with line 65? ************************************************ --------------------------------------------------------------------- /usr/ucblib/aliases: ####################### # Local aliases below # ####################### owner-owner: postmaster # Majordomo owner-majordomo: sysop majordomo: "|/home2/majordomo/wrapper majordomo" majordom: owner-majordomo Majordomo-Owner: owner-majordomo --------------------------------------------------------------------- # echo help | /usr/ucblib/sendmail -v majordomo majordomo... aliased to "|/home2/majordomo/wrapper majordomo" "|/home2/majordomo/wrapper majordomo"... Connecting to via prog... /home2/majordomo/wrapper: error: recompile with POSIX flags. "|/home2/majordomo/wrapper majordomo"... unknown mailer error 4 owner-majordomo... aliased to sysop Postmaster... aliased to sysop sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent I believe that this error is due to the wrapper compile error! --------------------------------------------------------- Robin Stuart The Gate Keeper! stuartr@pschools.st-albert.ab.ca [PC Eudora v1.4.4] St. Albert Protestant Schools (403)460-3712 "Opening up your mind to the world is called learning!" --------------------------------------------------------- From list-managers-owner Thu Mar 30 05:50:38 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id FAA23716 for list-managers-outgoing; Thu, 30 Mar 1995 05:49:42 -0800 Received: from FSM-1.PICA.ARMY.MIL (fsm-1.pica.army.mil [129.139.164.101]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id FAA23711 for ; Thu, 30 Mar 1995 05:49:40 -0800 Date: Thu, 30 Mar 95 8:49:47 EST From: Info-LabVIEW List Maintainer To: list-managers@greatcircle.com Subject: Please read and heed Organization: Electric Armts Div, US Army ARDEC, Picatinny Arsenal, NJ Message-ID: <9503300849.aa09279@fsm-1.pica.army.mil> Sender: list-managers-owner@GreatCircle.COM Precedence: bulk This is the List Managers list. It is not the majordomo list. If there's any part of that last paragraph you'd like clarified, please feel free to contact me directly. Tom Coradeschi, Info-LabVIEW List Maintainer http://k-whiner.pica.army.mil/info-labview.html From list-managers-owner Thu Mar 30 05:53:23 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id FAA23642 for list-managers-outgoing; Thu, 30 Mar 1995 05:43:15 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id FAA23634 for ; Thu, 30 Mar 1995 05:43:12 -0800 Message-Id: <199503301340.GAA27716@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id GAA27716; Thu, 30 Mar 1995 06:40:39 -0700 From: stp@earthlink.net (Stephen Porter) Subject: MajorDomo Question To: List-Managers@GreatCircle.COM (List-Managers@greatcircle.com) Date: Wed, 29 Mar 1995 23:45:57 -0800 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk To: ron@apollo.theta.com, stp@earthlink.net Cc: dhelrod@apollo.theta.com Subject: MajorDomo Question Date: Wed, 29 Mar 1995 16:17:58 -0800 From: "David H. Elrod" Do either of you know of a feature that would allow anyone NOT in some list post a message? This would be a "kill" feature to keep specific people from posting. Any ideas? dhelrod Stephen T. Porter / Los Angeles, CA stp@earthlink.net From list-managers-owner Thu Mar 30 05:55:56 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id FAA23646 for list-managers-outgoing; Thu, 30 Mar 1995 05:43:17 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id FAA23636 for ; Thu, 30 Mar 1995 05:43:13 -0800 Message-Id: <199503301340.GAA27724@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id GAA27724; Thu, 30 Mar 1995 06:40:40 -0700 From: stuartr@pschools.st-albert.ab.ca (Robin Stuart) Subject: UnixWare 1.1.3 & Majordomo 93 To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 95 01:54 MST Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I'm using UnixWare 1.1.3 and have the SDK 1.1 installed. I'm no expert in "C" and so I can'nt figure out the following error. Any ideas?? Thanks in advance! --------------------------------------------------------------------- Makefile: W_BIN=/home2/majordomo W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh W_MAJORDOMO_CF=$(W_BIN)/majordomo.cf # W_USER=daemon W_USER=majordom W_GROUP=majordom # W_CHOWN=${W_USER}.${W_GROUP} W_CHOWN=${W_USER} W_CHMOD=6755 WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" --------------------------------------------------------------------- # make wrapper cc -DBIN=\"/home2/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -DHOME=\"HOME=/home2/majordomo\" -DSHELL=\"SHELL=/bin/csh\" -DMAJORDOMO_CF= \"MAJORDOMO_CF=/home2/majordomo/majordomo.cf\" -o wrapper wrapper.c UX:acomp: WARNING: "wrapper.c", line 65: warning: improper pointer/integer combi nation: op "!=" ************************************************ Can anybody tell me whats going on with line 65? ************************************************ --------------------------------------------------------------------- /usr/ucblib/aliases: ####################### # Local aliases below # ####################### owner-owner: postmaster # Majordomo owner-majordomo: sysop majordomo: "|/home2/majordomo/wrapper majordomo" majordom: owner-majordomo Majordomo-Owner: owner-majordomo --------------------------------------------------------------------- # echo help | /usr/ucblib/sendmail -v majordomo majordomo... aliased to "|/home2/majordomo/wrapper majordomo" "|/home2/majordomo/wrapper majordomo"... Connecting to via prog... /home2/majordomo/wrapper: error: recompile with POSIX flags. "|/home2/majordomo/wrapper majordomo"... unknown mailer error 4 owner-majordomo... aliased to sysop Postmaster... aliased to sysop sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent I believe that this error is due to the wrapper compile error! --------------------------------------------------------- Robin Stuart The Gate Keeper! stuartr@pschools.st-albert.ab.ca [PC Eudora v1.4.4] St. Albert Protestant Schools (403)460-3712 "Opening up your mind to the world is called learning!" --------------------------------------------------------- From list-managers-owner Thu Mar 30 06:51:26 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id GAA24938 for list-managers-outgoing; Thu, 30 Mar 1995 06:43:28 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id GAA24922 for ; Thu, 30 Mar 1995 06:43:23 -0800 Message-Id: <199503301440.HAA28782@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id HAA28782; Thu, 30 Mar 1995 07:40:50 -0700 From: Info-LabVIEW List Maintainer Subject: Please read and heed To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 95 8:49:47 EST Sender: list-managers-owner@GreatCircle.COM Precedence: bulk This is the List Managers list. It is not the majordomo list. If there's any part of that last paragraph you'd like clarified, please feel free to contact me directly. Tom Coradeschi, Info-LabVIEW List Maintainer http://k-whiner.pica.army.mil/info-labview.html From list-managers-owner Thu Mar 30 06:55:07 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id GAA24939 for list-managers-outgoing; Thu, 30 Mar 1995 06:43:29 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id GAA24925 for ; Thu, 30 Mar 1995 06:43:25 -0800 Message-Id: <199503301440.HAA28787@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id HAA28787; Thu, 30 Mar 1995 07:40:52 -0700 From: stp@earthlink.net (Stephen Porter) Subject: MajorDomo Question To: List-Managers@GreatCircle.COM (List-Managers@greatcircle.com) Date: Wed, 29 Mar 1995 23:45:57 -0800 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk To: ron@apollo.theta.com, stp@earthlink.net Cc: dhelrod@apollo.theta.com Subject: MajorDomo Question Date: Wed, 29 Mar 1995 16:17:58 -0800 From: "David H. Elrod" Do either of you know of a feature that would allow anyone NOT in some list post a message? This would be a "kill" feature to keep specific people from posting. Any ideas? dhelrod Stephen T. Porter / Los Angeles, CA stp@earthlink.net From list-managers-owner Thu Mar 30 06:57:39 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id GAA24685 for list-managers-outgoing; Thu, 30 Mar 1995 06:28:38 -0800 Received: from flash (flash.flashback.com [199.227.19.33]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id GAA24677 for ; Thu, 30 Mar 1995 06:28:18 -0800 Received: from monday.FlashBack.COM by flash (5.0/SMI-SVR4) id AA08832; Thu, 30 Mar 1995 09:20:33 +0500 Received: by monday.FlashBack.COM (5.x/SMI-SVR4) id AA08652; Thu, 30 Mar 1995 09:15:37 -0500 Date: Thu, 30 Mar 1995 09:15:37 -0500 From: flash@FlashBack.COM (FlashBack) Message-Id: <9503301415.AA08652@monday.FlashBack.COM> To: list-managers@greatcircle.com Subject: MIME/MailTool mailing lists X-Sun-Charset: US-ASCII content-length: 1478 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I run a couple of large mailing lists, SunFlash and FlashBack, for users of Sun computers. Over the last year or so I have been offering a weekly digest in Sun's MailTool format. That is, the message body has a brief synopsis for each article posted that week and the full-text of all the articles included as MailTool attachements. After running the weekly version with a couple of hundred subscribers, I added MIME support. Since the start of this year, I have been offering my 'daily' lists in MIME and MailTool format. I have been encouraging people to move to the "multi-media" lists. I now have about 2,000 multi-media subscribers (of my 150,000+ subscriber base). My goal is to create an audience that can accept pictures, audio clips, PostScipt documents, screen shots, etc. Before I get too carried away, I was wondering, is anyone else is running 'multi-media' lists with MIME or MailTool ? Are there issues that I should be aware of ? Thanks! -johnj (I use majordomo to manage the distribution lists, and customer programs for formatting and posting.) John J. Mclaughlin Publisher/Editor SunFlash & FlashBack 1981 NW 38th Terrace Coconut Creek FL 33066 USA flash@flash@Flashback.COM (305) 351 4909 FAX (305) 776 7963 Sun Users Group Board Member Senior Sun Systems Engineer flash@Sun.COM http://www.flashback.com http://www.sun.com/sunflash ftp://draco.nova.edu/pub/sunflash/www/index.html From list-managers-owner Thu Mar 30 07:02:08 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id GAA24944 for list-managers-outgoing; Thu, 30 Mar 1995 06:43:33 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id GAA24937 for ; Thu, 30 Mar 1995 06:43:27 -0800 Message-Id: <199503301440.HAA28797@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id HAA28797; Thu, 30 Mar 1995 07:40:55 -0700 From: stuartr@pschools.st-albert.ab.ca (Robin Stuart) Subject: UnixWare 1.1.3 & Majordomo 93 To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 95 01:54 MST Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I'm using UnixWare 1.1.3 and have the SDK 1.1 installed. I'm no expert in "C" and so I can'nt figure out the following error. Any ideas?? Thanks in advance! --------------------------------------------------------------------- Makefile: W_BIN=/home2/majordomo W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh W_MAJORDOMO_CF=$(W_BIN)/majordomo.cf # W_USER=daemon W_USER=majordom W_GROUP=majordom # W_CHOWN=${W_USER}.${W_GROUP} W_CHOWN=${W_USER} W_CHMOD=6755 WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" --------------------------------------------------------------------- # make wrapper cc -DBIN=\"/home2/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -DHOME=\"HOME=/home2/majordomo\" -DSHELL=\"SHELL=/bin/csh\" -DMAJORDOMO_CF= \"MAJORDOMO_CF=/home2/majordomo/majordomo.cf\" -o wrapper wrapper.c UX:acomp: WARNING: "wrapper.c", line 65: warning: improper pointer/integer combi nation: op "!=" ************************************************ Can anybody tell me whats going on with line 65? ************************************************ --------------------------------------------------------------------- /usr/ucblib/aliases: ####################### # Local aliases below # ####################### owner-owner: postmaster # Majordomo owner-majordomo: sysop majordomo: "|/home2/majordomo/wrapper majordomo" majordom: owner-majordomo Majordomo-Owner: owner-majordomo --------------------------------------------------------------------- # echo help | /usr/ucblib/sendmail -v majordomo majordomo... aliased to "|/home2/majordomo/wrapper majordomo" "|/home2/majordomo/wrapper majordomo"... Connecting to via prog... /home2/majordomo/wrapper: error: recompile with POSIX flags. "|/home2/majordomo/wrapper majordomo"... unknown mailer error 4 owner-majordomo... aliased to sysop Postmaster... aliased to sysop sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent I believe that this error is due to the wrapper compile error! --------------------------------------------------------- Robin Stuart The Gate Keeper! stuartr@pschools.st-albert.ab.ca [PC Eudora v1.4.4] St. Albert Protestant Schools (403)460-3712 "Opening up your mind to the world is called learning!" --------------------------------------------------------- From list-managers-owner Thu Mar 30 07:22:01 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA25634 for list-managers-outgoing; Thu, 30 Mar 1995 07:05:28 -0800 Received: from SEARN.SUNET.SE (searn.sunet.se [192.36.125.4]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id HAA25621 for ; Thu, 30 Mar 1995 07:05:22 -0800 Message-Id: <199503301505.HAA25621@miles.greatcircle.com> Received: from SEARN.SUNET.SE by SEARN.SUNET.SE (IBM VM SMTP V2R2) with BSMTP id 1244; Thu, 30 Mar 95 16:58:54 +0200 Received: from SEARN.SUNET.SE (NJE origin ERIC@SEARN) by SEARN.SUNET.SE (LMail V1.2a/1.8a) with RFC822 id 6572; Thu, 30 Mar 1995 16:58:53 +0200 Date: Thu, 30 Mar 1995 16:49:17 +0200 From: Eric Thomas Subject: Re: Please read and heed To: list-managers@GreatCircle.COM In-Reply-To: Message of Thu, 30 Mar 95 8:49:47 EST from list-managers-owner@GreatCircle.COM Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Having had to deal with (involuntary) user support for about 10 years, I can safely say that there are only two ways to make users not use a service that they find useful but are not supposed to use. One is to prevent them from accessing the service altogether, which in this case is not possible. The other is to make the service unuseful to them, in other words, stop answering Majordomo questions on this list. Educating the users is always a good idea, but they are so numerous that even if 10% ignore the warnings, it will be 10 times above the pain threshold. And then you have the "why not me?" syndrome, the 75% or so of users who reluctantly heed the warning see Joe Bloke use the list anyway and get the answer he wants, and after 3-4 occurrences they figure that if it's ok for Joe, there's no reason for them not to do the same thing. Now if instead of answering the questions, you always reply that this is the wrong list and people should use list XYZ instead, users will get used to the fact that you don't get answers from this list, and quit polluting. Eric From list-managers-owner Thu Mar 30 07:51:18 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA26840 for list-managers-outgoing; Thu, 30 Mar 1995 07:43:25 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id HAA26829 for ; Thu, 30 Mar 1995 07:43:21 -0800 Message-Id: <199503301540.IAA00725@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id IAA00725; Thu, 30 Mar 1995 08:40:48 -0700 From: Info-LabVIEW List Maintainer Subject: Please read and heed To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 95 8:49:47 EST Sender: list-managers-owner@GreatCircle.COM Precedence: bulk This is the List Managers list. It is not the majordomo list. If there's any part of that last paragraph you'd like clarified, please feel free to contact me directly. Tom Coradeschi, Info-LabVIEW List Maintainer http://k-whiner.pica.army.mil/info-labview.html From list-managers-owner Thu Mar 30 07:54:27 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA26844 for list-managers-outgoing; Thu, 30 Mar 1995 07:43:28 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id HAA26831 for ; Thu, 30 Mar 1995 07:43:23 -0800 Message-Id: <199503301540.IAA00733@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id IAA00733; Thu, 30 Mar 1995 08:40:50 -0700 From: stp@earthlink.net (Stephen Porter) Subject: MajorDomo Question To: List-Managers@GreatCircle.COM (List-Managers@greatcircle.com) Date: Wed, 29 Mar 1995 23:45:57 -0800 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk To: ron@apollo.theta.com, stp@earthlink.net Cc: dhelrod@apollo.theta.com Subject: MajorDomo Question Date: Wed, 29 Mar 1995 16:17:58 -0800 From: "David H. Elrod" Do either of you know of a feature that would allow anyone NOT in some list post a message? This would be a "kill" feature to keep specific people from posting. Any ideas? dhelrod Stephen T. Porter / Los Angeles, CA stp@earthlink.net From list-managers-owner Thu Mar 30 07:58:38 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA26895 for list-managers-outgoing; Thu, 30 Mar 1995 07:43:45 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id HAA26858 for ; Thu, 30 Mar 1995 07:43:33 -0800 Message-Id: <199503301541.IAA00782@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id IAA00782; Thu, 30 Mar 1995 08:41:00 -0700 From: Eric Thomas Subject: Re: Please read and heed To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 1995 16:49:17 +0200 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Having had to deal with (involuntary) user support for about 10 years, I can safely say that there are only two ways to make users not use a service that they find useful but are not supposed to use. One is to prevent them from accessing the service altogether, which in this case is not possible. The other is to make the service unuseful to them, in other words, stop answering Majordomo questions on this list. Educating the users is always a good idea, but they are so numerous that even if 10% ignore the warnings, it will be 10 times above the pain threshold. And then you have the "why not me?" syndrome, the 75% or so of users who reluctantly heed the warning see Joe Bloke use the list anyway and get the answer he wants, and after 3-4 occurrences they figure that if it's ok for Joe, there's no reason for them not to do the same thing. Now if instead of answering the questions, you always reply that this is the wrong list and people should use list XYZ instead, users will get used to the fact that you don't get answers from this list, and quit polluting. Eric From list-managers-owner Thu Mar 30 08:04:44 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA26857 for list-managers-outgoing; Thu, 30 Mar 1995 07:43:34 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id HAA26843 for ; Thu, 30 Mar 1995 07:43:27 -0800 Message-Id: <199503301540.IAA00751@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id IAA00751; Thu, 30 Mar 1995 08:40:53 -0700 From: flash@FlashBack.COM (FlashBack) Subject: MIME/MailTool mailing lists To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 1995 09:15:37 -0500 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I run a couple of large mailing lists, SunFlash and FlashBack, for users of Sun computers. Over the last year or so I have been offering a weekly digest in Sun's MailTool format. That is, the message body has a brief synopsis for each article posted that week and the full-text of all the articles included as MailTool attachements. After running the weekly version with a couple of hundred subscribers, I added MIME support. Since the start of this year, I have been offering my 'daily' lists in MIME and MailTool format. I have been encouraging people to move to the "multi-media" lists. I now have about 2,000 multi-media subscribers (of my 150,000+ subscriber base). My goal is to create an audience that can accept pictures, audio clips, PostScipt documents, screen shots, etc. Before I get too carried away, I was wondering, is anyone else is running 'multi-media' lists with MIME or MailTool ? Are there issues that I should be aware of ? Thanks! -johnj (I use majordomo to manage the distribution lists, and customer programs for formatting and posting.) John J. Mclaughlin Publisher/Editor SunFlash & FlashBack 1981 NW 38th Terrace Coconut Creek FL 33066 USA flash@flash@Flashback.COM (305) 351 4909 FAX (305) 776 7963 Sun Users Group Board Member Senior Sun Systems Engineer flash@Sun.COM http://www.flashback.com http://www.sun.com/sunflash ftp://draco.nova.edu/pub/sunflash/www/index.html From list-managers-owner Thu Mar 30 08:09:50 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id HAA26870 for list-managers-outgoing; Thu, 30 Mar 1995 07:43:38 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id HAA26845 for ; Thu, 30 Mar 1995 07:43:28 -0800 Message-Id: <199503301540.IAA00758@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id IAA00758; Thu, 30 Mar 1995 08:40:54 -0700 From: stuartr@pschools.st-albert.ab.ca (Robin Stuart) Subject: UnixWare 1.1.3 & Majordomo 93 To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 95 01:54 MST Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I'm using UnixWare 1.1.3 and have the SDK 1.1 installed. I'm no expert in "C" and so I can'nt figure out the following error. Any ideas?? Thanks in advance! --------------------------------------------------------------------- Makefile: W_BIN=/home2/majordomo W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh W_MAJORDOMO_CF=$(W_BIN)/majordomo.cf # W_USER=daemon W_USER=majordom W_GROUP=majordom # W_CHOWN=${W_USER}.${W_GROUP} W_CHOWN=${W_USER} W_CHMOD=6755 WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" --------------------------------------------------------------------- # make wrapper cc -DBIN=\"/home2/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -DHOME=\"HOME=/home2/majordomo\" -DSHELL=\"SHELL=/bin/csh\" -DMAJORDOMO_CF= \"MAJORDOMO_CF=/home2/majordomo/majordomo.cf\" -o wrapper wrapper.c UX:acomp: WARNING: "wrapper.c", line 65: warning: improper pointer/integer combi nation: op "!=" ************************************************ Can anybody tell me whats going on with line 65? ************************************************ --------------------------------------------------------------------- /usr/ucblib/aliases: ####################### # Local aliases below # ####################### owner-owner: postmaster # Majordomo owner-majordomo: sysop majordomo: "|/home2/majordomo/wrapper majordomo" majordom: owner-majordomo Majordomo-Owner: owner-majordomo --------------------------------------------------------------------- # echo help | /usr/ucblib/sendmail -v majordomo majordomo... aliased to "|/home2/majordomo/wrapper majordomo" "|/home2/majordomo/wrapper majordomo"... Connecting to via prog... /home2/majordomo/wrapper: error: recompile with POSIX flags. "|/home2/majordomo/wrapper majordomo"... unknown mailer error 4 owner-majordomo... aliased to sysop Postmaster... aliased to sysop sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent I believe that this error is due to the wrapper compile error! --------------------------------------------------------- Robin Stuart The Gate Keeper! stuartr@pschools.st-albert.ab.ca [PC Eudora v1.4.4] St. Albert Protestant Schools (403)460-3712 "Opening up your mind to the world is called learning!" --------------------------------------------------------- From list-managers-owner Thu Mar 30 08:51:21 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id IAA28553 for list-managers-outgoing; Thu, 30 Mar 1995 08:43:23 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id IAA28548 for ; Thu, 30 Mar 1995 08:43:20 -0800 Message-Id: <199503301640.JAA04376@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id JAA04376; Thu, 30 Mar 1995 09:40:48 -0700 From: Info-LabVIEW List Maintainer Subject: Please read and heed To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 95 8:49:47 EST Sender: list-managers-owner@GreatCircle.COM Precedence: bulk This is the List Managers list. It is not the majordomo list. If there's any part of that last paragraph you'd like clarified, please feel free to contact me directly. Tom Coradeschi, Info-LabVIEW List Maintainer http://k-whiner.pica.army.mil/info-labview.html From list-managers-owner Thu Mar 30 09:21:49 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id IAA28564 for list-managers-outgoing; Thu, 30 Mar 1995 08:43:30 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id IAA28555 for ; Thu, 30 Mar 1995 08:43:25 -0800 Message-Id: <199503301640.JAA04401@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id JAA04401; Thu, 30 Mar 1995 09:40:53 -0700 From: stp@earthlink.net (Stephen Porter) Subject: MajorDomo Question To: List-Managers@GreatCircle.COM (List-Managers@greatcircle.com) Date: Wed, 29 Mar 1995 23:45:57 -0800 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk To: ron@apollo.theta.com, stp@earthlink.net Cc: dhelrod@apollo.theta.com Subject: MajorDomo Question Date: Wed, 29 Mar 1995 16:17:58 -0800 From: "David H. Elrod" Do either of you know of a feature that would allow anyone NOT in some list post a message? This would be a "kill" feature to keep specific people from posting. Any ideas? dhelrod Stephen T. Porter / Los Angeles, CA stp@earthlink.net From list-managers-owner Thu Mar 30 09:25:34 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id IAA28572 for list-managers-outgoing; Thu, 30 Mar 1995 08:43:32 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id IAA28563 for ; Thu, 30 Mar 1995 08:43:28 -0800 Message-Id: <199503301640.JAA04411@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id JAA04411; Thu, 30 Mar 1995 09:40:55 -0700 From: Eric Thomas Subject: Re: Please read and heed To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 1995 16:49:17 +0200 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Having had to deal with (involuntary) user support for about 10 years, I can safely say that there are only two ways to make users not use a service that they find useful but are not supposed to use. One is to prevent them from accessing the service altogether, which in this case is not possible. The other is to make the service unuseful to them, in other words, stop answering Majordomo questions on this list. Educating the users is always a good idea, but they are so numerous that even if 10% ignore the warnings, it will be 10 times above the pain threshold. And then you have the "why not me?" syndrome, the 75% or so of users who reluctantly heed the warning see Joe Bloke use the list anyway and get the answer he wants, and after 3-4 occurrences they figure that if it's ok for Joe, there's no reason for them not to do the same thing. Now if instead of answering the questions, you always reply that this is the wrong list and people should use list XYZ instead, users will get used to the fact that you don't get answers from this list, and quit polluting. Eric From list-managers-owner Thu Mar 30 09:31:04 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id IAA28597 for list-managers-outgoing; Thu, 30 Mar 1995 08:43:43 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id IAA28575 for ; Thu, 30 Mar 1995 08:43:35 -0800 Message-Id: <199503301641.JAA04441@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id JAA04441; Thu, 30 Mar 1995 09:41:01 -0700 From: flash@FlashBack.COM (FlashBack) Subject: MIME/MailTool mailing lists To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 1995 09:15:37 -0500 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I run a couple of large mailing lists, SunFlash and FlashBack, for users of Sun computers. Over the last year or so I have been offering a weekly digest in Sun's MailTool format. That is, the message body has a brief synopsis for each article posted that week and the full-text of all the articles included as MailTool attachements. After running the weekly version with a couple of hundred subscribers, I added MIME support. Since the start of this year, I have been offering my 'daily' lists in MIME and MailTool format. I have been encouraging people to move to the "multi-media" lists. I now have about 2,000 multi-media subscribers (of my 150,000+ subscriber base). My goal is to create an audience that can accept pictures, audio clips, PostScipt documents, screen shots, etc. Before I get too carried away, I was wondering, is anyone else is running 'multi-media' lists with MIME or MailTool ? Are there issues that I should be aware of ? Thanks! -johnj (I use majordomo to manage the distribution lists, and customer programs for formatting and posting.) John J. Mclaughlin Publisher/Editor SunFlash & FlashBack 1981 NW 38th Terrace Coconut Creek FL 33066 USA flash@flash@Flashback.COM (305) 351 4909 FAX (305) 776 7963 Sun Users Group Board Member Senior Sun Systems Engineer flash@Sun.COM http://www.flashback.com http://www.sun.com/sunflash ftp://draco.nova.edu/pub/sunflash/www/index.html From list-managers-owner Thu Mar 30 09:33:34 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id IAA28098 for list-managers-outgoing; Thu, 30 Mar 1995 08:22:12 -0800 Received: from SYSWRK.UCIS.Dal.Ca (syswrk.UCIS.Dal.Ca [129.173.2.108]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id IAA28087 for ; Thu, 30 Mar 1995 08:22:06 -0800 Received: from AC.Dal.Ca by SYSWRK.UCIS.DAL.CA (PMDF V4.3-13 #6307) id <01HOQW7PLUA8002PC0@SYSWRK.UCIS.DAL.CA>; Thu, 30 Mar 1995 12:19:04 -0400 Received: from biome.bio.dfo.ca by AC.DAL.CA (PMDF V4.3-13 #6307) id <01HOQW79YAW0002NSV@AC.DAL.CA>; Thu, 30 Mar 1995 12:18:32 -0400 Received: by biome.bio.dfo.ca (931110.SGI/931108.SGI.ANONFTP) for @ac.dal.ca:List-Managers@GreatCircle.COM id AA08636; Thu, 30 Mar 95 11:50:37 -0400 Date: Thu, 30 Mar 1995 11:50:36 -0400 (AST) From: bill@biome.bio.dfo.ca (Bill Silvert) Subject: Re: MIME/MailTool mailing lists In-reply-to: <9503301415.AA08652@monday.FlashBack.COM> from "FlashBack" at Mar 30, 95 09:15:37 am To: List-Managers@GreatCircle.COM (List Managers) Message-id: <9503301550.AA08636@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 Content-length: 1369 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk >After running the weekly version with a couple of hundred subscribers, >I added MIME support. Since the start of this year, I have been offering >my 'daily' lists in MIME and MailTool format. I have been encouraging >people to move to the "multi-media" lists. I now have about 2,000 >multi-media subscribers (of my 150,000+ subscriber base). > >My goal is to create an audience that can accept pictures, audio clips, >PostScipt documents, screen shots, etc. Before I get too carried >away, I was wondering, is anyone else is running 'multi-media' lists >with MIME or MailTool ? Are there issues that I should be aware of ? If a list's subscribers are sophisticated and know how to deal with this, fine, but I would suggest proceeding with caution. I run about 30 lists which address scientific issues, and most of the subscribers are baffled and irritated by the occasional MIME-encoded or UUencoded message that gets posted. For a list dealing with multi-media it would be great, but I wouldn't dream of doing it on a habitat ecology list. In fact, I'm thinking of installing a filter to bounce encoded messages to me for processing! -- Bill Silvert, Habitat Ecology Div., Bedford Inst. Oceanography P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2 Personal InterNet Address: silvert@biome.bio.ns.ca HED runs a WWW server at URL=http://biome.bio.dfo.ca From list-managers-owner Thu Mar 30 09:39:25 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id IAA28600 for list-managers-outgoing; Thu, 30 Mar 1995 08:43:45 -0800 Received: from meeker.UCAR.EDU (meeker.ucar.edu [128.117.64.25]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id IAA28584 for ; Thu, 30 Mar 1995 08:43:38 -0800 Message-Id: <199503301641.JAA04456@meeker.ucar.EDU> Received: by meeker.ucar.EDU (NCAR-local/ NCAR Backup Central Post Office 04/22/91) id JAA04456; Thu, 30 Mar 1995 09:41:04 -0700 From: stuartr@pschools.st-albert.ab.ca (Robin Stuart) Subject: UnixWare 1.1.3 & Majordomo 93 To: list-managers@GreatCircle.COM Date: Thu, 30 Mar 95 01:54 MST Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I'm using UnixWare 1.1.3 and have the SDK 1.1 installed. I'm no expert in "C" and so I can'nt figure out the following error. Any ideas?? Thanks in advance! --------------------------------------------------------------------- Makefile: W_BIN=/home2/majordomo W_PATH=/bin:/usr/bin:/usr/ucb W_HOME=${W_BIN} W_SHELL=/bin/csh W_MAJORDOMO_CF=$(W_BIN)/majordomo.cf # W_USER=daemon W_USER=majordom W_GROUP=majordom # W_CHOWN=${W_USER}.${W_GROUP} W_CHOWN=${W_USER} W_CHMOD=6755 WRAPPER_FLAGS = -DBIN=\"${W_BIN}\" -DPATH=\"PATH=${W_PATH}\" \ -DHOME=\"HOME=${W_HOME}\" -DSHELL=\"SHELL=${W_SHELL}\" \ -DMAJORDOMO_CF=\"MAJORDOMO_CF=${W_MAJORDOMO_CF}\" --------------------------------------------------------------------- # make wrapper cc -DBIN=\"/home2/majordomo\" -DPATH=\"PATH=/bin:/usr/bin:/usr/ucb\" -DHOME=\"HOME=/home2/majordomo\" -DSHELL=\"SHELL=/bin/csh\" -DMAJORDOMO_CF= \"MAJORDOMO_CF=/home2/majordomo/majordomo.cf\" -o wrapper wrapper.c UX:acomp: WARNING: "wrapper.c", line 65: warning: improper pointer/integer combi nation: op "!=" ************************************************ Can anybody tell me whats going on with line 65? ************************************************ --------------------------------------------------------------------- /usr/ucblib/aliases: ####################### # Local aliases below # ####################### owner-owner: postmaster # Majordomo owner-majordomo: sysop majordomo: "|/home2/majordomo/wrapper majordomo" majordom: owner-majordomo Majordomo-Owner: owner-majordomo --------------------------------------------------------------------- # echo help | /usr/ucblib/sendmail -v majordomo majordomo... aliased to "|/home2/majordomo/wrapper majordomo" "|/home2/majordomo/wrapper majordomo"... Connecting to via prog... /home2/majordomo/wrapper: error: recompile with POSIX flags. "|/home2/majordomo/wrapper majordomo"... unknown mailer error 4 owner-majordomo... aliased to sysop Postmaster... aliased to sysop sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent sysop... Connecting to via local... UX:rmail: ERROR: Cannot open /var/mail/: Is a directory sysop... Sent I believe that this error is due to the wrapper compile error! --------------------------------------------------------- Robin Stuart The Gate Keeper! stuartr@pschools.st-albert.ab.ca [PC Eudora v1.4.4] St. Albert Protestant Schools (403)460-3712 "Opening up your mind to the world is called learning!" --------------------------------------------------------- From list-managers-owner Thu Mar 30 09:51:00 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id JAA29161 for list-managers-outgoing; Thu, 30 Mar 1995 09:20:21 -0800 Received: from vhipub.vhi.com (VHIPUB.VHI.COM [167.18.73.5]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id JAA29156 for ; Thu, 30 Mar 1995 09:20:18 -0800 Received: from [167.18.110.3] by vhipub.vhi.com with SMTP (5.65/1.2-eef) id AA08111; Thu, 30 Mar 95 12:17:44 -0500 Received: from paul.mis.vrx.vhi.com by av2.vrx.vhi.com (5.4R2.10/1.3) id AA25991; Thu, 30 Mar 1995 09:17:24 -0800 X-Organization: RxNet, Inc. Fresno, CA 800/447-9638 To: list-managers@greatcircle.com From: Paul-Joseph de Werk Subject: Re: Please read and heed X-Originating-Host: paul.mis.vrx.vhi.com In-Reply-To: <9503300849.aa09279@fsm-1.pica.army.mil> Message-Id: <1995Mar29.091756-0800@paul.mis.vrx.vhi.com> Date: 29 Mar 1995 09:17:54 -0800 Mime-Version: 1.0 X-Mailer: BWMail for Windows Version 3.2 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk info list-managers __________________________________________________________________________ [ Paul-Joseph de Werk, B.S. \ RX Net, Inc. ] [ Systems Analyst II \ MIS Dept. ] [ \ vrx: paul@av2.vrx.vhi.com ] [ \ inet: paul%av2.vrx.vhi.com@vhipub.vhi.com ] [_______________________________\__________________________________________] From list-managers-owner Thu Mar 30 10:51:02 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA01227 for list-managers-outgoing; Thu, 30 Mar 1995 10:49:35 -0800 Received: from ncar.UCAR.EDU (ncar.ucar.edu [192.52.106.6]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id KAA01222 for ; Thu, 30 Mar 1995 10:49:31 -0800 Message-Id: <199503301846.LAA14907@ncar.ucar.EDU> Received: by ncar.ucar.EDU (NCAR-local/ NCAR Central Post Office 03/11/93) id LAA14907; Thu, 30 Mar 1995 11:46:56 -0700 Subject: mail list loop: mea culpa To: list-managers@greatcircle.com Date: Thu, 30 Mar 95 11:46:55 MST From: woods@ncar.ucar.edu (Greg Woods) X-Mailer: ELM [version 2.3 PL11] Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I am about as red faced as I have been in a long, long time, but suffice it to say that a cron script I was running was responsible for looping every message I got from any mailing list that puts its own submission address in the To: header (as many lists do) back to the list, due to a call to "sendmail -t". Serves me right for running a script I got from someone else without bothering to analyze it first. (Naturally, it worked fine for *him* since he does not subscribe to any mail lists and therefore the To: header never contained anything but his own address). My sincere apologies for the inconvenience this undoubtedly caused everyone on these lists. --Greg From list-managers-owner Thu Mar 30 10:54:33 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id KAA01024 for list-managers-outgoing; Thu, 30 Mar 1995 10:34:38 -0800 Received: from sunshine.eushc.org (sunshine.eushc.org [163.246.96.102]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id KAA01019 for ; Thu, 30 Mar 1995 10:34:35 -0800 Received: from mind.org (root@mind.org [163.246.10.101]) by sunshine.eushc.org (8.6.10/EUSHC) with ESMTP id NAA16441; Thu, 30 Mar 1995 13:32:00 -0500 Received: by mind.org (8.6.11/mind.org) with UUCP id NAA31302; Thu, 30 Mar 1995 13:18:27 -0500 Received: by knex.mind.org (1.65/waf) via UUCP; Thu, 30 Mar 95 11:47:41 EST for list-managers@GreatCircle.COM To: list-managers@GreatCircle.COM Subject: Re: Please read and heed From: Gess Shankar Reply-To: gess@knex.mind.org (Gess Shankar) Message-ID: <3Fcs3c1w165w@knex.mind.org> Date: Thu, 30 Mar 95 11:46:25 EST In-Reply-To: <199503301540.IAA00725@meeker.ucar.EDU> Organization: |<><>| Knowledge Exchange, GA, USA |<><>| Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Info-LabVIEW List Maintainer writes: > This is the List Managers list. It is not the majordomo list. > > If there's any part of that last paragraph you'd like clarified, please feel > free to contact me directly. > This and a few other postings (perhaps all the postings) are being recirculated again and again. Perhaps some subscriber site is sending the mail back to the list? Or am I the only one seeing this phenomenon? GeSS -- Gess Shankar |<><>|Internet: gess@knex.mind.ORG |<><>| Knowledge Exchange|<><>|:::::::::::::::::::::::::|<><>| From list-managers-owner Thu Mar 30 11:50:34 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id LAA02007 for list-managers-outgoing; Thu, 30 Mar 1995 11:20:34 -0800 Received: from gagme.wwa.com (gagme.wwa.com [198.49.174.33]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with SMTP id LAA02002 for ; Thu, 30 Mar 1995 11:20:29 -0800 Received: by gagme.wwa.com (Smail3.1.28.1 #8) id m0ruPnP-000FF2C; Thu, 30 Mar 95 13:22 CST Message-Id: From: dattier@wwa.com (David W. Tamkin) Subject: Re: Please read and heed To: gess@knex.mind.org Date: Thu, 30 Mar 1995 13:22:19 -0600 (CST) Cc: list-managers@GreatCircle.COM In-Reply-To: <3Fcs3c1w165w@knex.mind.org> from "Gess Shankar" at Mar 30, 95 11:46:25 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 660 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Gess Shankar wrote, [quote from an arbitrarily selected previous post] | This and a few other postings (perhaps all the postings) are being | recirculated again and again. Perhaps some subscriber site is sending | the mail back to the list? | | Or am I the only one seeing this phenomenon? No, you're not; I saw anywhere from two to nine copies of about five different posts to list-managers when I logged in early this afternoon. However, your post and the one before it came only once each, so I think the problem may be cured. Then again, perhaps my hopefulness is premature. If you see this one more than once, we'll know that the trouble persists. From list-managers-owner Fri Mar 31 01:20:27 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id BAA00354 for list-managers-outgoing; Fri, 31 Mar 1995 01:11:35 -0800 Received: from netcom22.netcom.com (netcom22.netcom.com [192.100.81.136]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id BAA00349 for ; Fri, 31 Mar 1995 01:11:33 -0800 Received: by netcom22.netcom.com (8.6.11/Netcom) id BAA04380; Fri, 31 Mar 1995 01:06:27 -0800 From: glosys@netcom.com (Eberhart Weber) Message-Id: <199503310906.BAA04380@netcom22.netcom.com> Subject: does anyone use MREPLY ? To: list-managers@greatcircle.com Date: Fri, 31 Mar 1995 01:06:27 -0800 (PST) ORGANIZATION: Research Project On Global Systems Reply-To: glosys@netcom.com X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 388 Sender: list-managers-owner@GreatCircle.COM Precedence: bulk I am looking at mreply as an MLM because it appears to be fairly easy to configure. Does anyone have experience with this program? Thanks in advance for sharing Eberhard Weber -- ----------------------------------------------------------------------- Research Project On Global Systems glosys@netcom.com 232 W. Lexington Ave #102 Fresno, CA 93711 From list-managers-owner Fri Mar 31 09:26:59 1995 Received: (daemon@localhost) by miles.greatcircle.com (8.6.9/Miles-941015-1) id IAA14048 for list-managers-outgoing; Fri, 31 Mar 1995 08:53:09 -0800 Received: from europe.std.com (europe.std.com [192.74.137.10]) by miles.greatcircle.com (8.6.9/Miles-941015-1) with ESMTP id IAA14043 for ; Fri, 31 Mar 1995 08:53:05 -0800 Received: from world.std.com by europe.std.com (8.6.11/Spike-8-1.0) id LAA28517; Fri, 31 Mar 1995 11:48:33 -0500 Received: by world.std.com (5.65c/Spike-2.0) id AA00571; Fri, 31 Mar 1995 11:48:37 -0500 Date: Fri, 31 Mar 1995 11:48:36 +0001 (EST) From: Sylvia Gerhard Subject: Re Full MajorDomo capability To: list-managers@greatcircle.com Cc: ncwebb@world.std.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: list-managers-owner@GreatCircle.COM Precedence: bulk Brent Chapman has suggested that I might query you to find which Internet servers use full majordomo capability. I'm involved in attempting to set up a system where people can request archived documents by email and receive them automatically via email. Would you be able to suggest something? The intended recepients of the archives probably will not be familiar with accessing files via www or ftp and may be accessing the Internet via aol or compuserve. Thank you in advance for your help. Sylvia Gerhard sgerhard@world.std.com