From majordomo-users-owner@greatcircle.com Tue Jul 8 01:28:15 2008 X-Greylist: delayed 61 seconds by postgrey-1.24 at mycroft; Tue, 08 Jul 2008 01:28:14 PDT Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by mycroft.greatcircle.com (Postfix) with ESMTP id BD02F4983DE for ; Tue, 8 Jul 2008 01:28:14 -0700 (PDT) Received: from mail3.siemens.de (localhost [127.0.0.1]) by goliath.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id m688LXWa000960 for ; Tue, 8 Jul 2008 10:21:33 +0200 Received: from mchp771a.ww002.siemens.net (mchp771a.ww002.siemens.net [139.25.131.189]) by mail3.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id m688LXdk026850 for ; Tue, 8 Jul 2008 10:21:33 +0200 Received: from MCHP7IDA.ww902.siemens.net ([139.25.131.144]) by mchp771a.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 8 Jul 2008 10:21:32 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: unvisible user unknown Date: Tue, 8 Jul 2008 10:21:31 +0200 Message-ID: <8081CEEB4FD535468F7738F83A2338E4153CA3@MCHP7IDA.ww902.siemens.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: unvisible user unknown Thread-Index: Acjg06BoZods1qkpQqmMsjMhhQkk6A== From: "Mattis, Oliver" To: X-OriginalArrivalTime: 08 Jul 2008 08:21:32.0410 (UTC) FILETIME=[A102DDA0:01C8E0D3] X-Archive-Number: 200807/1 X-Sequence-Number: 5740 Dear Majordomo-fellows, =20 i=B4m on the search about resolving problems with unvisible user unknown = errors. If majordomo runs on a mailgateway which contains all emailadresses of = the own domain in aliases.db, localhost gives back an user unknown error like this: =20 Jul 7 17:43:35 ownserver sendmail[24709]: m67FhYLm024705: = m67FhZLl024709: DSN: /usr/lib/majordomo/lists/tmuk-ver-int: line 7: = michael.foltz(at)xxxxx.com... User unknown =20 The owner will see, after the user unknown occurs this in his mailbox: =20 Your message To: TMUK VER INT List Subject: xxxxxxxxxxxxxxxxx Sent: Mon, 7 Jul 2008 13:03:21 +0200 did not reach the following recipient(s): tmuk-ver-int-list(at)xxxxxx.xxxxxxx.net on Mon, 7 Jul 2008 13:03:24 +0200 The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. < ownserver #5.1.1> =20 This problem doesn=B4t occurs if majordomo runs on a other server and = give all mails to his smarthost. Due to the constellation majordomo and smarthost together on the same = server, the owner is unable to resolve the problem, because he is unable to see which emailadress is faulty. I know this is not really a prob of majordomo himself, but it seems it = is not best practice to run majordomo on a smarthost.=20 Best regards, Oliver Mattis=20 From majordomo-users-owner@greatcircle.com Tue Jul 8 06:48:02 2008 Received: from dalexmm02.acs-inc.com (dalexmm02.acs-inc.com [63.101.151.4]) by mycroft.greatcircle.com (Postfix) with ESMTP id 18D6649839A for ; Tue, 8 Jul 2008 06:48:00 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoAAMQLc0g/V6pIo2dsb2JhbACCc491AQEBAQEBBwUIBxGdIw Received: from unknown (HELO atlexbr03.CORPATL.COM) ([63.87.170.72]) by dalexmm02.acs-inc.com with ESMTP; 08 Jul 2008 08:33:39 -0500 Received: by atlexbr03.acs-shc.com with Internet Mail Service (5.5.2657.72) id ; Tue, 8 Jul 2008 09:42:15 -0400 Message-ID: From: "Caldwell, Cedric" To: "'majordomo-users@greatcircle.com'" Subject: Majordomo + sendmail issue Date: Tue, 8 Jul 2008 09:42:14 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8E100.6E31A118" X-Archive-Number: 200807/2 X-Sequence-Number: 5741 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C8E100.6E31A118 Content-Type: text/plain Fellow Users, Need some help here.. I've got to the point where the I can send an email to majorodomo and get a reply to send back the auth code. But when I sent it back to the server it never receives it. I noticed that the domain is not correct on the reply. I've created another *.cf file for the other domain needed to accept mail. But still can't put my finger on the issue. Is this sendmail = virtualtable related? Any help would be appreciated. ------_=_NextPart_001_01C8E100.6E31A118 Content-Type: text/html Content-Transfer-Encoding: quoted-printable

 

 

Fellow Users,

 

Need some help here..

 

I've got to the point where the I can send an email to = majorodomo and get a reply to send back the auth = code.

 

But when I sent it back to the server it never receives = it.  I noticed that the domain is not correct on the reply. I've created another *.cf file for the other domain needed to accept mail. But still can't put my finger on the issue.  Is this sendmail =3D virtualtable = related?

 

Any help would be = appreciated. 

 

 

 

------_=_NextPart_001_01C8E100.6E31A118-- From majordomo-users-owner@greatcircle.com Tue Jul 8 11:39:20 2008 X-Greylist: delayed 299 seconds by postgrey-1.24 at mycroft; Tue, 08 Jul 2008 11:39:19 PDT Received: from moroni.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id 5EFA14D00C0 for ; Tue, 8 Jul 2008 11:39:19 -0700 (PDT) Received: from webmail.ourldsfamily.com (moroni0 [172.20.20.2]) by moroni.ourldsfamily.com (8.13.7/8.13.7) with ESMTP id m68ISU7a007125; Tue, 8 Jul 2008 12:28:31 -0600 Received: from ats ([207.173.117.242]) (SquirrelMail authenticated user karlp) by webmail.ourldsfamily.com with HTTP; Tue, 8 Jul 2008 12:28:32 -0600 (MDT) Message-ID: In-Reply-To: References: Date: Tue, 8 Jul 2008 12:28:32 -0600 (MDT) Subject: Re: Majordomo + sendmail issue From: "Karl Pearson" To: "Caldwell, Cedric" Cc: "Majordomo Users" User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Archive-Number: 200807/3 X-Sequence-Number: 5742 On Tue, July 8, 2008 7:42 am, Caldwell, Cedric wrote: > > > > > Fellow Users, > > > > Need some help here.. > > > > I've got to the point where the I can send an email to majorodomo and get a > reply to send back the auth code. > > > > But when I sent it back to the server it never receives it. I noticed that > the domain is not correct on the reply. I've created another *.cf file for > the other domain needed to accept mail. But still can't put my finger on the > issue. Is this sendmail = virtualtable related? I suspect it's a server/sendmail problem. Run hostname and see what's returned. If it's 'the default' of localhost.localdomain or something similar, then you may have to manually set the hostname on the server. Otherwise, you can setup sendmail.cw then run m4 sendmail.cw > sendmail.cf in /etc/mail. If the server uses virtual domains, then I'm not sure. I've not used those settings on my servers. Good luck. Karl > > > > Any help would be appreciated. > > > > > > > > -- Karl L. Pearson karlp@ourldsfamily.com http://consulting.ourldsfamily.com --- My Thoughts on Terrorism In America right after 9/11/2001: http://www.ourldsfamily.com/wtc.shtml --- The world is a dangerous place to live... not because of the people who are evil, but because of the people who don't do anything about it. - Albert Einstein --- "To mess up your Linux PC, you have to really work at it; to mess up a microsoft PC you just have to work on it." --- From majordomo-users-owner@greatcircle.com Wed Jul 9 04:17:14 2008 X-Greylist: delayed 400 seconds by postgrey-1.24 at mycroft; Wed, 09 Jul 2008 04:17:13 PDT Received: from smtp103.sbc.mail.mud.yahoo.com (smtp103.sbc.mail.mud.yahoo.com [68.142.198.202]) by mycroft.greatcircle.com (Postfix) with SMTP id 6600C49840F for ; Wed, 9 Jul 2008 04:17:13 -0700 (PDT) Received: (qmail 68531 invoked from network); 9 Jul 2008 11:04:43 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=yWAWHeAYOew6rhyiHbyk5EUiYRmAo976ZPDKepFlX/PhoRxBvGyfCHihCpdqN076daZkzgud4ldhV2dVbXSNF/xFNRmxNrUTS0YkTVOSVXceJPtp+W/4DcM1kR0kX88nQ8CGD4rC1Hbu4MMJZDeAx78wMBMoqL0UWUEqEgbCHjk= ; Received: from unknown (HELO DESKTOPPRO) (pattersontj@sbcglobal.net@65.66.217.31 with login) by smtp103.sbc.mail.mud.yahoo.com with SMTP; 9 Jul 2008 11:04:43 -0000 X-YMail-OSG: e49MrNsVM1nvN5PWXCKGAQSU.gVm652eQ47YOG9dKAUH28ungFDyrv.SoqfMVvGbvT0pX4uoJa2EFTHPZqCz3.j530pwUrTOD7cAVp3S7I67jx7ipHV3iX3YbwCc6Ia6QtwxkTUuAjxpUeuHvw-- X-Yahoo-Newman-Property: ymail-3 Message-ID: <18d901c8e1b3$94cb82e0$6400a8c0@DESKTOPPRO> From: "Tom Patterson" To: References: Subject: Majordomo and spammers Date: Wed, 9 Jul 2008 06:04:38 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_18D6_01C8E189.AB76FC10" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Archive-Number: 200807/4 X-Sequence-Number: 5743 This is a multi-part message in MIME format. ------=_NextPart_000_18D6_01C8E189.AB76FC10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have recently moved my site to a new server using Q Mail, and = reinstalled Majordomo. I am having two problems. 1. I am getting hit with a great amount of spam addressed to majordomo, = which is generating replies to non-existent addresses, which in turn = bounce back to me. The replies are the standard reply from majordomo = when it does not understand a message. Is there any way of stopping these replies from Majordomo or of = changing the majordomo's address from majordomo@domain.com? 2. All of these spam messages to majordomo are generating zero content = messages in the digest folder, which in turn, adds blank messages to the = digest. How can this be fixed? -Tom ------=_NextPart_000_18D6_01C8E189.AB76FC10 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have recently moved my site to a new server = using Q=20 Mail, and reinstalled Majordomo.  I am having two = problems.
 
1.  I am getting hit with a great amount of = spam=20 addressed to majordomo, which is generating replies to non-existent = addresses,=20 which in turn bounce back to me.  The replies are the standard = reply from=20 majordomo when it does not understand a message.
     Is there any way of = stopping=20 these replies from Majordomo or of changing the majordomo's address from = majordomo@domain.com?
 
2.  All of these spam messages to majordomo = are=20 generating zero content messages in the digest folder, which in turn, = adds blank=20 messages to the digest.  How can this be fixed?
 
