From majordomo-users-owner@greatcircle.com Mon Feb 5 23:50:30 2007 X-Original-To: majordomo-users@greatcircle.com X-Greylist: delayed 1229 seconds by postgrey-1.24 at mycroft; Mon, 05 Feb 2007 23:50:29 PST Received: from nifty.selfip.net (CPE-24-208-94-189.neb.res.rr.com [24.208.94.189]) by mycroft.greatcircle.com (Postfix) with ESMTP id 9699D21BD58 for ; Mon, 5 Feb 2007 23:50:29 -0800 (PST) Received: from nifty.selfip.net (localhost [127.0.0.1]) by nifty.selfip.net (8.13.4/8.13.4) with ESMTP id l167Tf2s002693 for ; Tue, 6 Feb 2007 01:29:41 -0600 Received: from localhost (matt@localhost) by nifty.selfip.net (8.13.4/8.13.4/Submit) with ESMTP id l167TdX9002690 for ; Tue, 6 Feb 2007 01:29:41 -0600 Date: Tue, 6 Feb 2007 01:29:39 -0600 (CST) From: matt V To: majordomo-users@greatcircle.com Subject: new to majordomo: very confused Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Archive-Number: 200702/1 X-Sequence-Number: 5595 hello all, I sure hope someone can help me with this big problem i have. I don't know if for some reason this isn't sinking in or if the examples and docs are as clear as mud but..i got along fine making a non-digest list called test, did the aliases right and everything, but now when i read the part about creating aliases for the digest and archive its as clear as mud not to mention testing the digest and regular lists, i get a mailer-daemon error showing me that test has been expanded, and it tries to use the include line as the email address or something along that line, i have no clue what is going wrong and really can't explain it better than that. also, one doc says one thing, one says another way, half way into the first doc, it seems like the person lost track of the directory which doesn't help a newbie. I am not new to linux at all, just new to mlm software and if it helps, these are all the lines i have added to my /etc/mail/aliases file that werent there before, i.e excluding the mailer-daemon and postmaster. also, i am using slackware 10.2 on a junky gateway p3(i know i know), 800mhz(not by choice) so, here are those alias lines: like i said, hope someone can clear this up for me majordomo: "|/home/majordomo/md/wrapper majordomo" owner-majordomo: matt majordomo-owner: matt test: :include:/home/majordomo/md/lists/test owner-test: matt test-request: "|/home/majordomo/md/wrapper request-answer test" test-approval: matt test-outgoing: :include:/home/majordomo/md/lists/test, test-digestify test-digestify: "|/home/majordomo/md/wrapper digest -r -C -l test-digest test-digest-outgoing" test-digest: test test-digest-outgoing: :include:/home/majordomo/md/lists/test-digest owner-test-digest-outgoing: matt test-digest-approval: matt From majordomo-users-owner@greatcircle.com Tue Feb 6 06:19:06 2007 X-Original-To: majordomo-users@GreatCircle.COM Received: from wrenkasky.com (esson.net [216.102.129.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 0445921BE58 for ; Tue, 6 Feb 2007 06:19:00 -0800 (PST) Received: from EDS.esson.net (eds.wrenkasky.com [10.10.10.11]) (authenticated bits=0) by wrenkasky.com (8.13.8/8.13.8) with ESMTP id l16EIr14014705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Feb 2007 06:18:59 -0800 Message-Id: <200702061418.l16EIr14014705@wrenkasky.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 06 Feb 2007 06:18:51 -0800 To: matt V From: Ed Kasky Subject: Re: new to majordomo: very confused Cc: majordomo-users@GreatCircle.COM In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Received-SPF: pass (wrenkasky.com: 10.10.10.11 is authenticated by a trusted mechanism) X-Virus-Scanned: ClamAV 0.90rc3/2527/Tue Feb 6 02:14:46 2007 on yoda2.wrenkasky.com X-Virus-Status: Clean X-Archive-Number: 200702/2 X-Sequence-Number: 5596 At 11:29 PM Monday, 2/5/2007, you wrote -=> >hello all, >I sure hope someone can help me with this big problem i have. I >don't know if for some reason this isn't sinking in or if the >examples and docs are as clear as mud but..i got along fine making a >non-digest list called test, did the aliases right and everything, >but now when i read the part about creating aliases for the digest >and archive its as clear as mud not to mention testing the digest >and regular lists, i get a mailer-daemon error showing me that test >has been expanded, and it tries to use the include line as the email >address or something along that line, i have no clue what is going >wrong and really can't explain it better than that. also, one doc >says one thing, one says another way, half It would be good if you include the exact error. >way into the first doc, it seems like the person lost track of the >directory which doesn't help a newbie. I am not new to linux at >all, just new to mlm software >and if it helps, these are all the lines i have added to my >/etc/mail/aliases file that werent there before, i.e excluding the >mailer-daemon and postmaster. > >also, i am using slackware 10.2 on a junky gateway p3(i know i >know), 800mhz(not by choice) >so, here are those alias lines: >like i said, hope someone can clear this up for me > >test: :include:/home/majordomo/md/lists/test Your test alias is supposed to be a command and you have it pointing to a text file. For example - and these include demime and archive: test: "|/usr/local/majordomo/demime '== /usr/local/majordomo/wrapper resend -l test test-list,nobody'" test-list: :include:/usr/local/majordomo/lists/test, test-archive, test-digestify test-digestify: "|/usr/local/majordomo/digest -r -C -l test-digest test-digest-outgoing" test-digest: test test-digest-outgoing: :include:/usr/local/majordomo/lists/test-digest test-archive: "|/usr/local/majordomo/wrapper archive -f /usr/local/majordomo/archives/test/test -a -M" In your case, you might try the following: test: "|home/majordomo/md/wrapper resend -l test test-outgoing,nobody" >test-outgoing: :include:/home/majordomo/md/lists/test, test-digestify >test-digestify: "|/home/majordomo/md/wrapper digest -r -C -l >test-digest test-digest-outgoing" >test-digest: test >test-digest-outgoing: :include:/home/majordomo/md/lists/test-digest As you can see, I set my lists up slightly differently but it works just fine if you can follow the logic.... HTH, Ed . . . . . . . . . . . . . . . . . . Randomly Generated Quote (698 of 1172): Keep on keepin' on. From majordomo-users-owner@greatcircle.com Tue Feb 6 08:44:22 2007 X-Original-To: majordomo-users@greatcircle.com Received: from nifty.selfip.net (CPE-24-208-94-189.neb.res.rr.com [24.208.94.189]) by mycroft.greatcircle.com (Postfix) with ESMTP id 6C6D52900B2 for ; Tue, 6 Feb 2007 08:44:21 -0800 (PST) Received: from nifty.selfip.net (localhost [127.0.0.1]) by nifty.selfip.net (8.13.4/8.13.4) with ESMTP id l16GhljE003160; Tue, 6 Feb 2007 10:43:47 -0600 Received: from localhost (matt@localhost) by nifty.selfip.net (8.13.4/8.13.4/Submit) with ESMTP id l16GhjMf003157; Tue, 6 Feb 2007 10:43:47 -0600 Date: Tue, 6 Feb 2007 10:43:45 -0600 (CST) From: matt V To: Ed Kasky Cc: majordomo-users@greatcircle.com Subject: Re: new to majordomo: very confused In-Reply-To: <200702061418.l16EIr14014705@wrenkasky.com> Message-ID: References: <200702061418.l16EIr14014705@wrenkasky.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Archive-Number: 200702/3 X-Sequence-Number: 5597 hello, I read this message several times just to make sure i had things right and understood them, well apparently i don't, i am still getting an error from the mailer anyway which says the directory is group writtable. the error message however i copied this time if it will help. the exact error was ----- The following addresses had permanent fatal errors ----- :include:/home/majordomo/md/lists/test (expanded from: ) ----- Transcript of session follows ----- 550 5.2.4 :include:/home/majordomo/md/lists/test... Cannot open /home/majordomo/md/lists/test: Group writable directory Receiving 2 the lines i payed attention to and added to my aliases were the ones below the "in your case" line hope this becomes clear soon On Tue, 6 Feb 2007, Ed Kasky wrote: > At 11:29 PM Monday, 2/5/2007, you wrote -=> >> hello all, >> I sure hope someone can help me with this big problem i have. I don't know >> if for some reason this isn't sinking in or if the examples and docs are as >> clear as mud but..i got along fine making a non-digest list called test, >> did the aliases right and everything, but now when i read the part about >> creating aliases for the digest and archive its as clear as mud not to >> mention testing the digest and regular lists, i get a mailer-daemon error >> showing me that test has been expanded, and it tries to use the include >> line as the email address or something along that line, i have no clue what >> is going wrong and really can't explain it better than that. also, one doc >> says one thing, one says another way, half > > It would be good if you include the exact error. > >> way into the first doc, it seems like the person lost track of the >> directory which doesn't help a newbie. I am not new to linux at all, just >> new to mlm software >> and if it helps, these are all the lines i have added to my >> /etc/mail/aliases file that werent there before, i.e excluding the >> mailer-daemon and postmaster. >> >> also, i am using slackware 10.2 on a junky gateway p3(i know i know), >> 800mhz(not by choice) >> so, here are those alias lines: >> like i said, hope someone can clear this up for me >> >> test: :include:/home/majordomo/md/lists/test > > Your test alias is supposed to be a command and you have it pointing to a > text file. For example - and these include demime and archive: > > test: "|/usr/local/majordomo/demime '== /usr/local/majordomo/wrapper resend > -l test test-list,nobody'" > test-list: :include:/usr/local/majordomo/lists/test, test-archive, > test-digestify > test-digestify: "|/usr/local/majordomo/digest -r -C -l test-digest > test-digest-outgoing" > test-digest: test > test-digest-outgoing: :include:/usr/local/majordomo/lists/test-digest > test-archive: "|/usr/local/majordomo/wrapper archive -f > /usr/local/majordomo/archives/test/test -a -M" > > In your case, you might try the following: > > test: "|home/majordomo/md/wrapper resend -l test test-outgoing,nobody" > >> test-outgoing: :include:/home/majordomo/md/lists/test, test-digestify >> test-digestify: "|/home/majordomo/md/wrapper digest -r -C -l test-digest >> test-digest-outgoing" >> test-digest: test >> test-digest-outgoing: :include:/home/majordomo/md/lists/test-digest > > As you can see, I set my lists up slightly differently but it works just fine > if you can follow the logic.... > > HTH, > > Ed > > . . . . . . . . . . . . . . . . . . > Randomly Generated Quote (698 of 1172): > Keep on keepin' on. > From majordomo-users-owner@greatcircle.com Tue Feb 6 08:57:50 2007 X-Original-To: majordomo-users@greatcircle.com Received: from nifty.selfip.net (CPE-24-208-94-189.neb.res.rr.com [24.208.94.189]) by mycroft.greatcircle.com (Postfix) with ESMTP id 22445290052 for ; Tue, 6 Feb 2007 08:57:50 -0800 (PST) Received: from nifty.selfip.net (localhost [127.0.0.1]) by nifty.selfip.net (8.13.4/8.13.4) with ESMTP id l16GvUh6003232 for ; Tue, 6 Feb 2007 10:57:30 -0600 Received: from localhost (matt@localhost) by nifty.selfip.net (8.13.4/8.13.4/Submit) with ESMTP id l16GvSL6003229 for ; Tue, 6 Feb 2007 10:57:30 -0600 Date: Tue, 6 Feb 2007 10:57:28 -0600 (CST) From: matt V To: majordomo-users@greatcircle.com Subject: problem fixed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Archive-Number: 200702/4 X-Sequence-Number: 5598 hello, just an update to my problem: i fixed the group writtable problem, my permissions on the lists directory somehow were set at 770 not 755 or whatnot, but the digest and files dirs were set fine, i have not a clue why but oh well, at least it works as far as i can tell and thanks for the reply in the first place matt From majordomo-users-owner@greatcircle.com Tue Feb 6 10:03:57 2007 X-Original-To: majordomo-users@greatcircle.com Received: from nifty.selfip.net (CPE-24-208-94-189.neb.res.rr.com [24.208.94.189]) by mycroft.greatcircle.com (Postfix) with ESMTP id 60733290052 for ; Tue, 6 Feb 2007 10:03:55 -0800 (PST) Received: from nifty.selfip.net (localhost [127.0.0.1]) by nifty.selfip.net (8.13.4/8.13.4) with ESMTP id l16I3Xux003434 for ; Tue, 6 Feb 2007 12:03:35 -0600 Received: from localhost (matt@localhost) by nifty.selfip.net (8.13.4/8.13.4/Submit) with ESMTP id l16I3Vdd003431 for ; Tue, 6 Feb 2007 12:03:33 -0600 Date: Tue, 6 Feb 2007 12:03:31 -0600 (CST) From: matt V To: majordomo-users@greatcircle.com Subject: another question on digests Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Archive-Number: 200702/5 X-Sequence-Number: 5599 hello again I was just wondering if there is a way to make a digest on the fly or not?I want to test my work, but all i see in the digests_work_directory that i have as /home/majordomo/md/digests/test-digest, is files 001 through 004 but when i do a command such as "echo mkdigest test-digest pluck | mail matt@nifty.selfip.net" all i get in that email is the result of what i echo'ed' e.g, "mkdigest test-digest pluck the doc i read was quick-digest-setup but for some reason, its not working thats where i see the digests password was pluck I have my $filedir set as /home/majordomo/md/files which has a directory under that called test-digest.archive am i as lost as i think i am? From majordomo-users-owner@greatcircle.com Tue Feb 6 11:11:43 2007 X-Original-To: majordomo-users@greatcircle.com X-Greylist: delayed 643 seconds by postgrey-1.24 at mycroft; Tue, 06 Feb 2007 11:11:42 PST Received: from mailx.css.edu (mailx.css.edu [143.110.1.14]) by mycroft.greatcircle.com (Postfix) with ESMTP id 9AD242901C6 for ; Tue, 6 Feb 2007 11:11:42 -0800 (PST) Received: from css.edu (gwmail.css.edu [143.110.1.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailx.css.edu (Spam Firewall) with ESMTP id 3786B3265A2 for ; Tue, 6 Feb 2007 13:00:57 -0600 (CST) Received: from CSS-MTA by css.edu with Novell_GroupWise; Tue, 06 Feb 2007 13:00:57 -0600 Message-Id: <45C87BFA.328C.00F4.0@css.edu> X-Mailer: Novell GroupWise Internet Agent 7.0.1 Date: Tue, 06 Feb 2007 13:00:48 -0600 From: "Michael Linval" To: Subject: Moderation of a list Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Archive-Number: 200702/6 X-Sequence-Number: 5600 I am working on setting up a list that will be moderated. My question that I cannot find the answer to is how long will the message that is awaiting approval be there? Is it set by the email system or Majordomo itself? Thanks Michael Linval WAN Manager College of St. Scholastica Duluth, MN 218 723-5914 From majordomo-users-owner@greatcircle.com Tue Feb 6 11:47:24 2007 X-Original-To: majordomo-users@greatcircle.com Received: from nifty.selfip.net (CPE-24-208-94-189.neb.res.rr.com [24.208.94.189]) by mycroft.greatcircle.com (Postfix) with ESMTP id 0A9B32900E6 for ; Tue, 6 Feb 2007 11:47:23 -0800 (PST) Received: from nifty.selfip.net (localhost [127.0.0.1]) by nifty.selfip.net (8.13.4/8.13.4) with ESMTP id l16Jl3K6003655 for ; Tue, 6 Feb 2007 13:47:03 -0600 Received: from localhost (matt@localhost) by nifty.selfip.net (8.13.4/8.13.4/Submit) with ESMTP id l16Jl29U003652 for ; Tue, 6 Feb 2007 13:47:03 -0600 Date: Tue, 6 Feb 2007 13:47:02 -0600 (CST) From: matt V To: majordomo-users@greatcircle.com Subject: more problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Archive-Number: 200702/7 X-Sequence-Number: 5601 hello yet again i thought it would be fine to not install majordomo in /usr/local but there are a few things that either aren't in this package i got, or it would have made life easier to install in /usr/local?for one thing, there is no mkdigest command that i can find, running majordomo under the home directory that i have it as, e.g /home/majordomo/md complains it can't find /etc/majordomo.cf well duh, because its not there but i'm wondering how many unseen problems i could avoid if i had or would, install majordomo into the /usr/local directory instead or if it wouldnt have solved anything From majordomo-users-owner@greatcircle.com Tue Feb 6 12:43:22 2007 X-Original-To: majordomo-users@greatcircle.com X-Greylist: delayed 1749 seconds by postgrey-1.24 at mycroft; Tue, 06 Feb 2007 12:43:22 PST Received: from smtp-out.neti.ee (mail.neti.ee [194.126.101.114]) by mycroft.greatcircle.com (Postfix) with ESMTP id 239332900CC for ; Tue, 6 Feb 2007 12:43:21 -0800 (PST) Received: from smtp-out.neti.ee (relay8.neti.ee [88.196.174.139]) by HOT-Bounce1.estpak.ee (Postfix) with ESMTP id 738CD4EBF88 for ; Tue, 6 Feb 2007 22:12:07 +0200 (EET) X-Virus-Scanned: by amavisd-new-2.4.3 (20060930) (Debian) at neti.ee Received: from Relayhost2.neti.ee (Relayhost2 [88.196.174.142]) by MXR-8.estpak.ee (Postfix) with ESMTP id 50AA3C0C73; Tue, 6 Feb 2007 22:11:56 +0200 (EET) Received: from [88.196.103.201] (88-196-103-201-dsl.trt.estpak.ee [88.196.103.201]) by Relayhost2.neti.ee (Postfix) with ESMTP id 7B78C10C233; Tue, 6 Feb 2007 22:11:54 +0200 (EET) Message-ID: <45C8E109.5030100@raad.tartu.ee> Date: Tue, 06 Feb 2007 22:11:53 +0200 From: Toomas Aas User-Agent: Thunderbird 1.5.0.7 (X11/20060918) MIME-Version: 1.0 To: Michael Linval , majordomo-users@greatcircle.com Subject: Re: Moderation of a list References: <45C87BFA.328C.00F4.0@css.edu> In-Reply-To: <45C87BFA.328C.00F4.0@css.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200702/8 X-Sequence-Number: 5602 Michael Linval wrote: > I am working on setting up a list that will be moderated. My question > that I cannot find the answer to is how long will the message that is > awaiting approval be there? It's been some years since I tried to work with moderated lists (which was an excercise in pain with todays point-and-click mail clients and point-and-click would-be list moderators) but as far as I remember, the message is not "there" at all. It gets forwarded to moderator, who then has to forward it back to the list, adding appropriate tags which indicate to majordomo that the message has been allowed by moderator. -- Toomas From majordomo-users-owner@greatcircle.com Tue Feb 6 17:15:15 2007 X-Original-To: majordomo-users@greatcircle.com Received: from nifty.selfip.net (CPE-24-208-94-189.neb.res.rr.com [24.208.94.189]) by mycroft.greatcircle.com (Postfix) with ESMTP id 9E75A2900E7 for ; Tue, 6 Feb 2007 17:15:13 -0800 (PST) Received: from nifty.selfip.net (localhost [127.0.0.1]) by nifty.selfip.net (8.13.4/8.13.4) with ESMTP id l171EpSZ007715 for ; Tue, 6 Feb 2007 19:14:51 -0600 Received: from localhost (matt@localhost) by nifty.selfip.net (8.13.4/8.13.4/Submit) with ESMTP id l171Ep5G007712 for ; Tue, 6 Feb 2007 19:14:51 -0600 Date: Tue, 6 Feb 2007 19:14:51 -0600 (CST) From: matt V To: majordomo-users@greatcircle.com Subject: digests: finally working! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Archive-Number: 200702/9 X-Sequence-Number: 5603 I don't know what i did but that command to test the digest or put in the cron table does absolutely nothing except echo back what you tell it and emails it, i.e the line that says "echo mkdigest ; Wed, 7 Feb 2007 07:40:22 -0800 (PST) Received: from [192.168.1.78] (father.sonny.com [192.168.1.78]) by magnia.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTPA id <0JD300205NIZI0@magnia.sonny.com> for majordomo-users@greatcircle.com; Wed, 07 Feb 2007 09:40:11 -0600 (CST) Date: Wed, 07 Feb 2007 09:40:46 -0600 From: Daniel Liston Subject: Re: Moderation of a list In-reply-to: <45C8E109.5030100@raad.tartu.ee> To: majordomo-users@greatcircle.com Message-id: <45C9F2FE.5010008@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) References: <45C87BFA.328C.00F4.0@css.edu> <45C8E109.5030100@raad.tartu.ee> X-Archive-Number: 200702/10 X-Sequence-Number: 5604 Toomas Aas wrote: > Michael Linval wrote: > >> I am working on setting up a list that will be moderated. My question >> that I cannot find the answer to is how long will the message that is >> awaiting approval be there? > > > It's been some years since I tried to work with moderated lists (which > was an excercise in pain with todays point-and-click mail clients and > point-and-click would-be list moderators) but as far as I remember, the > message is not "there" at all. It gets forwarded to moderator, who then > has to forward it back to the list, adding appropriate tags which > indicate to majordomo that the message has been allowed by moderator. > In addition to Toomas' response, the message will be available to the moderator for as long as his mail server will keep it. All moderated list email is forwarded to the moderator without depositing a copy on the archive or digest, if things are set up properly. There is not an automatic way to approve messages either, that would just be the same as setting the list up to be unmoderated. The moderator must use an email client that will allow them to append a header to their own mail, "Approved: moderator-password", which must appear to majordomo and any MTA between the moderator and majordomo to be before the first blank line separating headers from message bodies. Netscape, Mozilla, Thunderbird, Eudora, Pine, and Mutt are email clients that have this capability. I don't know if Evolution, Outlook Express, or Outlook can do this. I am fairly sure there are no webmail clients like Hotmail, AOL, MSN, Yahoo, Excite, or squirrelmail that can either. Ultimately, if you have a list-owner that insists their list be config'd as moderated, that list-owner needs to be, or appoint someone, that will take the time to learn more about email clients than they ever wanted to before. They will also need to read some majordomo docs, google some majordomo tips and hints regarding moderating a list, and probably write messages here for more help. From majordomo-users-owner@greatcircle.com Sun Feb 11 11:56:37 2007 X-Original-To: majordomo-users@greatcircle.com X-Greylist: delayed 118 seconds by postgrey-1.24 at mycroft; Sun, 11 Feb 2007 11:56:36 PST Received: from gcpws2.gosscomputerprojects.net (static-71-162-143-66.phlapa.fios.verizon.net [71.162.143.66]) by mycroft.greatcircle.com (Postfix) with ESMTP id 868AE19C245 for ; Sun, 11 Feb 2007 11:56:36 -0800 (PST) Received: from gcpws2.gosscomputerprojects.net (localhost [127.0.0.1]) by gcpws2.gosscomputerprojects.net (8.13.1/8.13.1) with ESMTP id l1BJrs0W010610 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 11 Feb 2007 14:53:54 -0500 Received: (from apache@localhost) by gcpws2.gosscomputerprojects.net (8.13.1/8.13.1/Submit) id l1BJrsow010609; Sun, 11 Feb 2007 14:53:54 -0500 X-Authentication-Warning: gcpws2.gosscomputerprojects.net: apache set sender to ClayGoss@ClayGoss.com using -f Received: from 71.162.143.66 (SquirrelMail authenticated user cgoss) by www.claygoss.com with HTTP; Sun, 11 Feb 2007 14:53:54 -0500 (EST) Message-ID: <4661.71.162.143.66.1171223634.squirrel@www.claygoss.com> Date: Sun, 11 Feb 2007 14:53:54 -0500 (EST) Subject: AOL user's post not delivered to other AOL addresses From: "Clay Goss" To: majordomo-users@greatcircle.com Reply-To: ClayGoss@gosscomputerprojects.net User-Agent: SquirrelMail/1.4.6 [CVS]-0.cvs20050812.1.fc3 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-GCP_NET-MailScanner-Information: Please contact the ISP for more information X-GCP_NET-MailScanner: Found to be clean X-MailScanner-From: claygoss@claygoss.com X-Archive-Number: 200702/11 X-Sequence-Number: 5605 When a list subscriber with an AOL address posts to the list, I get this long error message from an AOL system with error messages like: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ listname@listserver.listdomain.net on 2/11/2007 1:54 PM The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator. < listserver.listdomain.net #5.0.0 SMTP; 554-: (RLY:SN) http://postmaster.info.aol.com/errors/554rlysn.html> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ While it doesn't give the email address it is refusing to relay to, the number of these messages roughly matches the number of AOL addresses in my list. Any thoughts? From majordomo-users-owner@greatcircle.com Sun Feb 11 13:00:55 2007 X-Original-To: majordomo-users@greatcircle.com Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by mycroft.greatcircle.com (Postfix) with ESMTP id 4E20A21BD99 for ; Sun, 11 Feb 2007 13:00:53 -0800 (PST) Received: from [66.47.111.183] (helo=joeandlane.com) by elasmtp-curtail.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1HGLoV-0004NL-Qd; Sun, 11 Feb 2007 16:00:48 -0500 Received: from joeandlane.com (localhost.localnet.local [127.0.0.1]) by joeandlane.com (8.13.8/8.13.1) with ESMTP id l1BL2rA7038526; Sun, 11 Feb 2007 15:02:53 -0600 (CST) (envelope-from lane@joeandlane.com) Received: from localhost (localhost [[UNIX: localhost]]) by joeandlane.com (8.13.8/8.13.1/Submit) id l1BL2q08038525; Sun, 11 Feb 2007 15:02:52 -0600 (CST) (envelope-from lane@joeandlane.com) X-Authentication-Warning: joeandlane.com: lholcombe set sender to lane@joeandlane.com using -f From: Lane To: ClayGoss@gosscomputerprojects.net, majordomo-users@greatcircle.com Subject: Re: AOL user's post not delivered to other AOL addresses Date: Sun, 11 Feb 2007 15:02:52 -0600 User-Agent: KMail/1.9.4 References: <4661.71.162.143.66.1171223634.squirrel@www.claygoss.com> In-Reply-To: <4661.71.162.143.66.1171223634.squirrel@www.claygoss.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702111502.52824.lane@joeandlane.com> X-CD-SOLUTIONS-MailScanner-Information: Please contact the ISP for more information X-CD-SOLUTIONS-MailScanner: Found to be clean X-CD-SOLUTIONS-MailScanner-From: lane@joeandlane.com X-ELNK-Trace: e56a4b6ca9bdfda11aa676d7e74259b7b3291a7d08dfec7959e9a27a1996c2bb688e4b00f46dd1b2350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.47.111.183 X-Archive-Number: 200702/12 X-Sequence-Number: 5606 On Sunday 11 February 2007 13:53, Clay Goss wrote: > When a list subscriber with an AOL address posts to the list, I get this > long error message from an AOL system with error messages like: > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > listname@listserver.listdomain.net on 2/11/2007 1:54 PM > The e-mail system was unable to deliver the message, but did > not report a specific reason. Check the address and try > again. If it still fails, contact your system administrator. > < listserver.listdomain.net #5.0.0 SMTP; 554-: (RLY:SN) > http://postmaster.info.aol.com/errors/554rlysn.html> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > While it doesn't give the email address it is refusing to relay to, the > number of these messages roughly matches the number of AOL addresses in my > list. > > Any thoughts? Clay, I've been 'round-n-round' with AOL about this - for over three years. I get on their "white-list" and their policies change and things reject again. As I understand it, the current AOL policy is that when a certain trigger amount of email messages come from an individual ip (which is not otherwise a paying and/or "approved" email "service provider") over the course of a finite number of minutes, seconds, or whatever ... then AOL rejects everything AFTER the trigger has been tripped. In practice what I find is that usually two or three AOL users will receive the email but all of the others do not. And then I receive the lenghty rejection messages you mention. As a stop-gap measure, I have built an archival system which posts all majordomo email to a web page for the users to view. That means that everyone in the world can view the email, but only majordomo-registered users can send. It does not solve the problem, but it does get around it in some ways. I think a real solution would be to throttle the outgoing messages, so that only a couple are "released" every five or so minutes. But I'm fed up with trying to deal with AOL so I haven't done the necessary research to implement this plan. hth lane P.S. From majordomo-users-owner@greatcircle.com Sun Feb 11 15:06:56 2007 X-Original-To: majordomo-users@greatcircle.com X-Greylist: delayed 2000 seconds by postgrey-1.24 at mycroft; Sun, 11 Feb 2007 15:06:55 PST Received: from huntingcow.cyberthugs.com (mail.cyberthugs.com [74.39.192.241]) by mycroft.greatcircle.com (Postfix) with ESMTP id 95EF9290067 for ; Sun, 11 Feb 2007 15:06:55 -0800 (PST) Received: from localhost (unknown [127.0.0.1]) by huntingcow.cyberthugs.com (Postfix) with ESMTP id 1D8648D802A; Sun, 11 Feb 2007 22:33:34 +0000 (UTC) X-Virus-Scanned: amavisd-new at cyberthugs.com Received: from huntingcow.cyberthugs.com ([127.0.0.1]) by localhost (huntingcow.cyberthugs.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id m4kzkGrdluHB; Sun, 11 Feb 2007 17:33:34 -0500 (EST) Received: from huntingcow.cyberthugs.com (huntingcow.cyberthugs.com [127.0.0.1]) by huntingcow.cyberthugs.com (Postfix) with ESMTP id EB65E8D800D; Sun, 11 Feb 2007 17:33:33 -0500 (EST) Received: (from ddewey@localhost) by huntingcow.cyberthugs.com (8.13.4/8.13.4/Submit) id l1BMXXWM017834; Sun, 11 Feb 2007 17:33:33 -0500 From: Dave Dewey Date: Sun, 11 Feb 2007 17:33:33 -0500 To: Clay Goss Cc: majordomo-users@greatcircle.com Subject: Re: AOL user's post not delivered to other AOL addresses Message-ID: <20070211223333.GB5184@huntingcow.cyberthugs.com> References: <4661.71.162.143.66.1171223634.squirrel@www.claygoss.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4661.71.162.143.66.1171223634.squirrel@www.claygoss.com> User-Agent: Mutt/1.5.12-2006-07-14 X-Archive-Number: 200702/13 X-Sequence-Number: 5607 Quoting Clay Goss (ClayGoss@gosscomputerprojects.net): > When a list subscriber with an AOL address posts to the list, I get this > long error message from an AOL system with error messages like: > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > listname@listserver.listdomain.net on 2/11/2007 1:54 PM > The e-mail system was unable to deliver the message, but did > not report a specific reason. Check the address and try > again. If it still fails, contact your system administrator. > < listserver.listdomain.net #5.0.0 SMTP; 554-: (RLY:SN) > http://postmaster.info.aol.com/errors/554rlysn.html> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > While it doesn't give the email address it is refusing to relay to, the > number of these messages roughly matches the number of AOL addresses in my > list. > > Any thoughts? Have you tried the whitelist? I deliver loads of mail to AOL (although the volume is declining now pretty rapidly in favor of gmail). In my experience it works fine. Make sure you have a proper reverse set up, and set up a feedback loop. You can do the feedback loop and whitelist here: http://postmaster.info.aol.com/ I recently changed ip addresses on my sending server and forgot to update my whitelist entry - once I had done so, by calling them, mail started flowing again within a couple hours. I've found that AOLs postmaster staff has been very responsive when I've called, even more so in the last couple years. Don't hesitate to call them. -- http://www.last.fm/user/ddewey From majordomo-users-owner@greatcircle.com Sun Feb 11 16:29:57 2007 X-Original-To: majordomo-users@greatcircle.com Received: from wvmler2.mail.xerox.com (wvmler2.mail.xerox.com [13.8.138.217]) by mycroft.greatcircle.com (Postfix) with ESMTP id B9E4F29009E for ; Sun, 11 Feb 2007 16:29:56 -0800 (PST) Received: from wvmlir3.mail.xerox.com (wvmlir3.mail.xerox.com [13.147.8.223]) by wvmler2.mail.xerox.com (8.13.8/8.13.6) with ESMTP id l1C0TrU0028163; Sun, 11 Feb 2007 16:29:54 -0800 Received: from wvmlir3.mail.xerox.com (localhost.localdomain [127.0.0.1]) by wvmlir3.mail.xerox.com (8.13.8/8.13.6) with ESMTP id l1C0TnDG014824; Sun, 11 Feb 2007 16:29:49 -0800 Received: from usa0300gw02.na.xerox.net (usa0300gw02.na.xerox.net [13.129.0.42]) by wvmlir3.mail.xerox.com (8.13.8/8.13.6) with ESMTP id l1C0ThL6014802; Sun, 11 Feb 2007 16:29:45 -0800 Received: from usa0300ms02.na.xerox.net ([13.135.34.11]) by usa0300gw02.na.xerox.net with Microsoft SMTPSVC(6.0.3790.1830); Sun, 11 Feb 2007 19:29:44 -0500 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: AOL user's post not delivered to other AOL addresses Date: Sun, 11 Feb 2007 19:29:42 -0500 Message-ID: In-Reply-To: <200702111502.52824.lane@joeandlane.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: AOL user's post not delivered to other AOL addresses Thread-Index: AcdOH+tf+E/JfIm/Rg677t/C62JXbwAHCSog References: <4661.71.162.143.66.1171223634.squirrel@www.claygoss.com> <200702111502.52824.lane@joeandlane.com> From: "Doty, Robert" To: "Lane" , , X-OriginalArrivalTime: 12 Feb 2007 00:29:44.0123 (UTC) FILETIME=[E47510B0:01C74E3C] X-Archive-Number: 200702/14 X-Sequence-Number: 5608 I too had this problem. This was happening to me because AOL is only allowing e-mail from non-dhcp IP addresses. If your server is a home server and you didn't pay for a static IP address, you will get this error 'till the cows come home. To get around this, I found someone that would allow me to use their mail server to relay. There server has a static IP. Works like a charm now. Thanks, Rob -----Original Message----- From: majordomo-users-owner@greatcircle.com [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Lane Sent: Sunday, February 11, 2007 4:03 PM To: ClayGoss@gosscomputerprojects.net; majordomo-users@greatcircle.com Subject: Re: AOL user's post not delivered to other AOL addresses On Sunday 11 February 2007 13:53, Clay Goss wrote: > When a list subscriber with an AOL address posts to the list, I get this > long error message from an AOL system with error messages like: > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > listname@listserver.listdomain.net on 2/11/2007 1:54 PM > The e-mail system was unable to deliver the message, but did > not report a specific reason. Check the address and try > again. If it still fails, contact your system administrator. > < listserver.listdomain.net #5.0.0 SMTP; 554-: (RLY:SN) > http://postmaster.info.aol.com/errors/554rlysn.html> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > While it doesn't give the email address it is refusing to relay to, the > number of these messages roughly matches the number of AOL addresses in my > list. > > Any thoughts? Clay, I've been 'round-n-round' with AOL about this - for over three years. I get=20 on their "white-list" and their policies change and things reject again. As I understand it, the current AOL policy is that when a certain trigger=20 amount of email messages come from an individual ip (which is not otherwise a=20 paying and/or "approved" email "service provider") over the course of a=20 finite number of minutes, seconds, or whatever ... then AOL rejects=20 everything AFTER the trigger has been tripped. In practice what I find is that usually two or three AOL users will receive=20 the email but all of the others do not. And then I receive the lenghty=20 rejection messages you mention. As a stop-gap measure, I have built an archival system which posts all=20 majordomo email to a web page for the users to view. That means that=20 everyone in the world can view the email, but only majordomo-registered users=20 can send. It does not solve the problem, but it does get around it in some=20 ways. I think a real solution would be to throttle the outgoing messages, so that=20 only a couple are "released" every five or so minutes. But I'm fed up with=20 trying to deal with AOL so I haven't done the necessary research to implement=20 this plan. hth lane P.S. From majordomo-users-owner@greatcircle.com Sun Feb 11 16:48:29 2007 X-Original-To: majordomo-users@greatcircle.com X-Greylist: delayed 62 seconds by postgrey-1.24 at mycroft; Sun, 11 Feb 2007 16:48:28 PST Received: from mailbox.onlinepolicy.net (mailbox.onlinepolicy.net [209.237.247.99]) by mycroft.greatcircle.com (Postfix) with ESMTP id EBEB42900A8 for ; Sun, 11 Feb 2007 16:48:28 -0800 (PST) Received: from [192.168.7.103] (c-67-168-99-147.hsd1.wa.comcast.net [67.168.99.147]) by mailbox.onlinepolicy.net (Postfix) with ESMTP id 20AD6734E8; Sun, 11 Feb 2007 16:48:28 -0800 (PST) Message-ID: <45CFB952.3020403@queernet.org> Date: Sun, 11 Feb 2007 16:48:18 -0800 From: "Roger B.A. Klorese" User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: ClayGoss@gosscomputerprojects.net Cc: majordomo-users@greatcircle.com Subject: Re: AOL user's post not delivered to other AOL References: <4661.71.162.143.66.1171223634.squirrel@www.claygoss.com> In-Reply-To: <4661.71.162.143.66.1171223634.squirrel@www.claygoss.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200702/15 X-Sequence-Number: 5609 Clay Goss wrote: > When a list subscriber with an AOL address posts to the list, I get this > long error message from an AOL system with error messages like: > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > listname@listserver.listdomain.net on 2/11/2007 1:54 PM > The e-mail system was unable to deliver the message, but did > not report a specific reason. Check the address and try > again. If it still fails, contact your system administrator. > < listserver.listdomain.net #5.0.0 SMTP; 554-: (RLY:SN) > http://postmaster.info.aol.com/errors/554rlysn.html> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > While it doesn't give the email address it is refusing to relay to, the > number of these messages roughly matches the number of AOL addresses in my > list. > > Any thoughts? > Oops. I meant "blocking or scoring against mail coming to an AOL address via an outside connection that has an AOL From: address." From majordomo-users-owner@greatcircle.com Tue Feb 20 00:38:17 2007 X-Original-To: majordomo-users@greatcircle.com X-Greylist: delayed 300 seconds by postgrey-1.24 at mycroft; Tue, 20 Feb 2007 00:38:16 PST Received: from rwcrmhc14.comcast.net (rwcrmhc14.comcast.net [204.127.192.84]) by mycroft.greatcircle.com (Postfix) with ESMTP id DFD8029004B for ; Tue, 20 Feb 2007 00:38:16 -0800 (PST) Received: from [192.168.178.20] (p5b0744c6.dip0.t-ipconnect.de[91.7.68.198]) by comcast.net (rwcrmhc14) with SMTP id <20070220083314m1400g3ot5e>; Tue, 20 Feb 2007 08:33:14 +0000 Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: majordomo-users@greatcircle.com From: Bucky Junior Subject: Basically missing something Date: Tue, 20 Feb 2007 09:33:06 +0100 X-Mailer: Apple Mail (2.752.2) X-Archive-Number: 200702/16 X-Sequence-Number: 5610 Greetings Majordomo users. I am trying to configure Majordomo on a hosted site and I seem to be missing some very elementary syntax information. Since Majordomo is on a hosted site, I don't have write access to the configuration files. I was under the impression that one could do this configuration by email but I can't get the syntax correct. What I want to do for several lists is to make them "announcement only" as well as edit the footer and limit who access. I have figured out how to subcribe/unsubscribe myself and others by using the following single-line command in the body of the message sent to majordomo@mydomian. approve password subscribe my-list jdoe@domain Other user commands are available by send the single command "help" to majordomo. I have failed to figure out how to send configuration commands. The syntax must be very simple to those who know. I have tried--in various combinations of spaces and line breaks and order, the following to change the subject prefix for the list. Naturally, it was sent to majordomo@mydomain approve password my-list subject_prefix=[$LIST] I get back an error message like this: >>>> approve password my-list **** approve: unknown list ''. >>>> subject_prefix = [$LIST] **** Command 'subject_prefix' not recognized. >>>> This doesn't seem to recognize my-list nor the attempted command to set the subject prefix. It should be simple, yes? Just _what_ is the proper syntax for sending such commands to configure majordomo lists? Thank you, Bucky From majordomo-users-owner@greatcircle.com Tue Feb 20 09:42:43 2007 X-Original-To: majordomo-users@greatcircle.com Received: from smtp-out.neti.ee (mail.neti.ee [194.126.101.114]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2013521BD69 for ; Tue, 20 Feb 2007 09:42:42 -0800 (PST) Received: from smtp-out.neti.ee (unknown [88.196.174.136]) by HOT-Bounce1.estpak.ee (Postfix) with ESMTP id 85D3F50667D for ; Tue, 20 Feb 2007 19:42:39 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by MXR-5.estpak.ee (Postfix) with ESMTP id 76A361CB5DE; Tue, 20 Feb 2007 19:42:35 +0200 (EET) X-Virus-Scanned: by amavisd-new-2.4.3 (20060930) (Debian) at neti.ee Received: from smtp-out.neti.ee ([127.0.0.1]) by localhost (MXR-2.estpak.ee [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aSw4qaJtlO40; Tue, 20 Feb 2007 19:42:33 +0200 (EET) Received: from Relayhost2.neti.ee (Relayhost2 [88.196.174.142]) by MXR-5.estpak.ee (Postfix) with ESMTP id 0345A1CB5E9; Tue, 20 Feb 2007 19:42:32 +0200 (EET) Received: from [88.196.104.109] (88-196-104-109-dsl.trt.estpak.ee [88.196.104.109]) by Relayhost2.neti.ee (Postfix) with ESMTP id DB96F10C4FD; Tue, 20 Feb 2007 19:42:26 +0200 (EET) Message-ID: <45DB3302.9060507@raad.tartu.ee> Date: Tue, 20 Feb 2007 19:42:26 +0200 From: Toomas Aas User-Agent: Thunderbird 1.5.0.7 (X11/20060918) MIME-Version: 1.0 To: Bucky Junior , majordomo-users@greatcircle.com Subject: Re: Basically missing something References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200702/17 X-Sequence-Number: 5611 Bucky Junior wrote: > I have failed to figure out how to send configuration commands. The > syntax must be very simple to those who know. I have tried--in various > combinations of spaces and line breaks and order, the following to > change the subject prefix for the list. Naturally, it was sent to > majordomo@mydomain > > approve password my-list subject_prefix=[$LIST] > > I get back an error message like this: > > >>>> approve password my-list > **** approve: unknown list ''. > >>>> subject_prefix = [$LIST] > **** Command 'subject_prefix' not recognized. > >>>> The directives that appear in your list configuration file cannot be sent to Majordomo like this. Rather, you ask majordomo to send you the configuration file, make the changes you want and then send the configuration file back to majordomo. The process goes like this: ------------------------------------- From: you@yourdomain.com To: majordomo@hostingprovider.com Subject: whatever config my-list password ------------------------------------- You'll receive a message from Majordomo which contains the current configuration file for your list. And then: -------------------------------------------------- From: you@yourdomain.com To: majordomo@hostingprovider.com Subject: whateveer newconfig my-list password EOF -------------------------------------------------- Hope this helps, -- Toomas From majordomo-users-owner@greatcircle.com Tue Feb 20 12:34:46 2007 X-Original-To: majordomo-users@greatcircle.com Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.200.81]) by mycroft.greatcircle.com (Postfix) with ESMTP id AAB8A2900D1 for ; Tue, 20 Feb 2007 12:34:45 -0800 (PST) Received: from [192.168.178.20] (p5b0744c6.dip0.t-ipconnect.de[91.7.68.198]) by comcast.net (sccrmhc11) with SMTP id <20070220203354011004rca2e>; Tue, 20 Feb 2007 20:33:54 +0000 Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <16733C39-DAE2-4D87-919E-33305361621C@comcast.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: majordomo-users@greatcircle.com From: Bucky Junior Subject: Re: Basically missing something Date: Tue, 20 Feb 2007 21:33:47 +0100 X-Mailer: Apple Mail (2.752.2) X-Archive-Number: 200702/18 X-Sequence-Number: 5612 > The directives that appear in your list configuration file cannot > be sent to Majordomo like this. Rather, you ask majordomo to send > you the configuration file, make the changes you want and then send > the configuration file back to majordomo. > > The process goes like this: > > config my-list password > ------------------------------------- > > You'll receive a message from Majordomo which contains the current > configuration file for your list. And then: > > -------------------------------------------------- > > newconfig my-list password > > EOF > -------------------------------------------------- > > Hope this helps, > > -- > Toomas > Thank you Toomas, That allowed me to change the configuration for my list. In my reading over the past several days, I may have seen the solution to my problem, but you put it clearly. Ironically, my first attempts failed because a few lines in the first commented section broke to the next line and were interpreted as keywords. I recall being able to set the line length in mail clients like pine, but I don't see that in my current mail client. Or did majordomo break the lines? Either way, I'm able to change the configuration file. Thanks again Toomas. Bucky From majordomo-users-owner@greatcircle.com Wed Feb 21 04:58:54 2007 X-Original-To: majordomo-users@greatcircle.com Received: from gcpws2.gosscomputerprojects.net (static-71-162-143-66.phlapa.fios.verizon.net [71.162.143.66]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2163221BE51 for ; Wed, 21 Feb 2007 04:58:53 -0800 (PST) Received: from gcpws2.gosscomputerprojects.net (localhost [127.0.0.1]) by gcpws2.gosscomputerprojects.net (8.13.1/8.13.1) with ESMTP id l1LCwSwi025386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 21 Feb 2007 07:58:28 -0500 Received: (from apache@localhost) by gcpws2.gosscomputerprojects.net (8.13.1/8.13.1/Submit) id l1LCwSK0025385; Wed, 21 Feb 2007 07:58:28 -0500 X-Authentication-Warning: gcpws2.gosscomputerprojects.net: apache set sender to ClayGoss@ClayGoss.com using -f Received: from 63.138.133.35 (SquirrelMail authenticated user cgoss) by www.claygoss.com with HTTP; Wed, 21 Feb 2007 07:58:28 -0500 (EST) Message-ID: <3391.63.138.133.35.1172062708.squirrel@www.claygoss.com> Date: Wed, 21 Feb 2007 07:58:28 -0500 (EST) Subject: MAJORDOMO ABORT (mj_majordomo)!! From: "Clay Goss" To: majordomo-users@greatcircle.com Reply-To: ClayGoss@gosscomputerprojects.net User-Agent: SquirrelMail/1.4.6 [CVS]-0.cvs20050812.1.fc3 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-GCP_NET-MailScanner-Information: Please contact the ISP for more information X-GCP_NET-MailScanner: Found to be clean X-MailScanner-From: claygoss@claygoss.com X-Archive-Number: 200702/19 X-Sequence-Number: 5613 I received the following message from majordomo - what does it mean? Regards, Clay Goss Subject: MAJORDOMO ABORT (mj_majordomo) From: Majordomo@MyDomain.net Date: Sun, February 18, 2007 7:00 pm To: Majordomo-Owner@MyDomain.net Priority: Normal Options: View Full Header | View Printable Version -- MAJORDOMO ABORT (mj_majordomo)!! link("/var/lib/majordomo/lists/My-List", "/var/lib/majordomo/lists/My-List.old"): File exists From majordomo-users-owner@greatcircle.com Wed Feb 21 12:12:38 2007 X-Original-To: majordomo-users@greatcircle.com Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.238]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8AB9021BD87 for ; Wed, 21 Feb 2007 12:12:37 -0800 (PST) Received: by wx-out-0506.google.com with SMTP id s8so2469051wxc for ; Wed, 21 Feb 2007 12:12:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=FowWej+MAzGvQlxdYWeNKUI4OpW/S5XHlMUv7r9cEYdm/K2gmX4f/CnBNiLyKWfu3dusMk3fH0UCDVn1eyX7Zlk49i6fxlWeTsfvSymS/6oNRPYjrtl6seqaayRbh/IDIU1617d8QkDT7RDGMS1/cYh/UXzWi+vBAF3TMbB3pJY= Received: by 10.70.59.20 with SMTP id h20mr16407863wxa.1172088756134; Wed, 21 Feb 2007 12:12:36 -0800 (PST) Received: by 10.70.21.14 with HTTP; Wed, 21 Feb 2007 12:12:36 -0800 (PST) Message-ID: Date: Wed, 21 Feb 2007 15:12:36 -0500 From: burgerscigarsbeer@gmail.com To: majordomo-users@greatcircle.com Subject: Newbie Question MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5909_1301560.1172088756100" X-Archive-Number: 200702/20 X-Sequence-Number: 5614 ------=_Part_5909_1301560.1172088756100 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I have just started taking over a list and have question. When individuals post a message to our list, under the View Function we are being asked if we want to run an executable, with is named "list.com." The file has been viewed in text and is always the header information for the message and the text of the message. Originally, I thought it was individuals having html in their message but that is turning out to be less and less the case. Currently, we are rejecting these posts but I am begining to believe it a problem on our end. Oh... I see we are running 1.32 and the current verison is 1.94.5. Any thoughts... Thanks Art ------=_Part_5909_1301560.1172088756100 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

I have just started taking over a list and have question.

When individuals post a message to our list, under the View Function we are being asked if we want to run an executable, with is named "list.com." The file has been viewed in text and is always the header information for the message and the text of the message.

Originally, I thought it was individuals having html in their message but that is turning out to be less and less the case.

Currently, we are rejecting these posts but I am begining to believe it a problem on our end.

Oh... I see we are running 1.32 and the current verison is 1.94.5.

Any thoughts...

Thanks

Art

------=_Part_5909_1301560.1172088756100--