From majordomo-users-owner@greatcircle.com Thu Jul 7 10:32:34 2005 X-Original-To: majordomo-users@greatcircle.com Received: from dudley.casano.com (dudley.casano.com [209.191.27.30]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1611632C4E9 for ; Thu, 7 Jul 2005 10:32:32 -0700 (PDT) Received: from dudley.casano.com (localhost.casano.com [127.0.0.1]) by dudley.casano.com (8.13.3/8.13.3) with ESMTP id j67HVjD2049871; Thu, 7 Jul 2005 13:31:51 -0400 (EDT) (envelope-from wfd99@dudley.casano.com) Received: (from wfd99@localhost) by dudley.casano.com (8.13.3/8.13.3/Submit) id j67HVjHC049870; Thu, 7 Jul 2005 13:31:45 -0400 (EDT) (envelope-from wfd99) Date: Thu, 7 Jul 2005 13:31:45 -0400 (EDT) From: "William Dudley Jr." Message-Id: <200507071731.j67HVjHC049870@dudley.casano.com> To: majordomo-users@greatcircle.com Subject: proposed solution for spam sent to majordomo@yourdomain X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (dudley.casano.com [127.0.0.1]); Thu, 07 Jul 2005 13:31:51 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on dudley.casano.com X-Virus-Status: Clean X-Archive-Number: 200507/1 X-Sequence-Number: 5105 Recently, I've been seeing a fair number of spam messages that have been sent to my majordomo address. They are sent from bogus "From:" addresses, and since majordomo doesn't need Viagra, etc, "he" replies with a long stream of error messages: &squawk("Command '$cmd' not recognized."); This message with every line parroted back as "not recognized" PLUS the majordomo help text is then sent to the fake "From:" address, and the isp, if it exists, sends it BACK to me complaining about a non-existant user. As majordomo-owner, I get it in my inbox. To put a stop to this, I modified majordomo in the following ways: I added a threshold of 10 "not recognized" errors, which if exceeded AND we have NOT SEEN ANY valid commands, the following actions take place: 1. Processing of the message is terminated. 2. The help text is not sent. 3. Instead of replying to the "sender", we send just send a short note to majordomo-owner that says a message with > THRESHOLD errors was found and a reply was NOT sent to "sender". I'll be happy to make this code available in any way that is appropriate. Bill Dudley From majordomo-users-owner@greatcircle.com Thu Jul 7 13:06:27 2005 X-Original-To: majordomo-users@greatcircle.com Received: from dudley.casano.com (dudley.casano.com [209.191.27.30]) by mycroft.greatcircle.com (Postfix) with ESMTP id 95FE432C210 for ; Thu, 7 Jul 2005 13:06:26 -0700 (PDT) Received: from dudley.casano.com (localhost.casano.com [127.0.0.1]) by dudley.casano.com (8.13.3/8.13.3) with ESMTP id j67K5apY053798 for ; Thu, 7 Jul 2005 16:05:44 -0400 (EDT) (envelope-from wfd99@dudley.casano.com) Received: (from wfd99@localhost) by dudley.casano.com (8.13.3/8.13.3/Submit) id j67K5aTv053797 for majordomo-users@greatcircle.com; Thu, 7 Jul 2005 16:05:36 -0400 (EDT) (envelope-from wfd99) Date: Thu, 7 Jul 2005 16:05:36 -0400 (EDT) From: "William Dudley Jr." Message-Id: <200507072005.j67K5aTv053797@dudley.casano.com> To: majordomo-users@greatcircle.com Subject: Re: proposed solution for spam sent to majordomo@yourdomain In-Reply-To: <200507071731.j67HVjHC049870@dudley.casano.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (dudley.casano.com [127.0.0.1]); Thu, 07 Jul 2005 16:05:44 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on dudley.casano.com X-Virus-Status: Clean X-Archive-Number: 200507/2 X-Sequence-Number: 5106 In response to one (1) request, I've put my modified version of majordomo 1.94.5 up here: http://www.casano.com/majordomo/index.html Both the perl module itself and the diffs from the production version are available there. Please test this before you go and install it on a server that has a jillion customers depending upon it. I wouldn't want to be held responsible for anybody's lost email. Bill Dudley > From majordomo-users-owner+M5105@greatcircle.com Thu Jul 7 13:32:08 2005 > Date: Thu, 7 Jul 2005 13:31:45 -0400 (EDT) > From: "William Dudley Jr." > To: majordomo-users@greatcircle.com > Subject: proposed solution for spam sent to majordomo@yourdomain > > Recently, I've been seeing a fair number of spam messages that > have been sent to my majordomo address. They are sent from bogus > "From:" addresses, and since majordomo doesn't need Viagra, etc, > "he" replies with a long stream of error messages: > > &squawk("Command '$cmd' not recognized."); > > This message with every line parroted back as "not recognized" PLUS > the majordomo help text is then sent to the fake "From:" address, > and the isp, if it exists, sends it BACK to me complaining about > a non-existant user. As majordomo-owner, I get it in my inbox. > > To put a stop to this, I modified majordomo in the following ways: > > I added a threshold of 10 "not recognized" errors, which if exceeded > AND we have NOT SEEN ANY valid commands, the following actions take place: > > 1. Processing of the message is terminated. > > 2. The help text is not sent. > > 3. Instead of replying to the "sender", we send just send a short > note to majordomo-owner that says a message with > THRESHOLD errors was > found and a reply was NOT sent to "sender". > > I'll be happy to make this code available in any way that is appropriate. > > Bill Dudley > > !DSPAM:42cd6718498858384116375! > > From majordomo-users-owner@greatcircle.com Thu Jul 7 13:17:32 2005 X-Original-To: majordomo-users@greatcircle.com Received: from eagle.netwrx1.com (adsl-68-248-203-41.dsl.milwwi.ameritech.net [68.248.203.41]) by mycroft.greatcircle.com (Postfix) with ESMTP id E453732C338 for ; Thu, 7 Jul 2005 13:17:31 -0700 (PDT) Received: from [192.168.1.1] (helo=COV10020694.wfsi.priv ident=root) by eagle.netwrx1.com with smtp (Exim 3.36 #1) id 1Dqco5-0000QY-00; Thu, 07 Jul 2005 15:17:13 -0500 From: George R.Kasica To: "William Dudley Jr." Cc: majordomo-users@greatcircle.com Subject: Re: proposed solution for spam sent to majordomo@yourdomain Date: Thu, 07 Jul 2005 15:17:13 -0500 Organization: Netwrx Consulting Inc. Reply-To: georgek@netwrx1.com Message-ID: References: <200507071731.j67HVjHC049870@dudley.casano.com> In-Reply-To: <200507071731.j67HVjHC049870@dudley.casano.com> X-Mailer: Forte Agent 3.0/32.729 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Scanner: exiscan *1Dqco5-0000QY-00*/9iCra0V702* (Netwrx Consulting Inc., Jackson, WI USA) X-Archive-Number: 200507/3 X-Sequence-Number: 5107 >On Thu, 7 Jul 2005 13:31:45 -0400 (EDT), you wrote: >Recently, I've been seeing a fair number of spam messages that >have been sent to my majordomo address. They are sent from bogus >"From:" addresses, and since majordomo doesn't need Viagra, etc, >"he" replies with a long stream of error messages: > >&squawk("Command '$cmd' not recognized."); > >This message with every line parroted back as "not recognized" PLUS >the majordomo help text is then sent to the fake "From:" address, >and the isp, if it exists, sends it BACK to me complaining about >a non-existant user. As majordomo-owner, I get it in my inbox. > >To put a stop to this, I modified majordomo in the following ways: > >I added a threshold of 10 "not recognized" errors, which if exceeded >AND we have NOT SEEN ANY valid commands, the following actions take place: > >1. Processing of the message is terminated. > >2. The help text is not sent. > >3. Instead of replying to the "sender", we send just send a short >note to majordomo-owner that says a message with > THRESHOLD errors was >found and a reply was NOT sent to "sender". > >I'll be happy to make this code available in any way that is appropriate. > >Bill Dudley Bill: I'm having a similar problem here with spam going directly to the list addresses such as the digestify etc. Do you know a way I can stop this from getting in my digests as I am now to the point where it will generate a digest of only spam...I'm running spamassassin here and looking for various taboo headers and X-Spam type stuff but somehow they seem to get the messages past the spamassassin step. Feel free to reply off list if you feel its not appropriate here on list. I can provide samples or my settings if needed George ===[George R. Kasica]=== +1 262 677 0766 President +1 206 374 6482 FAX Netwrx Consulting Inc. Jackson, WI USA http://www.netwrx1.com georgek@netwrx1.com ICQ #12862186 From majordomo-users-owner@greatcircle.com Thu Jul 7 13:37:57 2005 X-Original-To: majordomo-users@greatcircle.com Received: from dudley.casano.com (dudley.casano.com [209.191.27.30]) by mycroft.greatcircle.com (Postfix) with ESMTP id AA0F632C509 for ; Thu, 7 Jul 2005 13:37:56 -0700 (PDT) Received: from dudley.casano.com (localhost.casano.com [127.0.0.1]) by dudley.casano.com (8.13.3/8.13.3) with ESMTP id j67Kb6Mq058946; Thu, 7 Jul 2005 16:37:14 -0400 (EDT) (envelope-from wfd99@dudley.casano.com) Received: (from wfd99@localhost) by dudley.casano.com (8.13.3/8.13.3/Submit) id j67Kb6KO058945; Thu, 7 Jul 2005 16:37:06 -0400 (EDT) (envelope-from wfd99) Date: Thu, 7 Jul 2005 16:37:06 -0400 (EDT) From: "William Dudley Jr." Message-Id: <200507072037.j67Kb6KO058945@dudley.casano.com> To: georgek@netwrx1.com, majordomo-users@greatcircle.com Subject: stopping spammers from sending via your mailing list In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (dudley.casano.com [127.0.0.1]); Thu, 07 Jul 2005 16:37:14 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on dudley.casano.com X-Virus-Status: Clean X-Archive-Number: 200507/4 X-Sequence-Number: 5108 George, First it's paramount that you determine what address the spam is being sent to. Once that is determined, you can act: I assume the list is closed and only list members are allowed to post messages. If so, then either a) a list member is spamming the list (unlikely) or b) there is a hole through which spammers are able to address the list that bypasses the list membership requirement. The following is only useful if you run sendmail: I had this problem a couple of years ago, and found that the problem was well-known: if the list is called foo, then foo-outgoing will be mentioned in the headers of each outgoing message. This is a mail alias on your machine that BYPASSES majordomo, so ANY mail to it will just get sent to the list. Spammer programs on zombie Windoze computers were harvesting the addresses from the headers of any email stored on the luser's computer. The standard fixes are: 1. change your alias for each list so that instead of: foo: "|/usr/local/majordomo/demime '|/usr/local/majordomo/wrapper resend -p bulk -M 10000 -l foo -h dudley.casano.com -I foo foo-outgoing' " You put foo: "|/usr/local/majordomo/demime '|/usr/local/majordomo/wrapper resend -p bulk -M 10000 -l foo -h dudley.casano.com -I foo f0o-0utgoing,null' " Note the addition of ",null" to the alias. This prevents sendmail from putting the outgoing address in the headers. As an extra step, I changed my outgoing address from foo-outgoing to f0o-0utgoing in order to invalidate the old compromised outgoing address. 2. Add this magic recipe to your virtusertable: f0o-0utgoing@casano.com error:nouser User unknown owner-f0o-0utgoing@casano.com error:nouser User unknown and do whatever it is on your machine that causes virtusertable.db to be rebuilt. ("make" on FreeBSD). This causes sendmail to bounce any message sent to your outgoing alias. I hope this helps. Bill Dudley Jackson, NJ P.S. funny coincidence on the city name, huh? > From georgek@netwrx1.com Thu Jul 7 16:16:57 2005 > From: "George R. Kasica" > To: "William Dudley Jr." > Cc: majordomo-users@greatcircle.com > Subject: Re: proposed solution for spam sent to majordomo@yourdomain > Date: Thu, 07 Jul 2005 15:17:13 -0500 > > Bill: > > I'm having a similar problem here with spam going directly to the list > addresses such as the digestify etc. Do you know a way I can stop this > from getting in my digests as I am now to the point where it will > generate a digest of only spam...I'm running spamassassin here and > looking for various taboo headers and X-Spam type stuff but somehow > they seem to get the messages past the spamassassin step. > > Feel free to reply off list if you feel its not appropriate here on > list. > > I can provide samples or my settings if needed > > George > ===[George R. Kasica]=== +1 262 677 0766 > President +1 206 374 6482 FAX > Netwrx Consulting Inc. Jackson, WI USA > http://www.netwrx1.com > georgek@netwrx1.com > ICQ #12862186 > > !DSPAM:42cd8db9560059412716617! > > From majordomo-users-owner@greatcircle.com Fri Jul 8 11:54:09 2005 X-Original-To: majordomo-users@greatcircle.com Received: from eagle.netwrx1.com (adsl-68-248-203-41.dsl.milwwi.ameritech.net [68.248.203.41]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8DFBD32C1B0 for ; Fri, 8 Jul 2005 11:54:08 -0700 (PDT) Received: from [192.168.1.1] (helo=COV10020694.wfsi.priv ident=root) by eagle.netwrx1.com with smtp (Exim 3.36 #1) id 1Dqxz4-0005eX-00; Fri, 08 Jul 2005 13:53:58 -0500 From: George R.Kasica To: "William Dudley Jr." Cc: majordomo-users@greatcircle.com Subject: Re: stopping spammers from sending via your mailing list Date: Fri, 08 Jul 2005 13:53:57 -0500 Organization: Netwrx Consulting Inc. Reply-To: georgek@netwrx1.com Message-ID: References: <200507072037.j67Kb6KO058945@dudley.casano.com> In-Reply-To: <200507072037.j67Kb6KO058945@dudley.casano.com> X-Mailer: Forte Agent 3.0/32.729 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Scanner: exiscan *1Dqxz4-0005eX-00*sCwakTdLClM* (Netwrx Consulting Inc., Jackson, WI USA) X-Archive-Number: 200507/5 X-Sequence-Number: 5109 Thanks for the note! Now, slight catch, I run exim here. Any thoughts on how that would function for the alias changes or should I take that up with the exim users list and the gurus there. As far as changing the outgoing aliases names, that is how this is happening I'm almost certain. I'll work on modifying them all this weekend. I don't know about the ,null though will need to look at that or do you think exim would tolerate that one?? George >On Thu, 7 Jul 2005 16:37:06 -0400 (EDT), you wrote: >George, > >First it's paramount that you determine what address the spam is being >sent to. Once that is determined, you can act: > >I assume the list is closed and only list members are allowed to post >messages. > >If so, then either a) a list member is spamming the list (unlikely) or >b) there is a hole through which spammers are able to address the >list that bypasses the list membership requirement. > >The following is only useful if you run sendmail: > >I had this problem a couple of years ago, and found that the problem >was well-known: if the list is called foo, then foo-outgoing will >be mentioned in the headers of each outgoing message. This is a >mail alias on your machine that BYPASSES majordomo, so ANY mail to >it will just get sent to the list. Spammer programs on zombie >Windoze computers were harvesting the addresses from the headers >of any email stored on the luser's computer. > >The standard fixes are: > >1. change your alias for each list so that instead of: > >foo: "|/usr/local/majordomo/demime '|/usr/local/majordomo/wrapper resend -p > bulk -M 10000 -l foo -h dudley.casano.com -I foo foo-outgoing' >" > >You put > >foo: "|/usr/local/majordomo/demime '|/usr/local/majordomo/wrapper resend -p > bulk -M 10000 -l foo -h dudley.casano.com -I foo f0o-0utgoing,null' >" > >Note the addition of ",null" to the alias. This prevents sendmail >from putting the outgoing address in the headers. As an extra step, >I changed my outgoing address from foo-outgoing to f0o-0utgoing in >order to invalidate the old compromised outgoing address. > >2. Add this magic recipe to your virtusertable: > >f0o-0utgoing@casano.com error:nouser User unknown >owner-f0o-0utgoing@casano.com error:nouser User unknown > >and do whatever it is on your machine that causes virtusertable.db >to be rebuilt. ("make" on FreeBSD). > >This causes sendmail to bounce any message sent to your outgoing alias. > >I hope this helps. > >Bill Dudley >Jackson, NJ > >P.S. funny coincidence on the city name, huh? > >> From georgek@netwrx1.com Thu Jul 7 16:16:57 2005 >> From: "George R. Kasica" >> To: "William Dudley Jr." >> Cc: majordomo-users@greatcircle.com >> Subject: Re: proposed solution for spam sent to majordomo@yourdomain >> Date: Thu, 07 Jul 2005 15:17:13 -0500 >> >> Bill: >> >> I'm having a similar problem here with spam going directly to the list >> addresses such as the digestify etc. Do you know a way I can stop this >> from getting in my digests as I am now to the point where it will >> generate a digest of only spam...I'm running spamassassin here and >> looking for various taboo headers and X-Spam type stuff but somehow >> they seem to get the messages past the spamassassin step. >> >> Feel free to reply off list if you feel its not appropriate here on >> list. >> >> I can provide samples or my settings if needed >> >> George >> ===[George R. Kasica]=== +1 262 677 0766 >> President +1 206 374 6482 FAX >> Netwrx Consulting Inc. Jackson, WI USA >> http://www.netwrx1.com >> georgek@netwrx1.com >> ICQ #12862186 >> >> !DSPAM:42cd8db9560059412716617! >> >> ===[George R. Kasica]=== +1 262 677 0766 President +1 206 374 6482 FAX Netwrx Consulting Inc. Jackson, WI USA http://www.netwrx1.com georgek@netwrx1.com ICQ #12862186 From majordomo-users-owner@greatcircle.com Fri Jul 8 11:59:32 2005 X-Original-To: majordomo-users@greatcircle.com Received: from mailbox.onlinepolicy.net (mailbox.onlinepolicy.net [64.62.161.194]) by mycroft.greatcircle.com (Postfix) with ESMTP id D4FA332C404 for ; Fri, 8 Jul 2005 11:59:31 -0700 (PDT) Received: by mailbox.onlinepolicy.net (Postfix, from userid 504) id 4546B18B1AF; Fri, 8 Jul 2005 11:54:15 -0700 (PDT) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by mailbox.onlinepolicy.net (Postfix) with ESMTP id 462B718B1AF; Fri, 8 Jul 2005 11:54:13 -0700 (PDT) Message-ID: <42CECD08.8020100@queernet.org> Date: Fri, 08 Jul 2005 11:59:20 -0700 From: "Roger B.A. Klorese " User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: georgek@netwrx1.com Cc: "William Dudley Jr." , majordomo-users@greatcircle.com Subject: Re: stopping spammers from sending via your mailing References: <200507072037.j67Kb6KO058945@dudley.casano.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200507/6 X-Sequence-Number: 5110 George R.Kasica wrote: >Thanks for the note! > >Now, slight catch, I run exim here. Any thoughts on how that would >function for the alias changes or should I take that up with the exim >users list and the gurus there. > > > See http://www.averillpark.net/exim/majordomo.html From majordomo-users-owner@greatcircle.com Fri Jul 8 12:17:56 2005 X-Original-To: majordomo-users@greatcircle.com Received: from ns.nrns.ca (ns.nrns.ca [216.191.212.230]) by mycroft.greatcircle.com (Postfix) with ESMTP id A6C1032C427 for ; Fri, 8 Jul 2005 12:17:55 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by ns.nrns.ca (_) with ESMTP id 8E5A2256F7 for ; Fri, 8 Jul 2005 15:17:54 -0400 (EDT) Received: from feline.nrns.ca (feline.nrns.ca [10.111.111.68]) by ns.nrns.ca (_) with ESMTP id DEF222560C for ; Fri, 8 Jul 2005 15:17:51 -0400 (EDT) Received: from nrns.ca (host76.nrns.ca [10.111.111.76]) by feline.nrns.ca (8.12.9/8.12.9) with ESMTP id j68JHpfu067496 for ; Fri, 8 Jul 2005 15:17:51 -0400 (EDT) Message-ID: <42CED1FC.8040308@nrns.ca> Date: Fri, 08 Jul 2005 15:20:28 -0400 From: "Allan P. Magmanlac" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: MAJORDOMO-USERS Subject: sender allowed to post but not in recipient list Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at nrns.ca X-Archive-Number: 200507/7 X-Sequence-Number: 5111 Hello all; Is is possible for a list be modified to allow "user@example.com" to send to the list but not be on the list of recipients, or be returned if a "Who" command is done on the list? Thanks Allan From majordomo-users-owner@greatcircle.com Fri Jul 8 12:42:05 2005 X-Original-To: majordomo-users@greatcircle.com Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 4FD7832C444 for ; Fri, 8 Jul 2005 12:42:04 -0700 (PDT) Received: from ylpvm01.prodigy.net (ylpvm01-int.prodigy.net [207.115.5.207]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id j68JfxXZ020248 for ; Fri, 8 Jul 2005 15:42:00 -0400 Received: from DEAN (adsl-64-170-3-6.dsl.mtry01.pacbell.net [64.170.3.6]) by ylpvm01.prodigy.net (8.13.4 dk-milter linux/8.13.4) with ESMTP id j68JfxPq017154 for ; Fri, 8 Jul 2005 15:42:00 -0400 Message-ID: <03b301c583f5$20023950$61acfea9@DEAN> From: "Dean Mail" To: "MAJORDOMO-USERS" References: <42CED1FC.8040308@nrns.ca> Subject: Re: sender allowed to post but not in recipient list Date: Fri, 8 Jul 2005 12:41:56 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Archive-Number: 200507/8 X-Sequence-Number: 5112 " ... Is is possible for a list be modified to allow "user@example.com" to send to the list but not be on the list of recipients, or be returned if a "Who" command is done on the list? ..." In your Majordomo lists directory, add a file (or create a list) called "posters" (or call it whatever you'd like). Put user@example.com in that file. In your config file for the list to which you want user@example.com to be able to post, add "posters" (or whatever you've named it) to the "restrict_post" variable. -- Dean From majordomo-users-owner@greatcircle.com Fri Jul 8 12:44:28 2005 X-Original-To: majordomo-users@greatcircle.com Received: from tomts13-srv.bellnexxia.net (tomts13.bellnexxia.net [209.226.175.34]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8C9E832C45A for ; Fri, 8 Jul 2005 12:43:45 -0700 (PDT) Received: from acer.sympatico.ca ([65.95.175.100]) by tomts13-srv.bellnexxia.net (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP id <20050708194344.SSBB25800.tomts13-srv.bellnexxia.net@acer.sympatico.ca> for ; Fri, 8 Jul 2005 15:43:44 -0400 Message-Id: <5.2.1.1.0.20050708152531.04f749f0@pop6.sympatico.ca> X-Sender: b1wudu74@pop6.sympatico.ca X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Fri, 08 Jul 2005 15:32:47 -0400 To: MAJORDOMO-USERS From: Frank Bax Subject: Re: sender allowed to post but not in recipient list In-Reply-To: <42CED1FC.8040308@nrns.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200507/9 X-Sequence-Number: 5113 At 03:20 PM 7/8/05, Allan P. Magmanlac wrote: >Is is possible for a list be modified to allow "user@example.com" to send >to the list but not be on the list of recipients, or be returned if a "Who" >command is done on the list? The list of subscribers (recipients) and the list of email addresses allowed to post (restrict_post) are two different things. Many people choose to point the "restrict_post" config option to the subscriber list, because that's easy and means "members only" can post to the list. It doesn't have to be that way. For an outgoing only list (like an announcement list) "restrict_post" would point to a file of posters only. The list of valid posters would be manually maintained in this case. If you want a combination of the two (subscribers, and additional posters), I suggest you write a script to combine the subscriber list with "additional poster" list and point "restrict_post" to this combined file. Run the script as often as necessary. From majordomo-users-owner@greatcircle.com Fri Jul 8 12:53:55 2005 X-Original-To: majordomo-users@greatcircle.com Received: from mercury.bard.edu (mercury.bard.edu [192.246.229.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 711AA32C43D for ; Fri, 8 Jul 2005 12:53:54 -0700 (PDT) Received: from femailcop.bard.edu ([10.20.10.28]) by mercury.bard.edu (AIX5.2/8.11.6p2/8.11.0) with ESMTP id j68JrqY786574 for ; Fri, 8 Jul 2005 15:53:52 -0400 Received: from billysol.bard.edu ([10.20.10.76]) by femailcop.bard.edu (MailMonitor for SMTP v1.2.2 ) ; Fri, 8 Jul 2005 15:31:31 -0400 (EDT) Message-ID: <42CEDA6B.3060103@bard.edu> Date: Fri, 08 Jul 2005 15:56:27 -0400 From: Richard Draves Organization: Bard College User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: MAJORDOMO-USERS Subject: Re: sender allowed to post but not in recipient list References: <5.2.1.1.0.20050708152531.04f749f0@pop6.sympatico.ca> In-Reply-To: <5.2.1.1.0.20050708152531.04f749f0@pop6.sympatico.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 0527-2, 07/08/2005), Outbound message X-Antivirus-Status: Clean X-Archive-Number: 200507/10 X-Sequence-Number: 5114 Frank Bax wrote: > At 03:20 PM 7/8/05, Allan P. Magmanlac wrote: > >> Is is possible for a list be modified to allow "user@example.com" to >> send >> to the list but not be on the list of recipients, or be returned if a >> "Who" >> command is done on the list? > > > > The list of subscribers (recipients) and the list of email addresses > allowed to post (restrict_post) are two different things. Many people > choose to point the "restrict_post" config option to the subscriber > list, because that's easy and means "members only" can post to the list. > > It doesn't have to be that way. For an outgoing only list (like an > announcement list) "restrict_post" would point to a file of posters > only. The list of valid posters would be manually maintained in this > case. > > If you want a combination of the two (subscribers, and additional > posters), I suggest you write a script to combine the subscriber list > with "additional poster" list and point "restrict_post" to this > combined file. Run the script as often as necessary. Or just put put both lists in the restrict_post variable, separated by a comma. -- Have a good day! Dick Draves Systems Administrator Bard College (845) 758-7119 From majordomo-users-owner@greatcircle.com Fri Jul 8 12:54:43 2005 X-Original-To: majordomo-users@greatcircle.com Received: from mail.bcpl.net (mail.bcpl.net [204.255.212.10]) by mycroft.greatcircle.com (Postfix) with ESMTP id 9E1B132C43A for ; Fri, 8 Jul 2005 12:54:42 -0700 (PDT) Received: from mail.bcpl.net (localhost [127.0.0.1]) by mail.bcpl.net (8.13.0/8.13.0) with ESMTP id j68JsfU4017665; Fri, 8 Jul 2005 15:54:41 -0400 (EDT) Received: from localhost (fold@localhost) by mail.bcpl.net (8.13.0/8.13.0/Submit) with ESMTP id j68JsaFB017652; Fri, 8 Jul 2005 15:54:36 -0400 (EDT) X-Authentication-Warning: mail.bcpl.net: fold owned process doing -bs Date: Fri, 8 Jul 2005 15:54:36 -0400 (EDT) From: Chip Old X-X-Sender: fold@mail To: Frank Bax Cc: MAJORDOMO-USERS Subject: Re: sender allowed to post but not in recipient In-Reply-To: <5.2.1.1.0.20050708152531.04f749f0@pop6.sympatico.ca> Message-ID: References: <5.2.1.1.0.20050708152531.04f749f0@pop6.sympatico.ca> X-Organization: BCPL.NET Internet Services X-Complaints-To: abuse@bcpl.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Archive-Number: 200507/11 X-Sequence-Number: 5115 On Fri, 8 Jul 2005 15:32 -0400, Frank Bax wrote: > If you want a combination of the two (subscribers, and additional > posters), I suggest you write a script to combine the subscriber list > with "additional poster" list and point "restrict_post" to this combined > file. Run the script as often as necessary. Not necessary. The restrict_post variable will accept multiple filenames. If your main list is "foo" and your post-only list is "bar", do this: restrict_post = foo:bar -- Chip Old (Francis E. Old) E-Mail: fold@bcpl.net BCPL Network Administrator Phone: 410-887-6180 BCPL.NET Internet Services Manager FAX: 410-887-2091 320 York Road Towson, MD 21204-5179 USA From majordomo-users-owner@greatcircle.com Fri Jul 8 13:55:58 2005 X-Original-To: majordomo-users@greatcircle.com Received: from S4.cableone.net (s4.cableone.net [24.116.0.230]) by mycroft.greatcircle.com (Postfix) with ESMTP id E014532C28B for ; Fri, 8 Jul 2005 13:55:57 -0700 (PDT) Received: from mail.sonny.com (unverified [24.116.58.25]) by S4.cableone.net (CableOne SMTP Service S4) with ESMTP id 24847226 for ; Fri, 08 Jul 2005 14:22:38 -0700 Received: from [192.168.1.60] (dad.sonny.com [192.168.1.60]) (authenticated bits=0) by mail.sonny.com (8.12.8/8.12.8) with ESMTP id j68KrrTx019439 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 8 Jul 2005 15:53:53 -0500 Message-ID: <42CEE7F8.9000802@sonny.org> Date: Fri, 08 Jul 2005 15:54:16 -0500 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Majordomo Users Subject: Re: sender allowed to post but not in recipient list References: <5.2.1.1.0.20050708152531.04f749f0@pop6.sympatico.ca> <42CEDA6B.3060103@bard.edu> In-Reply-To: <42CEDA6B.3060103@bard.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IP-stats: Incoming Outgoing Last 1, First 50, in=105, out=8, spam=0 Known=true X-External-IP: 24.116.58.25 X-Abuse-Info: Send abuse complaints to abuse@cableone.net X-Archive-Number: 200507/12 X-Sequence-Number: 5116 >> If you want a combination of the two (subscribers, and additional >> posters), I suggest you write a script to combine the subscriber list >> with "additional poster" list and point "restrict_post" to this >> combined file. Run the script as often as necessary. > > > Or just put put both lists in the restrict_post variable, separated by a > comma. > Unfortunately, I believe [space] and [colon] are the only allowed separators. From the top of the *.config file comments for every list... # restrict_post -- a series of space or : separated file names in # which to look up the senders address Dan Liston From majordomo-users-owner@greatcircle.com Fri Jul 8 14:06:12 2005 X-Original-To: majordomo-users@greatcircle.com Received: from eagle.netwrx1.com (adsl-68-248-203-41.dsl.milwwi.ameritech.net [68.248.203.41]) by mycroft.greatcircle.com (Postfix) with ESMTP id 7934A32C48B for ; Fri, 8 Jul 2005 14:06:11 -0700 (PDT) Received: from [192.168.1.1] (helo=COV10020694.wfsi.priv ident=root) by eagle.netwrx1.com with smtp (Exim 3.36 #1) id 1Dr02l-0007ns-00; Fri, 08 Jul 2005 16:05:55 -0500 From: George R.Kasica To: "Roger B.A. Klorese " Cc: "William Dudley Jr." , majordomo-users@greatcircle.com Subject: Re: stopping spammers from sending via your mailing list Date: Fri, 08 Jul 2005 16:05:51 -0500 Organization: Netwrx Consulting Inc. Reply-To: georgek@netwrx1.com Message-ID: <6hqtc1lhj1r5hics50545snvjbq18gb89s@4ax.com> References: <200507072037.j67Kb6KO058945@dudley.casano.com> <42CECD08.8020100@queernet.org> In-Reply-To: <42CECD08.8020100@queernet.org> X-Mailer: Forte Agent 3.0/32.729 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Scanner: exiscan *1Dr02l-0007ns-00*zYMEGELXNq6* (Netwrx Consulting Inc., Jackson, WI USA) X-Archive-Number: 200507/13 X-Sequence-Number: 5117 >On Fri, 08 Jul 2005 11:59:20 -0700, you wrote: >George R.Kasica wrote: > >>Thanks for the note! >> >>Now, slight catch, I run exim here. Any thoughts on how that would >>function for the alias changes or should I take that up with the exim >>users list and the gurus there. >> >> >> > >See http://www.averillpark.net/exim/majordomo.html > > Roger: Unfortunately, at this time I'm still Exim 3.36. If someone would like to assist in getting the 3.36 configs converted to 4.5x I'd go to it tomorrow, but I'm by no means an Exim expert and the conversion can't have any major hitches as this box supports 120+ users and about a dozen lists. Would you be willing to help with the conversion effort or know someone willing? I'm able to compile and install but when it comes to the config that's where I'm hesitant to mess with it. George From majordomo-users-owner@greatcircle.com Sun Jul 10 05:38:37 2005 X-Original-To: majordomo-users@greatcircle.com Received: from eagle.netwrx1.com (adsl-68-248-203-41.dsl.milwwi.ameritech.net [68.248.203.41]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1A4E432C159 for ; Sun, 10 Jul 2005 05:38:34 -0700 (PDT) Received: from [68.248.203.45] (helo=NOTEBOOK-LOCAL.netwrx1.com) by eagle.netwrx1.com with smtp (Exim 3.36 #1) id 1Drb4h-0004K9-00; Sun, 10 Jul 2005 07:38:23 -0500 From: George R.Kasica To: "William Dudley Jr." Cc: majordomo-users@greatcircle.com Subject: Re: stopping spammers from sending via your mailing list Date: Sun, 10 Jul 2005 07:37:51 -0500 Organization: Netwrx Consulting Inc. Reply-To: georgek@netwrx1.com Message-ID: <1e52d197b5tmqa9iauiaqb63t9d12g14fb@4ax.com> References: <200507072037.j67Kb6KO058945@dudley.casano.com> In-Reply-To: X-Mailer: Forte Agent 3.0/32.731 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Scanner: exiscan *1Drb4h-0004K9-00*62u9fgpqTes* (Netwrx Consulting Inc., Jackson, WI USA) X-Archive-Number: 200507/14 X-Sequence-Number: 5118 >On Fri, 08 Jul 2005 13:53:57 -0500, you wrote: >Thanks for the note! > >Now, slight catch, I run exim here. Any thoughts on how that would >function for the alias changes or should I take that up with the exim >users list and the gurus there. > >As far as changing the outgoing aliases names, that is how this is >happening I'm almost certain. I'll work on modifying them all this >weekend. I don't know about the ,null though will need to look at that >or do you think exim would tolerate that one?? > >George > > > >>On Thu, 7 Jul 2005 16:37:06 -0400 (EDT), you wrote: > >>George, >> >>First it's paramount that you determine what address the spam is being >>sent to. Once that is determined, you can act: >> >>I assume the list is closed and only list members are allowed to post >>messages. >> >>If so, then either a) a list member is spamming the list (unlikely) or >>b) there is a hole through which spammers are able to address the >>list that bypasses the list membership requirement. >> >>The following is only useful if you run sendmail: >> >>I had this problem a couple of years ago, and found that the problem >>was well-known: if the list is called foo, then foo-outgoing will >>be mentioned in the headers of each outgoing message. This is a >>mail alias on your machine that BYPASSES majordomo, so ANY mail to >>it will just get sent to the list. Spammer programs on zombie >>Windoze computers were harvesting the addresses from the headers >>of any email stored on the luser's computer. >> >>The standard fixes are: >> >>1. change your alias for each list so that instead of: >> >>foo: "|/usr/local/majordomo/demime '|/usr/local/majordomo/wrapper resend -p >> bulk -M 10000 -l foo -h dudley.casano.com -I foo foo-outgoing' >>" >> >>You put >> >>foo: "|/usr/local/majordomo/demime '|/usr/local/majordomo/wrapper resend -p >> bulk -M 10000 -l foo -h dudley.casano.com -I foo f0o-0utgoing,null' >>" >> >>Note the addition of ",null" to the alias. This prevents sendmail >>from putting the outgoing address in the headers. As an extra step, >>I changed my outgoing address from foo-outgoing to f0o-0utgoing in >>order to invalidate the old compromised outgoing address. >> >>2. Add this magic recipe to your virtusertable: >> >>f0o-0utgoing@casano.com error:nouser User unknown >>owner-f0o-0utgoing@casano.com error:nouser User unknown >> >>and do whatever it is on your machine that causes virtusertable.db >>to be rebuilt. ("make" on FreeBSD). >> >>This causes sendmail to bounce any message sent to your outgoing alias. >> >>I hope this helps. >> >>Bill Dudley >>Jackson, NJ >> >>P.S. funny coincidence on the city name, huh? >> Bill: Tried your suggestion in the part of changing the outgoing names here in both the majordomo-aliases and majordomo-private-aliases files and did 2 replaces, outgoing to Outgoing and digestify to Digestify and got the following error on attempting to send a message. It seems that it doesn't know the user. What am I missing? If I switch it back to what it was no problems.... To: owner-acg-l@netwrx1.com Subject: Mail delivery failed: returning message to sender From: Mail Delivery System Date: Sun, 10 Jul 2005 07:24:27 -0500 This message was created automatically by mail delivery software (Exim). A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: acg-l-Outgoing@netwrx1.com unknown local-part "acg-l-Outgoing" in domain "netwrx1.com" ------ This is a copy of the message, including all the headers. ------ Return-path: Received: from majordom by eagle.netwrx1.com with local (Exim 3.36 #1) id 1Drar8-0004BT-00 for acg-l-Outgoing@netwrx1.com; Sun, 10 Jul 2005 07:24:22 -0500 Received: from mail by eagle.netwrx1.com with spam-scanned (Exim 3.36 #1) id 1Draqt-0004BH-00 for acg-l@netwrx1.com; Sun, 10 Jul 2005 07:24:16 -0500 Received: from [68.248.203.45] (helo=NOTEBOOK-LOCAL.netwrx1.com) by eagle.netwrx1.com with smtp (Exim 3.36 #1) id 1Draql-0004B6-00 for acg-l@netwrx1.com; Sun, 10 Jul 2005 07:23:59 -0500 From: George R. Kasica To: acg-l@netwrx1.com Subject: ACG: TEST Date: Sun, 10 Jul 2005 07:23:24 -0500 Organization: Netwrx Consulting Inc. Message-ID: X-Mailer: Forte Agent 3.0/32.731 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Scanner: exiscan *1Draql-0004B6-00*i.1LLeRY9V.* (Netwrx Consulting Inc., Jackson, WI USA) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on eagle.netwrx1.com X-Spam-Status: No, score=-5.2 required=5.0 tests=ALL_TRUSTED,BAYES_00,TW_WR autolearn=ham version=3.0.4 Sender: owner-acg-l@netwrx1.com Precedence: list Reply-To: acg-l@netwrx1.com From majordomo-users-owner@greatcircle.com Mon Jul 11 07:01:40 2005 X-Original-To: majordomo-users@greatcircle.com Received: from ns.nrns.ca (ns.nrns.ca [216.191.212.230]) by mycroft.greatcircle.com (Postfix) with ESMTP id 7FF5F32C29A for ; Mon, 11 Jul 2005 07:01:34 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by ns.nrns.ca (_) with ESMTP id A7CAD257A7; Mon, 11 Jul 2005 10:01:37 -0400 (EDT) Received: from feline.nrns.ca (feline.nrns.ca [10.111.111.68]) by ns.nrns.ca (_) with ESMTP id 28A342579E; Mon, 11 Jul 2005 10:01:35 -0400 (EDT) Received: from nrns.ca (host76.nrns.ca [10.111.111.76]) by feline.nrns.ca (8.12.9/8.12.9) with ESMTP id j6BE1Qfu009031; Mon, 11 Jul 2005 10:01:30 -0400 (EDT) Message-ID: <42D27C54.70807@nrns.ca> Date: Mon, 11 Jul 2005 10:04:04 -0400 From: "Allan P. Magmanlac" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dean Mail Cc: MAJORDOMO-USERS Subject: Re: sender allowed to post but not in recipient list References: <42CED1FC.8040308@nrns.ca> <03b301c583f5$20023950$61acfea9@DEAN> In-Reply-To: <03b301c583f5$20023950$61acfea9@DEAN> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at nrns.ca X-Archive-Number: 200507/15 X-Sequence-Number: 5119 Thanks guys, actually this is my setup however during the test, i have 2 similar entries configured (1 in member list and 1 in the posters list) and so it messed up my testing. All is ok now. Dean Mail wrote: >" ... Is is possible for a list be modified to allow "user@example.com" to >send to the list but not be on the list of recipients, or be returned if a >"Who" command is done on the list? ..." > >In your Majordomo lists directory, add a file (or create a list) called >"posters" (or call it whatever you'd like). > >Put user@example.com in that file. > >In your config file for the list to which you want user@example.com to be >able to post, add "posters" (or whatever you've named it) to the >"restrict_post" variable. > >-- Dean > > > -- -- Allan P. Magmanlac allan.magmanlac@nrns.ca NRNS Incorporated DREnet Network Coordination Centre (NCC) Tel: (613) 599-7860 ext 107 From majordomo-users-owner@greatcircle.com Mon Jul 11 07:08:58 2005 X-Original-To: majordomo-users@greatcircle.com Received: from ns.nrns.ca (ns.nrns.ca [216.191.212.230]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8F6EC32C1A8 for ; Mon, 11 Jul 2005 07:08:55 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by ns.nrns.ca (_) with ESMTP id 08F0125696 for ; Mon, 11 Jul 2005 10:09:01 -0400 (EDT) Received: from feline.nrns.ca (feline.nrns.ca [10.111.111.68]) by ns.nrns.ca (_) with ESMTP id 7FE2F2563F for ; Mon, 11 Jul 2005 10:08:58 -0400 (EDT) Received: from nrns.ca (host76.nrns.ca [10.111.111.76]) by feline.nrns.ca (8.12.9/8.12.9) with ESMTP id j6BE8wfu009095 for ; Mon, 11 Jul 2005 10:08:58 -0400 (EDT) Message-ID: <42D27E17.2040006@nrns.ca> Date: Mon, 11 Jul 2005 10:11:35 -0400 From: "Allan P. Magmanlac" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: MAJORDOMO-USERS Subject: Re: sender allowed to post but not in recipient list References: <42CED1FC.8040308@nrns.ca> <03b301c583f5$20023950$61acfea9@DEAN> <42D27C54.70807@nrns.ca> In-Reply-To: <42D27C54.70807@nrns.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at nrns.ca X-Archive-Number: 200507/16 X-Sequence-Number: 5120 One more thing that I forgot to ask. How can I configure the list so that the list owner (not the majordomo admin) can add members to the "posters" file. Allan P. Magmanlac wrote: > Thanks guys, actually this is my setup however during the test, i have > 2 similar entries configured (1 in member list and 1 in the posters > list) and so it messed up my testing. > All is ok now. > > Dean Mail wrote: > >> " ... Is is possible for a list be modified to allow >> "user@example.com" to send to the list but not be on the list of >> recipients, or be returned if a "Who" command is done on the list? ..." >> >> In your Majordomo lists directory, add a file (or create a list) >> called "posters" (or call it whatever you'd like). >> >> Put user@example.com in that file. >> >> In your config file for the list to which you want user@example.com >> to be able to post, add "posters" (or whatever you've named it) to >> the "restrict_post" variable. >> >> -- Dean >> >> > -- -- Allan P. Magmanlac allan.magmanlac@nrns.ca NRNS Incorporated DREnet Network Coordination Centre (NCC) Tel: (613) 599-7860 ext 107 From majordomo-users-owner@greatcircle.com Mon Jul 11 07:29:30 2005 X-Original-To: majordomo-users@greatcircle.com Received: from mercury.bard.edu (mercury.bard.edu [192.246.229.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1E8BF32C17A for ; Mon, 11 Jul 2005 07:29:15 -0700 (PDT) Received: from femailcop.bard.edu ([10.20.10.28]) by mercury.bard.edu (AIX5.2/8.11.6p2/8.11.0) with ESMTP id j6BETDY1536124 for ; Mon, 11 Jul 2005 10:29:14 -0400 Received: from billysol.bard.edu ([10.20.10.76]) by femailcop.bard.edu (MailMonitor for SMTP v1.2.2 ) ; Mon, 11 Jul 2005 10:06:23 -0400 (EDT) Message-ID: <42D282DA.8040200@bard.edu> Date: Mon, 11 Jul 2005 10:31:54 -0400 From: Richard Draves Organization: Bard College User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: MAJORDOMO-USERS Subject: Re: sender allowed to post but not in recipient list References: <42CED1FC.8040308@nrns.ca> <03b301c583f5$20023950$61acfea9@DEAN> <42D27C54.70807@nrns.ca> <42D27E17.2040006@nrns.ca> In-Reply-To: <42D27E17.2040006@nrns.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 0528-0, 07/11/2005), Outbound message X-Antivirus-Status: Clean X-Archive-Number: 200507/17 X-Sequence-Number: 5121 One way would be to make the "posters' a totally restricted (for posting) list of itself, with an owner (the same) etc. Then the 'owner of posters' could remotely update the 'posters' list. Allan P. Magmanlac wrote: > One more thing that I forgot to ask. How can I configure the list so > that the list owner (not the majordomo admin) can add members to the > "posters" file. > > Allan P. Magmanlac wrote: > >> Thanks guys, actually this is my setup however during the test, i >> have 2 similar entries configured (1 in member list and 1 in the >> posters list) and so it messed up my testing. >> All is ok now. >> >> Dean Mail wrote: >> >>> " ... Is is possible for a list be modified to allow >>> "user@example.com" to send to the list but not be on the list of >>> recipients, or be returned if a "Who" command is done on the list? ..." >>> >>> In your Majordomo lists directory, add a file (or create a list) >>> called "posters" (or call it whatever you'd like). >>> >>> Put user@example.com in that file. >>> >>> In your config file for the list to which you want user@example.com >>> to be able to post, add "posters" (or whatever you've named it) to >>> the "restrict_post" variable. >>> >>> -- Dean >>> >>> >> > -- Have a good day! Dick Draves Systems Administrator Bard College (845) 758-7119 From majordomo-users-owner@greatcircle.com Mon Jul 11 10:58:39 2005 X-Original-To: majordomo-users@greatcircle.com Received: from ns.nrns.ca (ns.nrns.ca [216.191.212.230]) by mycroft.greatcircle.com (Postfix) with ESMTP id 08D6932C157 for ; Mon, 11 Jul 2005 10:58:38 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by ns.nrns.ca (_) with ESMTP id 48F7825723; Mon, 11 Jul 2005 13:58:33 -0400 (EDT) Received: from feline.nrns.ca (feline.nrns.ca [10.111.111.68]) by ns.nrns.ca (_) with ESMTP id 983A92571E; Mon, 11 Jul 2005 13:58:30 -0400 (EDT) Received: from nrns.ca (host76.nrns.ca [10.111.111.76]) by feline.nrns.ca (8.12.9/8.12.9) with ESMTP id j6BHwQfu011554; Mon, 11 Jul 2005 13:58:26 -0400 (EDT) Message-ID: <42D2B3E1.2080600@nrns.ca> Date: Mon, 11 Jul 2005 14:01:05 -0400 From: "Allan P. Magmanlac" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Richard Draves Cc: MAJORDOMO-USERS Subject: Re: sender allowed to post but not in recipient list References: <42CED1FC.8040308@nrns.ca> <03b301c583f5$20023950$61acfea9@DEAN> <42D27C54.70807@nrns.ca> <42D27E17.2040006@nrns.ca> <42D282DA.8040200@bard.edu> In-Reply-To: <42D282DA.8040200@bard.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at nrns.ca X-Archive-Number: 200507/18 X-Sequence-Number: 5122 It would create then a totally different list and this is not what is intended as there should only be one list with other people who can only post to the same and one list. Richard Draves wrote: > One way would be to make the "posters' a totally restricted (for > posting) list of itself, with an owner (the same) etc. > Then the 'owner of posters' could remotely update the 'posters' list. > > Allan P. Magmanlac wrote: > >> One more thing that I forgot to ask. How can I configure the list so >> that the list owner (not the majordomo admin) can add members to the >> "posters" file. >> >> Allan P. Magmanlac wrote: >> >>> Thanks guys, actually this is my setup however during the test, i >>> have 2 similar entries configured (1 in member list and 1 in the >>> posters list) and so it messed up my testing. >>> All is ok now. >>> >>> Dean Mail wrote: >>> >>>> " ... Is is possible for a list be modified to allow >>>> "user@example.com" to send to the list but not be on the list of >>>> recipients, or be returned if a "Who" command is done on the list? >>>> ..." >>>> >>>> In your Majordomo lists directory, add a file (or create a list) >>>> called "posters" (or call it whatever you'd like). >>>> >>>> Put user@example.com in that file. >>>> >>>> In your config file for the list to which you want user@example.com >>>> to be able to post, add "posters" (or whatever you've named it) to >>>> the "restrict_post" variable. >>>> >>>> -- Dean >>>> >>>> >>> >> > -- -- Allan P. Magmanlac allan.magmanlac@nrns.ca NRNS Incorporated DREnet Network Coordination Centre (NCC) Tel: (613) 599-7860 ext 107 From majordomo-users-owner@greatcircle.com Mon Jul 11 12:35:54 2005 X-Original-To: majordomo-users@greatcircle.com Received: from mailbox.onlinepolicy.net (mailbox.onlinepolicy.net [64.62.161.194]) by mycroft.greatcircle.com (Postfix) with ESMTP id 957CF32C319 for ; Mon, 11 Jul 2005 12:35:53 -0700 (PDT) Received: by mailbox.onlinepolicy.net (Postfix, from userid 504) id B375C18B28F; Mon, 11 Jul 2005 12:35:26 -0700 (PDT) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by mailbox.onlinepolicy.net (Postfix) with ESMTP id 24CD918B282; Mon, 11 Jul 2005 12:35:26 -0700 (PDT) Message-ID: <42D2CA12.8090900@queernet.org> Date: Mon, 11 Jul 2005 12:35:46 -0700 From: "Roger B.A. Klorese " User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Allan P. Magmanlac" Cc: Richard Draves , MAJORDOMO-USERS Subject: Re: sender allowed to post but not in recipient References: <42CED1FC.8040308@nrns.ca> <03b301c583f5$20023950$61acfea9@DEAN> <42D27C54.70807@nrns.ca> <42D27E17.2040006@nrns.ca> <42D282DA.8040200@bard.edu> <42D2B3E1.2080600@nrns.ca> In-Reply-To: <42D2B3E1.2080600@nrns.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200507/19 X-Sequence-Number: 5123 Allan P. Magmanlac wrote: > It would create then a totally different list and this is not what is > intended as there should only be one list with other people who can > only post to the same and one list. > You're thinking too narrowly. You're thinking "list == a set of addresses to which mail can be sent." We're telling you that "list == a set of addresses that can be managed using the Majordomo software, and, if proper aliases are set up, to which mail can be sent." Note the "if" portion. Don't set up the aliases (other than the -owner and owner- aliases), and no mail can be sent to this list -- it just becomes a file that can be managed remotely using the Majordomo software so you don't need shell access to the server. Than you list that "list" name in the restrict-post line of your real list. restrict_post = LISTNAME:LISTNAME-posters You're being incredibly resistant to this, and yet, it's how it's been done for years. From majordomo-users-owner@greatcircle.com Mon Jul 11 13:58:29 2005 X-Original-To: majordomo-users@greatcircle.com Received: from mercury.bard.edu (mercury.bard.edu [192.246.229.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2676532C300 for ; Mon, 11 Jul 2005 13:58:27 -0700 (PDT) Received: from femailcop.bard.edu ([10.20.10.28]) by mercury.bard.edu (AIX5.2/8.11.6p2/8.11.0) with ESMTP id j6BKwFY1384504; Mon, 11 Jul 2005 16:58:15 -0400 Received: from billysol.bard.edu ([10.20.10.76]) by femailcop.bard.edu (MailMonitor for SMTP v1.2.2 ) ; Mon, 11 Jul 2005 16:35:22 -0400 (EDT) Message-ID: <42D2DE03.5080407@bard.edu> Date: Mon, 11 Jul 2005 17:00:51 -0400 From: Richard Draves Organization: Bard College User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Roger B.A. Klorese" Cc: "Allan P. Magmanlac" , MAJORDOMO-USERS Subject: Re: sender allowed to post but not in recipient References: <42CED1FC.8040308@nrns.ca> <03b301c583f5$20023950$61acfea9@DEAN> <42D27C54.70807@nrns.ca> <42D27E17.2040006@nrns.ca> <42D282DA.8040200@bard.edu> <42D2B3E1.2080600@nrns.ca> <42D2CA12.8090900@queernet.org> In-Reply-To: <42D2CA12.8090900@queernet.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 0528-1, 07/11/2005), Outbound message X-Antivirus-Status: Clean X-Archive-Number: 200507/20 X-Sequence-Number: 5124 Or to get to the original (I think) plan to allow posters ONLY and not have the list members able to send: restrict_post: LISTNAME-posters Now ONLY those on the LISTNAME-posters list can send (post) to the LISTNAME list. And the LISTNAME-posters is remotely managable. Roger B.A. Klorese wrote: > Allan P. Magmanlac wrote: > >> It would create then a totally different list and this is not what is >> intended as there should only be one list with other people who can >> only post to the same and one list. >> > > You're thinking too narrowly. You're thinking "list == a set of > addresses to which mail can be sent." We're telling you that "list == > a set of addresses that can be managed using the Majordomo software, > and, if proper aliases are set up, to which mail can be sent." Note > the "if" portion. Don't set up the aliases (other than the -owner and > owner- aliases), and no mail can be sent to this list -- it just > becomes a file that can be managed remotely using the Majordomo > software so you don't need shell access to the server. Than you list > that "list" name in the restrict-post line of your real list. > > restrict_post = LISTNAME:LISTNAME-posters > > You're being incredibly resistant to this, and yet, it's how it's been > done for years. -- Have a good day! Dick Draves Systems Administrator Bard College (845) 758-7119 From majordomo-users-owner@greatcircle.com Mon Jul 11 14:00:40 2005 X-Original-To: majordomo-users@greatcircle.com Received: from mailbox.onlinepolicy.net (mailbox.onlinepolicy.net [64.62.161.194]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1491732C29C for ; Mon, 11 Jul 2005 14:00:39 -0700 (PDT) Received: by mailbox.onlinepolicy.net (Postfix, from userid 504) id 33AFC18B28B; Mon, 11 Jul 2005 14:00:18 -0700 (PDT) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by mailbox.onlinepolicy.net (Postfix) with ESMTP id B4E0B18B288; Mon, 11 Jul 2005 14:00:16 -0700 (PDT) Message-ID: <42D2DDF5.9060403@queernet.org> Date: Mon, 11 Jul 2005 14:00:37 -0700 From: "Roger B.A. Klorese " User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Richard Draves Cc: "Allan P. Magmanlac" , MAJORDOMO-USERS Subject: Re: sender allowed to post but not in recipient References: <42CED1FC.8040308@nrns.ca> <03b301c583f5$20023950$61acfea9@DEAN> <42D27C54.70807@nrns.ca> <42D27E17.2040006@nrns.ca> <42D282DA.8040200@bard.edu> <42D2B3E1.2080600@nrns.ca> <42D2CA12.8090900@queernet.org> <42D2DE03.5080407@bard.edu> In-Reply-To: <42D2DE03.5080407@bard.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200507/21 X-Sequence-Number: 5125 Richard Draves wrote: > Or to get to the original (I think) plan to allow posters ONLY and not > have the list members able to send: > > restrict_post: LISTNAME-posters > > Now ONLY those on the LISTNAME-posters list can send (post) to the > LISTNAME list. And the LISTNAME-posters is remotely managable. > Right. It's been so twisty I forgot the original request. Use the method I suggested for all of your subscribers PLUS additional addresses to be allowed to post. Use the method above for ONLY specific addresses to be allowed to post. From majordomo-users-owner@greatcircle.com Mon Jul 25 13:49:38 2005 X-Original-To: majordomo-users@greatcircle.com Received: from localhost.localdomain (unknown [209.190.113.26]) by mycroft.greatcircle.com (Postfix) with ESMTP id 7156A32C339 for ; Mon, 25 Jul 2005 13:49:37 -0700 (PDT) Received: from [209.190.113.26] ([209.190.113.26]) by localhost.localdomain (8.12.11.Beta0/8.12.11.Beta0) with ESMTP id j6PKn3uo029861 for ; Mon, 25 Jul 2005 16:49:03 -0400 Date: Mon, 25 Jul 2005 16:49:03 -0400 (EDT) From: Nick Bradaschia X-X-Sender: nick@localhost.localdomain To: majordomo-users@greatcircle.com Subject: new users needs help Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200507/22 X-Sequence-Number: 5126 Hi, I'm sure this has to have a simple solution but I can't figure it out. I've installed majordomo and it looks like everything went well. I am running sendmail 8.13. When I send a message to majordomo, I never get a response. I see the message in majordomo's inbox and there is mail waiting to be sent in the spool but it never goes anywhere. What's wrong?? Thanks!! Nick