-Tom
------=_NextPart_000_18D6_01C8E189.AB76FC10-- From majordomo-users-owner@greatcircle.com Wed Jul 9 07:41:55 2008 X-Greylist: delayed 1255 seconds by postgrey-1.24 at mycroft; Wed, 09 Jul 2008 07:41:52 PDT Received: from DNS1.swccd.edu (dns1.swccd.edu [209.129.112.65]) by mycroft.greatcircle.com (Postfix) with ESMTP id 3587C49839E for ; Wed, 9 Jul 2008 07:41:52 -0700 (PDT) Received: from DNS1.swccd.edu (unknown [127.0.0.1]) by DNS1.swccd.edu (Postfix) with ESMTP id C2711153A99; Wed, 9 Jul 2008 07:15:07 -0700 (PDT) Received: from mail1.swccd.edu (unknown [10.0.4.233]) by DNS1.swccd.edu (Postfix) with ESMTP; Wed, 9 Jul 2008 07:15:07 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8E1CE.305A9C3B" Subject: Re: Majordomo and spammers Date: Wed, 9 Jul 2008 07:15:07 -0700 Message-ID: In-Reply-To: <18d901c8e1b3$94cb82e0$6400a8c0@DESKTOPPRO> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Majordomo and spammers Thread-Index: AcjhtJfh+rg8gxQ9SV6PefG7NMDjawAGOWSQ From: "Al Garrett" To: "Tom Patterson" , X-Archive-Number: 200807/5 X-Sequence-Number: 5744 This is a multi-part message in MIME format. ------_=_NextPart_001_01C8E1CE.305A9C3B Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable This sounds like the back-scatter issue ( http://www.spamresource.com/2007/02/backscatter-what-is-it-how-do-i-stop -it.html ) we recently experienced on our regular mail system. Spammers spoofing a good email address from our institution to fire off a volley and the NDR's getting routed back to the us. Thousands were coming in every day. We deployed a BATV solution at the edge of the enterprise http://mipassoc.org/batv/ Could something like this be used in a majordomo arena? -----Original Message----- From: majordomo-users-owner@greatcircle.com [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Tom Patterson Sent: Wednesday, July 09, 2008 4:05 AM To: majordomo-users@greatcircle.com Subject: Majordomo and spammers =09 =09 I have recently moved my site to a new server using Q Mail, and reinstalled Majordomo. I am having two problems. =20 1. I am getting hit with a great amount of spam addressed to majordomo, which is generating replies to non-existent addresses, which in turn bounce back to me. The replies are the standard reply from majordomo when it does not understand a message. Is there any way of stopping these replies from Majordomo or of changing the majordomo's address from majordomo@domain.com? =20 2. All of these spam messages to majordomo are generating zero content messages in the digest folder, which in turn, adds blank messages to the digest. How can this be fixed? =20 -Tom ------_=_NextPart_001_01C8E1CE.305A9C3B Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Message
This=20 sounds like the back-scatter issue ( http://www.spamresource.com/2007/02/backscatter-what-is-= it-how-do-i-stop-it.html ) we=20 recently experienced on our regular mail system.
Spammers spoofing a good email address from our institution to = fire off a=20 volley and the NDR's getting routed back to the us. Thousands were = coming in=20 every day.
We=20 deployed a BATV solution at the edge of the enterprise  http://mipassoc.org/batv/
Could=20 something like this be used in a majordomo arena?
-----Original Message-----
From:=20 majordomo-users-owner@greatcircle.com=20 [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Tom = Patterson
Sent: Wednesday, July 09, 2008 4:05 = AM
To:=20 majordomo-users@greatcircle.com
Subject: Majordomo and=20 spammers

I have recently moved my site to a new server = using Q=20 Mail, and reinstalled Majordomo.  I am having two = problems.
 
1.  I am getting hit with a great amount = of spam=20 addressed to majordomo, which is generating replies to non-existent = addresses,=20 which in turn bounce back to me.  The replies are the standard = reply from=20 majordomo when it does not understand a message.
     Is there any way of = stopping=20 these replies from Majordomo or of changing the majordomo's address = from majordomo@domain.com?
 
2.  All of these spam messages to = majordomo are=20 generating zero content messages in the digest folder, which in turn, = adds=20 blank messages to the digest.  How can this be = fixed?
 
-Tom
------_=_NextPart_001_01C8E1CE.305A9C3B-- From majordomo-users-owner@greatcircle.com Wed Jul 9 20:09:08 2008 X-Greylist: delayed 672 seconds by postgrey-1.24 at mycroft; Wed, 09 Jul 2008 20:09:08 PDT Received: from cloud.ccsf.cc.ca.us (cloud.ccsf.cc.ca.us [147.144.1.212]) by mycroft.greatcircle.com (Postfix) with ESMTP id 20A7449840F for ; Wed, 9 Jul 2008 20:09:08 -0700 (PDT) Received: from localhost (jjah@localhost) by cloud.ccsf.cc.ca.us (8.11.6/8.11.2) with ESMTP id m6A2pwX06442; Wed, 9 Jul 2008 19:51:58 -0700 (PDT) Date: Wed, 9 Jul 2008 19:51:58 -0700 (PDT) From: "Joe R. Jah" To: Tom Patterson cc: majordomo-users@greatcircle.com Subject: Re: Majordomo and spammers In-Reply-To: <18d901c8e1b3$94cb82e0$6400a8c0@DESKTOPPRO> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200807/6 X-Sequence-Number: 5745 On Wed, 9 Jul 2008, Tom Patterson wrote: > Date: Wed, 9 Jul 2008 06:04:38 -0500 > From: Tom Patterson > To: majordomo-users@greatcircle.com > Subject: Majordomo and spammers > > I have recently moved my site to a new server using Q Mail, and reinstalled Majordomo. I am having two problems. > > 1. I am getting hit with a great amount of spam addressed to majordomo, which is generating replies to non-existent addresses, which in turn bounce back to me. The replies are the standard reply from majordomo when it does not understand a message. > Is there any way of stopping these replies from Majordomo or of changing the majordomo's address from majordomo@domain.com? > > 2. All of these spam messages to majordomo are generating zero content messages in the digest folder, which in turn, adds blank messages to the digest. How can this be fixed? > > -Tom ftp://ftp.ccsf.org/majordomo-patches/1.94.5/noCommand_noBounce.0 Regards, Joe -- _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ _-\<,_ _/ _/ _/_/_/ _/ _/ ......(_)/ (_) _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us From majordomo-users-owner@greatcircle.com Fri Jul 11 07:12:45 2008 Received: from smtp107.sbc.mail.mud.yahoo.com (smtp107.sbc.mail.mud.yahoo.com [68.142.198.206]) by mycroft.greatcircle.com (Postfix) with SMTP id 5849C4982FF for ; Fri, 11 Jul 2008 07:12:44 -0700 (PDT) Received: (qmail 22823 invoked from network); 11 Jul 2008 14:06:33 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=HpIhkeIB0pIA2b5LcLUtOBfuHJH0S0njiPiFkDY5JYQN8JLNdy9KcZpYoK3Q602OXcJLGPP8q2Svbc/Bn65RqS99CfaZRwpDQN7iagoQBGjC8Q+IETmRG0fpL7VtWJUZKx634epK/6494NyvaGovohsfugDjHoCu5NdqGbOLMHE= ; Received: from unknown (HELO DESKTOPPRO) (pattersontj@sbcglobal.net@69.151.213.213 with login) by smtp107.sbc.mail.mud.yahoo.com with SMTP; 11 Jul 2008 14:06:33 -0000 X-YMail-OSG: 7n5m588VM1kAGxp277FvzNx6uCsemtoXBJK4Rdt_QkKgkMFqE4LH_00WuoiktfLi0k5kVMun1ZbuZy7Ka3KQckoY3lWHgnO2vNMoWxF5F_.WCZjW5MYDhgR.iDvvsaA- X-Yahoo-Newman-Property: ymail-3 Message-ID: <01bd01c8e35f$53500310$6400a8c0@DESKTOPPRO> From: "Tom Patterson" To: References: Subject: Re: Majordomo and spammers Date: Fri, 11 Jul 2008 09:06:33 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Archive-Number: 200807/7 X-Sequence-Number: 5746 Thanks to Joe for help on this problem. The patch immediately cut out the messages which were bouncing back to me due to the use of invalid e-mail addresses by the spammers. I am however left with the problem that majordomo is still picking up on the spam messages and creating zero content messages in the digest folder. When the digest is created, it then shows these messages, albeit as blank. I have a script which deletes all zero content messages in the digest folder immediately before the mkdigest command is issued by a cron job. The problem then arises that the remaining messages are not sequentially numbered in the digest folder, and do not all get picked up by the digest. I can get around this problem by renumbering the messages, starting from zero. Also, I have two lists. Only the list starting with the letter "s" is picking up the blank messages. The list starting with the letter "v" does not pick up blank messages. As the spam is addressed to majordomo@domainname, I assume that majordomo is dumping the blank messages into the first folder he comes to. I also assume that if I created a dummy list starting with a alpha character prior to "s", the zero messages would end up there, leaving my list folders unaffected by the spam. I will try this next. However, is there some way to prevent majordomo from creating these zero content messages? -Tom ----- Original Message ----- From: "Joe R. Jah" To: "Tom Patterson" Cc: Sent: Wednesday, July 09, 2008 9:51 PM Subject: Re: Majordomo and spammers > On Wed, 9 Jul 2008, Tom Patterson wrote: > >> Date: Wed, 9 Jul 2008 06:04:38 -0500 >> From: Tom Patterson >> To: majordomo-users@greatcircle.com >> Subject: Majordomo and spammers >> >> I have recently moved my site to a new server using Q Mail, and >> reinstalled Majordomo. I am having two problems. >> >> 1. I am getting hit with a great amount of spam addressed to majordomo, >> which is generating replies to non-existent addresses, which in turn >> bounce back to me. The replies are the standard reply from majordomo >> when it does not understand a message. >> Is there any way of stopping these replies from Majordomo or of >> changing the majordomo's address from majordomo@domain.com? >> >> 2. All of these spam messages to majordomo are generating zero content >> messages in the digest folder, which in turn, adds blank messages to the >> digest. How can this be fixed? >> >> -Tom > > ftp://ftp.ccsf.org/majordomo-patches/1.94.5/noCommand_noBounce.0 > > Regards, > > Joe > -- > _/ _/_/_/ _/ ____________ __o > _/ _/ _/ _/ ______________ _-\<,_ > _/ _/ _/_/_/ _/ _/ ......(_)/ (_) > _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us > From majordomo-users-owner@greatcircle.com Fri Jul 11 08:40:03 2008 X-Greylist: delayed 2425 seconds by postgrey-1.24 at mycroft; Fri, 11 Jul 2008 08:40:03 PDT Received: from zappa.brainiac.com (ZAPPA.BRAINIAC.com [68.15.48.189]) by mycroft.greatcircle.com (Postfix) with ESMTP id 311234982F7 for ; Fri, 11 Jul 2008 08:40:02 -0700 (PDT) Received: from brainiac.com (eno [68.0.195.117]) (authenticated bits=0) by zappa.brainiac.com (8.13.1/8.13.1) with ESMTP id m6BErQIf011041 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 11 Jul 2008 10:53:27 -0400 Date: Fri, 11 Jul 2008 10:53:25 -0400 From: Joe Hartley To: majordomo-users@greatcircle.com Subject: Re: Majordomo and spammers Message-Id: <20080711105325.95dc05ed.jh@brainiac.com> In-Reply-To: <01bd01c8e35f$53500310$6400a8c0@DESKTOPPRO> References: <01bd01c8e35f$53500310$6400a8c0@DESKTOPPRO> X-Mailer: Sylpheed 2.5.0 (GTK+ 2.10.14; i686-pc-linux-gnu) X-Face: e<}kWVz7AOU%7Y[y%"Y%)jByI[9dsnKP{\??7E"4vTGx4){g\C&LaBmH1{dDNf0U_mPBv#c qp\nRqr]T^L:p_H=Tel/;Z$7-C/klmyQ*kB\{},N]n-7*sJ(dYlf(,?f2hekl"0$nD+~T-ZwNK~`oa n"I7[)O/_NOgn@]?b%=6SRU!]O5k9|OA]PF!qIvs>7sE3}Vr*eC|r""6/**uf3ak}Hm.HK$Cri^yyT BzeM Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200807/8 X-Sequence-Number: 5747 On Fri, 11 Jul 2008 09:06:33 -0500 "Tom Patterson" wrote: > Thanks to Joe for help on this problem. The patch immediately cut out the > messages which were bouncing back to me due to the use of invalid e-mail > addresses by the spammers. > > I am however left with the problem that majordomo is still picking up on the > spam messages and creating zero content messages in the digest folder. When > the digest is created, it then shows these messages, albeit as blank. > . . . > Also, I have two lists. Only the list starting with the letter "s" is > picking up the blank messages. The list starting with the letter "v" does > not pick up blank messages. I have never seen this problem on any of the list servers I've run over the years, and my majordomo addresses get more than their fair share of spam messages. Can you post the parts of your aliases file that pertain to the majordomo lists? I suspect the issue has more to do with the configuration there than any issue with majordomo itself. And a huge Thank You to Joe Jah for the posted patch - I've been looking for something like that for a while. -- ====================================================================== Joe Hartley - UNIX/network Consultant - jh@brainiac.com Without deviation from the norm, "progress" is not possible. - FZappa From majordomo-users-owner@greatcircle.com Fri Jul 11 09:24:52 2008 Received: from smtp106.sbc.mail.mud.yahoo.com (smtp106.sbc.mail.mud.yahoo.com [68.142.198.205]) by mycroft.greatcircle.com (Postfix) with SMTP id 9E986498360 for ; Fri, 11 Jul 2008 09:24:51 -0700 (PDT) Received: (qmail 15003 invoked from network); 11 Jul 2008 16:18:39 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=Q7cdX28vNnDKZv1goMTgIvlTrYpBuw0BF3vRpk7OorLiYTgjMqmC9Gy5V2kyDbc/uAZJvdlbkrqL+ccc8FKjZLsDdD3O844ThlzNTQIJ4amgK8vDu90EebmCPvdKmWd8jOQagNjzXhQVZLpOWAnj9FZSUarLcDHJQFdbDbbQ01Q= ; Received: from unknown (HELO DESKTOPPRO) (pattersontj@sbcglobal.net@69.151.213.213 with login) by smtp106.sbc.mail.mud.yahoo.com with SMTP; 11 Jul 2008 16:18:39 -0000 X-YMail-OSG: q8aMPa0VM1lx39_1O3Nejv3lFYdhlmMwQyhn05QWz.Ji7j.wS5unRrmTdP74Pufpsf76S3iAMt_FHyyZE3_.Qe9U.X2AA2dAWVjojX.fgkvsevV56CfwUUXoYFnkbIE- X-Yahoo-Newman-Property: ymail-3 Message-ID: <023f01c8e371$c7ccda80$6400a8c0@DESKTOPPRO> From: "Tom Patterson" To: References: <01bd01c8e35f$53500310$6400a8c0@DESKTOPPRO> <20080711105325.95dc05ed.jh@brainiac.com> Subject: Re: Majordomo and spammers Date: Fri, 11 Jul 2008 11:18:39 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Archive-Number: 200807/9 X-Sequence-Number: 5748 Here are the aliases for the list and digest. Each list has the same, except of course the domainname, owner and email address are shown. 1.) Majordomo # Majordomo's aliases majordomo: "|/usr/local/majordomo/demime - |/usr/local/majordomo/wrapper majordomo" owner-majordomo: owner@xxxxxxxxx.net majordomo-owner: owner-majordomo discard: /dev/null 2.) List #blanklist list aliases blanklist: "|/usr/local/majordomo/demime - |/usr/local/majordomo/resend -l blanklist -C /usr/local/majordomo/majordomo.cf -h domainname.com blanklist-outgoing" blanklist-outgoing: ":include:/usr/local/majordomo/lists/blanklist |/usr/local/majordomo/wrapper digest -R -C -l blanklist-digest blanklist-digest-outgoing" blanklist-request: "|/usr/local/majordomo/demime - |/usr/local/majordomo/wrapper majordomo -l blanklist" owner-blanklist: owner@xxxxxxxxx.net blanklist-owner: owner-blanklist #owner-approval: owner-blanklist 3.) Digest #blanklist-digest list aliases blanklist-digest-outgoing: ":include:/usr/local/majordomo/lists/blanklist-digest" blanklist-digest: blanklist owner-blanklist-digest: owner@xxxxxxxxx.net blanklist-digest-owner: owner-blanklist-digest blanklist-digest-request: "|/usr/local/majordomo/demime - |/usr/local/majordomo/wrapper majordomo -l blanklist-digest" blanklist-digest-approval: owner@xxxxxxxxx.net owner-blanklist-outgoing: owner@xxxxxxxxx.net owner-blanklist-digest-outgoing: owner@xxxxxxxxx.net -Tom ----- Original Message ----- From: "Joe Hartley" To: Sent: Friday, July 11, 2008 9:53 AM Subject: Re: Majordomo and spammers > On Fri, 11 Jul 2008 09:06:33 -0500 > "Tom Patterson" wrote: > >> Thanks to Joe for help on this problem. The patch immediately cut out >> the >> messages which were bouncing back to me due to the use of invalid e-mail >> addresses by the spammers. >> >> I am however left with the problem that majordomo is still picking up on >> the >> spam messages and creating zero content messages in the digest folder. >> When >> the digest is created, it then shows these messages, albeit as blank. >> . . . >> Also, I have two lists. Only the list starting with the letter "s" is >> picking up the blank messages. The list starting with the letter "v" >> does >> not pick up blank messages. > > I have never seen this problem on any of the list servers I've run over > the years, and my majordomo addresses get more than their fair share of > spam messages. > > Can you post the parts of your aliases file that pertain to the majordomo > lists? I suspect the issue has more to do with the configuration there > than > any issue with majordomo itself. > > And a huge Thank You to Joe Jah for the posted patch - I've been looking > for something like that for a while. > > -- > ====================================================================== > Joe Hartley - UNIX/network Consultant - jh@brainiac.com > Without deviation from the norm, "progress" is not possible. - FZappa From majordomo-users-owner@greatcircle.com Fri Jul 11 10:51:20 2008 Received: from dalexmm01.acs-inc.com (dalexmm01.acs-inc.com [63.101.151.3]) by mycroft.greatcircle.com (Postfix) with ESMTP id AC14D4982F7 for ; Fri, 11 Jul 2008 10:51:19 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsQBAI05d0g/V6pIiGdsb2JhbACCc481AQEBDyCdNQ Received: from unknown (HELO atlexbr04.CORPATL.COM) ([63.87.170.72]) by dalexmm01.acs-inc.com with ESMTP; 11 Jul 2008 12:39:06 -0500 Received: by anc0lw00009864.ghs.oneacs.com with Internet Mail Service (5.5.2657.72) id <3WRPYPLZ>; Fri, 11 Jul 2008 13:44:55 -0400 Message-ID: From: "Caldwell, Cedric" To: "'majordomo-users@greatcircle.com'" Subject: Majorcool Debugging Date: Fri, 11 Jul 2008 13:44:53 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8E37D.D38FF706" X-Archive-Number: 200807/10 X-Sequence-Number: 5749 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C8E37D.D38FF706 Content-Type: text/plain Are there any debug options for the majorcool interface. Last week while testing I was at least getting the emails. Now I don't get any response back from the server. Maillog is not showing anything that the message was received. Just need more eyes this to troubleshoot. Any help would be appreciated.. ------_=_NextPart_001_01C8E37D.D38FF706 Content-Type: text/html Content-Transfer-Encoding: quoted-printable

Are there any debug options for the majorcool = interface.  Last week while testing I was at least getting the emails. Now I don't get any response back from the server.

 

Maillog is not showing anything that the message was received.  Just need more eyes this to = troubleshoot.

 

Any help would be = appreciated..

 

 

 

 

 

 

------_=_NextPart_001_01C8E37D.D38FF706-- From majordomo-users-owner@greatcircle.com Fri Jul 11 16:05:14 2008 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1CDD4498359 for ; Fri, 11 Jul 2008 16:05:12 -0700 (PDT) Received: from mail.sonny.com (minute.sonny.com [192.168.1.4]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K3V00I126DDOO@mail.sonny.com> for majordomo-users@greatcircle.com; Fri, 11 Jul 2008 17:56:01 -0500 (CDT) Received: from magnum.sonny.com (magnum.sonny.com [192.168.1.68]) by minute.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K3V00B0T6CYPU@minute.sonny.com> for majordomo-users@greatcircle.com; Fri, 11 Jul 2008 17:55:47 -0500 (CDT) Date: Fri, 11 Jul 2008 17:58:28 -0500 From: Daniel Liston Subject: Re: Majordomo and spammers In-reply-to: <01bd01c8e35f$53500310$6400a8c0@DESKTOPPRO> To: majordomo-users@greatcircle.com Message-id: <4877E594.3050009@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.14 (X11/20080501) References: <01bd01c8e35f$53500310$6400a8c0@DESKTOPPRO> X-Archive-Number: 200807/11 X-Sequence-Number: 5750 I have a sneaky suspicion that your spam may be graphical in nature, where there is no body content, just an attached graphic. Demime removes the HTML content, leaving an empty message (just assuming here), before your aliases file passes the converted message to your -outgoing alias where the digest script is called. You are probably creating your own problem in this case. As for the sequentiality of your pre-digest files, I have seen this too, in some cases. The solution is another patch... I offer this piece of an email that I sent in September of 2003. > Do the timestamps on the digest.$$ messages coincide with times that > email was received for your list? Have you looked in the > $digest_work_dir > to see what files are queued up in there? Are there any skipped > numbers in the sequence of files? You might need to modify line > #176 of the digest script to say > > foreach (sort @files) { > > to clean things up. You might also consider creating a tmp directory > in the majordomo $HOME (or work directory if they are different) with > the proper majordomo ownership and permission, then setting $TMPDIR in > the majordomo.cf to use that directory. In fact, I found reference to the same change on line 176 of digest in a posting from Sept 2000 too. Dan Liston Tom Patterson wrote: > Thanks to Joe for help on this problem. The patch immediately cut out > the messages which were bouncing back to me due to the use of invalid > e-mail addresses by the spammers. > > I am however left with the problem that majordomo is still picking up > on the spam messages and creating zero content messages in the digest > folder. When the digest is created, it then shows these messages, > albeit as blank. > > I have a script which deletes all zero content messages in the digest > folder immediately before the mkdigest command is issued by a cron > job. The problem then arises that the remaining messages are not > sequentially numbered in the digest folder, and do not all get picked > up by the digest. I can get around this problem by renumbering the > messages, starting from zero. > > Also, I have two lists. Only the list starting with the letter "s" is > picking up the blank messages. The list starting with the letter "v" > does not pick up blank messages. > > As the spam is addressed to majordomo@domainname, I assume that > majordomo is dumping the blank messages into the first folder he comes > to. I also assume that if I created a dummy list starting with a > alpha character prior to "s", the zero messages would end up there, > leaving my list folders unaffected by the spam. I will try this next. > > However, is there some way to prevent majordomo from creating these > zero content messages? > > -Tom > > ----- Original Message ----- From: "Joe R. Jah" > > To: "Tom Patterson" > Cc: > Sent: Wednesday, July 09, 2008 9:51 PM > Subject: Re: Majordomo and spammers > > >> On Wed, 9 Jul 2008, Tom Patterson wrote: >> >>> Date: Wed, 9 Jul 2008 06:04:38 -0500 >>> From: Tom Patterson >>> To: majordomo-users@greatcircle.com >>> Subject: Majordomo and spammers >>> >>> I have recently moved my site to a new server using Q Mail, and >>> reinstalled Majordomo. I am having two problems. >>> >>> 1. I am getting hit with a great amount of spam addressed to >>> majordomo, which is generating replies to non-existent addresses, >>> which in turn bounce back to me. The replies are the standard reply >>> from majordomo when it does not understand a message. >>> Is there any way of stopping these replies from Majordomo or of >>> changing the majordomo's address from majordomo@domain.com? >>> >>> 2. All of these spam messages to majordomo are generating zero >>> content messages in the digest folder, which in turn, adds blank >>> messages to the digest. How can this be fixed? >>> >>> -Tom >> >> ftp://ftp.ccsf.org/majordomo-patches/1.94.5/noCommand_noBounce.0 >> >> Regards, >> >> Joe >> -- >> _/ _/_/_/ _/ ____________ __o >> _/ _/ _/ _/ ______________ _-\<,_ >> _/ _/ _/_/_/ _/ _/ ......(_)/ (_) >> _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us >> > From majordomo-users-owner@greatcircle.com Fri Jul 11 23:41:19 2008 X-Greylist: delayed 1870 seconds by postgrey-1.24 at mycroft; Fri, 11 Jul 2008 23:41:18 PDT Received: from yoda.wrenkasky.com (esson.net [216.102.129.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id D27024983BF for ; Fri, 11 Jul 2008 23:41:18 -0700 (PDT) Received: from EDS.esson.net (eds.wrenkasky.com [10.10.10.11]) (authenticated bits=0) by yoda.wrenkasky.com (8.14.2/8.14.2) with ESMTP id m6C63kXR020479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 11 Jul 2008 23:03:51 -0700 Message-Id: <200807120603.m6C63kXR020479@yoda.wrenkasky.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 11 Jul 2008 23:03:45 -0700 To: Daniel Liston , majordomo-users@greatcircle.com From: Ed Kasky Subject: Re: Majordomo and spammers In-Reply-To: <4877E594.3050009@sonny.org> References: <01bd01c8e35f$53500310$6400a8c0@DESKTOPPRO> <4877E594.3050009@sonny.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Received-SPF: pass (yoda.wrenkasky.com: 10.10.10.11 is authenticated by a trusted mechanism) X-Archive-Number: 200807/12 X-Sequence-Number: 5751 FYI, demime also strips attachments at the same time that it strips the mime from a message. I have lots of subscribers scratching their heads on that one... Ed At 03:58 PM Friday, 7/11/2008, Daniel Liston wrote -=> >I have a sneaky suspicion that your spam may be graphical in nature, >where there is no body content, just an attached graphic. >Demime removes the HTML content, leaving an empty message (just >assuming here), before your aliases file passes the >converted message to your -outgoing alias where the digest script is >called. You are probably creating your own problem in >this case. > >As for the sequentiality of your pre-digest files, I have seen this >too, in some cases. The solution is another patch... I offer >this piece of an email that I sent in September of 2003. > >>Do the timestamps on the digest.$$ messages coincide with times that >>email was received for your list? Have you looked in the >>$digest_work_dir >>to see what files are queued up in there? Are there any skipped >>numbers in the sequence of files? You might need to modify line >>#176 of the digest script to say >> >> foreach (sort @files) { >> >>to clean things up. You might also consider creating a tmp directory >>in the majordomo $HOME (or work directory if they are different) with >>the proper majordomo ownership and permission, then setting $TMPDIR in >>the majordomo.cf to use that directory. >In fact, I found reference to the same change on line 176 of digest >in a posting from Sept 2000 too. > >Dan Liston > >Tom Patterson wrote: >>Thanks to Joe for help on this problem. The patch immediately cut >>out the messages which were bouncing back to me due to the use of >>invalid e-mail addresses by the spammers. >> >>I am however left with the problem that majordomo is still picking >>up on the spam messages and creating zero content messages in the >>digest folder. When the digest is created, it then shows these >>messages, albeit as blank. >> >>I have a script which deletes all zero content messages in the >>digest folder immediately before the mkdigest command is issued by >>a cron job. The problem then arises that the remaining messages >>are not sequentially numbered in the digest folder, and do not all >>get picked up by the digest. I can get around this problem by >>renumbering the messages, starting from zero. >> >>Also, I have two lists. Only the list starting with the letter "s" >>is picking up the blank messages. The list starting with the >>letter "v" does not pick up blank messages. >> >>As the spam is addressed to majordomo@domainname, I assume that >>majordomo is dumping the blank messages into the first folder he >>comes to. I also assume that if I created a dummy list starting >>with a alpha character prior to "s", the zero messages would end up >>there, leaving my list folders unaffected by the spam. I will try this next. >> >>However, is there some way to prevent majordomo from creating these >>zero content messages? >> >>-Tom >> >>----- Original Message ----- From: "Joe R. Jah" >>To: "Tom Patterson" >>Cc: >>Sent: Wednesday, July 09, 2008 9:51 PM >>Subject: Re: Majordomo and spammers >> >> >>>On Wed, 9 Jul 2008, Tom Patterson wrote: >>> >>>>Date: Wed, 9 Jul 2008 06:04:38 -0500 >>>>From: Tom Patterson >>>>To: majordomo-users@greatcircle.com >>>>Subject: Majordomo and spammers >>>> >>>>I have recently moved my site to a new server using Q Mail, and >>>>reinstalled Majordomo. I am having two problems. >>>> >>>>1. I am getting hit with a great amount of spam addressed to >>>>majordomo, which is generating replies to non-existent addresses, >>>>which in turn bounce back to me. The replies are the standard >>>>reply from majordomo when it does not understand a message. >>>> Is there any way of stopping these replies from Majordomo >>>> or of changing the majordomo's address from majordomo@domain.com? >>>> >>>>2. All of these spam messages to majordomo are generating zero >>>>content messages in the digest folder, which in turn, adds blank >>>>messages to the digest. How can this be fixed? >>>> >>>>-Tom From majordomo-users-owner@greatcircle.com Sat Jul 12 02:50:10 2008 Received: from smtp110.sbc.mail.mud.yahoo.com (smtp110.sbc.mail.mud.yahoo.com [68.142.198.209]) by mycroft.greatcircle.com (Postfix) with SMTP id C8B5C498364 for ; Sat, 12 Jul 2008 02:50:08 -0700 (PDT) Received: (qmail 95508 invoked from network); 12 Jul 2008 09:43:49 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=YYptkXqVOqFMIAaScohUDVvzpJceaNHoVXDzmWC9pGdwPIwU7B7cqPwaaRmea5nK19M9LdgO31MFi8+S1wXu5d1we8EqLYFvheP8/OrPUBTC6Y9uiHwZbmzoy21gBkA7CVbwmOJ/ZbKh5cOaG5J2gkhPrTJfvZIkdhZ4g5ktLog= ; Received: from unknown (HELO DESKTOPPRO) (pattersontj@sbcglobal.net@69.151.213.213 with login) by smtp110.sbc.mail.mud.yahoo.com with SMTP; 12 Jul 2008 09:43:49 -0000 X-YMail-OSG: ky44oA0VM1nJILXaaM98NjCKlK9Yn_ydhalAQDy7_Rsvbpz8hoRa2bCzMwNKv15qouPKA952EcS_KCmoxmDBU2PN1MyvznrMzoibH9VpOw-- X-Yahoo-Newman-Property: ymail-3 Message-ID: <038201c8e403$c9684db0$6400a8c0@DESKTOPPRO> From: "Tom Patterson" To: References: <01bd01c8e35f$53500310$6400a8c0@DESKTOPPRO> <4877E594.3050009@sonny.org> <200807120603.m6C63kXR020479@yoda.wrenkasky.com> Subject: Re: Majordomo and spammers Date: Sat, 12 Jul 2008 04:43:48 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Archive-Number: 200807/13 X-Sequence-Number: 5752 Sorry All, I responded to earlier messages from Daniel Liston, and did so without copying in the list, as I just hit the reply to button. Following is my response to the first message: __________________________ Thanks Dan, Maybe you are correct in the graphical nature of the problem, but I doubt it. I have two lists with about 700-750 mostly long time members. They know that majordomo strips off any image files, and should not be submitting any. If they did, it would only be an occasional image - right now, I am getting a lot of these zero files. Prior to installing Joe's patch, I was able to tie the date and time of these blank files to the time that majordomo was bouncing messages back to the spammers. Also, I did not have this problem on my old server which also used demime. The problem started when I moved to a new server. I have already looked to see what files are queued up for the digests, and there are zero content files sitting there, and arriving regularly. The sequence problem I was running into seems to have ocurred as a result of deleting these zero files. The solution now appears to be in renaming and renumbering these files so that they start with 001. When I did that earlier today, I was able to pick them up in digests. I now have a script which will be tried with the cron job tonight. It will delete all zero content files, and then rename and renumber the remaining files immediately prior to calling the cron job to create the digest. If it works, the problem will be solved. I have no idea what is different now than with the earlier server, except for the mail program. Whatever, I will keep you posted on the outcome. -Tom _________________ ----- Original Message ----- From: "Ed Kasky" To: "Daniel Liston" ; Sent: Saturday, July 12, 2008 1:03 AM Subject: Re: Majordomo and spammers > FYI, demime also strips attachments at the same time that it strips the > mime from a message. I have lots of subscribers scratching their heads on > that one... > > Ed > From majordomo-users-owner@greatcircle.com Sat Jul 12 02:53:12 2008 Received: from smtp105.sbc.mail.mud.yahoo.com (smtp105.sbc.mail.mud.yahoo.com [68.142.198.204]) by mycroft.greatcircle.com (Postfix) with SMTP id 30390498364 for ; Sat, 12 Jul 2008 02:53:11 -0700 (PDT) Received: (qmail 25324 invoked from network); 12 Jul 2008 09:46:52 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=4AgaTFEZQj7+JDeyqfqNG2/XkVYDh4rB0W1O5lxvAWYRm71XOsSL5beCnayb8ixBf1+++NUMkypm3V4RWRL/WGJK+GOI9MYUtFV7KoCmoe9lqRsszhIv7WuWi+kaAwknBN4MLDiAnFyZ+ps8HYS8WkU+Qyb6IIovAnb8iAYgN28= ; Received: from unknown (HELO DESKTOPPRO) (pattersontj@sbcglobal.net@69.151.213.213 with login) by smtp105.sbc.mail.mud.yahoo.com with SMTP; 12 Jul 2008 09:46:52 -0000 X-YMail-OSG: nuwtQoIVM1miQFZZMJaMrM2Vdw6gQV.ve5fQrAH0Jf.ZfPXQEgJn8JaDNeCXmvYaABURSq61vt8AfX7B8DIso9MMcehjv_n_3X7m2A6AwDZ9rZrdu0zkwEs8R9Kcn2o- X-Yahoo-Newman-Property: ymail-3 Message-ID: <039001c8e404$3623b110$6400a8c0@DESKTOPPRO> From: "Tom Patterson" To: References: <01bd01c8e35f$53500310$6400a8c0@DESKTOPPRO> <4877E594.3050009@sonny.org> <200807120603.m6C63kXR020479@yoda.wrenkasky.com> Subject: Re: Majordomo and spammers Date: Sat, 12 Jul 2008 04:46:51 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Archive-Number: 200807/14 X-Sequence-Number: 5753 Still sorry All, Dan replied to my last response, which I also answered. Both are below: ________________ The more important point of my post, was to modify line 176 of the "digest" script so you don't have to run an external script to renumber the files in the $digest_work directory. As for the problem starting after moving to a new server, have you carefully examined all the ownerships and permissions of all the files and directories associated with majordomo AND your MTA? Is selinux involved? What about smrsh if you are running sendmail? Dan Liston Ok, The linux is Fedora 8. Qmail is the mail program. -Tom ____________________ ----- Original Message ----- From: "Ed Kasky" To: "Daniel Liston" ; Sent: Saturday, July 12, 2008 1:03 AM Subject: Re: Majordomo and spammers > FYI, demime also strips attachments at the same time that it strips the > mime from a message. I have lots of subscribers scratching their heads on > that one... > > Ed > > At 03:58 PM Friday, 7/11/2008, Daniel Liston wrote -=> >>I have a sneaky suspicion that your spam may be graphical in nature, where >>there is no body content, just an attached graphic. >>Demime removes the HTML content, leaving an empty message (just assuming >>here), before your aliases file passes the >>converted message to your -outgoing alias where the digest script is >>called. You are probably creating your own problem in >>this case. >> >>As for the sequentiality of your pre-digest files, I have seen this too, >>in some cases. The solution is another patch... I offer >>this piece of an email that I sent in September of 2003. >> >>>Do the timestamps on the digest.$$ messages coincide with times that >>>email was received for your list? Have you looked in the >>>$digest_work_dir >>>to see what files are queued up in there? Are there any skipped >>>numbers in the sequence of files? You might need to modify line >>>#176 of the digest script to say >>> >>> foreach (sort @files) { >>> >>>to clean things up. You might also consider creating a tmp directory >>>in the majordomo $HOME (or work directory if they are different) with >>>the proper majordomo ownership and permission, then setting $TMPDIR in >>>the majordomo.cf to use that directory. >>In fact, I found reference to the same change on line 176 of digest in a >>posting from Sept 2000 too. >> >>Dan Liston >> >>Tom Patterson wrote: >>>Thanks to Joe for help on this problem. The patch immediately cut out >>>the messages which were bouncing back to me due to the use of invalid >>>e-mail addresses by the spammers. >>> >>>I am however left with the problem that majordomo is still picking up on >>>the spam messages and creating zero content messages in the digest >>>folder. When the digest is created, it then shows these messages, albeit >>>as blank. >>> >>>I have a script which deletes all zero content messages in the digest >>>folder immediately before the mkdigest command is issued by a cron job. >>>The problem then arises that the remaining messages are not sequentially >>>numbered in the digest folder, and do not all get picked up by the >>>digest. I can get around this problem by renumbering the messages, >>>starting from zero. >>> >>>Also, I have two lists. Only the list starting with the letter "s" is >>>picking up the blank messages. The list starting with the letter "v" >>>does not pick up blank messages. >>> >>>As the spam is addressed to majordomo@domainname, I assume that majordomo >>>is dumping the blank messages into the first folder he comes to. I also >>>assume that if I created a dummy list starting with a alpha character >>>prior to "s", the zero messages would end up there, leaving my list >>>folders unaffected by the spam. I will try this next. >>> >>>However, is there some way to prevent majordomo from creating these zero >>>content messages? >>> >>>-Tom >>> >>>----- Original Message ----- From: "Joe R. Jah" >>> >>>To: "Tom Patterson" >>>Cc: >>>Sent: Wednesday, July 09, 2008 9:51 PM >>>Subject: Re: Majordomo and spammers >>> >>> >>>>On Wed, 9 Jul 2008, Tom Patterson wrote: >>>> >>>>>Date: Wed, 9 Jul 2008 06:04:38 -0500 >>>>>From: Tom Patterson >>>>>To: majordomo-users@greatcircle.com >>>>>Subject: Majordomo and spammers >>>>> >>>>>I have recently moved my site to a new server using Q Mail, and >>>>>reinstalled Majordomo. I am having two problems. >>>>> >>>>>1. I am getting hit with a great amount of spam addressed to >>>>>majordomo, which is generating replies to non-existent addresses, which >>>>>in turn bounce back to me. The replies are the standard reply from >>>>>majordomo when it does not understand a message. >>>>> Is there any way of stopping these replies from Majordomo or of >>>>> changing the majordomo's address from majordomo@domain.com? >>>>> >>>>>2. All of these spam messages to majordomo are generating zero content >>>>>messages in the digest folder, which in turn, adds blank messages to >>>>>the digest. How can this be fixed? >>>>> >>>>>-Tom > From majordomo-users-owner@greatcircle.com Sat Jul 12 03:01:03 2008 Received: from smtp114.sbc.mail.mud.yahoo.com (smtp114.sbc.mail.mud.yahoo.com [68.142.198.213]) by mycroft.greatcircle.com (Postfix) with SMTP id 35A6A498364 for ; Sat, 12 Jul 2008 03:01:01 -0700 (PDT) Received: (qmail 75217 invoked from network); 12 Jul 2008 09:54:43 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=cUiE9THBgdLn1MtUsd4R3XGfwkYG2KFGs/tyNOVU4RYQRI3KwjP69o4vGEKaraP/hJCyZsHtOMs8ayAnnbSbb8OV9B0SKgjI1Ca67e3dcG1RzElf9kR6wq1q64xFnBTj4DDof2FmOB8yOAJfnDo9GL/ngCJX4BUE3eqqe3PngZ4= ; Received: from unknown (HELO DESKTOPPRO) (pattersontj@sbcglobal.net@69.151.213.213 with login) by smtp114.sbc.mail.mud.yahoo.com with SMTP; 12 Jul 2008 09:54:42 -0000 X-YMail-OSG: HQMHTfkVM1nVkZ0nQVbtz7sUlpMe7BZUjUgqLbR8mf5LlG1H2K5pJu4GFqPQ9NdvblvxHpEeTnSoaPhXcWjeLg4xexBiG.yGeiQyIVOzM3DV7LyFY02dP01eulkfpok- X-Yahoo-Newman-Property: ymail-3 Message-ID: <03a201c8e405$4ecb12c0$6400a8c0@DESKTOPPRO> From: "Tom Patterson" To: Subject: Re: Majordomo and spammers Date: Sat, 12 Jul 2008 04:54:41 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Archive-Number: 200807/15 X-Sequence-Number: 5754 The script to which I referbelow ran overnight, and worked mostly. All blank messages were successfully deleted; the remaining messages were sequentially renumbered; the digests were created and sucessfully mailed out to the subscribers. There was one problem. Two messages in the queue for each list were not picked up and included in the digest for each list. Perhaps it is only co-incidence, but the number of the omitted messages in each case were 004 and 005. Also, probably really a co-incidence, for one list the first message was from Tokyo with a response to that message; in the second list, both omitted messages were in response to a message from Tokyo ??? Looking further into the problem now. -Tom ----- Original Message ----- From: "Tom Patterson" To: "Daniel Liston" Sent: Friday, July 11, 2008 6:19 PM Subject: Re: Majordomo and spammers > Thanks Dan, > > Maybe you are correct in the graphical nature of the problem, but I doubt > it. > > I have two lists with about 700-750 mostly long time members. They know > that majordomo strips off any image files, and should not be submitting > any. If they did, it would only be an occasional image - right now, I am > getting a lot of these zero files. Prior to installing Joe's patch, I was > able to tie the date and time of these blank files to the time that > majordomo was bouncing messages back to the spammers. Also, I did not > have this problem on my old server which also used demime. The problem > started when I moved to a new server. > > I have already looked to see what files are queued up for the digests, and > there are zero content files sitting there, and arriving regularly. The > sequence problem I was running into seems to have ocurred as a result of > deleting these zero files. The solution now appears to be in renaming and > renumbering these files so that they start with 001. When I did that > earlier today, I was able to pick them up in digests. > > I now have a script which will be tried with the cron job tonight. It > will delete all zero content files, and then rename and renumber the > remaining files immediately prior to calling the cron job to create the > digest. If it works, the problem will be solved. > > I have no idea what is different now than with the earlier server, except > for the mail program. Whatever, I will keep you posted on the outcome. > > -Tom > > ----- Original Message ----- > From: "Daniel Liston" > To: > Sent: Friday, July 11, 2008 5:58 PM > Subject: Re: Majordomo and spammers > > >>I have a sneaky suspicion that your spam may be graphical in nature, where >>there is no body content, just an attached graphic. >> Demime removes the HTML content, leaving an empty message (just assuming >> here), before your aliases file passes the >> converted message to your -outgoing alias where the digest script is >> called. You are probably creating your own problem in >> this case. >> >> As for the sequentiality of your pre-digest files, I have seen this too, >> in some cases. The solution is another patch... I offer >> this piece of an email that I sent in September of 2003. >> >>> Do the timestamps on the digest.$$ messages coincide with times that >>> email was received for your list? Have you looked in the >>> $digest_work_dir >>> to see what files are queued up in there? Are there any skipped >>> numbers in the sequence of files? You might need to modify line >>> #176 of the digest script to say >>> >>> foreach (sort @files) { >>> >>> to clean things up. You might also consider creating a tmp directory >>> in the majordomo $HOME (or work directory if they are different) with >>> the proper majordomo ownership and permission, then setting $TMPDIR in >>> the majordomo.cf to use that directory. >> In fact, I found reference to the same change on line 176 of digest in a >> posting from Sept 2000 too. >> >> Dan Liston >> >> Tom Patterson wrote: >>> Thanks to Joe for help on this problem. The patch immediately cut out >>> the messages which were bouncing back to me due to the use of invalid >>> e-mail addresses by the spammers. >>> >>> I am however left with the problem that majordomo is still picking up on >>> the spam messages and creating zero content messages in the digest >>> folder. When the digest is created, it then shows these messages, >>> albeit as blank. >>> >>> I have a script which deletes all zero content messages in the digest >>> folder immediately before the mkdigest command is issued by a cron job. >>> The problem then arises that the remaining messages are not sequentially >>> numbered in the digest folder, and do not all get picked up by the >>> digest. I can get around this problem by renumbering the messages, >>> starting from zero. >>> >>> Also, I have two lists. Only the list starting with the letter "s" is >>> picking up the blank messages. The list starting with the letter "v" >>> does not pick up blank messages. >>> >>> As the spam is addressed to majordomo@domainname, I assume that >>> majordomo is dumping the blank messages into the first folder he comes >>> to. I also assume that if I created a dummy list starting with a alpha >>> character prior to "s", the zero messages would end up there, leaving my >>> list folders unaffected by the spam. I will try this next. >>> >>> However, is there some way to prevent majordomo from creating these zero >>> content messages? >>> >>> -Tom >>> >>> ----- Original Message ----- From: "Joe R. Jah" >>> >>> To: "Tom Patterson" >>> Cc: >>> Sent: Wednesday, July 09, 2008 9:51 PM >>> Subject: Re: Majordomo and spammers >>> >>> >>>> On Wed, 9 Jul 2008, Tom Patterson wrote: >>>> >>>>> Date: Wed, 9 Jul 2008 06:04:38 -0500 >>>>> From: Tom Patterson >>>>> To: majordomo-users@greatcircle.com >>>>> Subject: Majordomo and spammers >>>>> >>>>> I have recently moved my site to a new server using Q Mail, and >>>>> reinstalled Majordomo. I am having two problems. >>>>> >>>>> 1. I am getting hit with a great amount of spam addressed to >>>>> majordomo, which is generating replies to non-existent addresses, >>>>> which in turn bounce back to me. The replies are the standard reply >>>>> from majordomo when it does not understand a message. >>>>> Is there any way of stopping these replies from Majordomo or of >>>>> changing the majordomo's address from majordomo@domain.com? >>>>> >>>>> 2. All of these spam messages to majordomo are generating zero >>>>> content messages in the digest folder, which in turn, adds blank >>>>> messages to the digest. How can this be fixed? >>>>> >>>>> -Tom >>>> >>>> ftp://ftp.ccsf.org/majordomo-patches/1.94.5/noCommand_noBounce.0 >>>> >>>> Regards, >>>> >>>> Joe >>>> -- >>>> _/ _/_/_/ _/ ____________ __o >>>> _/ _/ _/ _/ ______________ _-\<,_ >>>> _/ _/ _/_/_/ _/ _/ ......(_)/ (_) >>>> _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us >>>> >>> >> > From majordomo-users-owner@greatcircle.com Sun Jul 13 05:05:56 2008 X-Greylist: delayed 405 seconds by postgrey-1.24 at mycroft; Sun, 13 Jul 2008 05:05:53 PDT Received: from mail.emacolet.com (mail.emacolet.com [216.228.108.20]) by mycroft.greatcircle.com (Postfix) with ESMTP id 70119498373 for ; Sun, 13 Jul 2008 05:05:53 -0700 (PDT) Received: from akelalt ([192.168.0.10]) (authenticated bits=0) by mail.emacolet.com (8.14.2/8.14.2) with ESMTP id m6DBqb64031829 for ; Sun, 13 Jul 2008 07:52:37 -0400 X-DKIM: Sendmail DKIM Filter v2.5.2 mail.emacolet.com m6DBqb64031829 DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=emacolet.com; s=mail; t=1215949957; bh=qo+P+56bJGKljylZxL6pLtFKcQk=; h=From:To:References: In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding; b=FRpONSCApgdbpQ+YSKSyuUfYuT+23HsokF+ob pma+nBB7GGFFL0Vqc6sVy/2ccKc+C2SQNn1p3DGaO4jP26CRqDLvCk1VNg9gO2YdkOx s7BFIDYLxA0WT701LstWtr70lqN2i3ZgKXVva7o2AdrxssUPgLsJM5O/9isk1yKUpFo = From: "Peter P. Benac" To: References: <01bd01c8e35f$53500310$6400a8c0@DESKTOPPRO> <4877E594.3050009@sonny.org> <200807120603.m6C63kXR020479@yoda.wrenkasky.com> <038201c8e403$c9684db0$6400a8c0@DESKTOPPRO> In-Reply-To: <038201c8e403$c9684db0$6400a8c0@DESKTOPPRO> Subject: Re: Majordomo and spammers Date: Sun, 13 Jul 2008 07:52:29 -0400 Message-ID: <004b01c8e4de$ed8a8510$c89f8f30$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcjkA9bPo8jLR69DS9mE3YgLC5aVNwA2h3rQ Content-Language: en-us X-Scanned-By: MIMEDefang 2.53 on 192.168.0.253 X-Archive-Number: 200807/16 X-Sequence-Number: 5755 Tom, It is not your subscribers that are sending the graphical messages. = It is the spammers. =20 I would be more curious about what type of spam catching software you = are running on the front end of all of this. My mail server is running SpamAssassin, and Mimedefang. Plus I have the list set so only list = members can post. Rejects never end up archived or digested. The mail server = checks for RBDNS, DKIM and SPF records as well. =20 Very little Spam makes it to any list I host and 99% if that is = rejected because it comes from non-members. If that much spam is making to a = backend mail processor you might want to beef up the front end. =20 Regards, Pete ---- Peter P. Benac, CCNA Emacolet Networking Services, Inc Web and Mail Hosting. Phone: 252-657-9591 Web: http://www.emacolet.com To have principles... =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 First have courage.. With = principles comes integrity!!!=20 -----Original Message----- From: majordomo-users-owner@greatcircle.com [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Tom = Patterson Sent: Saturday, July 12, 2008 05:44 To: majordomo-users@greatcircle.com Subject: Re: Majordomo and spammers Sorry All, I responded to earlier messages from Daniel Liston, and did so without=20 copying in the list, as I just hit the reply to button. Following is my = response to the first message: __________________________ Thanks Dan, Maybe you are correct in the graphical nature of the problem, but I = doubt it. I have two lists with about 700-750 mostly long time members. They know that majordomo strips off any image files, and should not be submitting = any. If they did, it would only be an occasional image - right now, I am = getting a lot of these zero files. Prior to installing Joe's patch, I was able = to tie the date and time of these blank files to the time that majordomo = was bouncing messages back to the spammers. Also, I did not have this = problem on my old server which also used demime. The problem started when I = moved to a new server. I have already looked to see what files are queued up for the digests, = and there are zero content files sitting there, and arriving regularly. The sequence problem I was running into seems to have ocurred as a result of deleting these zero files. The solution now appears to be in renaming = and renumbering these files so that they start with 001. When I did that earlier today, I was able to pick them up in digests. I now have a script which will be tried with the cron job tonight. It = will delete all zero content files, and then rename and renumber the = remaining files immediately prior to calling the cron job to create the digest. = If it works, the problem will be solved. I have no idea what is different now than with the earlier server, = except for the mail program. Whatever, I will keep you posted on the outcome. -Tom _________________ ----- Original Message -----=20 From: "Ed Kasky" To: "Daniel Liston" ; = Sent: Saturday, July 12, 2008 1:03 AM Subject: Re: Majordomo and spammers > FYI, demime also strips attachments at the same time that it strips = the=20 > mime from a message. I have lots of subscribers scratching their = heads on > that one... > > Ed > From majordomo-users-owner@greatcircle.com Sun Jul 13 05:38:24 2008 Received: from smtp110.sbc.mail.mud.yahoo.com (smtp110.sbc.mail.mud.yahoo.com [68.142.198.209]) by mycroft.greatcircle.com (Postfix) with SMTP id AEB02498373 for ; Sun, 13 Jul 2008 05:38:23 -0700 (PDT) Received: (qmail 42035 invoked from network); 13 Jul 2008 12:31:53 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=bntSg8KTsi412QwIu8XHP+fxLzKP0ZVkgPL+vOw1M74+cWifJzLv7lwoXK56iIbJf1aubJXsybbjhK+WqEuSwuLY+cfGCD+4PDi9uj1HoqiBaACXbw4XGcPlLOeBkUzbKssdI3lX8NO/H5kQDjJ4mfuuqPuVFp1ZZjqhUYtnL40= ; Received: from unknown (HELO DESKTOPPRO) (pattersontj@sbcglobal.net@69.151.213.213 with login) by smtp110.sbc.mail.mud.yahoo.com with SMTP; 13 Jul 2008 12:31:53 -0000 X-YMail-OSG: JStWZgkVM1m6odIoFR_Wbo0JnCjMA9ZuKU0DPefCmMjCahCLba1Vl3dJ7kVJfcASyW6MIjsTE06sWYHar1fwlyH_q5Dg6u5tgGYS0J9kMq4gRcFJw.X.hknOHgmprhU- X-Yahoo-Newman-Property: ymail-3 Message-ID: <013301c8e4e4$6dd65aa0$6400a8c0@DESKTOPPRO> From: "Tom Patterson" To: References: <01bd01c8e35f$53500310$6400a8c0@DESKTOPPRO> <4877E594.3050009@sonny.org> <200807120603.m6C63kXR020479@yoda.wrenkasky.com> <038201c8e403$c9684db0$6400a8c0@DESKTOPPRO> <004b01c8e4de$ed8a8510$c89f8f30$@com> Subject: Re: Majordomo and spammers Date: Sun, 13 Jul 2008 07:31:51 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Archive-Number: 200807/17 X-Sequence-Number: 5756 I agree that the subscribers are not the ones sending the graphical messages if graphical messages are what is causing the problem. Actually, I think that it may be all messages from spammers, whether graphical or otherwise. I didn't save any of the bounces I was getting back, but I think that the times on at least some of them did correspond to times of some of the blank messages. Those messages were not all graphical, because they did have text that caused majordomo to respond. The thing is messages, apparently from spammers, are coming in, and apparently, are causing majordomo to create blank messages in the digest temporary directory. The messages are NOT going out to the regular list members - they never were. I do have my lists set up so that only list members can post. The blank messages have never gone out through the regular messages. They only show up in the digest temporary directory, and if left alone, appear as blank messages within the digest. I am running demime, and DrWeb to filter messages on the site. The digests last night did run without any problem. We modified line #176 as Daniel Liston suggested, and that, along with removing all zero content messages with a script as part of the cron job to create the digests, resulted in normal digests. I am still left with these blank messages being created in the digest temporary directory, but the problem is now at least manageable. Probably I will now create a new list starting with an alpha character lower than the two active lists, and see if I can dump any blank messages into that new list's directory to further ensure that blank messages don't get out to any digest subscribers. Right now, these blank messages are only going into one of the two active list digests directories, and it is the one with the starting with alpha "s" as opposed to alpha "v". -Tom ----- Original Message ----- From: "Peter P. Benac" To: Sent: Sunday, July 13, 2008 6:52 AM Subject: Re: Majordomo and spammers Tom, It is not your subscribers that are sending the graphical messages. It is the spammers. I would be more curious about what type of spam catching software you are running on the front end of all of this. My mail server is running SpamAssassin, and Mimedefang. Plus I have the list set so only list members can post. Rejects never end up archived or digested. The mail server checks for RBDNS, DKIM and SPF records as well. Very little Spam makes it to any list I host and 99% if that is rejected because it comes from non-members. If that much spam is making to a backend mail processor you might want to beef up the front end. Regards, Pete ---- Peter P. Benac, CCNA Emacolet Networking Services, Inc Web and Mail Hosting. Phone: 252-657-9591 Web: http://www.emacolet.com To have principles... First have courage.. With principles comes integrity!!! -----Original Message----- From: majordomo-users-owner@greatcircle.com [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Tom Patterson Sent: Saturday, July 12, 2008 05:44 To: majordomo-users@greatcircle.com Subject: Re: Majordomo and spammers Sorry All, I responded to earlier messages from Daniel Liston, and did so without copying in the list, as I just hit the reply to button. Following is my response to the first message: __________________________ Thanks Dan, Maybe you are correct in the graphical nature of the problem, but I doubt it. I have two lists with about 700-750 mostly long time members. They know that majordomo strips off any image files, and should not be submitting any. If they did, it would only be an occasional image - right now, I am getting a lot of these zero files. Prior to installing Joe's patch, I was able to tie the date and time of these blank files to the time that majordomo was bouncing messages back to the spammers. Also, I did not have this problem on my old server which also used demime. The problem started when I moved to a new server. I have already looked to see what files are queued up for the digests, and there are zero content files sitting there, and arriving regularly. The sequence problem I was running into seems to have ocurred as a result of deleting these zero files. The solution now appears to be in renaming and renumbering these files so that they start with 001. When I did that earlier today, I was able to pick them up in digests. I now have a script which will be tried with the cron job tonight. It will delete all zero content files, and then rename and renumber the remaining files immediately prior to calling the cron job to create the digest. If it works, the problem will be solved. I have no idea what is different now than with the earlier server, except for the mail program. Whatever, I will keep you posted on the outcome. -Tom _________________ ----- Original Message ----- From: "Ed Kasky" To: "Daniel Liston" ; Sent: Saturday, July 12, 2008 1:03 AM Subject: Re: Majordomo and spammers > FYI, demime also strips attachments at the same time that it strips the > mime from a message. I have lots of subscribers scratching their heads on > that one... > > Ed > From majordomo-users-owner@greatcircle.com Sun Jul 13 06:23:24 2008 Received: from mail.emacolet.com (mail.emacolet.com [216.228.108.20]) by mycroft.greatcircle.com (Postfix) with ESMTP id 3C47C49837F for ; Sun, 13 Jul 2008 06:23:22 -0700 (PDT) Received: from akelalt ([192.168.0.10]) (authenticated bits=0) by mail.emacolet.com (8.14.2/8.14.2) with ESMTP id m6DDGn2F000558 for ; Sun, 13 Jul 2008 09:16:49 -0400 X-DKIM: Sendmail DKIM Filter v2.5.2 mail.emacolet.com m6DDGn2F000558 DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=emacolet.com; s=mail; t=1215955009; bh=ksmjOXScvwynGnRVdYvDgSGpir8=; h=From:To:References: In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding; b=dbWdfinpNvYSDlzOGVk3CMq8z9mSrUd/OVzfb 1o9sEXUtt2V5H+9BoMP8Vd06rJLe8m0NyFZ9EajHEGFwrzB/M4F/+jL2Ri+a5wvyymg 6f8gmNxSCeYqPJcTI4kiuumrgWLy8t09tqsMCH21uZg2iAskv5FBE72LOG9TeTp6t7I = From: "Peter P. Benac" To: References: <01bd01c8e35f$53500310$6400a8c0@DESKTOPPRO> <4877E594.3050009@sonny.org> <200807120603.m6C63kXR020479@yoda.wrenkasky.com> <038201c8e403$c9684db0$6400a8c0@DESKTOPPRO> <004b01c8e4de$ed8a8510$c89f8f30$@com> <013301c8e4e4$6dd65aa0$6400a8c0@DESKTOPPRO> In-Reply-To: <013301c8e4e4$6dd65aa0$6400a8c0@DESKTOPPRO> Subject: Re: Majordomo and spammers Date: Sun, 13 Jul 2008 09:16:41 -0400 Message-ID: <006b01c8e4ea$b08b52a0$11a1f7e0$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acjk5HgtiUmrmsriSY69dys/fjH+2gAAvBig Content-Language: en-us X-Scanned-By: MIMEDefang 2.53 on 192.168.0.253 X-Archive-Number: 200807/18 X-Sequence-Number: 5757 OK I will say this again. If you have that many messages getting = through (blank or not) to a back end process you need to rethink your front in process. =20 If they are showing up in your digest (blank or not) and you have the = list subscription set to CLOSED+CONFIRM or OPEN+CONFIRM and the list is set = for List Members only then the spammer is a member of your list. My Mail Server rejects THOUSANDS of Spam messages a day. Maybe 1 or 2 = will get through any one list and is rejected because they are NOT valid = members of that list. Nothing shows up in the digest that hasn't made it though = the regular list. =20 The following is an example of my alias setup: discuss@discuss.org: "|/etc/mail/majordomo/wrapper resend @/etc/mail/majordomo/discuss.arg" discuss-out@discuss.org: :include:/etc/mail/majordomo/lists/discuss discuss-request@discuss.org: "|/etc/mail/majordomo/wrapper majordomo -l discuss" discuss-archive@discuss.org: "|/etc/mail/majordomo/wrapper archive2.pl = -f /etc/mail/majordomo/lists/archives/discuss -m -a" # # # discuss-digestify@discuss.org: "|/usr/local/bin/demime '|/etc/mail/majordomo/wrapper digest -r -C -l discuss-digest discuss-digest-out@discuss.org,nobody'" discuss-digest-out@discuss.org: :include:/etc/mail/majordomo/lists/discuss-digest discuss-digest-request@discuss.org: "|/usr/local/bin/demime '|/etc/mail/majordomo/wrapper majordomo -l discuss-digest'" Contents of the .arg file -h discuss.org -l discuss discuss-out@discuss.org,nobody Obviously I masked the real list name and domain. Regards, Pete ---- Peter P. Benac, CCNA Emacolet Networking Services, Inc Web and Mail Hosting. Phone: 252-657-9591 Web: http://www.emacolet.com To have principles... =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 First have courage.. With = principles comes integrity!!!=20 -----Original Message----- From: majordomo-users-owner@greatcircle.com [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Tom = Patterson Sent: Sunday, July 13, 2008 08:32 To: majordomo-users@greatcircle.com Subject: Re: Majordomo and spammers I agree that the subscribers are not the ones sending the graphical = messages if graphical messages are what is causing the problem. Actually, I = think=20 that it may be all messages from spammers, whether graphical or = otherwise.=20 I didn't save any of the bounces I was getting back, but I think that = the=20 times on at least some of them did correspond to times of some of the = blank=20 messages. Those messages were not all graphical, because they did have = text that caused majordomo to respond. The thing is messages, apparently from spammers, are coming in, and=20 apparently, are causing majordomo to create blank messages in the digest = temporary directory. The messages are NOT going out to the regular list = members - they never were. I do have my lists set up so that only list members can post. The blank = messages have never gone out through the regular messages. They only = show=20 up in the digest temporary directory, and if left alone, appear as blank = messages within the digest. I am running demime, and DrWeb to filter messages on the site. The digests last night did run without any problem. We modified line = #176=20 as Daniel Liston suggested, and that, along with removing all zero = content=20 messages with a script as part of the cron job to create the digests,=20 resulted in normal digests. I am still left with these blank messages being created in the digest=20 temporary directory, but the problem is now at least manageable. Probably I will now create a new list starting with an alpha character = lower than the two active lists, and see if I can dump any blank messages into = that new list's directory to further ensure that blank messages don't = get=20 out to any digest subscribers. Right now, these blank messages are only = going into one of the two active list digests directories, and it is the = one with the starting with alpha "s" as opposed to alpha "v". -Tom ----- Original Message -----=20 From: "Peter P. Benac" To: Sent: Sunday, July 13, 2008 6:52 AM Subject: Re: Majordomo and spammers Tom, It is not your subscribers that are sending the graphical messages. = It is the spammers. I would be more curious about what type of spam catching software you = are running on the front end of all of this. My mail server is running SpamAssassin, and Mimedefang. Plus I have the list set so only list = members can post. Rejects never end up archived or digested. The mail server = checks for RBDNS, DKIM and SPF records as well. Very little Spam makes it to any list I host and 99% if that is = rejected because it comes from non-members. If that much spam is making to a = backend mail processor you might want to beef up the front end. Regards, Pete ---- Peter P. Benac, CCNA Emacolet Networking Services, Inc Web and Mail Hosting. Phone: 252-657-9591 Web: http://www.emacolet.com To have principles... First have courage.. With principles comes integrity!!! -----Original Message----- From: majordomo-users-owner@greatcircle.com [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Tom = Patterson Sent: Saturday, July 12, 2008 05:44 To: majordomo-users@greatcircle.com Subject: Re: Majordomo and spammers Sorry All, I responded to earlier messages from Daniel Liston, and did so without copying in the list, as I just hit the reply to button. Following is my response to the first message: __________________________ Thanks Dan, Maybe you are correct in the graphical nature of the problem, but I = doubt it. I have two lists with about 700-750 mostly long time members. They know that majordomo strips off any image files, and should not be submitting = any. If they did, it would only be an occasional image - right now, I am = getting a lot of these zero files. Prior to installing Joe's patch, I was able = to tie the date and time of these blank files to the time that majordomo = was bouncing messages back to the spammers. Also, I did not have this = problem on my old server which also used demime. The problem started when I = moved to a new server. I have already looked to see what files are queued up for the digests, = and there are zero content files sitting there, and arriving regularly. The sequence problem I was running into seems to have ocurred as a result of deleting these zero files. The solution now appears to be in renaming = and renumbering these files so that they start with 001. When I did that earlier today, I was able to pick them up in digests. I now have a script which will be tried with the cron job tonight. It = will delete all zero content files, and then rename and renumber the = remaining files immediately prior to calling the cron job to create the digest. = If it works, the problem will be solved. I have no idea what is different now than with the earlier server, = except for the mail program. Whatever, I will keep you posted on the outcome. -Tom _________________ ----- Original Message -----=20 From: "Ed Kasky" To: "Daniel Liston" ; = Sent: Saturday, July 12, 2008 1:03 AM Subject: Re: Majordomo and spammers > FYI, demime also strips attachments at the same time that it strips = the > mime from a message. I have lots of subscribers scratching their = heads on > that one... > > Ed > From majordomo-users-owner@greatcircle.com Sun Jul 13 06:33:15 2008 Received: from smtp102.sbc.mail.mud.yahoo.com (smtp102.sbc.mail.mud.yahoo.com [68.142.198.201]) by mycroft.greatcircle.com (Postfix) with SMTP id 4272419C238 for ; Sun, 13 Jul 2008 06:33:13 -0700 (PDT) Received: (qmail 68284 invoked from network); 13 Jul 2008 13:26:42 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=YgMbDYIJ8u+rPtk6c/nNNUcTR2r9+UwC+ot2ZqRkATS6GjuNMJ/msEwg1lOKwK4u42uaODtg38+Hz29l/1d+cXmyOPVhvuncGmTQGc/JZ8ohCN7u/chlUK0dCMAUj7is2p8FtLFuuJN77wrkZ7o9TBp9gIh7JPXWjOU1RVOaDfw= ; Received: from unknown (HELO DESKTOPPRO) (pattersontj@sbcglobal.net@69.151.213.213 with login) by smtp102.sbc.mail.mud.yahoo.com with SMTP; 13 Jul 2008 13:26:42 -0000 X-YMail-OSG: tgiaxNIVM1l8yCjC3GcZUz.pgJ1wAAadLe4rhF8fZejXDE5NzdqA0HuQ9LI4vgggjP3tJbMIRZdwsNx0dnFz0pT7vTLTysOTJtgSTAzNiBVkqPsO15ZZcfswIMsrfg0- X-Yahoo-Newman-Property: ymail-3 Message-ID: <015901c8e4ec$16300640$6400a8c0@DESKTOPPRO> From: "Tom Patterson" To: References: <01bd01c8e35f$53500310$6400a8c0@DESKTOPPRO> <4877E594.3050009@sonny.org> <200807120603.m6C63kXR020479@yoda.wrenkasky.com> <038201c8e403$c9684db0$6400a8c0@DESKTOPPRO> <004b01c8e4de$ed8a8510$c89f8f30$@com> <013301c8e4e4$6dd65aa0$6400a8c0@DESKTOPPRO> <006b01c8e4ea$b08b52a0$11a1f7e0$@com> Subject: Re: Majordomo and spammers Date: Sun, 13 Jul 2008 08:26:40 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Archive-Number: 200807/19 X-Sequence-Number: 5758 If the spammer is a member of my list, then he/she has the ability to send messages only to the digest, and not to the list itself. That pretty much leaves the list itself as the spammer, because the digest config file has the restrict_post set to the list and the list-digest. -Tom ----- Original Message ----- From: "Peter P. Benac" To: Sent: Sunday, July 13, 2008 8:16 AM Subject: Re: Majordomo and spammers OK I will say this again. If you have that many messages getting through (blank or not) to a back end process you need to rethink your front in process. If they are showing up in your digest (blank or not) and you have the list subscription set to CLOSED+CONFIRM or OPEN+CONFIRM and the list is set for List Members only then the spammer is a member of your list. My Mail Server rejects THOUSANDS of Spam messages a day. Maybe 1 or 2 will get through any one list and is rejected because they are NOT valid members of that list. Nothing shows up in the digest that hasn't made it though the regular list. The following is an example of my alias setup: discuss@discuss.org: "|/etc/mail/majordomo/wrapper resend @/etc/mail/majordomo/discuss.arg" discuss-out@discuss.org: :include:/etc/mail/majordomo/lists/discuss discuss-request@discuss.org: "|/etc/mail/majordomo/wrapper majordomo -l discuss" discuss-archive@discuss.org: "|/etc/mail/majordomo/wrapper archive2.pl -f /etc/mail/majordomo/lists/archives/discuss -m -a" # # # discuss-digestify@discuss.org: "|/usr/local/bin/demime '|/etc/mail/majordomo/wrapper digest -r -C -l discuss-digest discuss-digest-out@discuss.org,nobody'" discuss-digest-out@discuss.org: :include:/etc/mail/majordomo/lists/discuss-digest discuss-digest-request@discuss.org: "|/usr/local/bin/demime '|/etc/mail/majordomo/wrapper majordomo -l discuss-digest'" Contents of the .arg file -h discuss.org -l discuss discuss-out@discuss.org,nobody Obviously I masked the real list name and domain. Regards, Pete ---- Peter P. Benac, CCNA Emacolet Networking Services, Inc Web and Mail Hosting. Phone: 252-657-9591 Web: http://www.emacolet.com To have principles... First have courage.. With principles comes integrity!!! -----Original Message----- From: majordomo-users-owner@greatcircle.com [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Tom Patterson Sent: Sunday, July 13, 2008 08:32 To: majordomo-users@greatcircle.com Subject: Re: Majordomo and spammers I agree that the subscribers are not the ones sending the graphical messages if graphical messages are what is causing the problem. Actually, I think that it may be all messages from spammers, whether graphical or otherwise. I didn't save any of the bounces I was getting back, but I think that the times on at least some of them did correspond to times of some of the blank messages. Those messages were not all graphical, because they did have text that caused majordomo to respond. The thing is messages, apparently from spammers, are coming in, and apparently, are causing majordomo to create blank messages in the digest temporary directory. The messages are NOT going out to the regular list members - they never were. I do have my lists set up so that only list members can post. The blank messages have never gone out through the regular messages. They only show up in the digest temporary directory, and if left alone, appear as blank messages within the digest. I am running demime, and DrWeb to filter messages on the site. The digests last night did run without any problem. We modified line #176 as Daniel Liston suggested, and that, along with removing all zero content messages with a script as part of the cron job to create the digests, resulted in normal digests. I am still left with these blank messages being created in the digest temporary directory, but the problem is now at least manageable. Probably I will now create a new list starting with an alpha character lower than the two active lists, and see if I can dump any blank messages into that new list's directory to further ensure that blank messages don't get out to any digest subscribers. Right now, these blank messages are only going into one of the two active list digests directories, and it is the one with the starting with alpha "s" as opposed to alpha "v". -Tom ----- Original Message ----- From: "Peter P. Benac" To: Sent: Sunday, July 13, 2008 6:52 AM Subject: Re: Majordomo and spammers Tom, It is not your subscribers that are sending the graphical messages. It is the spammers. I would be more curious about what type of spam catching software you are running on the front end of all of this. My mail server is running SpamAssassin, and Mimedefang. Plus I have the list set so only list members can post. Rejects never end up archived or digested. The mail server checks for RBDNS, DKIM and SPF records as well. Very little Spam makes it to any list I host and 99% if that is rejected because it comes from non-members. If that much spam is making to a backend mail processor you might want to beef up the front end. Regards, Pete ---- Peter P. Benac, CCNA Emacolet Networking Services, Inc Web and Mail Hosting. Phone: 252-657-9591 Web: http://www.emacolet.com To have principles... First have courage.. With principles comes integrity!!! -----Original Message----- From: majordomo-users-owner@greatcircle.com [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Tom Patterson Sent: Saturday, July 12, 2008 05:44 To: majordomo-users@greatcircle.com Subject: Re: Majordomo and spammers Sorry All, I responded to earlier messages from Daniel Liston, and did so without copying in the list, as I just hit the reply to button. Following is my response to the first message: __________________________ Thanks Dan, Maybe you are correct in the graphical nature of the problem, but I doubt it. I have two lists with about 700-750 mostly long time members. They know that majordomo strips off any image files, and should not be submitting any. If they did, it would only be an occasional image - right now, I am getting a lot of these zero files. Prior to installing Joe's patch, I was able to tie the date and time of these blank files to the time that majordomo was bouncing messages back to the spammers. Also, I did not have this problem on my old server which also used demime. The problem started when I moved to a new server. I have already looked to see what files are queued up for the digests, and there are zero content files sitting there, and arriving regularly. The sequence problem I was running into seems to have ocurred as a result of deleting these zero files. The solution now appears to be in renaming and renumbering these files so that they start with 001. When I did that earlier today, I was able to pick them up in digests. I now have a script which will be tried with the cron job tonight. It will delete all zero content files, and then rename and renumber the remaining files immediately prior to calling the cron job to create the digest. If it works, the problem will be solved. I have no idea what is different now than with the earlier server, except for the mail program. Whatever, I will keep you posted on the outcome. -Tom _________________ ----- Original Message ----- From: "Ed Kasky" To: "Daniel Liston" ; Sent: Saturday, July 12, 2008 1:03 AM Subject: Re: Majordomo and spammers > FYI, demime also strips attachments at the same time that it strips the > mime from a message. I have lots of subscribers scratching their heads on > that one... > > Ed > From majordomo-users-owner@greatcircle.com Tue Jul 15 08:14:30 2008 Received: from dalexmm01.acs-inc.com (dalexmm01.acs-inc.com [63.101.151.3]) by mycroft.greatcircle.com (Postfix) with ESMTP id 39CBE498359 for ; Tue, 15 Jul 2008 08:14:28 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AngBAPRZfEg/V6pIiGdsb2JhbACCco9GAQEBDyCcDg Received: from unknown (HELO ATLEXBR01.CORPATL.COM) ([63.87.170.72]) by dalexmm01.acs-inc.com with ESMTP; 15 Jul 2008 10:01:33 -0500 Received: by atlexbr01.acs-shc.com with Internet Mail Service (5.5.2657.72) id <39DD0N1S>; Tue, 15 Jul 2008 11:07:01 -0400 Message-ID: From: "Caldwell, Cedric" To: "'majordomo-users@greatcircle.com'" Subject: Majordomo ABORT Errors Date: Tue, 15 Jul 2008 11:07:25 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8E68C.7DA3CE5A" X-Archive-Number: 200807/20 X-Sequence-Number: 5759 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C8E68C.7DA3CE5A Content-Type: text/plain Got the majordomo tool working.. that's all that responded. Now, I have an issue with the nasty messages filling up disk space: MAJORDOMO ABORT (mj_majordomo)!! Majordomo@hoppipolla.net punting to avoid mail loop. I only seem to get these messages after I restart sendmail and then send a message to one of the lists. Any resolution have a resolution to this? ------_=_NextPart_001_01C8E68C.7DA3CE5A Content-Type: text/html Content-Transfer-Encoding: quoted-printable

 

 

Got the majordomo tool working.. that's all that = responded.

 

Now, I have an issue with the nasty messages filling up disk = space:

 

MAJORDOMO = ABORT (mj_majordomo)!!

Majordomo@hoppipolla.net = punting to avoid mail loop. 

 

 

I only seem to get these messages after I restart sendmail and = then send a message to one of the lists.

 

 

Any resolution have a resolution to = this?

 

 

 

------_=_NextPart_001_01C8E68C.7DA3CE5A-- From majordomo-users-owner@greatcircle.com Tue Jul 15 08:21:48 2008 Received: from smtp113.sbc.mail.mud.yahoo.com (smtp113.sbc.mail.mud.yahoo.com [68.142.198.212]) by mycroft.greatcircle.com (Postfix) with SMTP id 1C4A3498359 for ; Tue, 15 Jul 2008 08:21:46 -0700 (PDT) Received: (qmail 46730 invoked from network); 15 Jul 2008 15:14:55 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=mqg9o7Isczj8wI6teWlGBgj0FRZAhHJlrKSGp4T5dkQGohxXaNbO+CjDGUJzZBUNWWceJaZi6OuDZ7wtvk5L0IFCyJlWBPHPNRZEdVqZkp5Zaidv/2nG28bRppf6vzch64BywrhQZOLqmOgTlgfl/aw19vglRY8vLlR8AzmH238= ; Received: from unknown (HELO DESKTOPPRO) (pattersontj@sbcglobal.net@69.151.213.213 with login) by smtp113.sbc.mail.mud.yahoo.com with SMTP; 15 Jul 2008 15:14:54 -0000 X-YMail-OSG: _z4iv7UVM1kxKvptyh41MZg49y2k8FSjx1EEZ2bfLp4W9Jrd_UD6Wgar8_2SkUXQ5FdkL.zncmZ72EU.5YU0bKDYGC8NfKhM9e1WoYqXPHX_1mI_WwPxfMED6uIRFuA- X-Yahoo-Newman-Property: ymail-3 Message-ID: <042501c8e68d$87acdfd0$6400a8c0@DESKTOPPRO> From: "Tom Patterson" To: Subject: Fw: Majordomo ABORT Errors Date: Tue, 15 Jul 2008 10:14:51 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0422_01C8E663.9E4C9930" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Archive-Number: 200807/21 X-Sequence-Number: 5760 This is a multi-part message in MIME format. ------=_NextPart_000_0422_01C8E663.9E4C9930 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am getting these too, since I moved to a new server. I believe that = it is spammers sending e-mails to majordomo@mydomain.com and addressed = as coming from majordomo.com.=20 The abort is, as it says, to avoid getting into a mail look. I have directed all of these into my spam folder. -Tom ----- Original Message -----=20 From: Caldwell, Cedric=20 To: 'majordomo-users@greatcircle.com'=20 Sent: Tuesday, July 15, 2008 10:07 AM Subject: Majordomo ABORT Errors =20 =20 Got the majordomo tool working.. that's all that responded. =20 Now, I have an issue with the nasty messages filling up disk space: =20 MAJORDOMO ABORT (mj_majordomo)!! Majordomo@hoppipolla.net punting to avoid mail loop.=20 =20 =20 I only seem to get these messages after I restart sendmail and then = send a message to one of the lists. =20 =20 Any resolution have a resolution to this? =20 =20 =20 ------=_NextPart_000_0422_01C8E663.9E4C9930 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I am getting these too, since I moved to a new=20 server.  I believe that it is spammers sending e-mails to majordomo@mydomain.com and = addressed as=20 coming from majordomo.com.
 
The abort is, as it says, to avoid getting into = a mail=20 look.
 
I have directed all of these into my spam=20 folder.
 
-Tom
----- Original Message -----
From:=20 Caldwell, Cedric =
To: 'majordomo-users@greatc= ircle.com'=20
Sent: Tuesday, July 15, 2008 = 10:07=20 AM
Subject: Majordomo ABORT = Errors

 

 

Got the majordomo tool working.. that's all = that=20 responded.

 

Now, I have an issue with the nasty messages = filling=20 up disk space:

 

MAJORDOMO = ABORT=20 (mj_majordomo)!!

Majordomo@hoppipolla.net = punting to=20 avoid mail loop. 

 

 

I only seem to get these messages after I = restart=20 sendmail and then send a message to one of the=20 lists.

 

 

Any resolution have a resolution to=20 this?

 

 

 

------=_NextPart_000_0422_01C8E663.9E4C9930-- From majordomo-users-owner@greatcircle.com Tue Jul 15 08:34:06 2008 X-Greylist: delayed 301 seconds by postgrey-1.24 at mycroft; Tue, 15 Jul 2008 08:34:06 PDT Received: from fmailhost03.isp.att.net (fmailhost03.isp.att.net [207.115.11.53]) by mycroft.greatcircle.com (Postfix) with ESMTP id 4DA0F4983F0 for ; Tue, 15 Jul 2008 08:34:06 -0700 (PDT) Received: from fwebmail16.isp.att.net ([204.127.221.116]) by isp.att.net (frfwmhc03) with SMTP id <20080715152215H0300prlhne>; Tue, 15 Jul 2008 15:22:15 +0000 X-Originating-IP: [204.127.221.116] Received: from [68.152.95.130] by fwebmail16.isp.att.net; Tue, 15 Jul 2008 15:22:13 +0000 From: cald7786@bellsouth.net To: majordomo-users@greatcircle.com Subject: Majorcool - How To Date: Tue, 15 Jul 2008 15:22:13 +0000 Message-Id: <071520081522.6822.487CC0A5000CF87100001AA622218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> X-Mailer: AT&T Message Center Version 1 (Jun 10 2008) X-Authenticated-Sender: Y2FsZDc3ODZAYmVsbHNvdXRoLm5ldA== MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_6822_1216135333_0" X-Archive-Number: 200807/22 X-Sequence-Number: 5761 --NextPart_Webmail_9m3u9jl4l_6822_1216135333_0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Apologizes for what maybe a dump question.. Maybe I'm missing something here.. but does the majorcool interface not come with a way to post a message to a list of subscribers? It was installed with the admin rights for testing. Is this possible from the command line as well? If so, what command is used? New to using listservs. Thanks. --NextPart_Webmail_9m3u9jl4l_6822_1216135333_0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
Apologizes for what maybe a dump question..
 
Maybe I'm missing something here.. but does the majorcool in= terface not come with a way to post a message to a list of subscribers?&nbs= p;It was installed with the admin rights for testing. 
 
Is this possible from the command line as well? If so, what command is= used? 
 
New to using listservs.
 
Thanks.
--NextPart_Webmail_9m3u9jl4l_6822_1216135333_0-- From majordomo-users-owner@greatcircle.com Tue Jul 15 09:11:11 2008 Received: from zappa.brainiac.com (ZAPPA.BRAINIAC.com [68.15.48.189]) by mycroft.greatcircle.com (Postfix) with ESMTP id 9567751002C for ; Tue, 15 Jul 2008 09:11:07 -0700 (PDT) Received: from brainiac.com (eno [68.0.195.117]) (authenticated bits=0) by zappa.brainiac.com (8.13.1/8.13.1) with ESMTP id m6FG4EoP016642 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 15 Jul 2008 12:04:15 -0400 Date: Tue, 15 Jul 2008 12:04:14 -0400 From: Joe Hartley To: majordomo-users@greatcircle.com Subject: Re: Majorcool - How To Message-Id: <20080715120414.020b0850.jh@brainiac.com> In-Reply-To: <071520081522.6822.487CC0A5000CF87100001AA622218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> References: <071520081522.6822.487CC0A5000CF87100001AA622218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> X-Mailer: Sylpheed 2.5.0 (GTK+ 2.10.14; i686-pc-linux-gnu) X-Face: e<}kWVz7AOU%7Y[y%"Y%)jByI[9dsnKP{\??7E"4vTGx4){g\C&LaBmH1{dDNf0U_mPBv#c qp\nRqr]T^L:p_H=Tel/;Z$7-C/klmyQ*kB\{},N]n-7*sJ(dYlf(,?f2hekl"0$nD+~T-ZwNK~`oa n"I7[)O/_NOgn@]?b%=6SRU!]O5k9|OA]PF!qIvs>7sE3}Vr*eC|r""6/**uf3ak}Hm.HK$Cri^yyT BzeM Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200807/23 X-Sequence-Number: 5762 On Tue, 15 Jul 2008 15:22:13 +0000 cald7786@bellsouth.net wrote: > Maybe I'm missing something here.. but does the majorcool interface not come with a way to post a message to a list of subscribers? It was installed with the admin rights for testing. > > Is this possible from the command line as well? If so, what command is used? Majorcool does not have a way of posting any messages. It's simply for maintaining the list of subscribers and the configuration files. If you want to send a message to the list, you need to use email. That can be done from the command line with the "mail" command, but make sure the user you're logged in as is a valid subscriber to the list (if the list is set up to only allow subscribers to post). -- ====================================================================== Joe Hartley - UNIX/network Consultant - jh@brainiac.com Without deviation from the norm, "progress" is not possible. - FZappa From majordomo-users-owner@greatcircle.com Tue Jul 15 09:19:08 2008 Received: from fmailhost05.isp.att.net (fmailhost05.isp.att.net [207.115.11.55]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1F438510007 for ; Tue, 15 Jul 2008 09:19:08 -0700 (PDT) Received: from fwebmail16.isp.att.net ([207.115.9.156]) by isp.att.net (frfwmhc05) with SMTP id <20080715161217H0500e9sm1e>; Tue, 15 Jul 2008 16:12:17 +0000 X-Originating-IP: [207.115.9.156] Received: from [68.152.95.130] by fwebmail16.isp.att.net; Tue, 15 Jul 2008 16:12:16 +0000 From: cald7786@bellsouth.net To: Joe Hartley , majordomo-users@greatcircle.com Subject: Re: Majorcool - How To Date: Tue, 15 Jul 2008 16:12:16 +0000 Message-Id: <071520081612.2571.487CCC60000B12FC00000A0B22218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> In-Reply-To: <20080715120414.020b0850.jh@brainiac.com> References: <071520081522.6822.487CC0A5000CF87100001AA622218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> <20080715120414.020b0850.jh@brainiac.com> X-Mailer: AT&T Message Center Version 1 (Jun 10 2008) X-Authenticated-Sender: Y2FsZDc3ODZAYmVsbHNvdXRoLm5ldA== MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_2571_1216138336_0" X-Archive-Number: 200807/24 X-Sequence-Number: 5763 --NextPart_Webmail_9m3u9jl4l_2571_1216138336_0 Content-Type: text/plain Content-Transfer-Encoding: 8bit That makes me feel better.. any one have a recommended suggestion on another gui interface that will allow the functionality of send messages to subscribers. I'm all ears.. -------------- Original message from Joe Hartley : -------------- > On Tue, 15 Jul 2008 15:22:13 +0000 > cald7786@bellsouth.net wrote: > Maybe I'm missing something here.. but does the majorcool interface not come with a way to post a message to a list of subscribers? It was installed with the > admin rights for testing. > > > > Is this possible from the command line as well? If so, what command is used? > > Majorcool does not have a way of posting any messages. It's simply for > maintaining the list of subscribers and the configuration files. > > If you want to send a message to the list, you need to use email. That > can be done from the command line with the "mail" command, but make sure > the user you're logged in as is a valid subscriber to the list (if the list > is set up to only allow subscribers to post). > > -- > ====================================================================== > Joe Hartley - UNIX/network Consultant - jh@brainiac.com > Without deviation from the norm, "progress" is not possible. - FZappa --NextPart_Webmail_9m3u9jl4l_2571_1216138336_0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
That makes me feel better.. any one have a recommended suggestion on a= nother gui interface that will allow the functionality of send messages to = subscribers.
 
I'm all ears..
-------------- Original message from Joe Hartley <jh@brai= niac.com>: --------------


> On Tue, 15 Jul 2008 15:22:13 = +0000
> cald7786@bellsouth.net wrote: > Maybe I'm missing somethi= ng here.. but does the majorcool interface not come with a way to post a me= ssage to a list of subscribers? It was installed with the
> admin ri= ghts for testing.
> >
> > Is this possible from the com= mand line as well? If so, what command is used?
>
> Majorcool= does not have a way of posting any messages. It's simply for
> main= taining the list of subscribers and the configuration files.
>
&= gt; If you want to send a message to the list, you need to use email. That =
> can be done from the command line with the "mail" command, but mak= e sure
> the user you're logged in as is a valid subscriber to the l= ist (if the list
> is set up to only allow subscribers to post). >
> --
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D
> Joe Hartley - UNIX/network Consultant - jh@brainiac.c= om
> Without deviation from the norm, "progress" is not possible. - = FZappa
--NextPart_Webmail_9m3u9jl4l_2571_1216138336_0-- From majordomo-users-owner@greatcircle.com Tue Jul 15 09:22:53 2008 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 5BF2A510007 for ; Tue, 15 Jul 2008 09:22:52 -0700 (PDT) Received: from mail.sonny.com (minute.sonny.com [192.168.1.4]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K420012G2BQ7C@mail.sonny.com> for majordomo-users@greatcircle.com; Tue, 15 Jul 2008 11:11:50 -0500 (CDT) Received: from magnum.sonny.com (magnum.sonny.com [192.168.1.68]) by minute.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K4200P3F2BM6Q@minute.sonny.com> for majordomo-users@greatcircle.com; Tue, 15 Jul 2008 11:11:46 -0500 (CDT) Date: Tue, 15 Jul 2008 11:15:19 -0500 From: Daniel Liston Subject: Re: Majordomo ABORT Errors In-reply-to: To: "'majordomo-users@greatcircle.com'" Message-id: <487CCD17.2050509@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.14 (X11/20080501) References: X-Archive-Number: 200807/25 X-Sequence-Number: 5764 Do you understand what a mail loop is, and how to track one down? Most of us get lazy about this, but it really is required so we can help you with a problem that is not on our own machine. What linux/unix are you running your mail server on? What MTA does your mail server run? Include version numbers. Is your majordomo installed on the same or a separate host? What version of majordomo are you running? Did you install majordomo yourself? Was it from an rpm, pkg, zip, or other archive? What was the output result of executing `./wrapper config-test`? Now that introductions are out of the way, is your mail loop caused by DNS mx records, a misconfiguration of your MTA or aliases, or your majordomo config? What does your majordomo/Log say? What does your mail.log say? Are all of the permissions and ownerships for your majordomo configuration and the mailing lists themselves and the work directories for archives and digests compatible with both majordomo and your MTA? If your MTA is piping to a majordomo tool/utility, but does not have permission to execute it, you might see this kind of error. Also, if the majordomo-owner alias points to or evaluates to anything but a "REAL" user, you could get similar results. The same is true for each list's -owner or -approval address/alias. Dan Liston Caldwell, Cedric wrote: > > > > > Got the majordomo tool working.. that's all that responded. > > > > Now, I have an issue with the nasty messages filling up disk space: > > > > MAJORDOMO ABORT (mj_majordomo)!! > > Majordomo@hoppipolla.net punting to avoid > mail loop. > > > > > > I only seem to get these messages after I restart sendmail and then send a > message to one of the lists. > > > > > > Any resolution have a resolution to this? > > > > > > > > From majordomo-users-owner@greatcircle.com Tue Jul 15 09:31:26 2008 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id A0660510007 for ; Tue, 15 Jul 2008 09:31:25 -0700 (PDT) Received: from mail.sonny.com (minute.sonny.com [192.168.1.4]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K420012T2PZ7P@mail.sonny.com> for majordomo-users@greatcircle.com; Tue, 15 Jul 2008 11:20:23 -0500 (CDT) Received: from magnum.sonny.com (magnum.sonny.com [192.168.1.68]) by minute.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K4200P3N2PW7P@minute.sonny.com> for majordomo-users@greatcircle.com; Tue, 15 Jul 2008 11:20:20 -0500 (CDT) Date: Tue, 15 Jul 2008 11:23:53 -0500 From: Daniel Liston Subject: Re: Fw: Majordomo ABORT Errors In-reply-to: <042501c8e68d$87acdfd0$6400a8c0@DESKTOPPRO> To: majordomo-users@greatcircle.com Message-id: <487CCF19.5060606@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.14 (X11/20080501) References: <042501c8e68d$87acdfd0$6400a8c0@DESKTOPPRO> X-Archive-Number: 200807/26 X-Sequence-Number: 5765 I also should have mentioned to Cedric, that googling on "majordomo abort" comes up with a lot of hits (good suggestions) from this list dating back to 2000. Dan Liston Tom Patterson wrote: > I am getting these too, since I moved to a new server. I believe that it is spammers sending e-mails to majordomo@mydomain.com and addressed as coming from majordomo.com. > > The abort is, as it says, to avoid getting into a mail look. > > I have directed all of these into my spam folder. > > > Got the majordomo tool working.. that's all that responded. > > > > Now, I have an issue with the nasty messages filling up disk space: > > > > MAJORDOMO ABORT (mj_majordomo)!! > > Majordomo@hoppipolla.net punting to avoid mail loop. > From majordomo-users-owner@greatcircle.com Tue Jul 15 09:35:48 2008 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 18EE6498369 for ; Tue, 15 Jul 2008 09:35:48 -0700 (PDT) Received: from mail.sonny.com (minute.sonny.com [192.168.1.4]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K42001392XA8A@mail.sonny.com> for majordomo-users@greatcircle.com; Tue, 15 Jul 2008 11:24:46 -0500 (CDT) Received: from magnum.sonny.com (magnum.sonny.com [192.168.1.68]) by minute.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K4200P3T2X78B@minute.sonny.com> for majordomo-users@greatcircle.com; Tue, 15 Jul 2008 11:24:44 -0500 (CDT) Date: Tue, 15 Jul 2008 11:28:16 -0500 From: Daniel Liston Subject: Re: Majorcool - How To In-reply-to: <071520081612.2571.487CCC60000B12FC00000A0B22218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> To: cald7786@bellsouth.net, majordomo-users@greatcircle.com Message-id: <487CD020.7020504@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.14 (X11/20080501) References: <071520081522.6822.487CC0A5000CF87100001AA622218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> <20080715120414.020b0850.jh@brainiac.com> <071520081612.2571.487CCC60000B12FC00000A0B22218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> X-Archive-Number: 200807/27 X-Sequence-Number: 5766 I recommend and suggest thunderbird as your GUI interface to send mail to your list. Dan Liston cald7786@bellsouth.net wrote: > That makes me feel better.. any one have a recommended suggestion on another gui interface that will allow the functionality of send messages to subscribers. > > I'm all ears.. > -------------- Original message from Joe Hartley : -------------- > > >> On Tue, 15 Jul 2008 15:22:13 +0000 >> cald7786@bellsouth.net wrote: > Maybe I'm missing something here.. but does the majorcool interface not come with a way to post a message to a list of subscribers? It was installed with the >> admin rights for testing. >>> Is this possible from the command line as well? If so, what command is used? >> Majorcool does not have a way of posting any messages. It's simply for >> maintaining the list of subscribers and the configuration files. >> >> If you want to send a message to the list, you need to use email. That >> can be done from the command line with the "mail" command, but make sure >> the user you're logged in as is a valid subscriber to the list (if the list >> is set up to only allow subscribers to post). >> >> -- >> ====================================================================== >> Joe Hartley - UNIX/network Consultant - jh@brainiac.com >> Without deviation from the norm, "progress" is not possible. - FZappa > From majordomo-users-owner@greatcircle.com Tue Jul 15 10:54:51 2008 Received: from fmailhost05.isp.att.net (fmailhost05.isp.att.net [204.127.217.105]) by mycroft.greatcircle.com (Postfix) with ESMTP id 138E7498375 for ; Tue, 15 Jul 2008 10:54:51 -0700 (PDT) Received: from fwebmail16.isp.att.net ([207.115.9.156]) by isp.att.net (frfwmhc05) with SMTP id <20080715174759H0500edpgfe>; Tue, 15 Jul 2008 17:47:59 +0000 X-Originating-IP: [207.115.9.156] Received: from [68.152.95.130] by fwebmail16.isp.att.net; Tue, 15 Jul 2008 17:47:58 +0000 From: cald7786@bellsouth.net To: Joe Hartley , majordomo-users@greatcircle.com Subject: Re: Majorcool - How To Date: Tue, 15 Jul 2008 17:47:58 +0000 Message-Id: <071520081747.18687.487CE2CE0007689B000048FF22218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> In-Reply-To: <20080715120414.020b0850.jh@brainiac.com> References: <071520081522.6822.487CC0A5000CF87100001AA622218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> <20080715120414.020b0850.jh@brainiac.com> X-Mailer: AT&T Message Center Version 1 (Jun 10 2008) X-Authenticated-Sender: Y2FsZDc3ODZAYmVsbHNvdXRoLm5ldA== MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_18687_1216144078_0" X-Archive-Number: 200807/28 X-Sequence-Number: 5767 --NextPart_Webmail_9m3u9jl4l_18687_1216144078_0 Content-Type: text/plain Content-Transfer-Encoding: 8bit gotcha there.. but isn't there a way to send a message to a specific lists? For my test environment, I have to lists, and they are both owned by majordomo. Should they be owned by two seperate accounts in order for them to work or did I misconfigure something ?? -------------- Original message from Joe Hartley : -------------- > On Tue, 15 Jul 2008 15:22:13 +0000 > cald7786@bellsouth.net wrote: > Maybe I'm missing something here.. but does the majorcool interface not come with a way to post a message to a list of subscribers? It was installed with the > admin rights for testing. > > > > Is this possible from the command line as well? If so, what command is used? > > Majorcool does not have a way of posting any messages. It's simply for > maintaining the list of subscribers and the configuration files. > > If you want to send a message to the list, you need to use email. That > can be done from the command line with the "mail" command, but make sure > the user you're logged in as is a valid subscriber to the list (if the list > is set up to only allow subscribers to post). > > -- > ====================================================================== > Joe Hartley - UNIX/network Consultant - jh@brainiac.com > Without deviation from the norm, "progress" is not possible. - FZappa --NextPart_Webmail_9m3u9jl4l_18687_1216144078_0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
gotcha there.. but isn't there a way to send a message to a specific l= ists? For my test environment, I have to lists, and they are both owned by = majordomo.  Should they be owned by two seperate accounts in order for= them to work or did I misconfigure something ??
-------------- Original message from Joe Hartley <jh@brai= niac.com>: --------------


> On Tue, 15 Jul 2008 15:22:13 = +0000
> cald7786@bellsouth.net wrote: > Maybe I'm missing somethi= ng here.. but does the majorcool interface not come with a way to post a me= ssage to a list of subscribers? It was installed with the
> admin ri= ghts for testing.
> >
> > Is this possible from the com= mand line as well? If so, what command is used?
>
> Majorcool= does not have a way of posting any messages. It's simply for
> main= taining the list of subscribers and the configuration files.
>
&= gt; If you want to send a message to the list, you need to use email. That =
> can be done from the command line with the "mail" command, but mak= e sure
> the user you're logged in as is a valid subscriber to the l= ist (if the list
> is set up to only allow subscribers to post). >
> --
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D
> Joe Hartley - UNIX/network Consultant - jh@brainiac.c= om
> Without deviation from the norm, "progress" is not possible. - = FZappa
--NextPart_Webmail_9m3u9jl4l_18687_1216144078_0-- From majordomo-users-owner@greatcircle.com Tue Jul 15 11:01:45 2008 X-Greylist: delayed 62 seconds by postgrey-1.24 at mycroft; Tue, 15 Jul 2008 11:01:45 PDT Received: from abtmx1.abbott.com (abtmx1.abbott.com [130.36.44.91]) by mycroft.greatcircle.com (Postfix) with ESMTP id 579104983F6 for ; Tue, 15 Jul 2008 11:01:45 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.30,367,1212382800"; d="scan'208";a="15439144" Received: from abtapn551.northamerica.intra.abbott.com ([10.236.188.102]) by abtmx1.abbott.com with ESMTP; 15 Jul 2008 12:53:50 -0500 To: Majordomo-Users@GreatCircle.COM Subject: Removal from all mailing lists MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.4 HF972 April 26, 2006 Message-ID: From: Dennis T Fink Date: Tue, 15 Jul 2008 12:53:44 -0500 X-MIMETrack: Serialize by Router on ABTAPN551/ESVR/ABBOTT(Release 6.5.6FP2|October 17, 2007) at 07/15/2008 12:52:48, Serialize complete at 07/15/2008 12:52:48 Content-Type: multipart/alternative; boundary="=_alternative 00624D9A86257487_=" X-Archive-Number: 200807/29 X-Sequence-Number: 5768 This is a multipart message in MIME format. --=_alternative 00624D9A86257487_= Content-Type: text/plain; charset="US-ASCII" I wish to be removed from the Majordomo-Users list. How do I accomplish this? Dennis --=_alternative 00624D9A86257487_= Content-Type: text/html; charset="US-ASCII"
I wish to be removed from the Majordomo-Users list.  How do I accomplish this?

Dennis --=_alternative 00624D9A86257487_=-- From majordomo-users-owner@greatcircle.com Tue Jul 15 11:14:48 2008 Received: from zappa.brainiac.com (ZAPPA.BRAINIAC.com [68.15.48.189]) by mycroft.greatcircle.com (Postfix) with ESMTP id EBC9A4983FE for ; Tue, 15 Jul 2008 11:14:47 -0700 (PDT) Received: from brainiac.com (eno [68.0.195.117]) (authenticated bits=0) by zappa.brainiac.com (8.13.1/8.13.1) with ESMTP id m6FI7sdN009000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 15 Jul 2008 14:07:55 -0400 Date: Tue, 15 Jul 2008 14:07:53 -0400 From: Joe Hartley To: majordomo-users@greatcircle.com Subject: Re: Majorcool - How To Message-Id: <20080715140753.57b36552.jh@brainiac.com> In-Reply-To: <071520081747.18687.487CE2CE0007689B000048FF22218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> References: <071520081522.6822.487CC0A5000CF87100001AA622218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> <20080715120414.020b0850.jh@brainiac.com> <071520081747.18687.487CE2CE0007689B000048FF22218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> X-Mailer: Sylpheed 2.5.0 (GTK+ 2.10.14; i686-pc-linux-gnu) X-Face: e<}kWVz7AOU%7Y[y%"Y%)jByI[9dsnKP{\??7E"4vTGx4){g\C&LaBmH1{dDNf0U_mPBv#c qp\nRqr]T^L:p_H=Tel/;Z$7-C/klmyQ*kB\{},N]n-7*sJ(dYlf(,?f2hekl"0$nD+~T-ZwNK~`oa n"I7[)O/_NOgn@]?b%=6SRU!]O5k9|OA]PF!qIvs>7sE3}Vr*eC|r""6/**uf3ak}Hm.HK$Cri^yyT BzeM Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200807/30 X-Sequence-Number: 5769 On Tue, 15 Jul 2008 17:47:58 +0000 cald7786@bellsouth.net wrote: > gotcha there.. but isn't there a way to send a message to a specific lists? For my test environment, I have to lists, and they are both owned by majordomo. Should they be owned by two seperate accounts in order for them to work or did I misconfigure something ?? There is a way to send a message to specific lists, and it's email. Your lists are defined by addresses in your /etc/aliases (or /etc/mail/aliases) file. A list with the name of foo, for example, will have an alias that pipes the email to the wrapper program: foo: "|/usr/local/majordomo/wrapper resend -l foo foo,nobody" (This is just an example, and may not work - my configuration uses a set of aliases for security.) You'd then send a message to the list by emailing foo@example.com. It's worth taking the time to work through the FAQs on configuring aliases at http://greatcircle.com/majordomo/majordomo-faq.html#lists -- ====================================================================== Joe Hartley - UNIX/network Consultant - jh@brainiac.com Without deviation from the norm, "progress" is not possible. - FZappa From majordomo-users-owner@greatcircle.com Tue Jul 15 12:56:15 2008 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 7A7F9498401 for ; Tue, 15 Jul 2008 12:56:14 -0700 (PDT) Received: from mail.sonny.com (minute.sonny.com [192.168.1.4]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K420014KCE7BI@mail.sonny.com> for majordomo-users@greatcircle.com; Tue, 15 Jul 2008 14:49:19 -0500 (CDT) Received: from magnum.sonny.com (magnum.sonny.com [192.168.1.68]) by minute.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K420000DCE6MI@minute.sonny.com> for majordomo-users@greatcircle.com; Tue, 15 Jul 2008 14:49:19 -0500 (CDT) Date: Tue, 15 Jul 2008 14:49:20 -0500 From: Daniel Liston Subject: How to remove yourself from a majordomo mailing list In-reply-to: <200105160923430480.000A2D6D@gateway.imrg.org> To: Majordomo Users Message-id: <487CFF40.60909@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.14 (X11/20080501) References: <200105160923430480.000A2D6D@gateway.imrg.org> X-Archive-Number: 200807/31 X-Sequence-Number: 5770 I see the question asked fairly frequently, as to how to get off of the majordomo-users mailing list. Most recently, today. Ultimately, nobody put you on this list except yourself, unless you ended up at an ISP that allows the re-use of login/email IDs. In this case, the person that had the mailbox before you may have signed up and never removed themself from the list before leaving your ISP, leaving your account with a stale subscription to majordomo-users. If your mail client is web savy, clicking the link below should be enough to do what you want. If not, please resort to "the old fashioned way" which is described right after the link/URL. You can substitute greatcircle.com with any domain that runs majordomo mailing list software. You can substitute majordomo-users with the name of any majordomo list you are subscribed to. Make sure your "return address" or "From address" is the same as the one receiving messages from the majordomo mailing list. mailto:majordomo@greatcircle.com?body=unsubscribe%20majordomo-users or send a message the old fashioned way... To: majordomo@greatcircle.com From: address_to_be_unsubscribed Subject: (none) unsubscribe majordomo-users address_to_be_unsubscribed . End of message Dan Liston From majordomo-users-owner@greatcircle.com Tue Jul 15 14:08:27 2008 Received: from flat.berklix.org (flat.berklix.org [83.236.223.115]) by mycroft.greatcircle.com (Postfix) with ESMTP id E8A47498368 for ; Tue, 15 Jul 2008 14:08:25 -0700 (PDT) Received: from js.berklix.net (p549A57BC.dip.t-dialin.net [84.154.87.188]) (authenticated bits=0) by flat.berklix.org (8.13.8/8.13.8) with ESMTP id m6FL1RdE002256; Tue, 15 Jul 2008 23:01:27 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id m6FL1HmN075645; Tue, 15 Jul 2008 23:01:17 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id m6FL17He094211; Tue, 15 Jul 2008 23:01:12 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200807152101.m6FL17He094211@fire.js.berklix.net> To: Dennis T Fink cc: Majordomo-Users@greatcircle.com Subject: Re: Removal from all mailing lists From: "Julian Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://berklix.com In-reply-to: Your message "Tue, 15 Jul 2008 12:53:44 CDT." Date: Tue, 15 Jul 2008 23:01:07 +0200 X-Archive-Number: 200807/32 X-Sequence-Number: 5771 > I wish to be removed from the Majordomo-Users list. How do I accomplish > this? > > Dennis Chuckle, Dennis has a point, There's no hints in header or footer on this list. Maybe majordomo-users-owner@greatcircle.com could add some to the config file ? eg on 'domo lists I run I have eg Header: List-archive: List-help: List-id: gea List-post: List-robot: List-subscribe: List-unsubscribe: Footer: GEA - http://berklix.org/gea/ & http://berklix.org/gea/beergardens/ Join list: Mail "subscribe your@address" To gea-request@berklix.org Leave list: Mail "unsubscribe your@address" To gea-request@berklix.org Help: Mail "help" To majordomo@berklix.org in body, not Subject: line, Mail in ASCII plain text, not HTML. http://berklix.org/robot/ Lists for skiers & walkers: gea-ski@berklix.org & gea-walk@berklix.org Denis, try one of send unsubscribe to majordomo-users-request@greatcircle.com or send in body of mail eg unsubscribe Majordomo-Users Dennis.Fink@abbott.com to majordomo@greatcircle.com then return the confirmation password it will send you. or also send help to majordomo@greatcircle.com I'm not owner of this list & cant help further, except there's lot of info on how to use a majordomo on my server at http://www.berklix.org/robot/majordomo/ & some will be similar on any other. & heres a generic majordomo manual http://www.berklix.org/robot/majordomo/majordomo.asc Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org From majordomo-users-owner@greatcircle.com Wed Jul 16 07:26:35 2008 Received: from fmailhost01.isp.att.net (fmailhost01.isp.att.net [207.115.11.51]) by mycroft.greatcircle.com (Postfix) with ESMTP id C643D4983CA for ; Wed, 16 Jul 2008 07:26:34 -0700 (PDT) Received: from fwebmail34.isp.att.net ([207.115.9.164]) by isp.att.net (frfwmhc01) with SMTP id <20080716141434H0100mghgpe>; Wed, 16 Jul 2008 14:14:34 +0000 X-Originating-IP: [207.115.9.164] Received: from [68.152.95.130] by fwebmail34.isp.att.net; Wed, 16 Jul 2008 14:14:33 +0000 From: cald7786@bellsouth.net To: majordomo-users@greatcircle.com Subject: Subscribers not receiving emails - new setup Date: Wed, 16 Jul 2008 14:14:33 +0000 Message-Id: <071620081414.10225.487E024900073E62000027F122243429029B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> X-Mailer: AT&T Message Center Version 1 (Jun 10 2008) X-Authenticated-Sender: Y2FsZDc3ODZAYmVsbHNvdXRoLm5ldA== MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_10225_1216217673_0" X-Archive-Number: 200807/33 X-Sequence-Number: 5772 --NextPart_Webmail_9m3u9jl4l_10225_1216217673_0 Content-Type: text/plain Content-Transfer-Encoding: 8bit I'm doing so testing of my configuration, and the message is returned, but it only comes back to me and not the remainder of the subscribers on the list. Is there something misconfigured in the config file? majordomo: "|/usr/lib/majordomo/wrapper majordomo -C /etc/majordomo.cf" majordomo-owner: majordomo test: "|/usr/lib/majordomo/wrapper resend -l test -C test-list" test-list: :include:/var/lib/majordomo/lists/test owner-test: majordomo test-owner: majordomo test-outgoing: :include:/var/lib/majordomo/lists/test test-request: "|/usr/lib/majordomo/wrapper majordomo -l test -C /etc/majordomo.cf" --NextPart_Webmail_9m3u9jl4l_10225_1216217673_0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
I'm doing so testing of my configuration, and the message is returned,= but it only comes back to me and not the remainder of the subscribers on t= he list.  Is there something misconfigured in the config file?
 
 
majordomo: "|/usr/lib/majordomo/wrapper majordomo -C /etc/majordomo.cf= "
majordomo-owner: majordomo
test:           = ;       "|/usr/lib/majordomo/wrapper resend -= l test -C test-list"
test-list:       = ;       :include:/var/lib/majordomo/lists/tes= t
owner-test:          = ;   majordomo
test-owner:      &= nbsp;      majordomo
test-outgoing:  =         :include:/var/lib/majordomo/list= s/test
test-request:        &nbs= p;  "|/usr/lib/majordomo/wrapper majordomo -l test -C /etc/majordomo.c= f"
 
 

 
--NextPart_Webmail_9m3u9jl4l_10225_1216217673_0-- From majordomo-users-owner@greatcircle.com Wed Jul 16 09:51:31 2008 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 9F1234983DD for ; Wed, 16 Jul 2008 09:51:30 -0700 (PDT) Received: from mail.sonny.com (minute.sonny.com [192.168.1.4]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K4300133YHMS2@mail.sonny.com> for majordomo-users@greatcircle.com; Wed, 16 Jul 2008 11:44:10 -0500 (CDT) Received: from [127.0.0.1] (sedona.sonny.com [192.168.1.14]) by minute.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K4300325YHN7A@minute.sonny.com> for majordomo-users@greatcircle.com; Wed, 16 Jul 2008 11:44:12 -0500 (CDT) Date: Wed, 16 Jul 2008 11:44:21 -0500 From: Daniel Liston Subject: Re: Subscribers not receiving emails - new setup In-reply-to: <071620081414.10225.487E024900073E62000027F122243429029B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> To: cald7786@bellsouth.net, majordomo-users@greatcircle.com Message-id: <487E2565.5050509@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) References: <071620081414.10225.487E024900073E62000027F122243429029B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> X-Archive-Number: 200807/34 X-Sequence-Number: 5773 The majordomo-owner:majordomo owner-test and test-owner aliases are potential mail loops. In other words, why are you redirecting address that should reach a human, to a program? And unless you are on a hosted domain, why are you using -C name-of-config-file? Why do you have a test-list and a test-outgoing? Use one or the other, but use one. The final argument of your pipe to wrapper is missing the recipient address. This is how/where you make a call to test-list or test-outgoing. See my aliases below; In your case, you should probably remove aliases and recipients containing archive or digest. If you use these exactly as posted, you will need to solve dependencies in your majordomo.cf and file system directory structure. majordomo: "|/usr/lib/majordomo/wrapper majordomo" majordomo-owner: owner-majordomo owner-majordomo: real-person (at) anydomain (dot) com, # The above address is obfuscated, please use a real address. test: "|/usr/lib/majordomo/wrapper resend -l test test-outgoing,nobody" test-outgoing: :include:/var/lib/majordomo/lists/test,test-digestify,test-archiver test-archiver: "|/usr/lib/majordomo/wrapper archive2.pl -f /var/lib/majordomo/archive/test/test -a -M" test-digestify: "|/usr/lib/majordomo/wrapper digest -r -C -l test-digest test-digest-outgoing,nobody" owner-test: some-person (at) anydomain (dot) net, # The above address is obfuscated, please use a real address. test-owner: owner-test test-digest: test test-digest-outgoing: :include:/var/lib/majordomo/lists/test-digest,nobody test-digest-owner: owner-test test-request: "|/usr/lib/majordomo/wrapper majordomo -l test" test-digest-request: "|/usr/lib/majordomo/wrapper majordomo -l test-digest" test-approval: owner-test test-digest-approval: owner-test Dan Liston The aliases presented are for a sendmail MTA. If you are using qmail, postfix, exim, or some other MTA, please adjust accordingly. Never make untested changes to a production server. Do all testing in a dedicated test environment. cald7786@bellsouth.net wrote: > I'm doing so testing of my configuration, and the message is returned, but it only comes back to me and not the remainder of the subscribers on the list. Is there something misconfigured in the config file? > > > majordomo: "|/usr/lib/majordomo/wrapper majordomo -C /etc/majordomo.cf" > majordomo-owner: majordomo > > test: "|/usr/lib/majordomo/wrapper resend -l test -C test-list" > test-list: :include:/var/lib/majordomo/lists/test > owner-test: majordomo > test-owner: majordomo > test-outgoing: :include:/var/lib/majordomo/lists/test > test-request: "|/usr/lib/majordomo/wrapper majordomo -l test -C /etc/majordomo.cf" > From majordomo-users-owner@greatcircle.com Wed Jul 16 13:34:52 2008 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id C00BD4982FA for ; Wed, 16 Jul 2008 13:34:51 -0700 (PDT) Received: from mail.sonny.com (minute.sonny.com [192.168.1.4]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K440014P8TQUZ@mail.sonny.com> for majordomo-users@greatcircle.com; Wed, 16 Jul 2008 15:27:26 -0500 (CDT) Received: from magnum.sonny.com (magnum.sonny.com [192.168.1.68]) by minute.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K440030E8TRNQ@minute.sonny.com> for majordomo-users@greatcircle.com; Wed, 16 Jul 2008 15:27:28 -0500 (CDT) Date: Wed, 16 Jul 2008 15:27:45 -0500 From: Daniel Liston Subject: Re: Subscribers not receiving emails - new setup In-reply-to: <071620081927.1704.487E4B8A000B5A64000006A822218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> To: Majordomo Users Message-id: <487E59C1.9020208@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.14 (X11/20080501) References: <071620081927.1704.487E4B8A000B5A64000006A822218801869B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> X-Archive-Number: 200807/35 X-Sequence-Number: 5774 I hate to sound like a broken record, but the owner-anything and anything-owner aliases are still a potential mail loop. Unless you have a real human user named majordomo at the address in the alias, when majordomo has a problem and must contact a human to maintain or correct a configuration, the message is going to be sent to another automated majordomo address. THIS IS BAD! These aliases MUST point to a human address or group of human addresses, not an automated program. I hope you noticed the warning in my previous message that there are some pre-requisite settings in your majordomo.cf and on the file system in order to support the digest and archive aliases which you did not remove. Please walk before you try to run. Get one thing working, then add another. Keep configs simple until you are comfortable adding complexity. Let me back up a step in regards to testing your list. If you send a message to test (at) your (dot) domain, are you still the only one that receives the message? What if you send that message to test-outgoing (at) your (dot) domain? Does anyone else receive the message? I hate to ask the obvious, but how many email addresses are listed in the file /var/lib/majordomo/lists/test? If they are all local users, and all aliases to the same mailbox, your MTA may be the one condensing the distribution down to one user. Is this file owned by the majordomo account? The sendmail user? Root? I never did see your original post containing what version of OS, MTA, and majordomo you are running. What was the result `wrapper config-test` as the root or majordomo user? What was the result as a non-root non-majordomo user? What does /var/log/maillog or /var/lib/majordomo/Log show when you send a message to your test list? Dan Liston > Correction... here is the current /etc/aliases file in use: > > > majordomo: "|/usr/lib/majordomo/wrapper majordomo" > majordomo-owner: majordomo BAD! ^^^^ if nothing else, say owner-majordomo > owner-majordomo: majordomo @ mils.example.com BAD! ^^^^ if you don't want to ever see messages to the list or majordomo owner address redirect the alias to nobody(at)your(dot)domain or /dev/null. Otherwise, point them to YOUR real email address. I seriously doubt that majordomo (at) anydomain (dot) com is a REAL or HUMAN address. > test: "|/usr/lib/majordomo/wrapper resend -l test test-outgoing,nobody" > test-outgoing: :include:/var/lib/majordomo/lists/test,test-digestify,test-archiver Change this one to... test-outgoing: :include:/var/lib/majordomo/lists/test, > test-digestify: "|/usr/lib/majordomo/wrapper digest -r -C -l test-digest > test-digest-outgoing,nobody" Delete the previous two lines... > owner-test: majordomo @ mils.example.com BAD! ^^^^ same as above. Point this to YOUR address or /dev/null. > test-owner: owner-test > test-digest: test > test-digest-outgoing: :include:/var/lib/majordomo/lists/test-digest,nobody > test-digest-owner: owner-test Delete the previous three lines... > test-request: "|/usr/lib/majordomo/wrapper majordomo -l test" > test-digest-request: "|/usr/lib/majordomo/wrapper majordomo -l test-digest" Delete the line/alias above ^^^ > test-approval: owner-test > test-digest-approval: owner-test Delete this last line/alias ^^^ > > -------------- Original message from Daniel Liston > > The majordomo-owner:majordomo owner-test and test-owner aliases are > potential > > mail loops. In other words, why are you redirecting address that > should reach a human, to a > > program? > > And unless you are on a hosted domain, why are you using -C > name-of-config-file? Why do you have a test-list and a > test-outgoing? Use one or the other, but use > > one. The final argument of your pipe to wrapper is missing the > recipient address. > > This is how/where you make a call to test-list or test-outgoing. > See my aliases below; > > In your case, you should probably remove aliases and recipients > containing archive or > > digest. If you use these exactly as posted, you will need to > solve dependencies in your > > majordomo.cf > > and file system directory structure. > > > > majordomo: "|/usr/lib/majordomo/wrapper majordomo" > > majordomo-owner: owner-majordomo > > owner-majordomo: real-person (at) anydomain (dot) com, > > # The above address is obfuscated, please use a real address. > > > > test: "|/usr/lib/majordomo/wrapper resend -l test > test-outgoing,nobody" > > test-outgoing: > > :include:/var/lib/majordomo/lists/test,test-digestify,test-archiver > > test-archiver: "|/usr/lib/majordomo/wrapper archive2.pl -f > > /var/lib/majordomo/archive/test/test -a -M" > > test-digestify: "|/usr/lib/majordomo/wrapper digest -r -C -l > test-digest > > test-digest-outgoing,nobody" > > owner-test: some-person (at) anydomain (dot) net, > > # The above address is obfuscated, please use a real address. > > test-owner: owner-test > > test-digest: test > > test-digest-outgoing: > :include:/var/lib/majordomo/lists/test-digest,nobody > > test-digest-owner: owner-test > > test-request: "|/usr/lib/majordomo/wrapper majordomo -l test" > > test-digest-request: "|/usr/lib/majordomo/wrapper majordomo -l > test-digest" > > test-approval: owner-test > > test-digest-approval: owner-test > > > > Dan Liston > > > > The aliases presented are for a sendmail MTA. If you are using > qmail, postfix, > > exim, or some other > > MTA, please adjust accordingly. > > > > Never make untested changes to a production server. Do all > testing in a > > dedicated test environment. > > > > > I'm doing so testing of my configuration, and the message is > returned, but it > > only comes back to me and not the remainder of the subscribers on > the list. Is > > there something misconfigured in the config file? > > > > > > > > > majordomo: "|/usr/lib/majordomo/wrapper majordomo -C > /etc/majordomo.cf" > > > majordomo-owner: majordomo > > > > > > test: "|/usr/lib/majordomo/wrapper resend -l test -C > > test-list" > > > test-list: :include:/var/lib/majordomo/lists/test > > > owner-test: majordomo > > > test-owner: majordomo > > > test-outgoing: :include:/var/lib/majordomo/lists/test > > > test-request: "|/usr/lib/majordomo/wrapper majordomo -l test -C > > /etc/majordomo.cf" > > > > > > From majordomo-users-owner@greatcircle.com Fri Jul 18 21:07:20 2008 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id E08BD49837F for ; Fri, 18 Jul 2008 21:07:18 -0700 (PDT) Received: from mail.sonny.com (minute.sonny.com [192.168.1.4]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K480030AJ1X6H@mail.sonny.com> for majordomo-users@greatcircle.com; Fri, 18 Jul 2008 22:58:45 -0500 (CDT) Received: from magnum.sonny.com (magnum.sonny.com [192.168.1.68]) by minute.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K4800A0OJ264S@minute.sonny.com> for majordomo-users@greatcircle.com; Fri, 18 Jul 2008 22:58:54 -0500 (CDT) Date: Fri, 18 Jul 2008 22:59:47 -0500 From: Daniel Liston Subject: Re: Subscribers not receiving emails - new setup In-reply-to: <071720082010.16402.487FA72C0009B9560000401222230703729B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> To: Majordomo Users Message-id: <488166B3.2010405@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.14 (X11/20080501) References: <071720082010.16402.487FA72C0009B9560000401222230703729B0A02D2089B9A019C04040A0DBFC0C8C9C90B040E0C@att.net> X-Archive-Number: 200807/36 X-Sequence-Number: 5775 You left the digest aliases in, but anyway... Try one more test for me, and tell me what happens (via the list so others may learn from this experience too). First let me "assUme" you have an alias for nobody that looks like this; nobody:/dev/null or nobody:root Comment out the majordomo portions of your aliases file. #majordomo: "|/usr/lib/majordomo/wrapper majordomo" #majordomo-owner: owner-majordomo #owner-majordomo: dliston Now lets examine line by line what is happening through the aliases file. test: "|/usr/lib/majordomo/wrapper resend -l test test-outgoing,nobody" Messages to test@my.domain.com are received by sendmail and looked up in the password and/or aliases file for delivery/rewrite information. Test messages are piped through the majordomo wrapper into the resend script using the listname "test" as an argument to resend, and specifying new recipients of test-outgoing and nobody on the local machine. This means that test-outgoing and nobody are also looked up in the password and aliases files for delivery/rewrite information. If nobody:/dev/null is an entry in the aliases file, mail to the nobody address is redirected to the bitbucket and that "copy" is never seen again. The reason we want to keep this address in the recipient list, is to prevent sendmail from advertising the actual delivery address of test-outgoing in the message's header information. test-outgoing: :include:/var/lib/majordomo/lists/test This alias can be reached directly as test-outoing@ my.domain.com or through the test@ my.domain.com which processes test messages and forwards their output to this alias. At the point the message reaches this alias, sendmail will expand the :include: file for a new list of recipients of this message. This file must be readable by sendmail and majordomo for smooth operation. This alias needs to be protected from spammers, or you expose all the members of the list with a single address. test-owner: owner-test Like the other redirections, test-owner is sent/redirected to owner-test on the local machine. This could be a fully qualified address if necessary too. This address is only created to support users who cannot remember owner-test. owner-test: dliston The owner- is a hidden sendmail feature that sendmail uses to send notifications of errors/problems when it has trouble delivering to . In the case above, I chose a contact/notification address of a human that is responsible for my test mailing list. In most cases, this is the same human that is responsible for all my mailing lists and majordomo itself too. test-approval: owner-test This address is the default address majordomo will punt to when a list needs attention from a human. I aim this address at the list owner alias which in turn is aimed at a human mailbox. Lastly, I am going to "assUme" that the urls listed in your aliases below are a result of your email client, and not actually in the /etc/aliases file. When dealing with mailing lists, it is crucial that you only use pure ASCII text (not HTML or RTF) to deal with mailing lists. The alternative, is to pre-process messages to convert them to plain text or modify configurations to expect and accept fat bloated messages that are not compatible with every other mail reader on the planet. Now that you know what happens and why in the aliases (so far), I need to warn you, that majordomo has been disabled, and the test we are performing is specifically sendmail related. But before we start that, I need you to check two more sendmail settings. Does the sendmail.cf contain Tmajordomo? Does /etc/mail/trusted-users contain majordomo? If one of the above is true, you are all set to test. If neither is true, but you added one, you must restart sendmail. If you modify any line in your /etc/aliases file, you must rebuild the binary version of the file with "newaliases" or "sendmail -bi" as root. If cald7786 at bellsouth dot net is in the /var/lib/majordomo/lists/test file and test.config only allows members to post to the list, you should be able to send to every member by addressing a message to test at your dot domain from your bellsouth account. Regardless how test.config is set up addressing a message to test-outgoing at your domain from anywhere should deliver your message to all test members. Finally, here is the test. Send a message from any account you have either on or off of the system running majordomo, to test-outgoing at the domain name that has an mx pointed at the majordomo server. If the majordomo server is named moveit, and your domain is domain.com, the address to write a test message to is test-outgoing@ moveit.domain.com. If you have no typos in your aliases file, and pure ascii text in your test membership file owned by majordomo with 644 permission, and each line of the file contains nothing more than a simple email address, the message "should" be delivered to everyone in that file. /var/log/maillog should be able to validate messages going out to the recipients/members. SIDENOTE: all membership filenames must be in lower case, not upper or even mixed is allowed. IF/WHEN this works, you can reintroduce the majordomo portion of it. Write a test message to test@ your.domain instead of test-outgoing. Does it still work? I just installed majordomo 1.94.5 via RPM on a Fedora 8 machine and all is fine. Then again, I know how to interpret bounce messages, headers, and log files. When you are ready to test the "test" list again, do this first. Rename the test.config file to t.config (assuming you don't have a list called t), and send a message to majordomo with a blank subject and just this one word in the message body with no blank lines; lists This will make majordomo examine all files in the /var/lib/majordomo/lists directory and create default config files for each list that does not already have one. More comments to your specific questions/comments insterted "inline". Dan Liston cald7786 wrote: > test: "|/usr/lib/majordomo/wrapper resend -l test test-outgoing,nobody" > test-outgoing: :include:/var/lib/majordomo/lists/test These are the only aliases to worry about for now. > > > However, I'm still the only user receiving the emails. > > > > The list file for "test" is owned by majordomo. > > > > When I send a message to the list, if reports in /var/lib/majordomo/log: > > Jul 17 16:04:05 moveit-listsrv.domain majordomo[12517] {"User" > username@domain } help This error is NOT a result of sending a message to your list, this one indicates a message to majordomo that had no commands, so the help file was sent. This should mean that majordomo sent the help file to username@domain. As long as sendmail knows how to deliver to username@domain, you should have received the help file, not a copy of the message you sent. Also, keep in mind that majordomo only logs errors, not successes. To see successful distribution of your list, you must examine the /var/log/maillog file for a line containing several or all of the addresses in your list membership file. > > What linux/unix are you running your mail server on? *2.6.9-5.ELsmp* > > What MTA does your mailserver run? *sendmail-8.13.1-2* > > Is your majordomo installed on the same or a separate host? *Same host* > > What version of majordomo are you running? *1.94.5* > > Did you install majordomo yourself? *Rpm file* > > What was the output result of executing `./wrapper config-test`? > *"Nothing found bad"* All of the above seems reasonable. Nothing raises any red flags. I do need clarification however, that the log entry above is not a cut and paste, but modified for public consumption? If it is cut&paste, I have serious doubts about your aliases file. From majordomo-users-owner@greatcircle.com Mon Jul 28 09:35:12 2008 Received: from dalexmm02.acs-inc.com (dalexmm02.acs-inc.com [63.101.151.4]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2052D4B011D for ; Mon, 28 Jul 2008 09:35:10 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0AAOiQjUg/V6pIo2dsb2JhbACCciUBjzQBAQEBAQEMCAcRm2Q Received: from unknown (HELO atlexbr02.CORPATL.COM) ([63.87.170.72]) by dalexmm02.acs-inc.com with ESMTP; 28 Jul 2008 11:20:22 -0500 Received: by atlexbr02.acs-shc.com with Internet Mail Service (5.5.2657.72) id <39DM8XCB>; Mon, 28 Jul 2008 12:30:24 -0400 Message-ID: From: "Caldwell, Cedric" To: "'majordomo-users@greatcircle.com'" Subject: Group writable file ??? Date: Mon, 28 Jul 2008 12:29:09 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8F0CF.0FABD4B8" X-Archive-Number: 200807/37 X-Sequence-Number: 5776 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C8F0CF.0FABD4B8 Content-Type: text/plain Coming down the stretch with getting the tool working end-to-end.. Just stuck on why I continue to see this error when I test a new list. I've checked everything under the sun... Any thoughts or ideas why I'm seeing this: ----- Transcript of session follows ----- 550 5.2.4 :include:/var/lib/majordomo/lists/newlist... Cannot open /var/lib/majordomo/lists/newlist: Group writable file Cedric CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ------_=_NextPart_001_01C8F0CF.0FABD4B8 Content-Type: text/html Content-Transfer-Encoding: quoted-printable

Coming down the = stretch with getting the tool working end-to-end.. Just stuck on why I continue to = see this error when I test a new list. 

 

I've checked everything under the sun...

 

Any thoughts or = ideas why I'm seeing this:

 

----- Transcript = of session follows ----- 550 5.2.4 :include:/var/lib/majordomo/lists/newlist... = Cannot open /var/lib/majordomo/lists/newlist: Group writable = file

 

 

Cedric =

 

 

 

 

 

CONFIDENTIALITY NOTICE: This e-mail = message, including any attachments, is for the sole use of the intended = recipient(s) and may contain confidential and privileged information. = Any unauthorized review, use, disclosure or distribution is prohibited. = If you are not the intended recipient, please contact the sender by = reply e-mail and destroy all copies of the original message.

------_=_NextPart_001_01C8F0CF.0FABD4B8-- From majordomo-users-owner@greatcircle.com Mon Jul 28 09:52:45 2008 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id A19B24B011D for ; Mon, 28 Jul 2008 09:52:44 -0700 (PDT) Received: from mail.sonny.com (minute.sonny.com [192.168.1.4]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K4Q0062G6L85L@mail.sonny.com> for majordomo-users@greatcircle.com; Mon, 28 Jul 2008 11:46:20 -0500 (CDT) Received: from magnum.sonny.com (magnum.sonny.com [192.168.1.68]) by minute.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K4Q00H1F6LISV@minute.sonny.com> for majordomo-users@greatcircle.com; Mon, 28 Jul 2008 11:46:30 -0500 (CDT) Date: Mon, 28 Jul 2008 11:47:32 -0500 From: Daniel Liston Subject: Re: Group writable file ??? In-reply-to: To: "'majordomo-users@greatcircle.com'" Message-id: <488DF824.8050401@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.14 (X11/20080501) References: X-Archive-Number: 200807/38 X-Sequence-Number: 5777 You can consider the dontblamesendmail option in sendmail.cf; http://www.sendmail.org/tips/dontBlameSendmail Or you can change the permissions on /var/lib/majordomo/lists/newlist to 644 so it is not group writable. Dan Liston Caldwell, Cedric wrote: > Coming down the stretch with getting the tool working end-to-end.. Just > stuck on why I continue to see this error when I test a new list. > > I've checked everything under the sun... > Any thoughts or ideas why I'm seeing this: > > > > ----- Transcript of session follows ----- 550 5.2.4 > :include:/var/lib/majordomo/lists/newlist... Cannot open > /var/lib/majordomo/lists/newlist: Group writable file From majordomo-users-owner@greatcircle.com Mon Jul 28 10:53:26 2008 Received: from dalexmm02.acs-inc.com (dalexmm02.acs-inc.com [63.101.151.4]) by mycroft.greatcircle.com (Postfix) with ESMTP id 712024D00D8 for ; Mon, 28 Jul 2008 10:53:25 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvEAAKijjUg/V6pIo2dsb2JhbACCRC+PWgEBAQEBAQwIBxGcEw Received: from unknown (HELO atlexbr03.CORPATL.COM) ([63.87.170.72]) by dalexmm02.acs-inc.com with ESMTP; 28 Jul 2008 12:38:40 -0500 Received: by atlexbr03.acs-shc.com with Internet Mail Service (5.5.2657.72) id <39CMSLS7>; Mon, 28 Jul 2008 13:48:15 -0400 Message-ID: From: "Caldwell, Cedric" To: "'majordomo-users@greatcircle.com'" Subject: Auto Cache for majorcool Date: Mon, 28 Jul 2008 13:47:29 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8F0D9.502827BC" X-Archive-Number: 200807/39 X-Sequence-Number: 5778 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C8F0D9.502827BC Content-Type: text/plain Where can I find the auto cache for majorcool ? Been reading that its slow on when you have tons of lists??? Any thoughts on the best option to resolve majorcool showing dynamic lists on the server. Cedric ------_=_NextPart_001_01C8F0D9.502827BC Content-Type: text/html Content-Transfer-Encoding: quoted-printable

Where can I find the auto cache for majorcool = ?

 

Been reading that its slow on when you have tons of = lists???

 

Any thoughts on the best option to resolve majorcool = showing dynamic lists on the server.

 

 

Cedric =

 

 

 

 

------_=_NextPart_001_01C8F0D9.502827BC-- From majordomo-users-owner@greatcircle.com Mon Jul 28 11:05:37 2008 Received: from yoda.wrenkasky.com (esson.net [216.102.129.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id D4DDC4D00D8 for ; Mon, 28 Jul 2008 11:05:35 -0700 (PDT) Received: from EDS.esson.net (eds.wrenkasky.com [10.10.10.11]) (authenticated bits=0) by yoda.wrenkasky.com (8.14.2/8.14.2) with ESMTP id m6SI0BVn005824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 28 Jul 2008 11:00:17 -0700 Message-Id: <200807281800.m6SI0BVn005824@yoda.wrenkasky.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 28 Jul 2008 11:00:12 -0700 To: "Caldwell, Cedric" , From: Ed Kasky Subject: Re: Group writable file ??? In-Reply-To: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_307340890==.ALT" Received-SPF: pass (yoda.wrenkasky.com: 10.10.10.11 is authenticated by a trusted mechanism) X-Archive-Number: 200807/40 X-Sequence-Number: 5779 --=====================_307340890==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed What are the current rights on /var/lib/majordomo/lists/newlist? The error is telling you that the file is group writable and IIRC, for security pruposes, should only be writable by owner and readable only by group and other. For example: $ ls -al /usr/local/majordomo/lists/test -rw-r--r-- 1 majordom mail 13 Oct 1 2007 /usr/local/majordomo/lists/test At 09:29 AM Monday, 7/28/2008, Caldwell, Cedric wrote -=> >Coming down the stretch with getting the tool working end-to-end.. >Just stuck on why I continue to see this error when I test a new list. > >I've checked everything under the sun... > >Any thoughts or ideas why I'm seeing this: > >----- Transcript of session follows ----- 550 5.2.4 >:include:/var/lib/majordomo/lists/newlist... Cannot open >/var/lib/majordomo/lists/newlist: Group writable file ........................................................................... Randomly Generated Quote (740 of 1434): I'm moving to Mars next week, so if you have any boxes... --Steven Wright --=====================_307340890==.ALT Content-Type: text/html; charset="us-ascii" What are the current rights on /var/lib/majordomo/lists/newlist?  The error is telling you that the file is group writable and IIRC, for security pruposes, should only be writable by owner and readable only by group and other.  For example:

$ ls -al /usr/local/majordomo/lists/test
-rw-r--r-- 1 majordom mail 13 Oct  1  2007 /usr/local/majordomo/lists/test

At 09:29 AM Monday, 7/28/2008, Caldwell, Cedric wrote -=>
Coming down the stretch with getting the tool working end-to-end.. Just stuck on why I continue to see this error when I test a new list. 
 
I've checked everything under the sun...
 
Any thoughts or ideas why I'm seeing this:
 
----- Transcript of session follows ----- 550 5.2.4 :include:/var/lib/majordomo/lists/newlist... Cannot open /var/lib/majordomo/lists/newlist: Group writable file

...........................................................................
Randomly Generated Quote (740 of 1434):
I'm moving to Mars next week, so if you have any boxes...
--Steven Wright
 --=====================_307340890==.ALT-- From majordomo-users-owner@greatcircle.com Wed Jul 30 07:46:28 2008 Received: from dalexmm01.acs-inc.com (dalexmm01.acs-inc.com [63.101.151.3]) by mycroft.greatcircle.com (Postfix) with ESMTP id C6BEC4982FB for ; Wed, 30 Jul 2008 07:46:26 -0700 (PDT) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AucAAOkZkEg/V6pImGdsb2JhbACCRC+PYwEBAQEBDQ8Rnxs Received: from unknown (HELO atlexbr04.CORPATL.COM) ([63.87.170.72]) by dalexmm01.acs-inc.com with ESMTP; 30 Jul 2008 09:34:13 -0500 Received: by anc0lw00009864.ghs.oneacs.com with Internet Mail Service (5.5.2657.72) id ; Wed, 30 Jul 2008 10:40:58 -0400 Message-ID: From: "Caldwell, Cedric" To: "'majordomo-users@greatcircle.com'" Subject: Restrict Replies Date: Wed, 30 Jul 2008 10:40:00 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8F251.70F48A2A" X-Archive-Number: 200807/41 X-Sequence-Number: 5780 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C8F251.70F48A2A Content-Type: text/plain I've tried to disable our test users from replying to the original message that's being sent out. Our intent for majordomo is one-way communication. I've tried modifying these options from Majorcool : moderate=yes restrict_post = my email address what am I doing wrong to any replies to be approved first?? Cedric ------_=_NextPart_001_01C8F251.70F48A2A Content-Type: text/html Content-Transfer-Encoding: quoted-printable

I've tried to disable our test users from replying = to the original message that's being sent = out.

 

Our intent for majordomo is one-way = communication. 

 

I've tried modifying these options from Majorcool = :

 

moderate=3Dyes

restrict_post =3D my email = address

 

what am I doing wrong to any replies to be approved = first??

 

 

Cedric =

 

 

 

 

 

 

 

------_=_NextPart_001_01C8F251.70F48A2A-- From majordomo-users-owner@greatcircle.com Wed Jul 30 08:50:47 2008 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 6F38F498380 for ; Wed, 30 Jul 2008 08:50:46 -0700 (PDT) Received: from mail.sonny.com (minute.sonny.com [192.168.1.4]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K4T00I1TT0BZ4@mail.sonny.com> for majordomo-users@greatcircle.com; Wed, 30 Jul 2008 10:43:23 -0500 (CDT) Received: from magnum.sonny.com (magnum.sonny.com [192.168.1.68]) by minute.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0K4T00N1FT0RIM@minute.sonny.com> for majordomo-users@greatcircle.com; Wed, 30 Jul 2008 10:43:40 -0500 (CDT) Date: Wed, 30 Jul 2008 10:45:15 -0500 From: Daniel Liston Subject: Re: Restrict Replies In-reply-to: To: "'majordomo-users@greatcircle.com'" Message-id: <48908C8B.9020404@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.14 (X11/20080501) References: X-Archive-Number: 200807/42 X-Sequence-Number: 5781 When a user replies, is their message distributed to the list, or does it come only to the moderator? Does the sender address appear to be the sender, or does it appear as listname-owner? Without additional information, I have to assume you are on the right track with moderate and restrict_post. Dan Liston Caldwell, Cedric wrote: > I've tried to disable our test users from replying to the original > message that's being sent out. > > > > Our intent for majordomo is one-way communication. > > > > I've tried modifying these options from Majorcool : > > > > moderate=yes > > restrict_post = my email address > > > > what am I doing wrong to any replies to be approved first?? > > > > > > **Cedric ** > > > > > > > > > > > > > > > From majordomo-users-owner@greatcircle.com Wed Jul 30 10:57:27 2008 Received: from cloud.ccsf.cc.ca.us (cloud.ccsf.cc.ca.us [147.144.1.212]) by mycroft.greatcircle.com (Postfix) with ESMTP id 83B0A498396 for ; Wed, 30 Jul 2008 10:57:26 -0700 (PDT) Received: from cloud.ccsf.cc.ca.us (localhost [127.0.0.1]) by cloud.ccsf.cc.ca.us (8.14.2/8.14.2) with ESMTP id m6UHpsYA089978; Wed, 30 Jul 2008 10:51:54 -0700 (PDT) (envelope-from jjah@cloud.ccsf.cc.ca.us) Received: from localhost (jjah@localhost) by cloud.ccsf.cc.ca.us (8.14.2/8.14.2/Submit) with ESMTP id m6UHpsSq089960; Wed, 30 Jul 2008 10:51:54 -0700 (PDT) (envelope-from jjah@cloud.ccsf.cc.ca.us) Date: Wed, 30 Jul 2008 10:51:54 -0700 (PDT) From: "Joe R. Jah" To: "Caldwell, Cedric" cc: "'majordomo-users@greatcircle.com'" Subject: Re: Restrict Replies In-Reply-To: Message-ID: <20080730102149.X83200@cloud.ccsf.cc.ca.us> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Archive-Number: 200807/43 X-Sequence-Number: 5782 On Wed, 30 Jul 2008, Caldwell, Cedric wrote: > I've tried to disable our test users from replying to the original message > that's being sent out. > > Our intent for majordomo is one-way communication. > > I've tried modifying these options from Majorcool : > > moderate=yes > > restrict_post = my email address > > what am I doing wrong to any replies to be approved first?? > > Cedric For one-way communication you don't need to set moderate=yes. If you have applied this patch: ftp://ftp.ccsf.org/majordomo-patches/1.94.5/restrict2domain.1 All you'd need is to restrict post to a valid email address at: restrict_post = my_valid@email.address If you haven't applied the patch, you'd need to create a file in your list directory, say my_list_name-post, and enter one or more valid email addresses in that file. Then set the restrict post to that file: restrict_post = my_list_name-post Regards, Joe -- _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ _-\<,_ _/ _/ _/_/_/ _/ _/ ......(_)/ (_) _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us