From majordomo-users-owner@greatcircle.com Mon Mar 3 07:31:39 2003 Received: from mail.winnefox.org (mail.winnefox.org [199.242.176.171]) by mycroft.greatcircle.com (Postfix) with ESMTP id 0BAF7195F0E for ; Mon, 3 Mar 2003 07:31:37 -0800 (PST) Received: by MAIL with Internet Mail Service (5.5.2656.59) id ; Mon, 3 Mar 2003 09:31:52 -0600 Message-ID: <84CFA712F666B44A94CE6BE116BAF4B0B4E42E@MAIL> From: Jody Cleveland To: 'Daniel Liston' , Majordomo-Users@greatcircle.com Subject: Re: Not able to send email to list Date: Mon, 3 Mar 2003 09:31:49 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" X-Archive-Number: 200303/1 X-Sequence-Number: 2872 I've been trying this url for several days now, and it doesn't want to work. Keeps saying there are too many users. So, I did a search on redhat's site for an rpm. Nothing is found, only a few versions of Mailman. If I use the tarball off the majordomo site, is there anything I need to be aware of for setting it up on redhat 8? Jody > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Friday, February 28, 2003 6:44 AM > To: Jody Cleveland > Cc: Majordomo-Users@greatcircle.com > Subject: Re: Not able to send email to list > > > Redhat 8 is shipped with mailman as the list manager. You need to > rename the /etc/smrsh/wrapper link so that you can create a link > to majordomo's wrapper in that same directory. You might also try > changing the underscores in the list names to dashes. I seem to > recall majordomo not liking underscores very well. > > Dan Liston > > ftp://ftp.redhat.com/pub/redhat/linux/updates/6.1/en/powertool s/i386/majordomo-1.94.5-2.i386.rpm From majordomo-users-owner@greatcircle.com Mon Mar 3 08:17:43 2003 Received: from rbadb1.RBACPXCLU.BAS.ROCHE.COM (mail-external-basel.roche.com [196.3.50.190]) by mycroft.greatcircle.com (Postfix) with ESMTP id 15A2B1959E6 for ; Mon, 3 Mar 2003 08:17:41 -0800 (PST) Received: from CONVERSION-DAEMON.Roche.COM by Roche.COM (PMDF V6.0-025 #47170) id <01KT3G9VHJ1S99NMVL@Roche.COM> for majordomo-users@greatcircle.com; Mon, 03 Mar 2003 17:16:53 +0100 Received: from rbamsemcn1.emea.roche.com (rbamsemcn1.emea.roche.com [145.245.211.139]) by Roche.COM (PMDF V6.0-025 #47170) with ESMTP id <01KT3G9IZLAC98NPT7@Roche.COM>; Mon, 03 Mar 2003 17:16:35 +0100 Received: from rkamsem1.emea.roche.com ([145.245.247.233]) by rbamsemcn1.emea.roche.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 03 Mar 2003 17:16:25 +0100 Date: Mon, 03 Mar 2003 17:16:19 +0100 From: "Cencigh, Maurizio {PGID~Kaiseraugst}" Subject: Re: Error Msg sending newsletter To: Daniel Liston , majordomo-users Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6334.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable Thread-Topic: Error Msg sending newsletter Thread-Index: AcLdxbqLVQk6iWssQBq/1UNOMxX4RwD2kfFw content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: X-OriginalArrivalTime: 03 Mar 2003 16:16:25.0559 (UTC) FILETIME=[3D14DE70:01C2E1A0] X-Archive-Number: 200303/2 X-Sequence-Number: 2873 Hi once again, I tried with the faq article you send me. I changed sendmail.cf to DontBlameSendmail=3Dsafe. The group is the same since installation. I still get the same error msg. any more hints? I'm desperate seeking the solution..... Thanks. -----Original Message----- From: Daniel Liston [mailto:dliston@sonny.org]=20 Sent: Wednesday, February 26, 2003 7:34 PM To: Cencigh, Maurizio {PGID~Kaiseraugst}; majordomo-users Subject: Re: Error Msg sending newsletter I kind of have an aversion to using daemon for the majordomo group. Please notice sendmail's FAQ on the majordomo subject: http://www.sendmail.org/faq/section3.html#3.32 If you did change the group without recompiling majordomo's wrapper you could get error messages in the log, but another possibility is the version of sendmail you upgraded to (as a side effect of the newer OS) might utilize a submit.cf similar to the sendmail.cf. If this is the case, make sure you have a "trust" statement for the majordomo user in that file too. Dan Liston >=20 >=20 > Hi again, >=20 > the old server was: Solaris 2.6 with Sendmail 8.8.8 running on E450 > the new server is: Solaris 8 with Sendmail 8.11.6 running on V480 > Majordomo 1.94.5 >=20 > I only copied the lists. The lists directory was created by the=20 > majordomo installation. Then changed owner on the lists and=20 > list.config files. Uid still the same, but other group. Now I'm using=20 > group daemon before majord had an own group. In the Log file this=20 > error isn't logged. I don't understand the linking and the smrsh=20 > thing. And the group writable issue shouldn't be bothering as group=20 > has no write permission the hole path down to majordomo. >=20 > Thank for help. > Maurizio >=20 >=20 >=20 > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Friday, February 21, 2003 7:08 PM > To: majordomo-users@greatcircle.com > Subject: Re: Error Msg sending newsletter >=20 >=20 > You also need to check down to /usr/local/majordomo/lists actually.=20 > NO, Definately do NOT change any permissions to group writable if you=20 > want to keep sendmail happy. >=20 > You have not mentioned your hardware, operating system, or versions of > sendmail or majordomo. If you just "copied" majordomo from one server > to the other, did you make SURE that you used the same UID and GID on=20 > both machines? I mean the number, not the name. Wrapper is dependent=20 > on this. If sendmail is new on one machine than the other, you may=20 > also need to add a link to wrapper in the proper smrsh directory.=20=20 > Perhaps a cut and paste of the exact error message from the log file=20 > would be helpful here too. >=20 > Dan Liston >=20 > Cencigh, Maurizio {PGID~Kaiseraugst} wrote: >=20 >>I checked permissions on my subscriber files, but still get the error. >=20 >=20 >>The directory structure down to majordomo is not group writable. I=20 >>installed with daemon as group, but majord is not member of it. any=20 >>other hints? must the dir structure be group writable? I'm SysAdmin=20 >>but I don't know Sendmail and its behaviors...... any help is=20 >>apreciated a lot. >> >>Maurizio >> >>-----Original Message----- >>From: Daniel Liston [mailto:dliston@sonny.org] >>Sent: Friday, February 21, 2003 4:50 PM >>To: Cencigh, Maurizio {PGID~Kaiseraugst}; >>majordomo-users@greatcircle.com >>Subject: Re: Error Msg sending newsletter >> >> >>Check the ownership/permission on your new majordomo installation. If=20 >>you are running sendmail on the new server, it might now allow group=20 >>or world "writable" permission down the path to majordomo's directory. >=20 >=20 >>For example, /, /usr, /usr/local, /usr/local/majordomo. Sendmail will=20 >>also complain about group or world writable :include: files in your=20 >>lists directory. These are your list membership or zubscriber files. >> >>Dan Liston >> >>Cencigh, Maurizio {PGID~Kaiseraugst} wrote: >> >> >>>hi all, >>> >>>I'm migrating a Server, so I installed a new Majordomo on the new >>>server. I copied the old lists and aliases. When I send a mail to=20 >>>majordomo like who listname or lists, I get back an answer. When I try >> >> >>>to send a newsletter to a list I get the error message below. Anybody >>>an idea? Please help. My majordomo isn't working right now. >>> >>> Unable to expand a distribution list to deliver the message to its >>>members. Try again or contact your system administrator. >>> >>>Thanks in advance. >>>Maurizio >> >> >> >=20 >=20 From majordomo-users-owner@greatcircle.com Mon Mar 3 10:36:43 2003 Received: from pilot25.cl.msu.edu (pilot25.cl.msu.edu [35.9.5.45]) by mycroft.greatcircle.com (Postfix) with ESMTP id D24CB1959F7 for ; Mon, 3 Mar 2003 10:36:41 -0800 (PST) Received: from msu.edu (glass.cl.msu.edu [35.8.1.176]) by pilot25.cl.msu.edu (8.10.2/8.10.2) with ESMTP id h23IaeE25470 for ; Mon, 3 Mar 2003 13:36:40 -0500 Message-ID: <3E639F30.78996FEA@msu.edu> Date: Mon, 03 Mar 2003 13:30:08 -0500 From: Joe Glass X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Majorcool - logout button? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/3 X-Sequence-Number: 2874 Hi, I'm trying to add functionality to majorcool to prevent unauthorized usage of majorcool. Right now, if a majorcool list admin enters in a list password on a web browser, and then leaves the majorcool page, the list password is remembered until the user exists the browser. So, I'd like to add a logout button. Looking at the code of majorcool, it's easy enough to physically put the button in there, but I'm having trouble figuring where to place code to to forget the password (which I believe is stored in $args{passwd}). If anyone is familiar with the code and can help me, I'd appreciate it. Thank you! -- Joe Glass Systems Management, Michigan State University 517-355-4500 x240 glassjos@msu.edu From majordomo-users-owner@greatcircle.com Mon Mar 3 11:51:18 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id B7A7F195FB2 for ; Mon, 3 Mar 2003 11:51:14 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.5/8.12.5) with ESMTP id h23JqwNe016097; Mon, 3 Mar 2003 13:53:00 -0600 Message-ID: <3E63B238.5010205@sonny.org> Date: Mon, 03 Mar 2003 13:51:20 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Cencigh, Maurizio {PGID~Kaiseraugst}" Cc: majordomo-users Subject: Re: Error Msg sending newsletter References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/4 X-Sequence-Number: 2875 Please do these comparisons to validate uid:gid are the same between the old and the new systems. On each machine, run as root; grep majordom /etc/passwd majordom:*:54:1:Majordomo List Mgr:/var/majordomo:/usr/local/bin/bash majordom:*:1007:1007:Majordomo Server:/home/majordom:/bin/false majordomo:x:91:91:Majordomo List Manager:/usr/lib/majordomo:/bin/bash As you can see, I have three machines running majordomo, but none of them have the same uid or gid. For that matter, none of them even have the same home directory. There is no way I could just copy these instances between machines, I would have to recompile the wrapper for each system, not to mention chown'ing files and directories. Your majordomo address/alias is working, or you would not get replies to the lists and who commands. Have you tried using sendmail to verify your list or list-outgoing addresses? sendmail -bv listname sendmail -bv listname-outgoing Try these commands as both the root and the majordomo user. Dan Liston Cencigh, Maurizio {PGID~Kaiseraugst} wrote: > Hi once again, > > I tried with the faq article you send me. I changed sendmail.cf to > DontBlameSendmail=safe. The group is the same since installation. I > still get the same error msg. any more hints? I'm desperate seeking the > solution..... > > Thanks. > > > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Wednesday, February 26, 2003 7:34 PM > To: Cencigh, Maurizio {PGID~Kaiseraugst}; majordomo-users > Subject: Re: Error Msg sending newsletter > > > > I kind of have an aversion to using daemon for the majordomo group. > Please notice sendmail's FAQ on the majordomo subject: > > http://www.sendmail.org/faq/section3.html#3.32 > > If you did change the group without recompiling majordomo's wrapper you > could get error messages in the log, but another possibility is the > version of sendmail you upgraded to (as a side effect of the newer OS) > might utilize a submit.cf similar to the sendmail.cf. If this is the > case, make sure you have a "trust" statement for the majordomo user in > that file too. > > Dan Liston > > >> >>Hi again, >> >>the old server was: Solaris 2.6 with Sendmail 8.8.8 running on E450 >>the new server is: Solaris 8 with Sendmail 8.11.6 running on V480 >>Majordomo 1.94.5 >> >>I only copied the lists. The lists directory was created by the >>majordomo installation. Then changed owner on the lists and >>list.config files. Uid still the same, but other group. Now I'm using >>group daemon before majord had an own group. In the Log file this >>error isn't logged. I don't understand the linking and the smrsh >>thing. And the group writable issue shouldn't be bothering as group >>has no write permission the hole path down to majordomo. >> >>Thank for help. >>Maurizio >> >> >> >>-----Original Message----- >>From: Daniel Liston [mailto:dliston@sonny.org] >>Sent: Friday, February 21, 2003 7:08 PM >>To: majordomo-users@greatcircle.com >>Subject: Re: Error Msg sending newsletter >> >> >>You also need to check down to /usr/local/majordomo/lists actually. >>NO, Definately do NOT change any permissions to group writable if you >>want to keep sendmail happy. >> >>You have not mentioned your hardware, operating system, or versions of > > >>sendmail or majordomo. If you just "copied" majordomo from one server > > >>to the other, did you make SURE that you used the same UID and GID on >>both machines? I mean the number, not the name. Wrapper is dependent >>on this. If sendmail is new on one machine than the other, you may >>also need to add a link to wrapper in the proper smrsh directory. >>Perhaps a cut and paste of the exact error message from the log file >>would be helpful here too. >> >>Dan Liston >> >>Cencigh, Maurizio {PGID~Kaiseraugst} wrote: >> >> >>>I checked permissions on my subscriber files, but still get the error. >> >> >>>The directory structure down to majordomo is not group writable. I >>>installed with daemon as group, but majord is not member of it. any >>>other hints? must the dir structure be group writable? I'm SysAdmin >>>but I don't know Sendmail and its behaviors...... any help is >>>apreciated a lot. >>> >>>Maurizio >>> >>>-----Original Message----- >>>From: Daniel Liston [mailto:dliston@sonny.org] >>>Sent: Friday, February 21, 2003 4:50 PM >>>To: Cencigh, Maurizio {PGID~Kaiseraugst}; >>>majordomo-users@greatcircle.com >>>Subject: Re: Error Msg sending newsletter >>> >>> >>>Check the ownership/permission on your new majordomo installation. If >>>you are running sendmail on the new server, it might now allow group >>>or world "writable" permission down the path to majordomo's directory. >> >> >>>For example, /, /usr, /usr/local, /usr/local/majordomo. Sendmail will >>>also complain about group or world writable :include: files in your >>>lists directory. These are your list membership or zubscriber files. >>> >>>Dan Liston >>> >>>Cencigh, Maurizio {PGID~Kaiseraugst} wrote: >>> >>> >>> >>>>hi all, >>>> >>>>I'm migrating a Server, so I installed a new Majordomo on the new >>>>server. I copied the old lists and aliases. When I send a mail to >>>>majordomo like who listname or lists, I get back an answer. When I >>> > try > >>> >>>>to send a newsletter to a list I get the error message below. Anybody >>>>an idea? Please help. My majordomo isn't working right now. >>>> >>>>Unable to expand a distribution list to deliver the message to its >>>>members. Try again or contact your system administrator. >>>> >>>>Thanks in advance. >>>>Maurizio >>> >>> >>> >> > > From majordomo-users-owner@greatcircle.com Tue Mar 4 02:13:29 2003 Received: from rbadb2.rbacpxclu.bas.roche.com (gw.bas.roche.com [196.3.50.241]) by mycroft.greatcircle.com (Postfix) with ESMTP id 7A035195A95 for ; Tue, 4 Mar 2003 02:13:24 -0800 (PST) Received: from CONVERSION-DAEMON.Roche.COM by Roche.COM (PMDF V6.0-025 #47170) id <01KT4HQ2QJ8G98O6RZ@Roche.COM> for majordomo-users@greatcircle.com; Tue, 04 Mar 2003 11:09:33 +0100 Received: from rbamsemcn1.emea.roche.com (rbamsemcn1.emea.roche.com [145.245.211.139]) by Roche.COM (PMDF V6.0-025 #47170) with ESMTP id <01KT4HPX2WPI99OJYC@Roche.COM>; Tue, 04 Mar 2003 11:09:22 +0100 Received: from rkamsemcn1.emea.roche.com ([145.245.247.234]) by rbamsemcn1.emea.roche.com with Microsoft SMTPSVC(5.0.2195.2966); Tue, 04 Mar 2003 11:07:40 +0100 Received: from rkamsem1.emea.roche.com ([145.245.247.233]) by rkamsemcn1.emea.roche.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 04 Mar 2003 11:03:22 +0100 Date: Tue, 04 Mar 2003 11:03:19 +0100 From: "Cencigh, Maurizio {PGID~Kaiseraugst}" Subject: Re: Error Msg sending newsletter To: Daniel Liston Cc: majordomo-users Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6334.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable Thread-Topic: Error Msg sending newsletter Thread-Index: AcLhvkgpS3ok62W2RnaZRPyJzkt+SQAcO2qA content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: X-OriginalArrivalTime: 04 Mar 2003 10:03:22.0663 (UTC) FILETIME=[4A3FBB70:01C2E235] X-Archive-Number: 200303/5 X-Sequence-Number: 2876 I don't think the problem concers uid and gid. I installed a fresh version of majordomo on the new machine. Compiling the wrapper and everything on the new machine with the uid and gid I gave. The ONLY thing I copied from the old machine is the content of the lists directory and then chown the listname, listname.conf, listname.poster. I tried the sendmail commands. When I run as root: sendmail -bv listname, gives as output the entry after listname of the aliases file. sendmail -bv listname-outgoing, tells me user unknown. I think this may be the problem. as the majord user I get: sendmail -bv listname, tells about misleading output for non-privileged user and says can not chdir (/var/spool/mqueue): Permission denied. Program mode requires special privilege, eg. root or TrustedUser. I tried to change the TrustedUser in sendmail.cf, and set it to majord and restarted sendmail. Same error msg. as usual. sendmail -bv listname-outgoing, gives the same. Can you tell me more about? I think or the user unknown is the problem or non-privilege thing on /var/spool/mqueue. What permissions are needed on /var/spool/mqueue. Or which TrustedUser should I configure in sendmail.cf? Thanks a lot. I feel getting near to the solution... -----Original Message----- From: Daniel Liston [mailto:dliston@sonny.org]=20 Sent: Monday, March 03, 2003 8:51 PM To: Cencigh, Maurizio {PGID~Kaiseraugst} Cc: majordomo-users Subject: Re: Error Msg sending newsletter Please do these comparisons to validate uid:gid are the same between the old and the new systems. On each machine, run as root; grep majordom /etc/passwd majordom:*:54:1:Majordomo List Mgr:/var/majordomo:/usr/local/bin/bash majordom:*:1007:1007:Majordomo Server:/home/majordom:/bin/false majordomo:x:91:91:Majordomo List Manager:/usr/lib/majordomo:/bin/bash As you can see, I have three machines running majordomo, but none of them have the same uid or gid. For that matter, none of them even have the same home directory. There is no way I could just copy these instances between machines, I would have to recompile the wrapper for each system, not to mention chown'ing files and directories. Your majordomo address/alias is working, or you would not get replies to the lists and who commands. Have you tried using sendmail to verify your list or list-outgoing addresses? sendmail -bv listname sendmail -bv listname-outgoing Try these commands as both the root and the majordomo user. Dan Liston Cencigh, Maurizio {PGID~Kaiseraugst} wrote: > Hi once again, >=20 > I tried with the faq article you send me. I changed sendmail.cf to=20 > DontBlameSendmail=3Dsafe. The group is the same since installation. I=20 > still get the same error msg. any more hints? I'm desperate seeking=20 > the solution..... >=20 > Thanks. >=20 >=20 > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Wednesday, February 26, 2003 7:34 PM > To: Cencigh, Maurizio {PGID~Kaiseraugst}; majordomo-users > Subject: Re: Error Msg sending newsletter >=20 >=20 >=20 > I kind of have an aversion to using daemon for the majordomo group.=20 > Please notice sendmail's FAQ on the majordomo subject: >=20 > http://www.sendmail.org/faq/section3.html#3.32 >=20 > If you did change the group without recompiling majordomo's wrapper=20 > you could get error messages in the log, but another possibility is=20 > the version of sendmail you upgraded to (as a side effect of the newer > OS) might utilize a submit.cf similar to the sendmail.cf. If this is=20 > the case, make sure you have a "trust" statement for the majordomo=20 > user in that file too. >=20 > Dan Liston >=20 >=20 >> >>Hi again, >> >>the old server was: Solaris 2.6 with Sendmail 8.8.8 running on E450 >>the new server is: Solaris 8 with Sendmail 8.11.6 running on V480 >>Majordomo 1.94.5 >> >>I only copied the lists. The lists directory was created by the >>majordomo installation. Then changed owner on the lists and=20 >>list.config files. Uid still the same, but other group. Now I'm using=20 >>group daemon before majord had an own group. In the Log file this=20 >>error isn't logged. I don't understand the linking and the smrsh=20 >>thing. And the group writable issue shouldn't be bothering as group=20 >>has no write permission the hole path down to majordomo. >> >>Thank for help. >>Maurizio >> >> >> >>-----Original Message----- >>From: Daniel Liston [mailto:dliston@sonny.org] >>Sent: Friday, February 21, 2003 7:08 PM >>To: majordomo-users@greatcircle.com >>Subject: Re: Error Msg sending newsletter >> >> >>You also need to check down to /usr/local/majordomo/lists actually. >>NO, Definately do NOT change any permissions to group writable if you=20 >>want to keep sendmail happy. >> >>You have not mentioned your hardware, operating system, or versions of >=20 >=20 >>sendmail or majordomo. If you just "copied" majordomo from one server >=20 >=20 >>to the other, did you make SURE that you used the same UID and GID on >>both machines? I mean the number, not the name. Wrapper is dependent=20 >>on this. If sendmail is new on one machine than the other, you may=20 >>also need to add a link to wrapper in the proper smrsh directory.=20=20 >>Perhaps a cut and paste of the exact error message from the log file=20 >>would be helpful here too. >> >>Dan Liston >> >>Cencigh, Maurizio {PGID~Kaiseraugst} wrote: >> >> >>>I checked permissions on my subscriber files, but still get the=20 >>>error. >> >> >>>The directory structure down to majordomo is not group writable. I >>>installed with daemon as group, but majord is not member of it. any=20 >>>other hints? must the dir structure be group writable? I'm SysAdmin=20 >>>but I don't know Sendmail and its behaviors...... any help is=20 >>>apreciated a lot. >>> >>>Maurizio >>> >>>-----Original Message----- >>>From: Daniel Liston [mailto:dliston@sonny.org] >>>Sent: Friday, February 21, 2003 4:50 PM >>>To: Cencigh, Maurizio {PGID~Kaiseraugst};=20 >>>majordomo-users@greatcircle.com >>>Subject: Re: Error Msg sending newsletter >>> >>> >>>Check the ownership/permission on your new majordomo installation. If >>>you are running sendmail on the new server, it might now allow group=20 >>>or world "writable" permission down the path to majordomo's directory. >> >> >>>For example, /, /usr, /usr/local, /usr/local/majordomo. Sendmail will >>>also complain about group or world writable :include: files in your=20 >>>lists directory. These are your list membership or zubscriber files. >>> >>>Dan Liston >>> >>>Cencigh, Maurizio {PGID~Kaiseraugst} wrote: >>> >>> >>> >>>>hi all, >>>> >>>>I'm migrating a Server, so I installed a new Majordomo on the new=20 >>>>server. I copied the old lists and aliases. When I send a mail to=20 >>>>majordomo like who listname or lists, I get back an answer. When I >>> > try >=20 >>> >>>>to send a newsletter to a list I get the error message below.=20 >>>>Anybody an idea? Please help. My majordomo isn't working right now. >>>> >>>>Unable to expand a distribution list to deliver the message to its=20 >>>>members. Try again or contact your system administrator. >>>> >>>>Thanks in advance. >>>>Maurizio >>> >>> >>> >> >=20 >=20 From majordomo-users-owner@greatcircle.com Tue Mar 4 10:59:35 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id B839E195A43 for ; Tue, 4 Mar 2003 10:59:31 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h24J1mEt003451; Tue, 4 Mar 2003 13:01:49 -0600 Message-ID: <3E64F79F.4090805@sonny.org> Date: Tue, 04 Mar 2003 12:59:43 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Cencigh, Maurizio {PGID~Kaiseraugst}" Cc: majordomo-users Subject: Re: Error Msg sending newsletter References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/6 X-Sequence-Number: 2877 I am not certain if this is the same for solaris or linux using the same version of sendmail 8.11.6, but the "trusted" majord user has to be added to the submit.cf file as well as the sendmail.cf. Dan Liston Cencigh, Maurizio {PGID~Kaiseraugst} wrote: > I don't think the problem concers uid and gid. I installed a fresh > version of majordomo on the new machine. Compiling the wrapper and > everything on the new machine with the uid and gid I gave. The ONLY > thing I copied from the old machine is the content of the lists > directory and then chown the listname, listname.conf, listname.poster. > > I tried the sendmail commands. When I run as root: > sendmail -bv listname, gives as output the entry after listname of the > aliases file. > sendmail -bv listname-outgoing, tells me user unknown. I think this may > be the problem. > > as the majord user I get: > sendmail -bv listname, tells about misleading output for non-privileged > user and says can not chdir (/var/spool/mqueue): Permission denied. > Program mode requires special privilege, eg. root or TrustedUser. I > tried to change the TrustedUser in sendmail.cf, and set it to majord and > restarted sendmail. Same error msg. as usual. > sendmail -bv listname-outgoing, gives the same. > > Can you tell me more about? I think or the user unknown is the problem > or non-privilege thing on /var/spool/mqueue. What permissions are needed > on /var/spool/mqueue. Or which TrustedUser should I configure in > sendmail.cf? > > Thanks a lot. > I feel getting near to the solution... > > > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Monday, March 03, 2003 8:51 PM > To: Cencigh, Maurizio {PGID~Kaiseraugst} > Cc: majordomo-users > Subject: Re: Error Msg sending newsletter > > > Please do these comparisons to validate uid:gid are the same between the > old and the new systems. On each machine, run as root; > > grep majordom /etc/passwd > > majordom:*:54:1:Majordomo List Mgr:/var/majordomo:/usr/local/bin/bash > majordom:*:1007:1007:Majordomo Server:/home/majordom:/bin/false > majordomo:x:91:91:Majordomo List Manager:/usr/lib/majordomo:/bin/bash > > As you can see, I have three machines running majordomo, but none of > them have the same uid or gid. For that matter, none of them even have > the same home directory. There is no way I could just copy these > instances between machines, I would have to recompile the wrapper for > each system, not to mention chown'ing files and directories. > > Your majordomo address/alias is working, or you would not get replies to > the lists and who commands. Have you tried using sendmail to verify > your list or list-outgoing addresses? > > sendmail -bv listname > sendmail -bv listname-outgoing > > Try these commands as both the root and the majordomo user. > > Dan Liston > > Cencigh, Maurizio {PGID~Kaiseraugst} wrote: > >>Hi once again, >> >>I tried with the faq article you send me. I changed sendmail.cf to >>DontBlameSendmail=safe. The group is the same since installation. I >>still get the same error msg. any more hints? I'm desperate seeking >>the solution..... >> >>Thanks. >> >> >>-----Original Message----- >>From: Daniel Liston [mailto:dliston@sonny.org] >>Sent: Wednesday, February 26, 2003 7:34 PM >>To: Cencigh, Maurizio {PGID~Kaiseraugst}; majordomo-users >>Subject: Re: Error Msg sending newsletter >> >> >> >>I kind of have an aversion to using daemon for the majordomo group. >>Please notice sendmail's FAQ on the majordomo subject: >> >>http://www.sendmail.org/faq/section3.html#3.32 >> >>If you did change the group without recompiling majordomo's wrapper >>you could get error messages in the log, but another possibility is >>the version of sendmail you upgraded to (as a side effect of the newer > > >>OS) might utilize a submit.cf similar to the sendmail.cf. If this is >>the case, make sure you have a "trust" statement for the majordomo >>user in that file too. >> >>Dan Liston >> >> >> >>>Hi again, >>> >>>the old server was: Solaris 2.6 with Sendmail 8.8.8 running on E450 >>>the new server is: Solaris 8 with Sendmail 8.11.6 running on V480 >>>Majordomo 1.94.5 >>> >>>I only copied the lists. The lists directory was created by the >>>majordomo installation. Then changed owner on the lists and >>>list.config files. Uid still the same, but other group. Now I'm using >>>group daemon before majord had an own group. In the Log file this >>>error isn't logged. I don't understand the linking and the smrsh >>>thing. And the group writable issue shouldn't be bothering as group >>>has no write permission the hole path down to majordomo. >>> >>>Thank for help. >>>Maurizio >>> >>> >>> >>>-----Original Message----- >>>From: Daniel Liston [mailto:dliston@sonny.org] >>>Sent: Friday, February 21, 2003 7:08 PM >>>To: majordomo-users@greatcircle.com >>>Subject: Re: Error Msg sending newsletter >>> >>> >>>You also need to check down to /usr/local/majordomo/lists actually. >>>NO, Definately do NOT change any permissions to group writable if you >>>want to keep sendmail happy. >>> >>>You have not mentioned your hardware, operating system, or versions of >> >> >>>sendmail or majordomo. If you just "copied" majordomo from one server >> >> >>>to the other, did you make SURE that you used the same UID and GID on >>>both machines? I mean the number, not the name. Wrapper is dependent >>>on this. If sendmail is new on one machine than the other, you may >>>also need to add a link to wrapper in the proper smrsh directory. >>>Perhaps a cut and paste of the exact error message from the log file >>>would be helpful here too. >>> >>>Dan Liston >>> >>>Cencigh, Maurizio {PGID~Kaiseraugst} wrote: >>> >>> >>> >>>>I checked permissions on my subscriber files, but still get the >>>>error. >>> >>> >>>>The directory structure down to majordomo is not group writable. I >>>>installed with daemon as group, but majord is not member of it. any >>>>other hints? must the dir structure be group writable? I'm SysAdmin >>>>but I don't know Sendmail and its behaviors...... any help is >>>>apreciated a lot. >>>> >>>>Maurizio >>>> >>>>-----Original Message----- >>>>From: Daniel Liston [mailto:dliston@sonny.org] >>>>Sent: Friday, February 21, 2003 4:50 PM >>>>To: Cencigh, Maurizio {PGID~Kaiseraugst}; >>>>majordomo-users@greatcircle.com >>>>Subject: Re: Error Msg sending newsletter >>>> >>>> >>>>Check the ownership/permission on your new majordomo installation. If >>>>you are running sendmail on the new server, it might now allow group >>>>or world "writable" permission down the path to majordomo's >>> > directory. > >>> >>>>For example, /, /usr, /usr/local, /usr/local/majordomo. Sendmail will >>>>also complain about group or world writable :include: files in your >>>>lists directory. These are your list membership or zubscriber files. >>>> >>>>Dan Liston >>>> >>>>Cencigh, Maurizio {PGID~Kaiseraugst} wrote: >>>> >>>> >>>> >>>> >>>>>hi all, >>>>> >>>>>I'm migrating a Server, so I installed a new Majordomo on the new >>>>>server. I copied the old lists and aliases. When I send a mail to >>>>>majordomo like who listname or lists, I get back an answer. When I >>>> >>try >> >> >>>>>to send a newsletter to a list I get the error message below. >>>>>Anybody an idea? Please help. My majordomo isn't working right now. >>>>> >>>>>Unable to expand a distribution list to deliver the message to its >>>>>members. Try again or contact your system administrator. >>>>> >>>>>Thanks in advance. >>>>>Maurizio >>>> >>>> >>>> >> > > From majordomo-users-owner@greatcircle.com Tue Mar 4 11:28:12 2003 Received: from mail.bcpl.net (mail.bcpl.net [204.255.212.10]) by mycroft.greatcircle.com (Postfix) with ESMTP id D5012195A3A for ; Tue, 4 Mar 2003 11:28:09 -0800 (PST) Received: from mail (mail [204.255.212.10]) by mail.bcpl.net (8.11.3/8.11.3) with ESMTP id h24JS5509231 for ; Tue, 4 Mar 2003 14:28:07 -0500 (EST) Date: Tue, 4 Mar 2003 14:28:05 -0500 (EST) From: Chip Old X-X-Sender: fold@mail To: majordomo-users Subject: Re: Error Msg sending newsletter In-Reply-To: <3E64F79F.4090805@sonny.org> Message-ID: References: <3E64F79F.4090805@sonny.org> X-Organization: BCPL.NET Internet Services X-Complaints-To: abuse@bcpl.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200303/7 X-Sequence-Number: 2878 On Tue, 4 Mar 2003 12:59 -0600, Daniel Liston wrote: > I am not certain if this is the same for solaris or linux using the > same version of sendmail 8.11.6, but the "trusted" majord user has > to be added to the submit.cf file as well as the sendmail.cf. submit.cf didn't come along until sendmail 8.12 -- Chip Old (Francis E. Old) E-Mail: fold@bcpl.net Manager, BCPL Network Services Phone: 410-887-6180 Manager, BCPL.NET Internet Services FAX: 410-887-2091 320 York Road Towson, MD 21204 USA From majordomo-users-owner@greatcircle.com Tue Mar 4 11:35:09 2003 Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by mycroft.greatcircle.com (Postfix) with ESMTP id 17FF0195F97; Tue, 4 Mar 2003 11:35:09 -0800 (PST) Received: from h-66-167-135-80.phndaz91.covad.net ([66.167.135.80] helo=Vaio.earthlink.net) by avocet.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18qIBw-0003cz-00; Tue, 04 Mar 2003 11:35:08 -0800 Message-Id: <5.2.0.9.2.20030304123209.00bb7da8@pop.earthlink.net> X-Sender: bobbish@pop.earthlink.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 04 Mar 2003 12:35:08 -0700 To: list-managers@greatcircle.com, majordomo-users@greatcircle.com From: Bob Bish Subject: List manager position in NYC open Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200303/8 X-Sequence-Number: 2879 I was contacted by a Bryan Calka about a list manager position which is open in NYC. I do not know any particulars about this, the software being used, the kind of list or company involved, or anything else. If you would like to contact Bryan, his e-mail address is: bcalka@yahoo.com ...Bob From majordomo-users-owner@greatcircle.com Tue Mar 4 13:31:04 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id DB505195F36 for ; Tue, 4 Mar 2003 13:31:01 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h24LXFEt007870; Tue, 4 Mar 2003 15:33:15 -0600 Message-ID: <3E651B1B.10407@sonny.org> Date: Tue, 04 Mar 2003 15:31:07 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chip Old Cc: majordomo-users Subject: Re: Error Msg sending newsletter References: <3E64F79F.4090805@sonny.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/9 X-Sequence-Number: 2880 Chip Old wrote: > On Tue, 4 Mar 2003 12:59 -0600, Daniel Liston wrote: > > >>I am not certain if this is the same for solaris or linux using the >>same version of sendmail 8.11.6, but the "trusted" majord user has >>to be added to the submit.cf file as well as the sendmail.cf. > > > submit.cf didn't come along until sendmail 8.12 > I must be losing track of features vs. version numbers again. I am actually running out of ideas. I have not had these kind of difficulties since I was first getting started in unix and sendmail and I am probably overlooking something that I do out of habit any more. I think I have a fresh solaris 8 with 8_recommended applied. Let me go grab/install gnu-cc so I can compile the wrapper, and try migrating one of my old FreeBSD majordomo's to it to see what happens. Dan Liston From majordomo-users-owner@greatcircle.com Tue Mar 4 14:13:55 2003 Received: from arisia.yall.org (c-24-98-29-38.atl.client2.attbi.com [24.98.29.38]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2CFFC195A4C for ; Tue, 4 Mar 2003 14:13:54 -0800 (PST) Received: from palain (delgon.yall.org [192.168.1.5]) by arisia.yall.org (Postfix) with SMTP id 6DFADD9025 for ; Tue, 4 Mar 2003 17:14:50 -0500 (EST) Message-ID: <054d01c2e29b$523553b0$0501a8c0@palain> From: "Robert Dana" To: Subject: Messages being truncated... Date: Tue, 4 Mar 2003 17:13:42 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Archive-Number: 200303/10 X-Sequence-Number: 2881 I'm having a problem where a few user messages to mailing lists I host are being truncated on their trip through resend. These tend to be HTML messages from webmail (Hotmail and Yahoo) users, but I don't have enough samples yet to identify any patterns in the messages - getting the original messages has turned out to be hard because the users are barely e-mail literate. I have one pristine example of a message that causes this problem where I've been able to examine the complete message source, the output delivered to a local mailbox (not going through resend) and the output delivered through resend. The text/plain MIME attachment (which is first) is untouched. The text/html is chopped from the end of the MIME header to mid-sentence about 3/4 of the way through the message text. So to HTML-literate MUAs, the message appears to be missing the beginning part. I've set up a test list and been able to reproduce the problem using this message with DEBUG=1 turned on in resend, but my perl and programming skills have been rusting for about 5 years and I'm not having much luck interpreting the output. There isn't any obvious taboo body content or headers. Any suggestions? My setup: Majordomo 1.94.5, with Majorcool 1.3.2 patches applied Perl 5.6.1 OpenBSD 3.2 postfix 2.0.3 as MTA Thanks in advance. -Robert From majordomo-users-owner@greatcircle.com Tue Mar 4 14:40:35 2003 Received: from eui3smtp.euskaltel.es (eui3smtp.euskaltel.es [212.55.8.58]) by mycroft.greatcircle.com (Postfix) with ESMTP id DDC76195A5E for ; Tue, 4 Mar 2003 14:40:30 -0800 (PST) Received: from marge ([62.99.93.52]) by eui3smtp.euskaltel.es (Netscape Messaging Server 4.15) with SMTP id HB8XNL01.Y8N for ; Tue, 4 Mar 2003 23:40:33 +0100 Message-ID: <004801c2e29f$b797c6d0$0200a8c0@marge> From: "Gonzalo Morales" To: Subject: script to create lists Date: Tue, 4 Mar 2003 23:45:12 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0045_01C2E2A8.191BCA70" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 X-Archive-Number: 200303/11 X-Sequence-Number: 2882 This is a multi-part message in MIME format. ------=_NextPart_000_0045_01C2E2A8.191BCA70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello everybody, I have set up Majordomo 1.94.5 on a linux RedHat 7.2. I am using a majo= rdomo.aliases file and if I write it by hand as sugested in the help file = to check the well functioning of the lists everything is ok. Problem is tha= t I'd like to use a script to generate the lists and its corresponding file= s and aliases. I have tried a file posted here newlists3.pl without success= . (i try changin the paths etc) my configuration is as follows. majordomo lives in /usr/local/majordomo its configuration file majordomo.cf in the same folder. Well what I am asking is where I could get some scripts to generate lists s= o that every time I need to create a list I dont have to do everything manu= ally.=20 Thanks in advance, Gonzalo.=20 ------=_NextPart_000_0045_01C2E2A8.191BCA70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello everybody,
    I have set up Majordomo= 1.94.5=20 on a linux RedHat 7.2. I am using a majordomo.aliases  file and if I w= rite=20 it by hand as sugested in the help file to check the well functioning of th= e=20 lists everything is ok. Problem is that I'd like to use a script to generat= e the=20 lists and its corresponding files and aliases. I have tried a file posted h= ere=20 newlists3.pl without success. (i try changin the paths etc) my configuratio= n is=20 as follows.
majordomo lives in
/usr/local/majordomo
its configuration file majordomo.cf in the= same=20 folder.
Well what I am asking is where I could get= some=20 scripts to generate lists so that every time I need to create a list I dont= have=20 to do everything manually.
Thanks in advance,
Gonzalo.
------=_NextPart_000_0045_01C2E2A8.191BCA70-- From majordomo-users-owner@greatcircle.com Tue Mar 4 14:44:19 2003 Received: from mail2.wfi.com (mail2.360.net [64.114.26.208]) by mycroft.greatcircle.com (Postfix) with SMTP id DA52F195A4C for ; Tue, 4 Mar 2003 14:44:15 -0800 (PST) Received: from svbcexgr01.wfi.com(172.16.16.68) by mail2.wfi.com via csmap id 11648; Tue, 04 Mar 2003 14:33:22 -0800 (PST) Received: by svbcexgr01.wfi.com with Internet Mail Service (5.5.2653.19) id ; Tue, 4 Mar 2003 14:42:03 -0800 Message-ID: <2DB8F063662FD511A0C7006008F6D05B031A7CCE@SVBCEXMB01.wfi.com> From: Gary Thandi To: 'Daniel Liston' , "Cencigh, Maurizio {PGID~Kaiseraugst}" Cc: majordomo-users Subject: Re: Error Msg sending newsletter Date: Tue, 4 Mar 2003 14:42:07 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Archive-Number: 200303/12 X-Sequence-Number: 2883 You can specify that majordomo is a trusted-user in one of two ways. 1. Add the user name to your trusted-users file, make sure sendmail.cf has the following line uncommented. Ft/etc/mail/trusted-users 2. Add the entry "Tmajordomo" to sendmail.cf (Don't forget to stop and start sendmail) Troot Tmajordomo - Permissions (if you are using smmsp) Permissions Owner Group File/Directory -rwxr-sr-x root smmsp /usr/lib/sendmail drwxr-x--- root staff /var/spool/mqueue drwxrwx--- smmsp smmsp /var/spool/clientmqueue -rw-r--r-- root other /etc/mail/sendmail.cf - Other mail file permissions chmod go-w / /etc /etc/mail /usr /var /var/spool /var/spool/mqueue chown root / /etc /etc/mail /usr /var /var/spool /var/spool/mqueue - This command is kind of cool to report back permissions stuff /usr/lib/sendmail -bi -d44.4 Keep in mind that my config is 8.12.6. Gary. -----Original Message----- From: Daniel Liston [mailto:dliston@sonny.org] Sent: Tuesday, March 04, 2003 11:00 AM To: Cencigh, Maurizio {PGID~Kaiseraugst} Cc: majordomo-users Subject: Re: Error Msg sending newsletter I am not certain if this is the same for solaris or linux using the same version of sendmail 8.11.6, but the "trusted" majord user has to be added to the submit.cf file as well as the sendmail.cf. Dan Liston Cencigh, Maurizio {PGID~Kaiseraugst} wrote: > I don't think the problem concers uid and gid. I installed a fresh > version of majordomo on the new machine. Compiling the wrapper and > everything on the new machine with the uid and gid I gave. The ONLY > thing I copied from the old machine is the content of the lists > directory and then chown the listname, listname.conf, listname.poster. > > I tried the sendmail commands. When I run as root: > sendmail -bv listname, gives as output the entry after listname of the > aliases file. > sendmail -bv listname-outgoing, tells me user unknown. I think this may > be the problem. > > as the majord user I get: > sendmail -bv listname, tells about misleading output for non-privileged > user and says can not chdir (/var/spool/mqueue): Permission denied. > Program mode requires special privilege, eg. root or TrustedUser. I > tried to change the TrustedUser in sendmail.cf, and set it to majord and > restarted sendmail. Same error msg. as usual. > sendmail -bv listname-outgoing, gives the same. > > Can you tell me more about? I think or the user unknown is the problem > or non-privilege thing on /var/spool/mqueue. What permissions are needed > on /var/spool/mqueue. Or which TrustedUser should I configure in > sendmail.cf? > > Thanks a lot. > I feel getting near to the solution... > > > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Monday, March 03, 2003 8:51 PM > To: Cencigh, Maurizio {PGID~Kaiseraugst} > Cc: majordomo-users > Subject: Re: Error Msg sending newsletter > > > Please do these comparisons to validate uid:gid are the same between the > old and the new systems. On each machine, run as root; > > grep majordom /etc/passwd > > majordom:*:54:1:Majordomo List Mgr:/var/majordomo:/usr/local/bin/bash > majordom:*:1007:1007:Majordomo Server:/home/majordom:/bin/false > majordomo:x:91:91:Majordomo List Manager:/usr/lib/majordomo:/bin/bash > > As you can see, I have three machines running majordomo, but none of > them have the same uid or gid. For that matter, none of them even have > the same home directory. There is no way I could just copy these > instances between machines, I would have to recompile the wrapper for > each system, not to mention chown'ing files and directories. > > Your majordomo address/alias is working, or you would not get replies to > the lists and who commands. Have you tried using sendmail to verify > your list or list-outgoing addresses? > > sendmail -bv listname > sendmail -bv listname-outgoing > > Try these commands as both the root and the majordomo user. > > Dan Liston > > Cencigh, Maurizio {PGID~Kaiseraugst} wrote: > >>Hi once again, >> >>I tried with the faq article you send me. I changed sendmail.cf to >>DontBlameSendmail=safe. The group is the same since installation. I >>still get the same error msg. any more hints? I'm desperate seeking >>the solution..... >> >>Thanks. >> >> >>-----Original Message----- >>From: Daniel Liston [mailto:dliston@sonny.org] >>Sent: Wednesday, February 26, 2003 7:34 PM >>To: Cencigh, Maurizio {PGID~Kaiseraugst}; majordomo-users >>Subject: Re: Error Msg sending newsletter >> >> >> >>I kind of have an aversion to using daemon for the majordomo group. >>Please notice sendmail's FAQ on the majordomo subject: >> >>http://www.sendmail.org/faq/section3.html#3.32 >> >>If you did change the group without recompiling majordomo's wrapper >>you could get error messages in the log, but another possibility is >>the version of sendmail you upgraded to (as a side effect of the newer > > >>OS) might utilize a submit.cf similar to the sendmail.cf. If this is >>the case, make sure you have a "trust" statement for the majordomo >>user in that file too. >> >>Dan Liston >> >> >> >>>Hi again, >>> >>>the old server was: Solaris 2.6 with Sendmail 8.8.8 running on E450 >>>the new server is: Solaris 8 with Sendmail 8.11.6 running on V480 >>>Majordomo 1.94.5 >>> >>>I only copied the lists. The lists directory was created by the >>>majordomo installation. Then changed owner on the lists and >>>list.config files. Uid still the same, but other group. Now I'm using >>>group daemon before majord had an own group. In the Log file this >>>error isn't logged. I don't understand the linking and the smrsh >>>thing. And the group writable issue shouldn't be bothering as group >>>has no write permission the hole path down to majordomo. >>> >>>Thank for help. >>>Maurizio >>> >>> >>> >>>-----Original Message----- >>>From: Daniel Liston [mailto:dliston@sonny.org] >>>Sent: Friday, February 21, 2003 7:08 PM >>>To: majordomo-users@greatcircle.com >>>Subject: Re: Error Msg sending newsletter >>> >>> >>>You also need to check down to /usr/local/majordomo/lists actually. >>>NO, Definately do NOT change any permissions to group writable if you >>>want to keep sendmail happy. >>> >>>You have not mentioned your hardware, operating system, or versions of >> >> >>>sendmail or majordomo. If you just "copied" majordomo from one server >> >> >>>to the other, did you make SURE that you used the same UID and GID on >>>both machines? I mean the number, not the name. Wrapper is dependent >>>on this. If sendmail is new on one machine than the other, you may >>>also need to add a link to wrapper in the proper smrsh directory. >>>Perhaps a cut and paste of the exact error message from the log file >>>would be helpful here too. >>> >>>Dan Liston >>> >>>Cencigh, Maurizio {PGID~Kaiseraugst} wrote: >>> >>> >>> >>>>I checked permissions on my subscriber files, but still get the >>>>error. >>> >>> >>>>The directory structure down to majordomo is not group writable. I >>>>installed with daemon as group, but majord is not member of it. any >>>>other hints? must the dir structure be group writable? I'm SysAdmin >>>>but I don't know Sendmail and its behaviors...... any help is >>>>apreciated a lot. >>>> >>>>Maurizio >>>> >>>>-----Original Message----- >>>>From: Daniel Liston [mailto:dliston@sonny.org] >>>>Sent: Friday, February 21, 2003 4:50 PM >>>>To: Cencigh, Maurizio {PGID~Kaiseraugst}; >>>>majordomo-users@greatcircle.com >>>>Subject: Re: Error Msg sending newsletter >>>> >>>> >>>>Check the ownership/permission on your new majordomo installation. If >>>>you are running sendmail on the new server, it might now allow group >>>>or world "writable" permission down the path to majordomo's >>> > directory. > >>> >>>>For example, /, /usr, /usr/local, /usr/local/majordomo. Sendmail will >>>>also complain about group or world writable :include: files in your >>>>lists directory. These are your list membership or zubscriber files. >>>> >>>>Dan Liston >>>> >>>>Cencigh, Maurizio {PGID~Kaiseraugst} wrote: >>>> >>>> >>>> >>>> >>>>>hi all, >>>>> >>>>>I'm migrating a Server, so I installed a new Majordomo on the new >>>>>server. I copied the old lists and aliases. When I send a mail to >>>>>majordomo like who listname or lists, I get back an answer. When I >>>> >>try >> >> >>>>>to send a newsletter to a list I get the error message below. >>>>>Anybody an idea? Please help. My majordomo isn't working right now. >>>>> >>>>>Unable to expand a distribution list to deliver the message to its >>>>>members. Try again or contact your system administrator. >>>>> >>>>>Thanks in advance. >>>>>Maurizio >>>> >>>> >>>> >> > > From majordomo-users-owner@greatcircle.com Tue Mar 4 16:39:45 2003 Received: from grouse.mail.pas.earthlink.net (grouse.mail.pas.earthlink.net [207.217.120.116]) by mycroft.greatcircle.com (Postfix) with ESMTP id C5E2E196286; Tue, 4 Mar 2003 16:39:43 -0800 (PST) Received: from h-66-167-135-80.phndaz91.covad.net ([66.167.135.80] helo=Vaio.earthlink.net) by grouse.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18qMwX-0000OR-00; Tue, 04 Mar 2003 16:39:33 -0800 Message-Id: <5.2.0.9.2.20030304173603.028ba330@pop.earthlink.net> X-Sender: bobbish@pop.earthlink.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 04 Mar 2003 17:39:33 -0700 To: list-managers@greatcircle.com, majordomo-users@greatcircle.com From: Bob Bish Subject: Mail loops Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200303/13 X-Sequence-Number: 2884 Is anyone else getting a huge number of bounce messages all saying "too many hops", "mail loop detected", etc? I received over 500 of them in a 50-minute period! They started suddenly about 2 hours ago (maybe around 5:30pm EST). I need to know if this is a generalized problem (perhaps a hacking or virus attack on the Internet as a whole) or if there's a problem on our server's end. ...Bob From majordomo-users-owner@greatcircle.com Tue Mar 4 17:04:08 2003 Received: from mail.realtimeweb.com (wsip68-98-209-51.ph.ph.cox.net [68.98.209.51]) by mycroft.greatcircle.com (Postfix) with ESMTP id DAD5E195A3F for ; Tue, 4 Mar 2003 17:04:06 -0800 (PST) Received: from kramer (cpe-66-1-198-180.az.sprintbbd.net [66.1.198.180]) by mail.realtimeweb.com (8.11.6/linuxconf) with ESMTP id h25145h08940 for ; Tue, 4 Mar 2003 18:04:05 -0700 From: "Mike Olbinski" To: Subject: Problem Date: Tue, 4 Mar 2003 18:03:48 -0700 Message-ID: <003c01c2e2b3$153651e0$b4c60142@kramer> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Archive-Number: 200303/14 X-Sequence-Number: 2885 Wondering if someone can help me. Earlier today, around 11:15am, this email was basically shown in the error log with this in the Subject: Subject: BOUNCE baseball@stoogesffl.com: Admin request of type /^\s*get\s+\S+\s*$/i at line 2 The actual message was (without the quotes): "i know, people should be sending lists...like Rob did last night...I don't get it." Suddenly, since then, the email list has basically stopped working for no apparent reason. Everything is being held in the spool/mqueue directory. Any ideas? Mike From majordomo-users-owner@greatcircle.com Tue Mar 4 17:09:32 2003 Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by mycroft.greatcircle.com (Postfix) with ESMTP id 557CB19643F; Tue, 4 Mar 2003 17:09:25 -0800 (PST) Received: from h-66-167-135-80.phndaz91.covad.net ([66.167.135.80] helo=Vaio.earthlink.net) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18qNPQ-0004sa-00; Tue, 04 Mar 2003 17:09:24 -0800 Message-Id: <5.2.0.9.2.20030304175358.00bb4390@pop.earthlink.net> X-Sender: bobbish@pop.earthlink.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 04 Mar 2003 18:09:23 -0700 To: list-managers@greatcircle.com, majordomo-users@greatcircle.com From: Bob Bish Subject: Mail loops - Found the problem Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200303/15 X-Sequence-Number: 2886 It affected only one of my lists and was tracked down to one particular e-mail address on that list. It was at "princelaw.com" in case any other addresses there are doing the same thing and anyone here has one on a mailing list. The firewall and SMTP server at Prince Law (princelaw.com) are in a retransmission loop. ...Bob From majordomo-users-owner@greatcircle.com Tue Mar 4 17:34:17 2003 Received: from pheriche.sun.com (pheriche.sun.com [192.18.98.34]) by mycroft.greatcircle.com (Postfix) with ESMTP id 70DB6196521 for ; Tue, 4 Mar 2003 17:34:16 -0800 (PST) Received: from engmail1mpk.Eng.Sun.COM ([129.146.1.45]) by pheriche.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA13670; Tue, 4 Mar 2003 18:34:13 -0700 (MST) Received: from phys-ha5mpk-2 (mailsrv@phys-ha5mpk-2.Eng.Sun.COM [129.146.19.84]) by engmail1mpk.Eng.Sun.COM (8.12.8+Sun/8.12.8/ENSMAIL,v2.2) with ESMTP id h251YDvx026077; Tue, 4 Mar 2003 17:34:13 -0800 (PST) Received: from sunray2 (sunray2.Eng.Sun.COM [129.146.58.95]) by ha5mpk-mail1.eng.sun.com (iPlanet Messaging Server 5.2 HotFix 1.03 (built Oct 1 2002)) with SMTP id <0HB900EOO5OWWC@ha5mpk-mail1.eng.sun.com>; Tue, 04 Mar 2003 17:34:09 -0800 (PST) Date: Tue, 04 Mar 2003 17:34:00 -0800 (PST) From: Mike Oliver Subject: Re: Messages being truncated... To: beto@yall.org Cc: majordomo-users@greatcircle.com Reply-To: Mike Oliver Message-id: <0HB900EOP5OXWC@ha5mpk-mail1.eng.sun.com> MIME-version: 1.0 X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.5.2_04 SunOS 5.9 sun4u sparc Content-type: TEXT/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-MD5: YgV4e34ilACNY8CDlLl/8w== X-Archive-Number: 200303/16 X-Sequence-Number: 2887 Robert Dana wrote: > I'm having a problem where a few user messages to mailing lists I host are > being truncated on their trip through resend. These tend to be HTML > messages from webmail (Hotmail and Yahoo) users, but I don't have enough > samples yet to identify any patterns in the messages - getting the original > messages has turned out to be hard because the users are barely e-mail > literate. One stab in the dark: 'resend' spools the incoming message into a temporary file and then replays it from that file to the list. If you run out out of space in the filesystem where the temporary file is placed then I can imagine that that might cause data loss. How much room do you have in the filesystem where the temporary files go? (The location is defined by the TMPDIR variable in majordomo.cf.) Mike. -- mike.oliver@sun.com From majordomo-users-owner@greatcircle.com Tue Mar 4 23:26:55 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 29C49195F96 for ; Tue, 4 Mar 2003 23:26:54 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h257TSEt010977 for ; Wed, 5 Mar 2003 01:29:28 -0600 Message-ID: <3E65A6DA.6090805@sonny.org> Date: Wed, 05 Mar 2003 01:27:22 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Re: Messages being truncated... References: <054d01c2e29b$523553b0$0501a8c0@palain> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/17 X-Sequence-Number: 2888 It sounds like you have been able to prove this only happens when email is processed by resend. I am curious. Do or does the list or lists in question have fronters or footers enabled? Dan Liston From majordomo-users-owner@greatcircle.com Tue Mar 4 23:43:30 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id E6D4D195A72 for ; Tue, 4 Mar 2003 23:43:27 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h257k2Et011195; Wed, 5 Mar 2003 01:46:02 -0600 Message-ID: <3E65AABB.9010606@sonny.org> Date: Wed, 05 Mar 2003 01:43:55 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Olbinski Cc: majordomo-users@greatcircle.com Subject: Re: Problem References: <003c01c2e2b3$153651e0$b4c60142@kramer> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/18 X-Sequence-Number: 2889 This means you have administrivia enabled on your list an one of the first 10 lines of the message matched the regular expression below in the admin_body section of the majordomo.cf file. The expression states a line with 0 or more spaces or tabs (whitespace) followed immediately by the letters G then E then T with at least one whitespace and one or more non-whitespace characters and zero or more whitespaces until the end of the line and match all of this case insensitively. "get it." was the line that matched this expression. The solution? Turn off administrivia in your list, or remove the "get" filters from the admin_body section of majordomo.cf. These filters can not just be commented out, they either have to be deleted, or moved outside the boundaries of the < Wondering if someone can help me. Earlier today, around 11:15am, this > email was basically shown in the error log with this in the Subject: > > Subject: BOUNCE baseball@stoogesffl.com: Admin request of type > /^\s*get\s+\S+\s*$/i at line 2 > > The actual message was (without the quotes): > > "i know, people should be sending lists...like Rob did last night...I > don't > get it." > > Suddenly, since then, the email list has basically stopped working for > no apparent reason. Everything is being held in the spool/mqueue > directory. > > Any ideas? > > Mike > From majordomo-users-owner@greatcircle.com Tue Mar 4 23:50:38 2003 Received: from motgate3.mot.com (motgate3.mot.com [144.189.100.103]) by mycroft.greatcircle.com (Postfix) with ESMTP id CE5101959DB for ; Tue, 4 Mar 2003 23:50:34 -0800 (PST) Received: from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate3.mot.com (Motorola/Motgate3) with ESMTP id h257o6Yk003283 for ; Wed, 5 Mar 2003 00:50:06 -0700 (MST) Received: [from zch07exb01.corp.mot.com (zch07exb01.corp.mot.com [200.3.1.150]) by mothost.mot.com (MOT-pobox 2.0) with ESMTP id AAA09739 for ; Wed, 5 Mar 2003 00:50:32 -0700 (MST)] Received: by zch07exb01.corp.mot.com with Internet Mail Service (5.5.2656.59) id ; Wed, 5 Mar 2003 15:50:29 +0800 Message-ID: <1B2D9E22CDF7D611BD2200805FA7B779181C69@hou204.cig.mcel.mot.com> From: Chen Jervy-qch1408 To: "'Majordomo-Users@GreatCircle.COM'" Subject: majordomo problem after upgrading the sendmail to 8.12.8 Date: Wed, 5 Mar 2003 15:50:29 +0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2E2EB.E4148B3E" X-Archive-Number: 200303/19 X-Sequence-Number: 2890 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_01C2E2EB.E4148B3E Content-Type: text/plain; charset="gb2312" Hello, guys, Could anybody help me to resolve the following problem? Any idea will be appreciated! I am majordomo admin and have a majordomo server (Sun Ultra 2), majordomo 1.94.4 and sendmail 8.8.5 installed on it, it works fine for 2 years already after I setup it. The following is my setting before in /etc/mail/sendmail.cf. OA/usr/majordomo/majordomo-1.94.4/majordomo_aliases Now, for the security reason, I have to upgrade sendmail from 8.8.5 to 8.12.8, I finished it already and added the above line in sendmail.cf also but majordomo could not work as normal. The following is error message when I try to send mail to majordomo list but it can send email to normal user successfully. Mar 5 11:55:44 zchps01 sendmail[764]: h253tip9000764: SYSERR(root): dbm map "Alias0": unsafe map file /usr/majordomo/majordomo-1.94.4/majordomo_aliases: No such file or directory Here is the output when I try to send out majordomo list. # /usr/lib/sendmail -v -bi WARNING: World writable directory /var/spool/mqueue /etc/mail/aliases: 9 aliases, longest 52 bytes, 294 bytes total WARNING: Group writable directory /usr/majordomo WARNING: Group writable directory /usr/majordomo/majordomo-1.94.4 newaliases: cannot open /usr/majordomo/majordomo-1.94.4/majordomo_aliases: Executable files not allowed # /usr/lib/sendmail -v test . test... Connecting to [127.0.0.1] via relay... 220 majordomo.motor.com ESMTP Sendmail 8.12.8/8.12.8; Wed, 5 Mar 2003 14:46:36 +0800 (CST) >>> EHLO majordomo.motor.com 250-majordomo.motor.com Hello localhost [127.0.0.1], pleased to meet you 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-EXPN 250-VERB 250-8BITMIME 250-SIZE 250-DSN 250-ETRN 250-DELIVERBY 250 HELP >>> MAIL From:< root@majordomo.motor.com> 250 2.1.0 < root@majordomo.motor.com>... Sender ok >>> RCPT To:< test@majordomo.motor.com> >>> DATA 250 2.1.5 < test@majordomo.motor.com>... Recipient ok (will queue) 354 Enter mail, end with "." on a line by itself >>> . 250 2.0.0 h256ka8v002492 Message accepted for delivery test... Sent (h256ka8v002492 Message accepted for delivery) Closing connection to [127.0.0.1] >>> QUIT 221 2.0.0 majordomo.motor.com closing connection # mailq /var/spool/mqueue (1 request) -----Q-ID----- --Size-- -----Q-Time----- ------------Sender/Recipient----------- h256ka8v002492 0 Wed Mar 5 14:46 < root@majordomo.motor.com> (dbm map "Alias1": unsafe map file /usr/majordomo/majordomo-1) < test@majordomo.motor.com> Total requests: 1 Kind Regards Jervy Chen * Fear can hold you prisoner * * Hope can set you free * ------_=_NextPart_001_01C2E2EB.E4148B3E Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable
Hello, guys,
 
Could anybody help me to resolve the following problem?= Any idea will be appreciated!
 
am majordomo ad= min and=20 have a majordomo server (Sun Ultra 2), majordomo 1.94.4 and sendmail= =20 8.8.5 installed on it, it works fine for 2 years already after I setup it. The following is my setting bef= ore in=20 /etc/mail/sendmail.cf.
 
OA/usr/majordomo/majordomo-1.94.4/majordomo_aliases
 
Now, for the security reason, I ha= ve to=20 upgrade sendmail from 8.8.5 to 8.12.8, I finished it already and added the = above=20 line in sendmail.cf also but majordomo could not work as normal. The follow= ing=20 is error message when I try to send mail to majordomo list but it can send email to normal user=20 successfully.
 
Mar  5 11:55:44 zchps01 sendmail[764]= :=20 h253tip9000764: SYSERR(root): dbm map "Alias0": unsafe map=20 file
/usr/majordomo/majordomo-1.94.4/majordomo_aliases: No such file or= =20 directory
 
Here is the output when I try to send ou= t=20 majordomo list.
 
# /usr/lib/sendmail = -v=20 -bi
WARNING: World writable directory /var/spool/mqueue
/etc/mail/ali= ases:=20 9 aliases, longest 52 bytes, 294 bytes total
WARNING: Group writable=20 directory /usr/majordomo
WARNING: Group writable directory=20 /usr/majordomo/majordomo-1.94.4
newaliases: cannot= open=20 /usr/majordomo/majordomo-1.94.4/majordomo_aliases: Executable files not=20 allowed
 
# /usr/lib/sendmail = -v=20 test
.
test... Connecting to [127.0.0.1] via relay...
220=20 majordomo.motor.com ESMTP Sendmail 8.12.8/8.12.8; Wed, 5 Mar 2003 14:46:36 = +0800=20 (CST)
>>> EHLO majordomo.motor.com
250-majordomo.motor.com H= ello=20 localhost [127.0.0.1], pleased to meet=20 you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-EXPN
250-VERB250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-DELIVERBY
250=20 HELP
>>> MAIL From:<
root@majordomo.motor.com>= ;
250=20 2.1.0 <
root@majordomo.motor.com>= ;... Sender=20 ok
>>> RCPT To:<
test@majordomo.motor.com>
>>> DATA
250 2.1.5 <
test@majordomo.motor.com>...=20 Recipient ok (will queue)
354=20 Enter mail, end with "." on a line by itself
>>> .
250 2.0.0= =20 h256ka8v002492 Message accepted for delivery
test... Sent (h256ka8v00249= 2=20 Message accepted for delivery)
Closing connection to=20 [127.0.0.1]
>>> QUIT
221 2.0.0 majordomo.motor.com closing= =20 connection
 
#=20 mailq
           =     =20 /var/spool/mqueue (1 request)
-----Q-ID----- --Size-- -----Q-Time-----= =20 ------------Sender/Recipient-----------
h256ka8v002492   =     =20 0 Wed Mar  5 14:46 <
root@majordomo.motor.com>
         &nbs= p;      =20 (dbm map "Alias1": unsafe map file=20 /usr/majordomo/majordomo-1)
       &n= bsp;            = ;            &n= bsp;       =20 <
test@majordomo.motor.com>
         &nbs= p;     =20 Total requests: 1
 
 
 

Kind Regards
Jervy Chen
*  Fear can hold you prisoner  *
*  = Hope=20 can set you free          *=20
------_=_NextPart_001_01C2E2EB.E4148B3E-- From majordomo-users-owner@greatcircle.com Wed Mar 5 00:51:03 2003 Received: from rbadb2.rbacpxclu.bas.roche.com (unknown [196.3.50.241]) by mycroft.greatcircle.com (Postfix) with ESMTP id AD8C5195ABA for ; Wed, 5 Mar 2003 00:50:59 -0800 (PST) Received: from CONVERSION-DAEMON.Roche.COM by Roche.COM (PMDF V6.0-025 #47170) id <01KT5T6Q0MSG98OGG4@Roche.COM> for majordomo-users@greatcircle.com; Wed, 05 Mar 2003 09:49:08 +0100 Received: from rbamsemcn1.emea.roche.com (rbamsemcn1.emea.roche.com [145.245.211.139]) by Roche.COM (PMDF V6.0-025 #47170) with ESMTP id <01KT5T5OAS7C99PXU9@Roche.COM> for majordomo-users@greatcircle.com; Wed, 05 Mar 2003 09:47:59 +0100 Received: from rkamsemcn1.emea.roche.com ([145.245.247.234]) by rbamsemcn1.emea.roche.com with Microsoft SMTPSVC(5.0.2195.2966); Wed, 05 Mar 2003 09:47:56 +0100 Received: from rkamsem1.emea.roche.com ([145.245.247.233]) by rkamsemcn1.emea.roche.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 05 Mar 2003 09:44:11 +0100 Date: Wed, 05 Mar 2003 09:44:07 +0100 From: "Cencigh, Maurizio {PGID~Kaiseraugst}" Subject: Re: Error Msg sending newsletter To: Gary Thandi , Daniel Liston Cc: majordomo-users Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6334.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable Thread-Topic: Error Msg sending newsletter Thread-Index: AcLin6pcIFIb6P+fQmqRp2gClL7pSAAUq0qw content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: X-OriginalArrivalTime: 05 Mar 2003 08:44:11.0369 (UTC) FILETIME=[64AB8D90:01C2E2F3] X-Archive-Number: 200303/20 X-Sequence-Number: 2891 I tried everything !! The permissions were as they should be. I entered majord in the trusted-users file, also in sendmail.cf submit.cf and main.cf below TrustedUsers. The command to check permissions worked fine and gave only "ok" back. As I get back mails from majord which I send using info commands (lists, who) I don't think it is a env problem.=20 But what the hell can it be then? Here the complete error-msg: Your message did not reach some or all of the intended recipients. Subject: test newsletter Sent: 05.03.2003 09:36 The following recipient(s) could not be reached: listname-list@host.domain.com on 05.03.2003 09:34 Unable to expand a distribution list to deliver the message to its members. Try again or contact your system administrator. < host.domain.com #5.2.4> Any help is apreciated a lot. Thanks to all who replied and will reply helping me out. Maurizio -----Original Message----- From: Gary Thandi [mailto:Gary.Thandi@360.net]=20 Sent: Tuesday, March 04, 2003 11:42 PM To: 'Daniel Liston'; Cencigh, Maurizio {PGID~Kaiseraugst} Cc: majordomo-users Subject: RE: Error Msg sending newsletter You can specify that majordomo is a trusted-user in one of two ways. 1. Add the user name to your trusted-users file, make sure sendmail.cf has the following line uncommented. Ft/etc/mail/trusted-users 2. Add the entry "Tmajordomo" to sendmail.cf (Don't forget to stop and start sendmail) Troot Tmajordomo - Permissions (if you are using smmsp) Permissions Owner Group File/Directory -rwxr-sr-x root smmsp /usr/lib/sendmail drwxr-x--- root staff /var/spool/mqueue drwxrwx--- smmsp smmsp /var/spool/clientmqueue -rw-r--r-- root other /etc/mail/sendmail.cf - Other mail file permissions chmod go-w / /etc /etc/mail /usr /var /var/spool /var/spool/mqueue chown root / /etc /etc/mail /usr /var /var/spool /var/spool/mqueue - This command is kind of cool to report back permissions stuff /usr/lib/sendmail -bi -d44.4 Keep in mind that my config is 8.12.6. Gary. -----Original Message----- From: Daniel Liston [mailto:dliston@sonny.org] Sent: Tuesday, March 04, 2003 11:00 AM To: Cencigh, Maurizio {PGID~Kaiseraugst} Cc: majordomo-users Subject: Re: Error Msg sending newsletter I am not certain if this is the same for solaris or linux using the same version of sendmail 8.11.6, but the "trusted" majord user has to be added to the submit.cf file as well as the sendmail.cf. Dan Liston Cencigh, Maurizio {PGID~Kaiseraugst} wrote: > I don't think the problem concers uid and gid. I installed a fresh=20 > version of majordomo on the new machine. Compiling the wrapper and=20 > everything on the new machine with the uid and gid I gave. The ONLY=20 > thing I copied from the old machine is the content of the lists=20 > directory and then chown the listname, listname.conf, listname.poster. >=20 > I tried the sendmail commands. When I run as root: > sendmail -bv listname, gives as output the entry after listname of the > aliases file. sendmail -bv listname-outgoing, tells me user unknown.=20 > I think this may be the problem. >=20 > as the majord user I get: > sendmail -bv listname, tells about misleading output for=20 > non-privileged user and says can not chdir (/var/spool/mqueue):=20 > Permission denied. Program mode requires special privilege, eg. root=20 > or TrustedUser. I tried to change the TrustedUser in sendmail.cf, and=20 > set it to majord and restarted sendmail. Same error msg. as usual.=20 > sendmail -bv listname-outgoing, gives the same. >=20 > Can you tell me more about? I think or the user unknown is the problem > or non-privilege thing on /var/spool/mqueue. What permissions are=20 > needed on /var/spool/mqueue. Or which TrustedUser should I configure=20 > in sendmail.cf? >=20 > Thanks a lot. > I feel getting near to the solution... >=20 >=20 > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Monday, March 03, 2003 8:51 PM > To: Cencigh, Maurizio {PGID~Kaiseraugst} > Cc: majordomo-users > Subject: Re: Error Msg sending newsletter >=20 >=20 > Please do these comparisons to validate uid:gid are the same between=20 > the old and the new systems. On each machine, run as root; >=20 > grep majordom /etc/passwd >=20 > majordom:*:54:1:Majordomo List Mgr:/var/majordomo:/usr/local/bin/bash > majordom:*:1007:1007:Majordomo Server:/home/majordom:/bin/false=20 > majordomo:x:91:91:Majordomo List Manager:/usr/lib/majordomo:/bin/bash >=20 > As you can see, I have three machines running majordomo, but none of=20 > them have the same uid or gid. For that matter, none of them even=20 > have the same home directory. There is no way I could just copy these > instances between machines, I would have to recompile the wrapper for=20 > each system, not to mention chown'ing files and directories. >=20 > Your majordomo address/alias is working, or you would not get replies=20 > to the lists and who commands. Have you tried using sendmail to=20 > verify your list or list-outgoing addresses? >=20 > sendmail -bv listname > sendmail -bv listname-outgoing >=20 > Try these commands as both the root and the majordomo user. >=20 > Dan Liston >=20 > Cencigh, Maurizio {PGID~Kaiseraugst} wrote: >=20 >>Hi once again, >> >>I tried with the faq article you send me. I changed sendmail.cf to >>DontBlameSendmail=3Dsafe. The group is the same since installation. I=20 >>still get the same error msg. any more hints? I'm desperate seeking=20 >>the solution..... >> >>Thanks. >> >> >>-----Original Message----- >>From: Daniel Liston [mailto:dliston@sonny.org] >>Sent: Wednesday, February 26, 2003 7:34 PM >>To: Cencigh, Maurizio {PGID~Kaiseraugst}; majordomo-users >>Subject: Re: Error Msg sending newsletter >> >> >> >>I kind of have an aversion to using daemon for the majordomo group. >>Please notice sendmail's FAQ on the majordomo subject: >> >>http://www.sendmail.org/faq/section3.html#3.32 >> >>If you did change the group without recompiling majordomo's wrapper >>you could get error messages in the log, but another possibility is=20 >>the version of sendmail you upgraded to (as a side effect of the newer >=20 >=20 >>OS) might utilize a submit.cf similar to the sendmail.cf. If this is >>the case, make sure you have a "trust" statement for the majordomo=20 >>user in that file too. >> >>Dan Liston >> >> >> >>>Hi again, >>> >>>the old server was: Solaris 2.6 with Sendmail 8.8.8 running on E450 >>>the new server is: Solaris 8 with Sendmail 8.11.6 running on V480 >>>Majordomo 1.94.5 >>> >>>I only copied the lists. The lists directory was created by the=20 >>>majordomo installation. Then changed owner on the lists and=20 >>>list.config files. Uid still the same, but other group. Now I'm using >>>group daemon before majord had an own group. In the Log file this=20 >>>error isn't logged. I don't understand the linking and the smrsh=20 >>>thing. And the group writable issue shouldn't be bothering as group=20 >>>has no write permission the hole path down to majordomo. >>> >>>Thank for help. >>>Maurizio >>> >>> >>> >>>-----Original Message----- >>>From: Daniel Liston [mailto:dliston@sonny.org] >>>Sent: Friday, February 21, 2003 7:08 PM >>>To: majordomo-users@greatcircle.com >>>Subject: Re: Error Msg sending newsletter >>> >>> >>>You also need to check down to /usr/local/majordomo/lists actually.=20 >>>NO, Definately do NOT change any permissions to group writable if you >>>want to keep sendmail happy. >>> >>>You have not mentioned your hardware, operating system, or versions=20 >>>of >> >> >>>sendmail or majordomo. If you just "copied" majordomo from one=20 >>>server >> >> >>>to the other, did you make SURE that you used the same UID and GID on >>>both machines? I mean the number, not the name. Wrapper is dependent >>>on this. If sendmail is new on one machine than the other, you may=20 >>>also need to add a link to wrapper in the proper smrsh directory. >>>Perhaps a cut and paste of the exact error message from the log file=20 >>>would be helpful here too. >>> >>>Dan Liston >>> >>>Cencigh, Maurizio {PGID~Kaiseraugst} wrote: >>> >>> >>> >>>>I checked permissions on my subscriber files, but still get the >>>>error. >>> >>> >>>>The directory structure down to majordomo is not group writable. I=20 >>>>installed with daemon as group, but majord is not member of it. any=20 >>>>other hints? must the dir structure be group writable? I'm SysAdmin=20 >>>>but I don't know Sendmail and its behaviors...... any help is=20 >>>>apreciated a lot. >>>> >>>>Maurizio >>>> >>>>-----Original Message----- >>>>From: Daniel Liston [mailto:dliston@sonny.org] >>>>Sent: Friday, February 21, 2003 4:50 PM >>>>To: Cencigh, Maurizio {PGID~Kaiseraugst}; >>>>majordomo-users@greatcircle.com >>>>Subject: Re: Error Msg sending newsletter >>>> >>>> >>>>Check the ownership/permission on your new majordomo installation.=20 >>>>If you are running sendmail on the new server, it might now allow=20 >>>>group or world "writable" permission down the path to majordomo's >>> > directory. >=20 >>> >>>>For example, /, /usr, /usr/local, /usr/local/majordomo. Sendmail=20 >>>>will also complain about group or world writable :include: files in=20 >>>>your lists directory. These are your list membership or zubscriber=20 >>>>files. >>>> >>>>Dan Liston >>>> >>>>Cencigh, Maurizio {PGID~Kaiseraugst} wrote: >>>> >>>> >>>> >>>> >>>>>hi all, >>>>> >>>>>I'm migrating a Server, so I installed a new Majordomo on the new >>>>>server. I copied the old lists and aliases. When I send a mail to=20 >>>>>majordomo like who listname or lists, I get back an answer. When I >>>> >>try >> >> >>>>>to send a newsletter to a list I get the error message below. >>>>>Anybody an idea? Please help. My majordomo isn't working right now. >>>>> >>>>>Unable to expand a distribution list to deliver the message to its >>>>>members. Try again or contact your system administrator. >>>>> >>>>>Thanks in advance. >>>>>Maurizio >>>> >>>> >>>> >> >=20 >=20 From majordomo-users-owner@greatcircle.com Wed Mar 5 10:33:14 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 31800195AEE for ; Wed, 5 Mar 2003 10:33:12 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h25Ia0Et014475; Wed, 5 Mar 2003 12:36:00 -0600 Message-ID: <3E6642E7.3090709@sonny.org> Date: Wed, 05 Mar 2003 12:33:11 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chen Jervy-qch1408 Cc: "'Majordomo-Users@GreatCircle.COM'" Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 References: <1B2D9E22CDF7D611BD2200805FA7B779181C69@hou204.cig.mcel.mot.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/21 X-Sequence-Number: 2892 Hi, Several points here, 1. Upgrade majordomo to 1.94.5 (or higher) 2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf 3a. Create a symbolic link from your majordomo_aliases to /etc/mail 4. Restart sendmail Dan Liston Chen Jervy-qch1408 wrote: > Hello, guys, > > Could anybody help me to resolve the following problem? Any idea will be > appreciated! > > I am majordomo admin and have a majordomo server (Sun Ultra 2), > majordomo 1.94.4 and sendmail 8.8.5 installed on it, it works fine for 2 > years already after I setup it. The following is my setting before in > /etc/mail/sendmail.cf. > > OA/usr/majordomo/majordomo-1.94.4/majordomo_aliases > > Now, for the security reason, I have to upgrade sendmail from 8.8.5 to > 8.12.8, I finished it already and added the above line in sendmail.cf > also but majordomo could not work as normal. The following is error > message when I try to send mail to majordomo list but it can send email > to normal user successfully. > > Mar 5 11:55:44 zchps01 sendmail[764]: h253tip9000764: SYSERR(root): dbm > map "Alias0": unsafe map file > /usr/majordomo/majordomo-1.94.4/majordomo_aliases: No such file or directory > > Here is the output when I try to send out majordomo list. > > # /usr/lib/sendmail -v -bi > WARNING: World writable directory /var/spool/mqueue > /etc/mail/aliases: 9 aliases, longest 52 bytes, 294 bytes total > WARNING: Group writable directory /usr/majordomo > WARNING: Group writable directory /usr/majordomo/majordomo-1.94.4 > newaliases: cannot open > /usr/majordomo/majordomo-1.94.4/majordomo_aliases: Executable files not > allowed > > # /usr/lib/sendmail -v test > . > test... Connecting to [127.0.0.1] via relay... > 220 majordomo.motor.com ESMTP Sendmail 8.12.8/8.12.8; Wed, 5 Mar 2003 > 14:46:36 +0800 (CST) > >>> EHLO majordomo.motor.com > 250-majordomo.motor.com Hello localhost [127.0.0.1], pleased to meet you > 250-ENHANCEDSTATUSCODES > 250-PIPELINING > 250-EXPN > 250-VERB > 250-8BITMIME > 250-SIZE > 250-DSN > 250-ETRN > 250-DELIVERBY > 250 HELP > >>> MAIL From:> > 250 2.1.0 >... Sender ok > >>> RCPT To:> > >>> DATA > 250 2.1.5 >... Recipient ok (will queue) > 354 Enter mail, end with "." on a line by itself > >>> . > 250 2.0.0 h256ka8v002492 Message accepted for delivery > test... Sent (h256ka8v002492 Message accepted for delivery) > Closing connection to [127.0.0.1] > >>> QUIT > 221 2.0.0 majordomo.motor.com closing connection > > # mailq > /var/spool/mqueue (1 request) > -----Q-ID----- --Size-- -----Q-Time----- > ------------Sender/Recipient----------- > h256ka8v002492 0 Wed Mar 5 14:46 > > (dbm map "Alias1": unsafe map file > /usr/majordomo/majordomo-1) > > > Total requests: 1 > > > > > Kind Regards > Jervy Chen > * Fear can hold you prisoner * > * Hope can set you free * From majordomo-users-owner@greatcircle.com Wed Mar 5 13:18:40 2003 Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by mycroft.greatcircle.com (Postfix) with ESMTP id D1EC8195F1F for ; Wed, 5 Mar 2003 13:18:39 -0800 (PST) Received: from fwd00.sul.t-online.de by mailout02.sul.t-online.com with smtp id 18qgHe-0007cC-0A; Wed, 05 Mar 2003 22:18:38 +0100 Received: from t-online.de (320087908768-0001@[217.238.61.121]) by fwd00.sul.t-online.com with esmtp id 18qgHY-0UtWgiC; Wed, 5 Mar 2003 22:18:32 +0100 Message-ID: <3E6669A9.1080306@t-online.de> Date: Wed, 05 Mar 2003 22:18:33 +0100 From: Manfred.Riese@t-online.de (Manfred Riese) User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; de-AT; rv:1.2.1) Gecko/20021130 X-Accept-Language: de, de-at, en-us, en MIME-Version: 1.0 To: MDOMO-Users Mailingliste Subject: how to cascade mailing lists? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Sender: 320087908768-0001@t-dialin.net X-Archive-Number: 200303/22 X-Sequence-Number: 2893 Hi all, we have about 30 different mailing lists at our homepage (own webserver), which all contain several discussionboards about, let's say cars. One about chrysler voyager, another about peugeot 307, etc. Every list is unmoderated, we had no need until now. But there is one discussionboard about the homepage itself, which should be distributed to every mailing list (every car). My first idea was just putting the name of the "car-lists" (list1, list2, list3) into the "homepagelist", but this doesn't work. I tried several ways, but none was sucessful, but that one in the aliases-file: homepagelist: :include:/path/to/lists-dir/list1, :include:/path/to/lists-dir/list2, etc. But i think, this isn't the luckiest way to do this, particularly when the number of lists is still growing. Does anyone know the ingeniously way ? best regards manfred From majordomo-users-owner@greatcircle.com Wed Mar 5 14:20:44 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id DEDAD195A19 for ; Wed, 5 Mar 2003 14:20:40 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h25MNXEt015448; Wed, 5 Mar 2003 16:23:33 -0600 Message-ID: <3E66783A.6010107@sonny.org> Date: Wed, 05 Mar 2003 16:20:42 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Manfred Riese Cc: MDOMO-Users Mailingliste Subject: Re: how to cascade mailing lists? References: <3E6669A9.1080306@t-online.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/23 X-Sequence-Number: 2894 As long as the people signing up for just a cars list are aware that your site is going to also send them email by virtue of joining any specific list... As a comparison, the majordomo-announce list does not automatically include me in announcements just because I belong to the majordomo-users list. What you are aiming to do is the first thing that would get me to rethink my membership in any of your lists. With that out of the way; Every list has a resend address and an include alias. Create a separate list, maybe homepage-announce, that is a moderated, post only list. If none of your other lists are archived or digested, just add the include alias for each list in the membership file of the homepage-annouce list. Do some experimenting with this idea before you put it into production. It may expose your :include: addresses to the recipients. If that is the case, use the resend address in the homepage-announce file instead, (strip -outgoing). The downside to this, could be a VERY heavy hit to your server all at once when it comes to delivering/resending all the messages. /etc/aliases homepage-announce: "|/path-to/majordomo/wrapper resend -l hompage-announce homepage-announce-outgoing,nobody" homepage-announce-outgoing: :include:/path-to/majordomo/lists/homepage-announce /path-to/majordomo/lists/homepage-announce carlist1-outgoing@mydomain.com carlist2-outgoing@mydomain.com carlist3-outgoing@mydomain.com . . . carlist30-outgoing@mydomain.com Dan Liston Manfred Riese wrote: > Hi all, > > we have about 30 different mailing lists at our homepage (own > webserver), which all contain several discussionboards about, let's say > cars. One about chrysler voyager, another about peugeot 307, etc. Every > list is unmoderated, we had no need until now. > > But there is one discussionboard about the homepage itself, which should > be distributed to every mailing list (every car). > My first idea was just putting the name of the "car-lists" (list1, > list2, list3) into the "homepagelist", but this doesn't work. > I tried several ways, but none was sucessful, but that one in the > aliases-file: > > homepagelist: :include:/path/to/lists-dir/list1, > :include:/path/to/lists-dir/list2, etc. > > But i think, this isn't the luckiest way to do this, particularly when > the number of lists is still growing. > Does anyone know the ingeniously way ? > > best regards > > manfred From majordomo-users-owner@greatcircle.com Wed Mar 5 22:08:51 2003 Received: from trip.mrball.net (66-214-180-43.la-cbi.charterpipeline.net [66.214.180.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 99671195AB6 for ; Wed, 5 Mar 2003 22:08:50 -0800 (PST) Received: by trip.mrball.net (Postfix, from userid 501) id 35B792C066; Thu, 6 Mar 2003 01:08:50 -0500 (EST) Date: Wed, 5 Mar 2003 22:08:50 -0800 From: Todd Lyons To: "'Majordomo-Users@GreatCircle.COM'" Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 Message-ID: <20030306060850.GO7208@mrball.net> Mail-Followup-To: "'Majordomo-Users@GreatCircle.COM'" References: <1B2D9E22CDF7D611BD2200805FA7B779181C69@hou204.cig.mcel.mot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <1B2D9E22CDF7D611BD2200805FA7B779181C69@hou204.cig.mcel.mot.com> Organization: Progressive Linux Consultants X-mailer-flag: Outlook? Viral infections & bugs non-stop! Use another mailer if you value your data. User-Agent: Mutt/1.5.3i X-Archive-Number: 200303/24 X-Sequence-Number: 2895 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chen Jervy-qch1408 wanted us to know: ># /usr/lib/sendmail -v -bi >WARNING: World writable directory /var/spool/mqueue >/etc/mail/aliases: 9 aliases, longest 52 bytes, 294 bytes total >WARNING: Group writable directory /usr/majordomo >WARNING: Group writable directory /usr/majordomo/majordomo-1.94.4 >newaliases: cannot open /usr/majordomo/majordomo-1.94.4/majordomo_aliases: Executable files not allowed Sendmail changed their allowable permissions so that you *MUST* remove the group and world write bits from every directory up to the file it's trying to read: /usr /usr/majordomo /usr/majordomo/majordomo-1.94.4 /usr/majordomo/majordomo-1.94.4/majordomo_aliases - -- Blue skies... Todd Proprietary Software Licenses: Duping a person into making a vow of ignorance and then selling them the fruits of knowledge is like making them believe they benefit from having their head held under water while someone sells them oxygen. Linux kernel 2.4.19-16mdk 4 users, load average: 0.00, 0.00, 0.00 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: http://www.mrball.net/todd.asc iD8DBQE+ZuXyIBT1264ScBURAkmWAJ9smd0S1aky/iXNorh3ADkgA2nH8ACbB4qe zo2hfOncONcPggwrcKx5ISg= =Ltgr -----END PGP SIGNATURE----- From majordomo-users-owner@greatcircle.com Wed Mar 5 23:05:06 2003 Received: from mail1.hku.hk (ccnfs4.hku.hk [147.8.2.98]) by mycroft.greatcircle.com (Postfix) with ESMTP id 816C7195F3F for ; Wed, 5 Mar 2003 23:05:04 -0800 (PST) Received: from win98pc (pc1.cc.hku.hk [147.8.96.86]) by mail1.hku.hk (8.12.8/8.12.8) with SMTP id h2674oQR017868 for ; Thu, 6 Mar 2003 15:04:52 +0800 (CST) Message-ID: <031101c2e3ae$a6769880$56600893@hku.hk> From: "kenneth" To: "'Majordomo-Users@GreatCircle.COM'" References: <1B2D9E22CDF7D611BD2200805FA7B779181C69@hou204.cig.mcel.mot.com> <20030306060850.GO7208@mrball.net> Subject: List protection using virtusertable not working in sendmail 8.12.8 Date: Thu, 6 Mar 2003 15:04:35 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-MailScanner: 0 X-Archive-Number: 200303/25 X-Sequence-Number: 2896 Hi After upgrading our sendmail from 8.11.x to 8.12.8, we found that the protection that we used to protect moderated list with virtusertable is not working anymore. It simply bounced all emails to a list with the error: (reason: 553 5.3.0 list-outgoing@xxxxx... User does not exist) even if the mail is sent to list@xxxxx. We are forced to remove the list protection from the virtusertable in order to make the list work again. Does anyone catch similar problem? We are using majordomo 1.94.4. Thanks in advance. Regards, Kenneth From majordomo-users-owner@greatcircle.com Wed Mar 5 23:55:01 2003 Received: from planet.fef.com (unknown [166.90.172.7]) by mycroft.greatcircle.com (Postfix) with ESMTP id 02955195A2D for ; Wed, 5 Mar 2003 23:54:59 -0800 (PST) Received: from planet.fef.com (localhost.localdomain [127.0.0.1]) by planet.fef.com (8.12.8/8.12.8/check_local-5) with ESMTP id h267snim021662; Wed, 5 Mar 2003 23:54:50 -0800 Received: (from alvin@localhost) by planet.fef.com (8.12.8/8.12.4/Submit) id h267sne7021661; Wed, 5 Mar 2003 23:54:49 -0800 From: Alvin Oga Message-Id: <200303060754.h267sne7021661@planet.fef.com> Subject: Re: List protection using virtusertable not working in sendmail 8.12.8 To: kkyyip@hkusua.hku.hk (kenneth) Date: Wed, 5 Mar 2003 23:54:49 -0800 (PST) Cc: Majordomo-Users@greatcircle.com In-Reply-To: <031101c2e3ae$a6769880$56600893@hku.hk> from "kenneth" at Mar 06, 2003 03:04:35 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/26 X-Sequence-Number: 2897 hi ya kenneth yup.. we changed one of our boxes from 8.9.x and had some problems to deal with -- owner and group ids for smmsp -- directory permissions try theses hints to get things working that used to work http://www.Linux-Sec.net/Mail/Sendmail-Install-HOWTO/permissions.txt also check that /etc/mail/*files* is correct too http://www.Linux-Sec.net/Mail/etc.mail/ specifically local-host-names - dont know about your majord alias definitions ... files might have moved around ??? ( /etc/aliases vs /etc/mail/aliases ... ) ( sendmail.* etc .. - removing virtusertable does NOT make sense... - we had to add it to get 8.12.8 working right :-) ( needed to at least have its own domain listed ) have fun alvin > kenneth wrote: > > Hi > > After upgrading our sendmail from 8.11.x to 8.12.8, we found that > the protection that we used to protect moderated list with > virtusertable is not working anymore. It simply bounced all > emails to a list with the error: > (reason: 553 5.3.0 list-outgoing@xxxxx... User does not exist) > even if the mail is sent to list@xxxxx. > > We are forced to remove the list protection from the virtusertable > in order to make the list work again. > > Does anyone catch similar problem? We are using majordomo 1.94.4. > > Thanks in advance. > > Regards, > Kenneth > From majordomo-users-owner@greatcircle.com Thu Mar 6 00:58:24 2003 Received: from etzion.org.il (linux.hertzog.macam98.ac.il [192.114.207.34]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1A04A196020 for ; Thu, 6 Mar 2003 00:58:21 -0800 (PST) Received: from etzion.org.il (localhost [127.0.0.1]) by etzion.org.il (8.12.6/8.12.6/Debian-7) with ESMTP id h268sqsc016313; Thu, 6 Mar 2003 10:54:53 +0200 Received: (from ebick@localhost) by etzion.org.il (8.12.6/8.12.6/Debian-7) id h268sNht016308; Thu, 6 Mar 2003 10:54:23 +0200 Date: Thu, 6 Mar 2003 10:54:23 +0200 (IST) From: Ezra Bick To: Daniel Liston Cc: Manfred Riese , MDOMO-Users Mailingliste Subject: Re: how to cascade mailing lists? In-Reply-To: <3E66783A.6010107@sonny.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200303/27 X-Sequence-Number: 2898 The problem with cascading the lists is that if you have subscribers to more than one list, they will receive multiple copies of the "announce" mailing. On our server, we have a perl script that reads all our lists, appends them, takes out the multiple listings and creates a new file which is the subscribers file of the announce-list. On Wed, 5 Mar 2003, Daniel Liston wrote: > As long as the people signing up for just a cars list are aware that > your site is going to also send them email by virtue of joining any > specific list... As a comparison, the majordomo-announce list does > not automatically include me in announcements just because I belong > to the majordomo-users list. > > What you are aiming to do is the first thing that would get me to > rethink my membership in any of your lists. With that out of the > way; > > Every list has a resend address and an include alias. Create a > separate list, maybe homepage-announce, that is a moderated, post > only list. If none of your other lists are archived or digested, > just add the include alias for each list in the membership file > of the homepage-annouce list. Do some experimenting with this > idea before you put it into production. It may expose your :include: > addresses to the recipients. If that is the case, use the resend > address in the homepage-announce file instead, (strip -outgoing). > The downside to this, could be a VERY heavy hit to your server all > at once when it comes to delivering/resending all the messages. > > /etc/aliases > homepage-announce: "|/path-to/majordomo/wrapper resend -l hompage-announce homepage-announce-outgoing,nobody" > homepage-announce-outgoing: :include:/path-to/majordomo/lists/homepage-announce > > /path-to/majordomo/lists/homepage-announce > carlist1-outgoing@mydomain.com > carlist2-outgoing@mydomain.com > carlist3-outgoing@mydomain.com > . > . > . > carlist30-outgoing@mydomain.com > > Dan Liston > > Manfred Riese wrote: > > Hi all, > > > > we have about 30 different mailing lists at our homepage (own > > webserver), which all contain several discussionboards about, let's say > > cars. One about chrysler voyager, another about peugeot 307, etc. Every > > list is unmoderated, we had no need until now. > > > > But there is one discussionboard about the homepage itself, which should > > be distributed to every mailing list (every car). > > My first idea was just putting the name of the "car-lists" (list1, > > list2, list3) into the "homepagelist", but this doesn't work. > > I tried several ways, but none was sucessful, but that one in the > > aliases-file: > > > > homepagelist: :include:/path/to/lists-dir/list1, > > :include:/path/to/lists-dir/list2, etc. > > > > But i think, this isn't the luckiest way to do this, particularly when > > the number of lists is still growing. > > Does anyone know the ingeniously way ? > > > > best regards > > > > manfred > > From majordomo-users-owner@greatcircle.com Thu Mar 6 11:32:20 2003 Received: from mailout01.sul.t-online.com (mailout01.sul.t-online.com [194.25.134.80]) by mycroft.greatcircle.com (Postfix) with ESMTP id BFD601966FE for ; Thu, 6 Mar 2003 11:29:26 -0800 (PST) Received: from fwd00.sul.t-online.de by mailout01.sul.t-online.com with smtp id 18r13U-0008Eq-03; Thu, 06 Mar 2003 20:29:24 +0100 Received: from t-online.de (320087908768-0001@[217.229.136.123]) by fwd00.sul.t-online.com with esmtp id 18r13D-050jGSC; Thu, 6 Mar 2003 20:29:07 +0100 Message-ID: <3E67A185.608@t-online.de> Date: Thu, 06 Mar 2003 20:29:09 +0100 From: Manfred.Riese@t-online.de (Manfred Riese) User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; de-AT; rv:1.2.1) Gecko/20021130 X-Accept-Language: de, de-at, en-us, en MIME-Version: 1.0 To: MDOMO-Users Mailingliste Subject: Re: how to cascade mailing lists? References: <3E6669A9.1080306@t-online.de> <3E66783A.6010107@sonny.org> In-Reply-To: <3E66783A.6010107@sonny.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Sender: 320087908768-0001@t-dialin.net X-Archive-Number: 200303/28 X-Sequence-Number: 2899 Hi all, first of all, thanks for the solution of my problem. I think, i forget to mention 2 points: 1. Everyone who subscribes our lists, knows that the messages of the homepageforum will be distributed through all lists. This was before we had our own server, and I think, this makes sense for i.e. announcing changes at the homepage. 2. In the last days the number of wrong placed messages in the discussionforums grew enormously. therefor we decided two things: First, we made another group for cars, we don't discuss at the moment; Secound, we want to change the homepageforum to moderated. But how to manage moderated messages in a unmoderated mailinglist? So I had the idea of cascading mailing lists: one moderated into the other unmnoderated. I think, Daniel guessed it, and included in his solution the moderated homepagelist. Thanks again for helping so quickly, Manfred From majordomo-users-owner@greatcircle.com Thu Mar 6 13:16:21 2003 Received: from delivery.infowest.com (delivery.infowest.com [204.17.177.5]) by mycroft.greatcircle.com (Postfix) with ESMTP id 31E2C1959F3 for ; Thu, 6 Mar 2003 13:16:21 -0800 (PST) Received: from infowest.com (slc-ppp-208-187-113-130.infowest.net [208.187.113.130]) by delivery.infowest.com (Postfix) with ESMTP id E4C06E4364E for ; Thu, 6 Mar 2003 14:16:15 -0700 (MST) Message-ID: <3E67B9DB.3060303@infowest.com> Date: Thu, 06 Mar 2003 14:12:59 -0700 From: Lorin Lund User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en,ja MIME-Version: 1.0 To: Majordomo-Users@greatcircle.com Subject: I am interested in numbers - facility requirements for high volume list Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/29 X-Sequence-Number: 2900 Does anyone have experience they can share regarding high volume lists? Bandwidth limitations? CPU speed limitations? From majordomo-users-owner@greatcircle.com Thu Mar 6 15:18:58 2003 Received: from smtp.idi.net (smtp.idi.net [209.70.84.4]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8C6B1195A5C for ; Thu, 6 Mar 2003 15:18:57 -0800 (PST) Received: from pbender (unknown [209.70.84.47]) by smtp.idi.net (Postfix) with SMTP id EDCAF56203 for ; Thu, 6 Mar 2003 18:18:57 -0500 (EST) Message-ID: <00bf01c2e436$bfc01a40$2f5446d1@idi.net> From: "Philip Bender" To: Subject: Encryption Date: Thu, 6 Mar 2003 18:18:51 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00BC_01C2E40C.D6B7B7A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Archive-Number: 200303/30 X-Sequence-Number: 2901 This is a multi-part message in MIME format. ------=_NextPart_000_00BC_01C2E40C.D6B7B7A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable What, if any, methods exist for encrypting messages distributed by majordom= o? ------=_NextPart_000_00BC_01C2E40C.D6B7B7A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
What, if any, methods exist for encrypting= messages=20 distributed by majordomo?
 
------=_NextPart_000_00BC_01C2E40C.D6B7B7A0-- From majordomo-users-owner@greatcircle.com Thu Mar 6 20:58:17 2003 Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by mycroft.greatcircle.com (Postfix) with ESMTP id 6F672195A0E for ; Thu, 6 Mar 2003 20:58:16 -0800 (PST) Received: from h-66-167-135-14.phndaz91.covad.net ([66.167.135.14] helo=Vaio.earthlink.net) by hawk.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18r9vz-0003aN-00 for majordomo-users@greatcircle.com; Thu, 06 Mar 2003 20:58:15 -0800 Message-Id: <5.2.0.9.2.20030306215103.00b89ca0@pop.earthlink.net> X-Sender: bobbish@pop.earthlink.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Thu, 06 Mar 2003 21:58:15 -0700 To: majordomo-users@greatcircle.com From: Bob Bish Subject: No subject Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200303/31 X-Sequence-Number: 2902 If the sender of a message does not include a subject line (leaves it blank), is there a way to get majordomo to add one or, at least, to add the subject prefix? Many members sort out list mail using the subject prefix, but apparently majordomo doesn't add the prefix if there is no subject. Using version 1.94.5 ...Bob From majordomo-users-owner@greatcircle.com Thu Mar 6 21:06:35 2003 Received: from mail.speakeasy.net (mail15.speakeasy.net [216.254.0.215]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1CD5C195A0E for ; Thu, 6 Mar 2003 21:06:34 -0800 (PST) Received: (qmail 7463 invoked from network); 7 Mar 2003 05:06:46 -0000 Received: from unknown (HELO att.net) (w6go@[66.93.44.143]) (envelope-sender ) by mail15.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 7 Mar 2003 05:06:46 -0000 Message-ID: <3E6828D8.2030505@att.net> Date: Thu, 06 Mar 2003 21:06:32 -0800 From: Jay O'Brien User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bob Bish Cc: majordomo-users@greatcircle.com Subject: Re: No subject References: <5.2.0.9.2.20030306215103.00b89ca0@pop.earthlink.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/32 X-Sequence-Number: 2903 Bob, You need the resend.1 patch. See ftp://ftp.ccsf.org/majordomo-patches/1.94.5/ Jay O'Brien Bob Bish wrote: > If the sender of a message does not include a subject line (leaves it > blank), is there a way to get majordomo to add one or, at least, to add the > subject prefix? Many members sort out list mail using the subject prefix, > but apparently majordomo doesn't add the prefix if there is no > subject. Using version 1.94.5 > > ...Bob > > From majordomo-users-owner@greatcircle.com Thu Mar 6 21:18:51 2003 Received: from trip.mrball.net (66-214-180-43.la-cbi.charterpipeline.net [66.214.180.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 7599119685F for ; Thu, 6 Mar 2003 21:18:49 -0800 (PST) Received: by trip.mrball.net (Postfix, from userid 501) id C14872C0B3; Fri, 7 Mar 2003 00:18:48 -0500 (EST) Date: Thu, 6 Mar 2003 21:18:48 -0800 From: Todd Lyons To: Majordomo-Users@greatcircle.com Subject: Re: I am interested in numbers - facility requirements for high volume list Message-ID: <20030307051848.GF31821@mrball.net> Mail-Followup-To: Majordomo-Users@greatcircle.com References: <3E67B9DB.3060303@infowest.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <3E67B9DB.3060303@infowest.com> Organization: Progressive Linux Consultants X-mailer-flag: Outlook? Viral infections & bugs non-stop! Use another mailer if you value your data. User-Agent: Mutt/1.5.3i X-Archive-Number: 200303/33 X-Sequence-Number: 2904 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lorin Lund wanted us to know: >Does anyone have experience they can share regarding high volume lists? >Bandwidth limitations? CPU speed limitations? I'm not familiar with any high volume lists that use majordomo, but I do know that the Linux Kernel Mailing List uses majordomo. I am familiar with the Mandrake mailing lists and they run across a couple of machines that are using postfix and sympa (postfix is spread across multiple queues). They are dual PIII 650 machines with 512 Megs of RAM. There are about 15 mailing lists. The three main ones seem to have about 5000 users each. A _LOT_ of mail goes through those machines and they're not hurting too badly. Personally, I administer a couple of machines. One with majordomo/sendmail (about 30 messages a day, 226 users) runs under essentially no load all day long. We also use bulk_mailer to break up the outbound mails (opting not to use the built in stuff to sendmail). It's a Pentium 200 with 64 Megs of RAM running RedHat 7.2 IIRC. A second one with mailman/postfix (about 5 messages a day, 125 users) runs with essentially no load as well. Personally I prefer postfix over sendmail and don't have a problem with running either majordomo or mailman as long as it's on postfix. It's a vm run at a professional colo company (http://www.johncompanies.com) and it's a dual P4 with 2 Gigs of RAM (but multiple vm's on one physical box). - -- Blue skies... Todd Public key: http://www.mrball.net/todd.asc I think we in the open source movement are the invisible hand of the market, baby, or its middle finger, anyway." --Eric S. Raymond Linux kernel 2.4.19-24mdk load average: 0.01, 0.02, 0.00 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: http://www.mrball.net/todd.asc iD8DBQE+aCu4IBT1264ScBURAgQCAJ4mUFAQdMxhH1edwUJ9Srn0oRh58QCePDeN CXQ2ncHFvkdV2B2P4SqxteY= =0ev6 -----END PGP SIGNATURE----- From majordomo-users-owner@greatcircle.com Thu Mar 6 21:25:37 2003 Received: from trip.mrball.net (66-214-180-43.la-cbi.charterpipeline.net [66.214.180.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 61A37195A29 for ; Thu, 6 Mar 2003 21:25:34 -0800 (PST) Received: by trip.mrball.net (Postfix, from userid 501) id 164A42C0B3; Fri, 7 Mar 2003 00:25:34 -0500 (EST) Date: Thu, 6 Mar 2003 21:25:34 -0800 From: Todd Lyons To: majordomo-users@greatcircle.com Subject: Re: Encryption Message-ID: <20030307052534.GG31821@mrball.net> Mail-Followup-To: majordomo-users@greatcircle.com References: <00bf01c2e436$bfc01a40$2f5446d1@idi.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <00bf01c2e436$bfc01a40$2f5446d1@idi.net> Organization: Progressive Linux Consultants X-mailer-flag: Outlook? Viral infections & bugs non-stop! Use another mailer if you value your data. User-Agent: Mutt/1.5.3i X-Archive-Number: 200303/34 X-Sequence-Number: 2905 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Philip Bender wanted us to know: > What, if any, methods exist for encrypting messages distributed by > majordomo? None. That's done at the originating end by the user. I have _heard_ of places that generate a key specifically for a list and piping the inbound messages through gpg --encrypt, but I don't know any specifics. Blue skies... Todd - -- A: No Q: Should I quote at the end of the message? Linux kernel 2.4.19-24mdk load average: 0.00, 0.00, 0.00 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: http://www.mrball.net/todd.asc iD8DBQE+aC1OIBT1264ScBURAoH6AJ9I6zB9bvmg3CvpEYa/mbGLq0Mr1ACgxFGy oLYJH/JNY8o4joIAZtKc9h0= =iksG -----END PGP SIGNATURE----- From majordomo-users-owner@greatcircle.com Thu Mar 6 21:39:18 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 3F1801968D6 for ; Thu, 6 Mar 2003 21:39:15 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h275glEt024035; Thu, 6 Mar 2003 23:42:47 -0600 Message-ID: <3E6830DB.8030702@sonny.org> Date: Thu, 06 Mar 2003 23:40:43 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Philip Bender Cc: majordomo-users@greatcircle.com Subject: Re: Encryption References: <00bf01c2e436$bfc01a40$2f5446d1@idi.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/35 X-Sequence-Number: 2906 Think of majordomo as a phone company. It will make your connections for you, but will not do anything with them in the process. Scrambling and descrambing of communications is the responsibility of the sender and the receiver. The phone company neither sends nor receives, it only connects the sender to the receiver. Dan Liston Philip Bender wrote: > What, if any, methods exist for encrypting messages distributed by > majordomo? > From majordomo-users-owner@greatcircle.com Thu Mar 6 22:44:19 2003 Received: from albatross.mail.pas.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by mycroft.greatcircle.com (Postfix) with ESMTP id 21481195AF7 for ; Thu, 6 Mar 2003 22:44:18 -0800 (PST) Received: from h-66-167-135-14.phndaz91.covad.net ([66.167.135.14] helo=Vaio.earthlink.net) by albatross.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18rBaR-0000Cr-00 for majordomo-users@greatcircle.com; Thu, 06 Mar 2003 22:44:07 -0800 Message-Id: <5.2.0.9.2.20030306234243.00bb4dd0@pop.earthlink.net> X-Sender: bobbish@pop.earthlink.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Thu, 06 Mar 2003 23:44:10 -0700 To: majordomo-users@greatcircle.com From: Bob Bish Subject: Re: No subject In-Reply-To: <3E6828D8.2030505@att.net> References: <5.2.0.9.2.20030306215103.00b89ca0@pop.earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200303/36 X-Sequence-Number: 2907 Is there anything I could put in taboo_headers that would reject a message with a blank subject header? ...Bob From majordomo-users-owner@greatcircle.com Fri Mar 7 01:08:13 2003 Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10]) by mycroft.greatcircle.com (Postfix) with ESMTP id 438B21959D7 for ; Fri, 7 Mar 2003 01:08:10 -0800 (PST) Received: from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate2.mot.com (Motorola/Motgate2) with ESMTP id h27991EL012804 for ; Fri, 7 Mar 2003 02:09:01 -0700 (MST) Received: [from zch07exm05.corp.mot.com (ZCH07EXM05.corp.mot.com [200.3.1.211]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id CAA14547 for ; Fri, 7 Mar 2003 02:06:14 -0700 (MST)] Received: by ZCH07EXM05.corp.mot.com with Internet Mail Service (5.5.2656.59) id ; Fri, 7 Mar 2003 17:08:06 +0800 Message-ID: <1B2D9E22CDF7D611BD2200805FA7B779181C76@hou204.cig.mcel.mot.com> From: Chen Jervy-qch1408 To: "'Daniel Liston'" Cc: "'Majordomo-Users@greatcircle.com'" Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 Date: Fri, 7 Mar 2003 17:08:06 +0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain X-Archive-Number: 200303/37 X-Sequence-Number: 2908 Dan, Thanks for your help, the following is answer, please try to give me more point form you. 1. Upgrade majordomo to 1.94.5 (or higher) This is my deadline to follow it. 2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 I use 8.12.8 sendmail.cf 3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf I tried it but failed 3a. Create a symbolic link from your majordomo_aliases to /etc/mail It could not work anymore. 4. Restart sendmail Now, I resolved some problems, I used "majordomo" account to replace "smmsp" in sendmail, so aliases can work as normal. But web interface (majorcool) could not work for all features, it always displayed permission error as the following messages in IE. : ABORT shlock: '/usr/majordomo/majordomo-1.94.4' is not writable by UID 60001 GID 60001 Recipient names must be specified #ls -ld /usr/majordomo/majordomo-1.94.4 drwxr-xr-x 13 majordomomajordomo 2048 Mar 5 21:06 /usr/majordomo/majordomo-1.94.4 60001 is "nobody" account & group, it seems that sendmail audit more strictly. Kind Regards Jervy Chen * Fear can hold you prisoner * * Hope can set you free * -----Original Message----- From: Daniel Liston [mailto:dliston@sonny.org] Sent: Thursday, March 06, 2003 2:33 AM To: Chen Jervy-qch1408 Cc: Majordomo-Users@greatcircle.com Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 Hi, Several points here, 1. Upgrade majordomo to 1.94.5 (or higher) 2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf 3a. Create a symbolic link from your majordomo_aliases to /etc/mail 4. Restart sendmail Dan Liston Chen Jervy-qch1408 wrote: > Hello, guys, > > Could anybody help me to resolve the following problem? Any idea will be > appreciated! > > I am majordomo admin and have a majordomo server (Sun Ultra 2), > majordomo 1.94.4 and sendmail 8.8.5 installed on it, it works fine for 2 > years already after I setup it. The following is my setting before in > /etc/mail/sendmail.cf. > > OA/usr/majordomo/majordomo-1.94.4/majordomo_aliases > > Now, for the security reason, I have to upgrade sendmail from 8.8.5 to > 8.12.8, I finished it already and added the above line in sendmail.cf > also but majordomo could not work as normal. The following is error > message when I try to send mail to majordomo list but it can send email > to normal user successfully. > > Mar 5 11:55:44 zchps01 sendmail[764]: h253tip9000764: SYSERR(root): dbm > map "Alias0": unsafe map file > /usr/majordomo/majordomo-1.94.4/majordomo_aliases: No such file or directory > > Here is the output when I try to send out majordomo list. > > # /usr/lib/sendmail -v -bi > WARNING: World writable directory /var/spool/mqueue > /etc/mail/aliases: 9 aliases, longest 52 bytes, 294 bytes total > WARNING: Group writable directory /usr/majordomo > WARNING: Group writable directory /usr/majordomo/majordomo-1.94.4 > newaliases: cannot open > /usr/majordomo/majordomo-1.94.4/majordomo_aliases: Executable files not > allowed > > # /usr/lib/sendmail -v test > . > test... Connecting to [127.0.0.1] via relay... > 220 majordomo.motor.com ESMTP Sendmail 8.12.8/8.12.8; Wed, 5 Mar 2003 > 14:46:36 +0800 (CST) > >>> EHLO majordomo.motor.com > 250-majordomo.motor.com Hello localhost [127.0.0.1], pleased to meet you > 250-ENHANCEDSTATUSCODES > 250-PIPELINING > 250-EXPN > 250-VERB > 250-8BITMIME > 250-SIZE > 250-DSN > 250-ETRN > 250-DELIVERBY > 250 HELP > >>> MAIL From:> > 250 2.1.0 >... Sender ok > >>> RCPT To:> > >>> DATA > 250 2.1.5 >... Recipient ok (will queue) > 354 Enter mail, end with "." on a line by itself > >>> . > 250 2.0.0 h256ka8v002492 Message accepted for delivery > test... Sent (h256ka8v002492 Message accepted for delivery) > Closing connection to [127.0.0.1] > >>> QUIT > 221 2.0.0 majordomo.motor.com closing connection > > # mailq > /var/spool/mqueue (1 request) > -----Q-ID----- --Size-- -----Q-Time----- > ------------Sender/Recipient----------- > h256ka8v002492 0 Wed Mar 5 14:46 > > (dbm map "Alias1": unsafe map file > /usr/majordomo/majordomo-1) > > > Total requests: 1 > > > > > Kind Regards > Jervy Chen > * Fear can hold you prisoner * > * Hope can set you free * From majordomo-users-owner@greatcircle.com Fri Mar 7 03:28:36 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 46236195B72 for ; Fri, 7 Mar 2003 03:28:35 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h27BWDEt001410; Fri, 7 Mar 2003 05:32:13 -0600 Message-ID: <3E6882BA.8040500@sonny.org> Date: Fri, 07 Mar 2003 05:30:02 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bob Bish Cc: majordomo-users@greatcircle.com Subject: Re: No subject References: <5.2.0.9.2.20030306215103.00b89ca0@pop.earthlink.net> <5.2.0.9.2.20030306234243.00bb4dd0@pop.earthlink.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/38 X-Sequence-Number: 2909 You might try something like; /^Subject:\s*$/i Dan Liston Bob Bish wrote: > Is there anything I could put in taboo_headers that would reject a > message with a blank subject header? > > ...Bob From majordomo-users-owner@greatcircle.com Fri Mar 7 03:40:25 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id DDF46196878 for ; Fri, 7 Mar 2003 03:40:22 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h27Bi3Et001471; Fri, 7 Mar 2003 05:44:03 -0600 Message-ID: <3E688580.8040105@sonny.org> Date: Fri, 07 Mar 2003 05:41:52 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chen Jervy-qch1408 Cc: "'Majordomo-Users@greatcircle.com'" Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 References: <1B2D9E22CDF7D611BD2200805FA7B779181C76@hou204.cig.mcel.mot.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/39 X-Sequence-Number: 2910 Chen Jervy-qch1408 wrote: > Dan, > > Thanks for your help, the following is answer, please try to give me more point form you. > 1. Upgrade majordomo to 1.94.5 (or higher) > This is my deadline to follow it. > 2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 > I use 8.12.8 sendmail.cf DZ8.12.8 > 3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf > I tried it but failed Please describe "failed". I use this successfully; O AliasFile=/etc/aliases,/etc/mail/majordomo.aliases The same could be written as two separate lines like; O AliasFile=/etc/aliases O AliasFile=/etc/mail/majordomo.aliases > 3a. Create a symbolic link from your majordomo_aliases to /etc/mail > It could not work anymore. I do not understand what you mean. Majordomo could not work, or sendmail? lrwxrwxrwx 1 root root 31 May 5 2002 /etc/mail/majordomo.aliases -> ../../var/lib/majordomo/aliases > 4. Restart sendmail > > > Now, I resolved some problems, I used "majordomo" account to replace "smmsp" in sendmail, so aliases can work as normal. > > But web interface (majorcool) could not work for all features, it always displayed permission error as the following messages in IE. > : ABORT > shlock: '/usr/majordomo/majordomo-1.94.4' is not writable by UID 60001 GID 60001 > > Recipient names must be specified > > #ls -ld /usr/majordomo/majordomo-1.94.4 > drwxr-xr-x 13 majordomomajordomo 2048 Mar 5 21:06 /usr/majordomo/majordomo-1.94.4 > > 60001 is "nobody" account & group, it seems that sendmail audit more strictly. Sendmail is definitely more strict on security than it used to be. You might have to reconfigure your majorcool to run as the majordomo user and group. Dan Liston > > Kind Regards > Jervy Chen > > * Fear can hold you prisoner * > * Hope can set you free * > > > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Thursday, March 06, 2003 2:33 AM > To: Chen Jervy-qch1408 > Cc: Majordomo-Users@greatcircle.com > Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 > > > Hi, > > Several points here, > > 1. Upgrade majordomo to 1.94.5 (or higher) > 2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 > 3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf > 3a. Create a symbolic link from your majordomo_aliases to /etc/mail > 4. Restart sendmail > > Dan Liston > > > Chen Jervy-qch1408 wrote: > >>Hello, guys, >> >>Could anybody help me to resolve the following problem? Any idea will be >>appreciated! >> >>I am majordomo admin and have a majordomo server (Sun Ultra 2), >>majordomo 1.94.4 and sendmail 8.8.5 installed on it, it works fine for 2 >>years already after I setup it. The following is my setting before in >>/etc/mail/sendmail.cf. >> >>OA/usr/majordomo/majordomo-1.94.4/majordomo_aliases >> >>Now, for the security reason, I have to upgrade sendmail from 8.8.5 to >>8.12.8, I finished it already and added the above line in sendmail.cf >>also but majordomo could not work as normal. The following is error >>message when I try to send mail to majordomo list but it can send email >>to normal user successfully. >> >>Mar 5 11:55:44 zchps01 sendmail[764]: h253tip9000764: SYSERR(root): dbm >>map "Alias0": unsafe map file >>/usr/majordomo/majordomo-1.94.4/majordomo_aliases: No such file or directory >> >>Here is the output when I try to send out majordomo list. >> >># /usr/lib/sendmail -v -bi >>WARNING: World writable directory /var/spool/mqueue >>/etc/mail/aliases: 9 aliases, longest 52 bytes, 294 bytes total >>WARNING: Group writable directory /usr/majordomo >>WARNING: Group writable directory /usr/majordomo/majordomo-1.94.4 >>newaliases: cannot open >>/usr/majordomo/majordomo-1.94.4/majordomo_aliases: Executable files not >>allowed >> >># /usr/lib/sendmail -v test >>. >>test... Connecting to [127.0.0.1] via relay... >>220 majordomo.motor.com ESMTP Sendmail 8.12.8/8.12.8; Wed, 5 Mar 2003 >>14:46:36 +0800 (CST) >> >>> EHLO majordomo.motor.com >>250-majordomo.motor.com Hello localhost [127.0.0.1], pleased to meet you >>250-ENHANCEDSTATUSCODES >>250-PIPELINING >>250-EXPN >>250-VERB >>250-8BITMIME >>250-SIZE >>250-DSN >>250-ETRN >>250-DELIVERBY >>250 HELP >> >>> MAIL From:> >>250 2.1.0 >>... Sender ok >> >>> RCPT To:> >> >>> DATA >>250 2.1.5 >>... Recipient ok (will queue) >>354 Enter mail, end with "." on a line by itself >> >>> . >>250 2.0.0 h256ka8v002492 Message accepted for delivery >>test... Sent (h256ka8v002492 Message accepted for delivery) >>Closing connection to [127.0.0.1] >> >>> QUIT >>221 2.0.0 majordomo.motor.com closing connection >> >># mailq >> /var/spool/mqueue (1 request) >>-----Q-ID----- --Size-- -----Q-Time----- >>------------Sender/Recipient----------- >>h256ka8v002492 0 Wed Mar 5 14:46 >> >> (dbm map "Alias1": unsafe map file >>/usr/majordomo/majordomo-1) >> >> >> Total requests: 1 >> >> >> >> >>Kind Regards >>Jervy Chen >>* Fear can hold you prisoner * >>* Hope can set you free * > From majordomo-users-owner@greatcircle.com Fri Mar 7 05:23:03 2003 Received: from mailserv.mecnet.net (mailserv.mecnet.net [216.20.10.4]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1DEE41959D7 for ; Fri, 7 Mar 2003 05:23:02 -0800 (PST) Received: from [192.168.1.253] (HELO mailfilter2.mecnet.net) by mailserv.mecnet.net (CommuniGate Pro SMTP 4.0.5) with ESMTP id 10181631 for Majordomo-Users@greatcircle.com; Fri, 07 Mar 2003 08:30:02 -0500 Received: from [216.20.87.2] (helo=[10.0.0.41]) by mailfilter2.mecnet.net with esmtp (Exim 4.10) id 18rHtn-0001wc-00 for Majordomo-Users@greatcircle.com; Fri, 07 Mar 2003 08:28:31 -0500 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Fri, 07 Mar 2003 08:22:56 -0500 Subject: Re: List protection using virtusertable not working in sendmail From: John Heffernan To: Majordomo-Users Message-ID: In-Reply-To: <031101c2e3ae$a6769880$56600893@hku.hk> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Scanner: exiscan for exim4 (http://duncanthrax.net/exiscan/) *18rHtn-0001wc-00*5HXRRjQIN12* X-Archive-Number: 200303/40 X-Sequence-Number: 2911 We are having the same problem after applying the sendmail security patch for the problem discovered a few days ago. The patch upgraded sendmail to version 8.12.7 (we used a "patch" supplied by Apple via software update). We are using majordomo version 1.94.5. I also disabled the virtusertable (removed the FEATURE line in the sendmail MC file and regenerated sendmail.cf ) to get things working again but was wondering if there was a better solution. -- John Heffernan -- Educational Technology Consultant -- Hampshire Educational Collaborative -- 97 Hawley Street -- Northampton, MA 01060-2327 -- 413.586.4900 x144 (tel) -- 413.586-0180 (fax) -- http://www.collaborative.org/ From majordomo-users-owner@greatcircle.com Fri Mar 7 09:53:12 2003 Received: from mail.innovativebusiness.net (mail.innovativebusiness.net [65.209.59.13]) by mycroft.greatcircle.com (Postfix) with ESMTP id 5A55E195AD3 for ; Fri, 7 Mar 2003 09:53:09 -0800 (PST) Received: from PETE (bastion.innovativebusiness.net [65.209.59.11]) by mail.innovativebusiness.net (8.12.2/8.12.2) with ESMTP id h27Hr85s021200 for ; Fri, 7 Mar 2003 12:53:08 -0500 From: "Peter Dumpert" To: majordomo-users@greatcircle.com Date: Fri, 7 Mar 2003 12:56:06 -0500 MIME-Version: 1.0 Subject: sendmail 8.12.8 permission problem - fixed Message-ID: <3E6896E6.10126.29ABE8@localhost> X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Archive-Number: 200303/41 X-Sequence-Number: 2912 I just upgraded to sendmail 8.12.8 for security reasons. Then, after getting a request to send out an emergency message from a client through her mailing list, I found that the upgrade broke majordomo. The message in the mail log was this: Mar 6 13:39:19 mail sendmail[957]: NOQUEUE: SYSERR(majordomo): can not write to queue directory /var/spool/clientmqueue/ (RunAsGid=0, required=12): Permission denied After some frantic searching, I found that the problem was with the permissions of the new sendmail program. This is how the permissions need to be: -r-xr-sr-x 1 root mail 622429 Mar 3 20:07 /usr/sbin/sendmail I think the set group id bit is what did the trick. I hope this helps. -- Peter A. Dumpert Innovative Computer Services LLC - web design/e-pubs/consulting Innovative BusinessNet - an ISP for Business www.innovativebusiness.net Phone: 732-683-0092 ext 102 Fax: 732-577-9390 From majordomo-users-owner@greatcircle.com Fri Mar 7 11:20:34 2003 Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by mycroft.greatcircle.com (Postfix) with ESMTP id BCD6D195A32 for ; Fri, 7 Mar 2003 11:18:30 -0800 (PST) Received: from h-69-3-76-110.phndaz91.covad.net ([69.3.76.110] helo=Vaio.earthlink.net) by snipe.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18rNMD-0002ao-00; Fri, 07 Mar 2003 11:18:13 -0800 Message-Id: <5.2.0.9.2.20030307121744.00bc6248@pop.earthlink.net> X-Sender: bobbish@pop.earthlink.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Fri, 07 Mar 2003 12:18:16 -0700 To: Daniel Liston From: Bob Bish Subject: Re: No subject Cc: majordomo-users@greatcircle.com In-Reply-To: <3E6882BA.8040500@sonny.org> References: <5.2.0.9.2.20030306215103.00b89ca0@pop.earthlink.net> <5.2.0.9.2.20030306234243.00bb4dd0@pop.earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200303/42 X-Sequence-Number: 2913 At 04:30 AM 3/7/2003, Daniel Liston wrote: >You might try something like; > >/^Subject:\s*$/i > >Dan Liston Nope, that didn't work. ...Bob >Bob Bish wrote: >> Is there anything I could put in taboo_headers that would reject a >> message with a blank subject header? From majordomo-users-owner@greatcircle.com Fri Mar 7 12:01:12 2003 Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mycroft.greatcircle.com (Postfix) with ESMTP id 3030D1959C8 for ; Fri, 7 Mar 2003 12:01:11 -0800 (PST) Received: from 216-240-38-250.ip.idiom.com ([216.240.38.250] helo=APTITUDE) by stork.mail.pas.earthlink.net with asmtp (Exim 3.33 #1) id 18rO1a-0000wt-00; Fri, 07 Mar 2003 12:00:58 -0800 From: "Roger B.A. Klorese" To: "'Bob Bish'" , "'Daniel Liston'" Cc: Subject: Re: No subject Date: Fri, 7 Mar 2003 12:01:17 -0800 Message-ID: <7AD6B1A7CA734A48B95E96591302A9B90B9519@sfdc.us.sychron.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <5.2.0.9.2.20030307121744.00bc6248@pop.earthlink.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-ELNK-Trace: 95a5daa1092a4a38d780f4a490ca69564776905774d2ac4b781dd7a38ee03e6eed702f2e6329bf52350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Archive-Number: 200303/43 X-Sequence-Number: 2914 > From: majordomo-users-owner@greatcircle.com > [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of Bob Bish > Sent: Friday, March 07, 2003 11:18 AM > To: Daniel Liston > Cc: majordomo-users@greatcircle.com > Subject: Re: No subject > > > At 04:30 AM 3/7/2003, Daniel Liston wrote: > >You might try something like; > > > >/^Subject:\s*$/i > > > >Dan Liston > > Nope, that didn't work. > > ...Bob I suspect this is little consolation, but it worked perfectly on Mj2. From majordomo-users-owner@greatcircle.com Fri Mar 7 12:08:35 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 66C4A1960E5 for ; Fri, 7 Mar 2003 12:08:32 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h27KCLEt003564; Fri, 7 Mar 2003 14:12:21 -0600 Message-ID: <3E68FC98.4010102@sonny.org> Date: Fri, 07 Mar 2003 14:10:00 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bob Bish Cc: majordomo-users@greatcircle.com Subject: Re: No subject References: <5.2.0.9.2.20030306215103.00b89ca0@pop.earthlink.net> <5.2.0.9.2.20030306234243.00bb4dd0@pop.earthlink.net> <5.2.0.9.2.20030307121744.00bc6248@pop.earthlink.net> X-Enigmail-Version: 0.71.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/44 X-Sequence-Number: 2915 For the message that this did not work, did the "Subject:" header even exist? The regular expression I posted does exactly what you asked, it checks for a Subject: line that contains zero or more whitespaces up to the "end of line". (blank) If the Subject line does not exist at all, the regular expression, or even the taboo_headers for that matter, can help you. If the Subject: line does exist, you should also check for (none) or variations that indicate (no subject) as well as the empty line. It would probably be better to apply the patch posted that will insert a subject_prefix, even for messages missing a Subject:. Dan Bob Bish wrote: > At 04:30 AM 3/7/2003, Daniel Liston wrote: > >> You might try something like; >> >> /^Subject:\s*$/i >> >> Dan Liston > > > Nope, that didn't work. > > ...Bob > > >> Bob Bish wrote: >> >>> Is there anything I could put in taboo_headers that would reject a >>> message with a blank subject header? >> From majordomo-users-owner@greatcircle.com Fri Mar 7 12:13:49 2003 Received: from albatross.mail.pas.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by mycroft.greatcircle.com (Postfix) with ESMTP id 318681969B6 for ; Fri, 7 Mar 2003 12:11:12 -0800 (PST) Received: from h-69-3-76-110.phndaz91.covad.net ([69.3.76.110] helo=Vaio.earthlink.net) by albatross.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18rOAx-0007Fq-00; Fri, 07 Mar 2003 12:10:40 -0800 Message-Id: <5.2.0.9.2.20030307131023.021af008@pop.earthlink.net> X-Sender: bobbish@pop.earthlink.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Fri, 07 Mar 2003 13:10:42 -0700 To: "Roger B.A. Klorese" , "'Daniel Liston'" From: Bob Bish Subject: Re: No subject Cc: In-Reply-To: <7AD6B1A7CA734A48B95E96591302A9B90B9519@sfdc.us.sychron.com > References: <5.2.0.9.2.20030307121744.00bc6248@pop.earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200303/45 X-Sequence-Number: 2916 >I suspect this is little consolation, but it worked perfectly on Mj2. Using version 1.94.5 ...Bob From majordomo-users-owner@greatcircle.com Fri Mar 7 20:41:53 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 5B8081964D7 for ; Fri, 7 Mar 2003 20:41:51 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h284jpEt005742; Fri, 7 Mar 2003 22:45:51 -0600 Message-ID: <3E6974E8.4000801@sonny.org> Date: Fri, 07 Mar 2003 22:43:20 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bob Bish Cc: majordomo-users@greatcircle.com Subject: Re: No subject References: <5.2.0.9.2.20030306215103.00b89ca0@pop.earthlink.net> X-Enigmail-Version: 0.63.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/46 X-Sequence-Number: 2917 I know I have commented on later versions of this message, but I did not mention that users should be educated on other email headers available for sorting their mailing list messages. Specifically, the "Sender:", "To:", or "Cc:" headers. Whatever tool you choose as your favorite mail client, examine "full headers" on this message from the majordomo-users list. You will see at least two of these three headers will indicate this message went through the majordomo-users mailing list. Also note that this list does NOT use the list name in the subject field. If you really want to get technical, the first (bottom) "Received:" line will also indicate the message was originally destined to majordomo-users. A sort/match on any of these fields looking for either majordomo or greatcircle should indicate the list they/you are subscribed to. In my case, I am subscribed to ALL greatcircle.com mailing lists, so my first sort filters on the domain of the list Sender, followed by one more sort to determine the actual list within that domain I subscribe to. Dan Liston Bob Bish wrote: > If the sender of a message does not include a subject line (leaves it > blank), is there a way to get majordomo to add one or, at least, to add > the subject prefix? Many members sort out list mail using the subject > prefix, but apparently majordomo doesn't add the prefix if there is no > subject. Using version 1.94.5 > > ...Bob From majordomo-users-owner@greatcircle.com Fri Mar 7 20:51:50 2003 Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.120.84]) by mycroft.greatcircle.com (Postfix) with ESMTP id 3AEB8195F90 for ; Fri, 7 Mar 2003 20:51:49 -0800 (PST) Received: from h-66-167-134-13.phndaz91.covad.net ([66.167.134.13] helo=Vaio.earthlink.net) by gull.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18rWJB-0003wb-00; Fri, 07 Mar 2003 20:51:41 -0800 Message-Id: <5.2.0.9.2.20030307215102.00bca1d0@pop.earthlink.net> X-Sender: bobbish@pop.earthlink.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Fri, 07 Mar 2003 21:51:38 -0700 To: Daniel Liston From: Bob Bish Subject: Re: No subject Cc: majordomo-users@greatcircle.com In-Reply-To: <3E6974E8.4000801@sonny.org> References: <5.2.0.9.2.20030306215103.00b89ca0@pop.earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200303/47 X-Sequence-Number: 2918 At 09:43 PM 3/7/2003, Daniel Liston wrote: >users should be educated on other email headers available >for sorting their mailing list messages. Specifically, the "Sender:", >"To:", or "Cc:" headers. That's an excellent suggestion. Thanks! ...Bob From majordomo-users-owner@greatcircle.com Sun Mar 9 19:02:25 2003 Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101]) by mycroft.greatcircle.com (Postfix) with ESMTP id C8D661959D9 for ; Sun, 9 Mar 2003 19:02:21 -0800 (PST) Received: from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id h2A32F05007107 for ; Sun, 9 Mar 2003 20:02:15 -0700 (MST) Received: [from zch07exm05.corp.mot.com (ZCH07EXM05.corp.mot.com [200.3.1.211]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id UAA10580 for ; Sun, 9 Mar 2003 20:00:16 -0700 (MST)] Received: by ZCH07EXM05.corp.mot.com with Internet Mail Service (5.5.2656.59) id ; Mon, 10 Mar 2003 11:01:25 +0800 Message-ID: <1B2D9E22CDF7D611BD2200805FA7B779181C77@hou204.cig.mcel.mot.com> From: Chen Jervy-qch1408 To: "'Daniel Liston'" Cc: Majordomo-Users@greatcircle.com Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 Date: Mon, 10 Mar 2003 10:54:04 +0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain X-Archive-Number: 200303/48 X-Sequence-Number: 2919 Dan, Only one question remained, how to reconfigure the majorcool to run as the majordomo user and group (what configuration file)? I check the daemon status when I submitted the request on the web, "majorcool" daemon always run with nobody permission. Thanks a lot. > 4. Restart sendmail >Sendmail is definitely more strict on security than it used to be. You might have to reconfigure your majorcool to run as the majordomo user and group. Kind Regards Jervy Chen * Fear can hold you prisoner * * Hope can set you free * -----Original Message----- From: Daniel Liston [mailto:dliston@sonny.org] Sent: Friday, March 07, 2003 7:42 PM To: Chen Jervy-qch1408 Cc: Majordomo-Users@greatcircle.com Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 Chen Jervy-qch1408 wrote: > Dan, > > Thanks for your help, the following is answer, please try to give me more point form you. > 1. Upgrade majordomo to 1.94.5 (or higher) > This is my deadline to follow it. > 2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 > I use 8.12.8 sendmail.cf DZ8.12.8 > 3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf > I tried it but failed Please describe "failed". I use this successfully; O AliasFile=/etc/aliases,/etc/mail/majordomo.aliases The same could be written as two separate lines like; O AliasFile=/etc/aliases O AliasFile=/etc/mail/majordomo.aliases > 3a. Create a symbolic link from your majordomo_aliases to /etc/mail > It could not work anymore. I do not understand what you mean. Majordomo could not work, or sendmail? lrwxrwxrwx 1 root root 31 May 5 2002 /etc/mail/majordomo.aliases -> ../../var/lib/majordomo/aliases > 4. Restart sendmail > > > Now, I resolved some problems, I used "majordomo" account to replace "smmsp" in sendmail, so aliases can work as normal. > > But web interface (majorcool) could not work for all features, it always displayed permission error as the following messages in IE. > : ABORT > shlock: '/usr/majordomo/majordomo-1.94.4' is not writable by UID 60001 GID 60001 > > Recipient names must be specified > > #ls -ld /usr/majordomo/majordomo-1.94.4 > drwxr-xr-x 13 majordomomajordomo 2048 Mar 5 21:06 /usr/majordomo/majordomo-1.94.4 > > 60001 is "nobody" account & group, it seems that sendmail audit more strictly. Sendmail is definitely more strict on security than it used to be. You might have to reconfigure your majorcool to run as the majordomo user and group. Dan Liston > > Kind Regards > Jervy Chen > > * Fear can hold you prisoner * > * Hope can set you free * > > > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Thursday, March 06, 2003 2:33 AM > To: Chen Jervy-qch1408 > Cc: Majordomo-Users@greatcircle.com > Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 > > > Hi, > > Several points here, > > 1. Upgrade majordomo to 1.94.5 (or higher) > 2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 > 3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf > 3a. Create a symbolic link from your majordomo_aliases to /etc/mail > 4. Restart sendmail > > Dan Liston > > > Chen Jervy-qch1408 wrote: > >>Hello, guys, >> >>Could anybody help me to resolve the following problem? Any idea will be >>appreciated! >> >>I am majordomo admin and have a majordomo server (Sun Ultra 2), >>majordomo 1.94.4 and sendmail 8.8.5 installed on it, it works fine for 2 >>years already after I setup it. The following is my setting before in >>/etc/mail/sendmail.cf. >> >>OA/usr/majordomo/majordomo-1.94.4/majordomo_aliases >> >>Now, for the security reason, I have to upgrade sendmail from 8.8.5 to >>8.12.8, I finished it already and added the above line in sendmail.cf >>also but majordomo could not work as normal. The following is error >>message when I try to send mail to majordomo list but it can send email >>to normal user successfully. >> >>Mar 5 11:55:44 zchps01 sendmail[764]: h253tip9000764: SYSERR(root): dbm >>map "Alias0": unsafe map file >>/usr/majordomo/majordomo-1.94.4/majordomo_aliases: No such file or directory >> >>Here is the output when I try to send out majordomo list. >> >># /usr/lib/sendmail -v -bi >>WARNING: World writable directory /var/spool/mqueue >>/etc/mail/aliases: 9 aliases, longest 52 bytes, 294 bytes total >>WARNING: Group writable directory /usr/majordomo >>WARNING: Group writable directory /usr/majordomo/majordomo-1.94.4 >>newaliases: cannot open >>/usr/majordomo/majordomo-1.94.4/majordomo_aliases: Executable files not >>allowed >> >># /usr/lib/sendmail -v test >>. >>test... Connecting to [127.0.0.1] via relay... >>220 majordomo.motor.com ESMTP Sendmail 8.12.8/8.12.8; Wed, 5 Mar 2003 >>14:46:36 +0800 (CST) >> >>> EHLO majordomo.motor.com >>250-majordomo.motor.com Hello localhost [127.0.0.1], pleased to meet you >>250-ENHANCEDSTATUSCODES >>250-PIPELINING >>250-EXPN >>250-VERB >>250-8BITMIME >>250-SIZE >>250-DSN >>250-ETRN >>250-DELIVERBY >>250 HELP >> >>> MAIL From:> >>250 2.1.0 >>... Sender ok >> >>> RCPT To:> >> >>> DATA >>250 2.1.5 >>... Recipient ok (will queue) >>354 Enter mail, end with "." on a line by itself >> >>> . >>250 2.0.0 h256ka8v002492 Message accepted for delivery >>test... Sent (h256ka8v002492 Message accepted for delivery) >>Closing connection to [127.0.0.1] >> >>> QUIT >>221 2.0.0 majordomo.motor.com closing connection >> >># mailq >> /var/spool/mqueue (1 request) >>-----Q-ID----- --Size-- -----Q-Time----- >>------------Sender/Recipient----------- >>h256ka8v002492 0 Wed Mar 5 14:46 >> >> (dbm map "Alias1": unsafe map file >>/usr/majordomo/majordomo-1) >> >> >> Total requests: 1 >> >> >> >> >>Kind Regards >>Jervy Chen >>* Fear can hold you prisoner * >>* Hope can set you free * > From majordomo-users-owner@greatcircle.com Mon Mar 10 07:13:38 2003 Received: from inst.augie.edu (inst.augie.edu [192.103.41.1]) by mycroft.greatcircle.com (Postfix) with ESMTP id 3591C1960DA for ; Mon, 10 Mar 2003 07:13:37 -0800 (PST) Received: from [10.1.138.78] ([10.1.138.78]) by inst.augie.edu (AIX4.3/8.9.3/8.9.3) with ESMTP id JAA56652 for ; Mon, 10 Mar 2003 09:02:34 -0600 Subject: Re: No subject From: "Tim (TTUG)" To: majordomo-users@greatcircle.com In-Reply-To: <5.2.0.9.2.20030306234243.00bb4dd0@pop.earthlink.net> References: <5.2.0.9.2.20030306215103.00b89ca0@pop.earthlink.net> <5.2.0.9.2.20030306234243.00bb4dd0@pop.earthlink.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2-5mdk Date: 10 Mar 2003 09:19:11 -0600 Message-Id: <1047309552.17706.38.camel@tag3503.augie.edu> Mime-Version: 1.0 X-Archive-Number: 200303/49 X-Sequence-Number: 2920 That reminds me: of a question I have. Is is possible to have certain taboo_{headers/body/subjects} cause majordomo not to bounce it to the moderator but a real kill ie bounce to dev/null. I am willing to try to do this is someone can give me someinfo on the basics of bounce.routine as I have already hardcoded a lot of modifications to our single and only list. Tim On Fri, 2003-03-07 at 00:44, Bob Bish wrote: > Is there anything I could put in taboo_headers that would reject a > message with a blank subject header? > > ...Bob > > From majordomo-users-owner@greatcircle.com Mon Mar 10 12:16:29 2003 Received: from wizard.firn.edu (wizard.firn.edu [150.176.12.39]) by mycroft.greatcircle.com (Postfix) with ESMTP id 0B10D195F8F for ; Mon, 10 Mar 2003 12:16:28 -0800 (PST) Received: from CONVERSION-DAEMON by WIZARD.FIRN.EDU (PMDF V5.2-33 #41769) id <01KTD3V5L22800A8C4@WIZARD.FIRN.EDU> for majordomo-users@greatcircle.com; Mon, 10 Mar 2003 15:09:51 EST Received: from popmail.firn.edu ([204.194.36.191]) by WIZARD.FIRN.EDU (PMDF V5.2-33 #41769) with SMTP id <01KTD3SIVEW000AWWY@WIZARD.FIRN.EDU> for majordomo-users@greatcircle.com; Mon, 10 Mar 2003 15:09:51 -0500 (EST) Date: Mon, 10 Mar 2003 15:14:16 -0500 From: Paul Diaguila Subject: new install - can't send mail to list To: majordomo-users@greatcircle.com Message-id: <3E6CF218.50707@popmail.firn.edu> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en X-Archive-Number: 200303/50 X-Sequence-Number: 2921 Greetings... Have installed Majordomo-1.94.5 on FreeBSD. Am able to retrieve command replies such as help ok, but after creating a list test-l, I'm get the following error: 550 5.2.4 :include:/usr/majordomo-1.94.5/lists/test-l... Cannot open /usr/majordomo-1.94.5/lists/test-l: Group writable directory Went so far as to set the directory and file permissions to owner, group, and world read, exe, and write, but no change... Have majordomo set as trusted in the sendmail.cnf and submit.cf file. Any ideas would be appreciated...... Thanks...... Paul From majordomo-users-owner@greatcircle.com Mon Mar 10 12:31:48 2003 Received: from SACEX2.ad.water.ca.gov (sacex2.water.ca.gov [136.200.117.23]) by mycroft.greatcircle.com (Postfix) with ESMTP id 0872E19601A for ; Mon, 10 Mar 2003 12:31:44 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: Re: new install - can't send mail to list Date: Mon, 10 Mar 2003 12:31:41 -0800 Message-ID: <3EE436BDAFE0044A8D6997B74EC3FAB1813433@SACEX2.ad.water.ca.gov> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: new install - can't send mail to list Thread-Index: AcLnQ1yMhbwDsUdVQMGjDlnxv6+kBgAAGraw From: "Vo, Phillip" To: X-Archive-Number: 200303/51 X-Sequence-Number: 2922 Paul, What is the permission (user, group and chmod mode) of your directory "lists"? Phillip -----Original Message----- From: Paul Diaguila [mailto:paul@popmail.firn.edu]=20 Sent: Monday, March 10, 2003 12:14 PM To: majordomo-users@greatcircle.com Subject: new install - can't send mail to list Greetings... Have installed Majordomo-1.94.5 on FreeBSD. Am able to retrieve command replies such as help ok, but after creating a list test-l, I'm get the=20 following error: 550 5.2.4 :include:/usr/majordomo-1.94.5/lists/test-l... Cannot open /usr/majordomo-1.94.5/lists/test-l: Group writable directory Went so far as to set the directory and file permissions to owner,=20 group, and world read, exe, and write, but no change... Have majordomo=20 set as trusted in the sendmail.cnf and submit.cf file. Any ideas would be appreciated...... Thanks...... Paul From majordomo-users-owner@greatcircle.com Mon Mar 10 14:41:09 2003 Received: from web20418.mail.yahoo.com (web20406.mail.yahoo.com [66.163.169.94]) by mycroft.greatcircle.com (Postfix) with SMTP id E1924195A46 for ; Mon, 10 Mar 2003 14:41:07 -0800 (PST) Message-ID: <20030310224106.24007.qmail@web20418.mail.yahoo.com> Received: from [128.18.230.254] by web20406.mail.yahoo.com via HTTP; Mon, 10 Mar 2003 14:41:06 PST Date: Mon, 10 Mar 2003 14:41:06 -0800 (PST) From: paras dagli Subject: Majordomo not working after Sendmail upgrade To: majordomo-users@greatcircle.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Archive-Number: 200303/52 X-Sequence-Number: 2923 Hi, I updated sendmail to 8.12.8 and now the messages sent to the mailing lists on majordomo are not working. I installed majordomo 1.94.5. I changed the group write permission on the files, and the path to the files, in the lists directory. So the current bits are rwxr-xr-x. I looked at the log file /usr/local/majordomo/log and the messages I sent today to the mailing list don't show up on the log file. Any ideas on what I should do next? Where to look to fix this problem? Thanks, Paras Dagli ===== paras dagli - itchyhands@yahoo.com ===== "All fingers are not alike, If you cut bigger ones to make all equal it is communism, If you stretch smaller ones to make all equal it is socialism, If you do nothing to make all equal it is capitalism." -- B.J. Gupta __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ From majordomo-users-owner@greatcircle.com Mon Mar 10 15:20:43 2003 Received: from wrenkasky.com (esson.net [216.102.129.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 0E290195F75 for ; Mon, 10 Mar 2003 15:20:41 -0800 (PST) Received: from yoda2.wrenkasky.com (IDENT:ZsVgW9FIr8q85UXlooI3La97X74fFprE@localhost [127.0.0.1]) by wrenkasky.com (8.12.5/8.12.5) with ESMTP id h2ANKl4e031993 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Mon, 10 Mar 2003 15:20:47 -0800 Received: (from ed@localhost) by yoda2.wrenkasky.com (8.12.5/8.12.5/Submit) id h2ANKl5s031992; Mon, 10 Mar 2003 15:20:47 -0800 Date: Mon, 10 Mar 2003 15:20:47 -0800 Message-Id: <200303102320.h2ANKl5s031992@yoda2.wrenkasky.com> From: "Ed Kasky" Subject: Re: Majordomo not working after Sendmail upgrade To: paras dagli Cc: majordomo-users@greatcircle.com X-Originating-IP: 128.125.63.168 X-Mailer: Usermin 0.990 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/53 X-Sequence-Number: 2924 paras dagli wrote .. > I updated sendmail to 8.12.8 and now the messages sent > to the mailing lists on majordomo are not working. > I looked at the log file /usr/local/majordomo/log and > the messages I sent today to the mailing list don't > show up on the log file. Look for errors in the maillog and in the messages log. More than likely you either need to create trusted users in submit.cf since you upgraded to 8.12 or symbolic links for smrsh to use the wrapper... Ed Kasky Los Angeles, CA ~~~~~~~~~~~~~~~ "Trust in God, but row away from the rocks." From majordomo-users-owner@greatcircle.com Mon Mar 10 16:57:11 2003 Received: from web20414.mail.yahoo.com (web20402.mail.yahoo.com [66.163.169.90]) by mycroft.greatcircle.com (Postfix) with SMTP id 22BA7195F97 for ; Mon, 10 Mar 2003 16:57:08 -0800 (PST) Message-ID: <20030311005704.2295.qmail@web20414.mail.yahoo.com> Received: from [128.18.230.254] by web20402.mail.yahoo.com via HTTP; Mon, 10 Mar 2003 16:57:04 PST Date: Mon, 10 Mar 2003 16:57:04 -0800 (PST) From: paras dagli Subject: Re: Majordomo not working after Sendmail upgrade To: majordomo-users@greatcircle.com Cc: Ed Kasky In-Reply-To: <200303102320.h2ANKl5s031992@yoda2.wrenkasky.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Archive-Number: 200303/54 X-Sequence-Number: 2925 The problem was with the permissions for the lists directory. The persmissions weren't set for user majordomo. Thanks, Paras --- Ed Kasky wrote: > paras dagli wrote .. > > I updated sendmail to 8.12.8 and now the messages > sent > > to the mailing lists on majordomo are not working. > > > I looked at the log file /usr/local/majordomo/log > and > > the messages I sent today to the mailing list > don't > > show up on the log file. > > Look for errors in the maillog and in the messages > log. More than likely you either need to create > trusted users in submit.cf since you upgraded to > 8.12 or symbolic links for smrsh to use the > wrapper... > > Ed Kasky > Los Angeles, CA > ~~~~~~~~~~~~~~~ > "Trust in God, but row away from the rocks." > ===== paras dagli - itchyhands@yahoo.com ===== "All fingers are not alike, If you cut bigger ones to make all equal it is communism, If you stretch smaller ones to make all equal it is socialism, If you do nothing to make all equal it is capitalism." -- B.J. Gupta __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ From majordomo-users-owner@greatcircle.com Mon Mar 10 16:58:06 2003 Received: from web20421.mail.yahoo.com (web20409.mail.yahoo.com [66.163.169.97]) by mycroft.greatcircle.com (Postfix) with SMTP id D97FD19635E for ; Mon, 10 Mar 2003 16:58:04 -0800 (PST) Message-ID: <20030311005804.39171.qmail@web20421.mail.yahoo.com> Received: from [128.18.230.254] by web20409.mail.yahoo.com via HTTP; Mon, 10 Mar 2003 16:58:04 PST Date: Mon, 10 Mar 2003 16:58:04 -0800 (PST) From: paras dagli Subject: Re: Majordomo not working after Sendmail upgrade To: Ed Kasky Cc: majordomo-users@greatcircle.com In-Reply-To: <200303102320.h2ANKl5s031992@yoda2.wrenkasky.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Archive-Number: 200303/55 X-Sequence-Number: 2926 Ed, The problem was with the permissions for the lists directory. The persmissions weren't set for user majordomo. Thanks, Paras --- Ed Kasky wrote: > paras dagli wrote .. > > I updated sendmail to 8.12.8 and now the messages > sent > > to the mailing lists on majordomo are not working. > > > I looked at the log file /usr/local/majordomo/log > and > > the messages I sent today to the mailing list > don't > > show up on the log file. > > Look for errors in the maillog and in the messages > log. More than likely you either need to create > trusted users in submit.cf since you upgraded to > 8.12 or symbolic links for smrsh to use the > wrapper... > > Ed Kasky > Los Angeles, CA > ~~~~~~~~~~~~~~~ > "Trust in God, but row away from the rocks." ===== paras dagli - itchyhands@yahoo.com ===== "All fingers are not alike, If you cut bigger ones to make all equal it is communism, If you stretch smaller ones to make all equal it is socialism, If you do nothing to make all equal it is capitalism." -- B.J. Gupta __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ From majordomo-users-owner@greatcircle.com Mon Mar 10 20:46:40 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id C9B25195A9A for ; Mon, 10 Mar 2003 20:46:38 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2B4qBEt007984; Mon, 10 Mar 2003 22:52:12 -0600 Message-ID: <3E6D6A8F.9070403@sonny.org> Date: Mon, 10 Mar 2003 22:48:15 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Paul Diaguila Cc: majordomo-users@greatcircle.com Subject: Re: new install - can't send mail to list References: <3E6CF218.50707@popmail.firn.edu> In-Reply-To: <3E6CF218.50707@popmail.firn.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/56 X-Sequence-Number: 2927 Paul Diaguila wrote: > > Greetings... > > Have installed Majordomo-1.94.5 on FreeBSD. Am able to retrieve command > replies such as help ok, but after creating a list test-l, I'm get the > following error: > > 550 5.2.4 :include:/usr/majordomo-1.94.5/lists/test-l... Cannot open > /usr/majordomo-1.94.5/lists/test-l: Group writable directory > > Went so far as to set the directory and file permissions to owner, > group, and world read, exe, and write, but no change... Have majordomo > set as trusted in the sendmail.cnf and submit.cf file. Any ideas would > be appreciated...... > This was the wrong direction. Sendmail was complaining that the directory was already "group" writable. You need to take away group write permission on the entire tree up to and including the directory your lists live in. You did the right thing setting sendmail to trust majordomo though. chmod 755 or 751 the majordomo and majordomo/lists directory, but ALSO chmod 755 "/" and "/usr" Dan Liston PS. In the above comment, majordomo = majordomo-1.94.5 From majordomo-users-owner@greatcircle.com Mon Mar 10 20:53:09 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 960F1196352 for ; Mon, 10 Mar 2003 20:53:08 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2B4wgEt008004; Mon, 10 Mar 2003 22:58:42 -0600 Message-ID: <3E6D6C15.9020805@sonny.org> Date: Mon, 10 Mar 2003 22:54:45 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Tim (TTUG)" Cc: majordomo-users@greatcircle.com Subject: Re: No subject References: <5.2.0.9.2.20030306215103.00b89ca0@pop.earthlink.net> <5.2.0.9.2.20030306234243.00bb4dd0@pop.earthlink.net> <1047309552.17706.38.camel@tag3503.augie.edu> In-Reply-To: <1047309552.17706.38.camel@tag3503.augie.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/57 X-Sequence-Number: 2928 You could, but would you really trust not losing valid list traffic to this kind of modification? I would start by looking at what Joe did with the resend.1 patch. You might use that as your starting point, but do be VERY careful. Dan Liston Tim (TTUG) wrote: > That reminds me: of a question I have. > > Is is possible to have certain taboo_{headers/body/subjects} > cause majordomo not to bounce it to the moderator but a real kill > ie bounce to dev/null. > > I am willing to try to do this is someone can give me someinfo > on the basics of bounce.routine as I have already hardcoded a lot of > modifications to our single and only list. > > Tim > > On Fri, 2003-03-07 at 00:44, Bob Bish wrote: > >> Is there anything I could put in taboo_headers that would reject a >>message with a blank subject header? >> >>...Bob >> >> > > > From majordomo-users-owner@greatcircle.com Tue Mar 11 00:11:00 2003 Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by mycroft.greatcircle.com (Postfix) with ESMTP id 691DE195B61 for ; Tue, 11 Mar 2003 00:10:58 -0800 (PST) Received: from vitesse.cs.utah.edu (vitesse.cs.utah.edu [155.99.197.71]) by wrath.cs.utah.edu (8.11.6/8.11.6) with ESMTP id h2B8Au500247 for ; Tue, 11 Mar 2003 01:10:56 -0700 (MST) Received: by vitesse.cs.utah.edu (Postfix, from userid 124) id 33594E033F; Tue, 11 Mar 2003 01:10:56 -0700 (MST) From: "Mark J. Bradakis" To: majordomo-users@greatcircle.com Subject: Archive format questions Message-Id: <20030311081056.33594E033F@vitesse.cs.utah.edu> Date: Tue, 11 Mar 2003 01:10:56 -0700 (MST) X-Archive-Number: 200303/58 X-Sequence-Number: 2929 So I've got over a decade's worth of archives from several dozen lists, and plan to do some cleanup, reshuffling and such of the files involved. The archives are available via a searchable web interface using WILMA to glue together MHonarc and glimpse. What I would like to do have all the message headers in the archive files to contain only three fields - From, Date and Subject. No received, no X-info, no Mailer-ID, no MIME-type or such. And as an attempt to thwart basic address mining, I'd like to have the 'From ' header lines encrypted, and have the web server spit out the unencrypted text for queries that come through the 'official' interface, while scumbag thievin' spammers get the encrypted and useless strings from their 'bots - or perhaps encrypted address are returned as root@[127.0.0.1] or some such. With Apache's 2.0 external filter ability it seems that delivering readable text to honest queries should be quite possible. Anyway, I'm guessing that something similar has already been done somewhere by someone. Are such filters available? Should I be looking at some new and improved replacement for the WILMA suite? The old Listquest site had some method of replacing email addresses with a .gif or .jpg file so that one could not easily harvest addresses from an archive. Is anything else like this out there? Or should I just plan on rewriting the version of archive2.pl [1.95] currently in use on my servers? mjb. From majordomo-users-owner@greatcircle.com Tue Mar 11 06:09:40 2003 Received: from smtp.idi.net (smtp.idi.net [209.70.84.4]) by mycroft.greatcircle.com (Postfix) with ESMTP id CFE03195A0D for ; Tue, 11 Mar 2003 06:09:39 -0800 (PST) Received: from pbender (unknown [209.70.84.47]) by smtp.idi.net (Postfix) with SMTP id 71646563EE for ; Tue, 11 Mar 2003 09:09:38 -0500 (EST) Message-ID: <001501c2e7d7$d98d5ba0$2f5446d1@idi.net> From: "Philip Bender" To: Subject: Posting from $Sender Date: Tue, 11 Mar 2003 09:09:36 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Archive-Number: 200303/59 X-Sequence-Number: 2930 How can I configure my list to post messages "from" the sender - as opposed to from majordomo, on behalf of the sender? From majordomo-users-owner@greatcircle.com Tue Mar 11 09:29:39 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 9764F195A90 for ; Tue, 11 Mar 2003 09:29:37 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2BHZQEt011703; Tue, 11 Mar 2003 11:35:27 -0600 Message-ID: <3E6E1D63.6020207@sonny.org> Date: Tue, 11 Mar 2003 11:31:15 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Philip Bender , majordomo-users@greatcircle.com Subject: Re: Posting from $Sender References: <001501c2e7d7$d98d5ba0$2f5446d1@idi.net> In-Reply-To: <001501c2e7d7$d98d5ba0$2f5446d1@idi.net> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/60 X-Sequence-Number: 2931 Philip Bender wrote: > How can I configure my list to post messages "from" the sender - as opposed > to from majordomo, on behalf of the sender? Your message showed up as being "from" you, and not "on behalf of" you. Then again, I do not use a Microsoft email client. I think what you really want to get rid of, is the "on behalf of" piece, right? Line 749 of an unpatched "resend" script is where majordomo inserts the Sender: owner-listname@your.domain into the headers of the outgoing messages. 748: # add new header fields 749: print OUT "Sender: $sender\n"; 750: if (defined($opt_p)) { 751: print OUT "Precedence: $opt_p\n"; 752: } See the way the Precedence: header is wrapped in an "if" statement? This could be done for the Sender: header too. 748: # add new header fields 749: if (defined($opt_f)) { 750: print OUT "Sender: $sender\n"; 751: } 752: if (defined($opt_p)) { 753: print OUT "Precedence: $opt_p\n"; 754: } The result of this change would mean you have to leave the "sender =" in the .config file for your list blank. The other scripts that depend on this value would use the default of listname-request, but the resend script would only add the Sender: header if that variable contained a value. Sorry, I also made an assumption in my previous sentence. I am assUming that "-f sender" is not used in the alias for the list either. Finally, you could take a really easy way out, and just comment out line 749 of the resend script. 748: # add new header fields 749: # print OUT "Sender: $sender\n"; Dan Liston From majordomo-users-owner@greatcircle.com Tue Mar 11 10:32:56 2003 Received: from smtp.comcast.net (smtp.comcast.net [24.153.64.2]) by mycroft.greatcircle.com (Postfix) with ESMTP id 52C7A195F7F for ; Tue, 11 Mar 2003 10:32:55 -0800 (PST) Received: from icomcast.net (lb-ldap-155.icomcast.net [172.20.3.155]) by mtaout02.icomcast.net (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003)) with ESMTP id <0HBL008BVKUURN@mtaout02.icomcast.net> for majordomo-users@greatcircle.com; Tue, 11 Mar 2003 13:32:54 -0500 (EST) Received: from [172.20.3.196] by msgstore01.icomcast.net (mshttpd); Tue, 11 Mar 2003 13:32:44 -0500 Date: Tue, 11 Mar 2003 13:32:44 -0500 From: Christian Ready Subject: Denying attachments To: majordomo-users@greatcircle.com Message-id: <246303247fca.247fca246303@icomcast.net> MIME-version: 1.0 X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.12 (built Feb 13 2003) Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7BIT Content-disposition: inline X-Accept-Language: en X-Archive-Number: 200303/61 X-Sequence-Number: 2932 Greetings, I am considering making a change in my mailing list configurations. I'd like to know if I can prevent attachments from being sent and if I can have it set up such that if a user sends an attachment to the list, it would reply back to them with a message that I would define somewhere (e.g., "Your post was denied because you attached a file. This is a no-no in our organization."). Does anyone know how this would be accomplished in majordomo 2.0? Thanks! Chris From majordomo-users-owner@greatcircle.com Tue Mar 11 10:57:51 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 337F0195F8D for ; Tue, 11 Mar 2003 10:57:50 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2BJ3fEt012112; Tue, 11 Mar 2003 13:03:41 -0600 Message-ID: <3E6E3210.4000501@sonny.org> Date: Tue, 11 Mar 2003 12:59:28 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christian Ready , majordomo-users@greatcircle.com Subject: Re: Denying attachments References: <246303247fca.247fca246303@icomcast.net> In-Reply-To: <246303247fca.247fca246303@icomcast.net> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/62 X-Sequence-Number: 2933 Christian Ready wrote: > Greetings, > > I am considering making a change in my mailing list configurations. > I'd like to know if I can prevent attachments from being sent and if I > can have it set up such that if a user sends an attachment to the list, > it would reply back to them with a message that I would define > somewhere (e.g., "Your post was denied because you attached a file. > This is a no-no in our organization."). > > Does anyone know how this would be accomplished in majordomo 2.0? > > Thanks! > Chris Have you looked at "demime" to see if it will serve your purpose? http://scifi.squawk.com/demime.html Dan Liston From majordomo-users-owner@greatcircle.com Tue Mar 11 12:21:15 2003 Received: from mail.zeelandnet.nl (mail5.zeelandnet.nl [212.115.192.155]) by mycroft.greatcircle.com (Postfix) with ESMTP id 5D387195A56 for ; Tue, 11 Mar 2003 12:21:14 -0800 (PST) Received: from 10.255.255.155 (unknown [10.255.255.153]) by mail (Postfix) with SMTP id E06C23834F for ; Tue, 11 Mar 2003 21:21:13 +0100 (CET) Received: from celeron566 (kbl-gs201.zeelandnet.nl [62.238.64.201]) by mail.zeelandnet.nl (Postfix) with ESMTP id 914D7382ED for ; Tue, 11 Mar 2003 21:21:13 +0100 (CET) From: "Theo Richel" To: Subject: configure Date: Tue, 11 Mar 2003 21:21:13 +0100 Message-ID: <02ba01c2e80b$c34d1bd0$0100a8c0@richel.kpl> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <20030311173031.7A20F195B3D@mycroft.greatcircle.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Archive-Number: 200303/63 X-Sequence-Number: 2934 In the install procedure for Majorcool it is said to 'Run the Configure script ('sh Configure')' Where and how do I do this? Thank you very much Theo Richel From majordomo-users-owner@greatcircle.com Tue Mar 11 12:48:49 2003 Received: from wizard.firn.edu (wizard.firn.edu [150.176.12.39]) by mycroft.greatcircle.com (Postfix) with ESMTP id 5EA0A1959DC for ; Tue, 11 Mar 2003 12:48:46 -0800 (PST) Received: from CONVERSION-DAEMON by WIZARD.FIRN.EDU (PMDF V5.2-33 #41769) id <01KTEJAFXPYO00AGD3@WIZARD.FIRN.EDU> for majordomo-users@greatcircle.com; Tue, 11 Mar 2003 15:42:05 EST Received: from popmail.firn.edu ([204.194.36.191]) by WIZARD.FIRN.EDU (PMDF V5.2-33 #41769) with SMTP id <01KTEJAFNS2I00B0RK@WIZARD.FIRN.EDU>; Tue, 11 Mar 2003 15:42:05 -0500 (EST) Date: Tue, 11 Mar 2003 15:48:41 -0500 From: Paul Diaguila Subject: Re: new install - can't send mail to list To: Daniel Liston Cc: majordomo-users@greatcircle.com Message-id: <3E6E4BA9.7040609@popmail.firn.edu> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en References: <3E6CF218.50707@popmail.firn.edu> <3E6D6A8F.9070403@sonny.org> X-Archive-Number: 200303/64 X-Sequence-Number: 2935 Solved group writable problem with the chmod on the files and directory permissions. Now I see this: ----- The following addresses had permanent fatal errors ----- include:/usr/majordomo-1.94.5/lists/test-l (reason: Can't create output) (expanded from: Paul Diaguila wrote: > >> >> Greetings... >> >> Have installed Majordomo-1.94.5 on FreeBSD. Am able to retrieve >> command replies such as help ok, but after creating a list test-l, >> I'm get the following error: >> >> 550 5.2.4 :include:/usr/majordomo-1.94.5/lists/test-l... Cannot open >> /usr/majordomo-1.94.5/lists/test-l: Group writable directory >> >> Went so far as to set the directory and file permissions to owner, >> group, and world read, exe, and write, but no change... Have >> majordomo set as trusted in the sendmail.cnf and submit.cf file. >> Any ideas would be appreciated...... >> > This was the wrong direction. Sendmail was complaining that the > directory > was already "group" writable. You need to take away group write > permission > on the entire tree up to and including the directory your lists live in. > > You did the right thing setting sendmail to trust majordomo though. > > chmod 755 or 751 the majordomo and majordomo/lists directory, but ALSO > chmod 755 "/" and "/usr" > > Dan Liston > > PS. In the above comment, majordomo = majordomo-1.94.5 > > > From majordomo-users-owner@greatcircle.com Tue Mar 11 13:41:35 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 7F693195A20 for ; Tue, 11 Mar 2003 13:41:33 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2BLlSEt012945; Tue, 11 Mar 2003 15:47:28 -0600 Message-ID: <3E6E589D.50504@sonny.org> Date: Tue, 11 Mar 2003 15:43:57 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Theo Richel Cc: majordomo-users@greatcircle.com Subject: Re: configure References: <02ba01c2e80b$c34d1bd0$0100a8c0@richel.kpl> In-Reply-To: <02ba01c2e80b$c34d1bd0$0100a8c0@richel.kpl> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/65 X-Sequence-Number: 2936 At the shell prompt of the unix machine you are installing majorcool to, and in the installation directory, type: sh Configure and hit the enter key on your keyboard. You will probably have to be the root user to do this successfully. Dan Liston Theo Richel wrote: > In the install procedure for Majorcool it is said to > 'Run the Configure script ('sh Configure')' > Where and how do I do this? > > Thank you very much > Theo Richel From majordomo-users-owner@greatcircle.com Tue Mar 11 14:30:03 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 31FB1195A20 for ; Tue, 11 Mar 2003 14:29:59 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2BMZtEt013282; Tue, 11 Mar 2003 16:35:55 -0600 Message-ID: <3E6E63F7.5070904@sonny.org> Date: Tue, 11 Mar 2003 16:32:23 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Paul Diaguila Cc: majordomo-users@greatcircle.com Subject: Re: new install - can't send mail to list References: <3E6CF218.50707@popmail.firn.edu> <3E6D6A8F.9070403@sonny.org> <3E6E4BA9.7040609@popmail.firn.edu> In-Reply-To: <3E6E4BA9.7040609@popmail.firn.edu> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/66 X-Sequence-Number: 2937 What are the permissions and ownership on your */spool/mqueue directory? The only places I can think output would be created is in the outgoing mqueue. I'm not up to speed with sendmail on FreeBSD, but if it defaults to using smrsh, you need to make sure your link to majordomo's wrapper is in the right location too. Is it possible your partition was full? What about /tmp? Dan Liston Paul Diaguila wrote: > Solved group writable problem with the chmod on the files and directory > permissions. Now I see this: > ----- The following addresses had permanent fatal errors ----- > include:/usr/majordomo-1.94.5/lists/test-l (reason: Can't create output) > (expanded from: > Also was able send mail to test-l-outgoing and it was delivered to the > people on the list, which indicates a sendmail problem....?? > > thanks again... > > Paul > > > Daniel Liston wrote: > >> Paul Diaguila wrote: >> >>> >>> Greetings... >>> >>> Have installed Majordomo-1.94.5 on FreeBSD. Am able to retrieve >>> command replies such as help ok, but after creating a list test-l, >>> I'm get the following error: >>> >>> 550 5.2.4 :include:/usr/majordomo-1.94.5/lists/test-l... Cannot open >>> /usr/majordomo-1.94.5/lists/test-l: Group writable directory >>> >>> Went so far as to set the directory and file permissions to owner, >>> group, and world read, exe, and write, but no change... Have >>> majordomo set as trusted in the sendmail.cnf and submit.cf file. >>> Any ideas would be appreciated...... >>> >> This was the wrong direction. Sendmail was complaining that the >> directory >> was already "group" writable. You need to take away group write >> permission >> on the entire tree up to and including the directory your lists live in. >> >> You did the right thing setting sendmail to trust majordomo though. >> >> chmod 755 or 751 the majordomo and majordomo/lists directory, but ALSO >> chmod 755 "/" and "/usr" >> >> Dan Liston >> >> PS. In the above comment, majordomo = majordomo-1.94.5 >> >> >> > From majordomo-users-owner@greatcircle.com Wed Mar 12 01:34:50 2003 Received: from msg.ecetra.com (dollar.ecetra.com [193.164.224.209]) by mycroft.greatcircle.com (Postfix) with ESMTP id 713C7195F41 for ; Wed, 12 Mar 2003 01:34:48 -0800 (PST) Received: from vie-ms01.office.ecetra.com (vie-ms01.office.ecetra.com [10.251.154.11]) by msg.ecetra.com (8.11.6/8.9.3) with ESMTP id h2C9Ykq14329 for ; Wed, 12 Mar 2003 10:34:46 +0100 Received: from vie-ms02.office.ecetra.com ([10.251.154.13]) by vie-ms01.office.ecetra.com with Microsoft SMTPSVC(5.0.2195.4453); Wed, 12 Mar 2003 10:34:46 +0100 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: How to change the the "to:" field for mailing list recipients X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Wed, 12 Mar 2003 10:25:30 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: How to change the the "to:" field for mailing list recipients Thread-Index: AcLm80k0w6j+7FRiTj6Gu9Y/XlnZyw== From: "Brankovic, Dragan" To: X-OriginalArrivalTime: 12 Mar 2003 09:34:46.0642 (UTC) FILETIME=[9EB9B520:01C2E87A] X-Archive-Number: 200303/67 X-Sequence-Number: 2938 Dear all, we are running majordomo-1.94.5 on redhat linux and sendmail-8.11 with perl= -5.005 ! The problem is the following: When sending to a list the recipients see in the "to:" field listname@hostn= ame+domain ! What we would like is that it looks like this "to: listname@do= main.com! Is there any way to change this ? Dragan Brankovic Unix System Administrator ____________________________________________ ecetra Central European e-Finance AG =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF Neutorgasse 2 | A-1010 Vienna Tel: +43-1-536 89-17732 Mobil: +43-664-2024823 Fax: +43-1-536 89-17719 http://www.ecetra.com From majordomo-users-owner@greatcircle.com Wed Mar 12 01:34:55 2003 Received: from msg.ecetra.com (dollar.ecetra.com [193.164.224.209]) by mycroft.greatcircle.com (Postfix) with ESMTP id 907EB195F6B for ; Wed, 12 Mar 2003 01:34:48 -0800 (PST) Received: from vie-ms01.office.ecetra.com (vie-ms01.office.ecetra.com [10.251.154.11]) by msg.ecetra.com (8.11.6/8.9.3) with ESMTP id h2C9Ylq14338 for ; Wed, 12 Mar 2003 10:34:47 +0100 Received: from vie-ms02.office.ecetra.com ([10.251.154.13]) by vie-ms01.office.ecetra.com with Microsoft SMTPSVC(5.0.2195.4453); Wed, 12 Mar 2003 10:34:46 +0100 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Wed, 12 Mar 2003 10:27:32 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Index: AcLm80k0w6j+7FRiTj6Gu9Y/XlnZyw== From: "Brankovic, Dragan" To: X-OriginalArrivalTime: 12 Mar 2003 09:34:46.0642 (UTC) FILETIME=[9EB9B520:01C2E87A] X-Archive-Number: 200303/68 X-Sequence-Number: 2939 show Dragan Brankovic Unix System Administrator ____________________________________________ ecetra Central European e-Finance AG =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF Neutorgasse 2 | A-1010 Vienna Tel: +43-1-536 89-17732 Mobil: +43-664-2024823 Fax: +43-1-536 89-17719 http://www.ecetra.com From majordomo-users-owner@greatcircle.com Wed Mar 12 01:37:30 2003 Received: from msg.ecetra.com (dollar.ecetra.com [193.164.224.209]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8CF3B195F46 for ; Wed, 12 Mar 2003 01:34:48 -0800 (PST) Received: from vie-ms01.office.ecetra.com (vie-ms01.office.ecetra.com [10.251.154.11]) by msg.ecetra.com (8.11.6/8.9.3) with ESMTP id h2C9Ylq14335 for ; Wed, 12 Mar 2003 10:34:47 +0100 Received: from vie-ms02.office.ecetra.com ([10.251.154.13]) by vie-ms01.office.ecetra.com with Microsoft SMTPSVC(5.0.2195.4453); Wed, 12 Mar 2003 10:34:46 +0100 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Wed, 12 Mar 2003 10:29:25 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Index: AcLoed8XGvKd8NOoRuibjq7qoNg4hg== From: "Brankovic, Dragan" To: X-OriginalArrivalTime: 12 Mar 2003 09:34:46.0642 (UTC) FILETIME=[9EB9B520:01C2E87A] X-Archive-Number: 200303/69 X-Sequence-Number: 2940 show Dragan.Brankovic@ecetra.com Dragan Brankovic Unix System Administrator ____________________________________________ ecetra Central European e-Finance AG =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= =AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF Neutorgasse 2 | A-1010 Vienna Tel: +43-1-536 89-17732 Mobil: +43-664-2024823 Fax: +43-1-536 89-17719 http://www.ecetra.com From majordomo-users-owner@greatcircle.com Wed Mar 12 04:37:21 2003 Received: from hotmail.com (oe48.law8.hotmail.com [216.33.240.20]) by mycroft.greatcircle.com (Postfix) with ESMTP id 3618D195A4E for ; Wed, 12 Mar 2003 04:37:20 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 12 Mar 2003 04:37:19 -0800 X-Originating-IP: [216.112.124.12] From: "Tony Smith" To: Subject: Fw: How to change the the "to:" field for mailing list recipients Date: Wed, 12 Mar 2003 07:37:17 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: X-OriginalArrivalTime: 12 Mar 2003 12:37:19.0708 (UTC) FILETIME=[1F42F1C0:01C2E894] X-Archive-Number: 200303/70 X-Sequence-Number: 2941 Three ways: in majordomo.cf, specify $whereami = "domain.com" (to specify it globally) or in listname.config, specify resend_host = domain.com (to specify it for a particular list) or you can specify it directly in the resend command with -h domain.com (to specify it for a particular list) -tony ----- Original Message ----- Sent: Wednesday, March 12, 2003 4:25 AM Subject: How to change the the "to:" field for mailing list recipients Dear all, we are running majordomo-1.94.5 on redhat linux and sendmail-8.11 with perl-5.005 ! The problem is the following: When sending to a list the recipients see in the "to:" field listname@hostname+domain ! What we would like is that it looks like this "to: listname@domain.com! Is there any way to change this ? Dragan Brankovic Unix System Administrator ____________________________________________ ecetra Central European e-Finance AG ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ Neutorgasse 2 | A-1010 Vienna Tel: +43-1-536 89-17732 Mobil: +43-664-2024823 Fax: +43-1-536 89-17719 http://www.ecetra.com From majordomo-users-owner@greatcircle.com Wed Mar 12 06:47:30 2003 Received: from skipper.averillpark.net (alb-24-194-112-77.nycap.rr.com [24.194.112.77]) by mycroft.greatcircle.com (Postfix) with ESMTP id 6EBCD195FCE for ; Wed, 12 Mar 2003 06:47:21 -0800 (PST) Received: from rwelty by skipper.averillpark.net with local (Exim 4.10) id 18t7TQ-0005iA-00 for majordomo-users@greatcircle.com; Wed, 12 Mar 2003 09:44:52 -0500 Date: Wed, 12 Mar 2003 09:44:52 -0500 (EST) From: Richard Welty Subject: offtopic mhonarc question To: majordomo-users@greatcircle.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE X-Mailer: Mahogany 0.64 'Sparc', compiled for Linux 2.4.9-13 i686 Message-Id: X-Archive-Number: 200303/71 X-Sequence-Number: 2942 this is OT, so perhaps replies offlist would be best. does anyone have any pointers to scripts (perl would probably be best) for monthly rotation of mhonarc archives (that is, creating a directory for the next month or next month and year, generating a web page to point to the monthly archives, etc.)? i doubt it's that hard to write, but i'm not a perl hacker and i don't have the time right now to become a good enough one to do it myself. thanks, richard -- Richard Welty rwelty@suespammers.org Averill Park Networking rwelty@averillpark.net Unix, Linux, IP Network Engineering, Security rwelty@krusty-motorsports.com 518-573-7592 From majordomo-users-owner@greatcircle.com Wed Mar 12 14:28:25 2003 Received: from smtp.comcast.net (smtp.comcast.net [24.153.64.2]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8C868195AD3 for ; Wed, 12 Mar 2003 14:28:24 -0800 (PST) Received: from desktop1 (pcp01823258pcs.howard01.md.comcast.net [68.54.95.43]) by mtaout01.icomcast.net (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003)) with SMTP id <0HBN002T5QFADS@mtaout01.icomcast.net> for majordomo-users@greatcircle.com; Wed, 12 Mar 2003 17:28:23 -0500 (EST) Date: Wed, 12 Mar 2003 17:29:44 -0500 From: Christian Ready Subject: Re: Denying attachments In-reply-to: <3E6E3210.4000501@sonny.org> To: Daniel Liston , majordomo-users@greatcircle.com Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Archive-Number: 200303/72 X-Sequence-Number: 2943 Thanks for referring me to Demime. I don't think that's what I'm looking for, though. I was wondering if there was a config setting in majordomo that would send a message back to the sender informing them that they are not allowed to send messages to our list that have attachments. I know that there are some mime types that I can deny, but I wanted to see if I can deny all mime types. Is that possible? Chris > -----Original Message----- > From: majordomo-users-owner@greatcircle.com > [mailto:majordomo-users-owner@greatcircle.com]On Behalf Of Daniel Liston > Sent: Tuesday, March 11, 2003 1:59 PM > To: Christian Ready; majordomo-users@greatcircle.com > Subject: Re: Denying attachments > > > Christian Ready wrote: > > Greetings, > > > > I am considering making a change in my mailing list configurations. > > I'd like to know if I can prevent attachments from being sent and if I > > can have it set up such that if a user sends an attachment to the list, > > it would reply back to them with a message that I would define > > somewhere (e.g., "Your post was denied because you attached a file. > > This is a no-no in our organization."). > > > > Does anyone know how this would be accomplished in majordomo 2.0? > > > > Thanks! > > Chris > > Have you looked at "demime" to see if it will serve your purpose? > > http://scifi.squawk.com/demime.html > > Dan Liston > From majordomo-users-owner@greatcircle.com Wed Mar 12 15:05:56 2003 Received: from mail.zeelandnet.nl (mail5.zeelandnet.nl [212.115.192.155]) by mycroft.greatcircle.com (Postfix) with ESMTP id 873E41959F1 for ; Wed, 12 Mar 2003 15:05:54 -0800 (PST) Received: from 10.255.255.155 (unknown [10.255.255.153]) by mail (Postfix) with SMTP id 1810C383F6 for ; Thu, 13 Mar 2003 00:05:53 +0100 (CET) Received: from celeron566 (kbl-gs201.zeelandnet.nl [62.238.64.201]) by mail.zeelandnet.nl (Postfix) with ESMTP id AC55238469 for ; Thu, 13 Mar 2003 00:05:52 +0100 (CET) From: "Theo Richel" To: Subject: install problems Date: Thu, 13 Mar 2003 00:05:52 +0100 Message-ID: <03f701c2e8eb$edff10f0$0100a8c0@richel.kpl> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Archive-Number: 200303/73 X-Sequence-Number: 2944 When I try to install Majorcool the following happens. Has anyone an idea what I should do? See below. Thank you Theo Richel bash-2.04$ sh Configure : command not found : command not found 'onfigure: line 9: syntax error near unexpected token `$$) 'onfigure: line 9: `export PATH || (echo "This isn't sh. Feeding myself to sh."; sh $0 $*; kill $$) By the way: the command ./ Configure it says: No such file or directory From majordomo-users-owner@greatcircle.com Wed Mar 12 16:35:24 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 0E05F195A3D for ; Wed, 12 Mar 2003 16:35:23 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2D0fpEt022863; Wed, 12 Mar 2003 18:41:51 -0600 Message-ID: <3E6FD24A.8040108@sonny.org> Date: Wed, 12 Mar 2003 18:35:22 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christian Ready Cc: majordomo-users@greatcircle.com Subject: Re: Denying attachments References: In-Reply-To: X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/74 X-Sequence-Number: 2945 Since demime has the capability of stripping the attachments off the messages, email could still come to the list without requiring a notification to the sender about bouncing their message. If comments/complaints come in about the missing attachment, you can point them to your FAQ or AUA for that list. Adding these to the (global_)?taboo_headers section could help; /^Content-type: multipart/i /boundary=/i but they would not bounce to the sender, they would bounce to the owner or moderator. This person would then send out a notice that the attachment bearing message was denied distribution. With the proper filters in place, that notice could be automated as well. Dan Liston Christian Ready wrote: > Thanks for referring me to Demime. I don't think that's what I'm looking > for, though. > > I was wondering if there was a config setting in majordomo that would send a > message back to the sender informing them that they are not allowed to send > messages to our list that have attachments. I know that there are some mime > types that I can deny, but I wanted to see if I can deny all mime types. > > Is that possible? > > Chris > > >>-----Original Message----- >>From: majordomo-users-owner@greatcircle.com >>[mailto:majordomo-users-owner@greatcircle.com]On Behalf Of Daniel Liston >>Sent: Tuesday, March 11, 2003 1:59 PM >>To: Christian Ready; majordomo-users@greatcircle.com >>Subject: Re: Denying attachments >> >> >>Christian Ready wrote: >> >>>Greetings, >>> >>>I am considering making a change in my mailing list configurations. >>>I'd like to know if I can prevent attachments from being sent and if I >>>can have it set up such that if a user sends an attachment to the list, >>>it would reply back to them with a message that I would define >>>somewhere (e.g., "Your post was denied because you attached a file. >>>This is a no-no in our organization."). >>> >>>Does anyone know how this would be accomplished in majordomo 2.0? >>> >>>Thanks! >>>Chris >> >>Have you looked at "demime" to see if it will serve your purpose? >> >>http://scifi.squawk.com/demime.html >> >>Dan Liston >> From majordomo-users-owner@greatcircle.com Wed Mar 12 17:04:11 2003 Received: from wrenkasky.com (esson.net [216.102.129.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 972C4196215 for ; Wed, 12 Mar 2003 17:04:09 -0800 (PST) Received: from ekasky.wrenkasky.com (ekasky.priority.usc.edu [128.125.63.168]) by wrenkasky.com (8.12.5/8.12.5) with ESMTP id h2D14E4f007869 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT); Wed, 12 Mar 2003 17:04:15 -0800 Message-Id: <5.1.1.6.2.20030312165629.00abebc0@mail.esson.net> X-Sender: ed@mail.esson.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Wed, 12 Mar 2003 17:04:05 -0800 To: Christian Ready From: Ed Kasky Subject: Re: Denying attachments Cc: majordomo-users@greatcircle.com In-Reply-To: <3E6FD24A.8040108@sonny.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200303/75 X-Sequence-Number: 2946 To add what Dan had to say, demime also prints a little notification at the end of the offending email that it stripped the attachment. The sender would then see that it got stripped, get mad at you, threaten to force a coup on whoever installed demime and question why he/she can't send those pictures to an email list.... Of course, your faq will plainly state that attachments will be stripped and should only be sent to private email addresses and only if requested. They will then tell you they never saw the faq even though it was asked of them to read it before posting to the list. "What intro email? I never saw any stinking intro email!! You mean that thing I got years ago that said don't delete? I deleted it!" And I got this sardonic after only administering half a dozen lists over the years.... }B->) Ed Kasky Los Angeles, CA . . . . . . . . Growth for the sake of growth is the ideology of the cancer cell. -John Nichols, novelist (1940- ) At 06:35 PM Wednesday, 3/12/2003, Daniel Liston wrote -=> >Since demime has the capability of stripping the attachments >off the messages, email could still come to the list without >requiring a notification to the sender about bouncing their >message. If comments/complaints come in about the missing >attachment, you can point them to your FAQ or AUA for that >list. > >Adding these to the (global_)?taboo_headers section could help; > >/^Content-type: multipart/i >/boundary=/i > >but they would not bounce to the sender, they would bounce to the >owner or moderator. This person would then send out a notice that >the attachment bearing message was denied distribution. With the >proper filters in place, that notice could be automated as well. > >Dan Liston > >Christian Ready wrote: >>Thanks for referring me to Demime. I don't think that's what I'm looking >>for, though. >>I was wondering if there was a config setting in majordomo that would send a >>message back to the sender informing them that they are not allowed to send >>messages to our list that have attachments. I know that there are some mime >>types that I can deny, but I wanted to see if I can deny all mime types. >>Is that possible? >>Chris >> >>>-----Original Message----- >>>From: majordomo-users-owner@greatcircle.com >>>[mailto:majordomo-users-owner@greatcircle.com]On Behalf Of Daniel Liston >>>Sent: Tuesday, March 11, 2003 1:59 PM >>>To: Christian Ready; majordomo-users@greatcircle.com >>>Subject: Re: Denying attachments >>> >>> >>>Christian Ready wrote: >>> >>>>Greetings, >>>> >>>>I am considering making a change in my mailing list configurations. >>>>I'd like to know if I can prevent attachments from being sent and if I >>>>can have it set up such that if a user sends an attachment to the list, >>>>it would reply back to them with a message that I would define >>>>somewhere (e.g., "Your post was denied because you attached a file. >>>>This is a no-no in our organization."). >>>> >>>>Does anyone know how this would be accomplished in majordomo 2.0? From majordomo-users-owner@greatcircle.com Wed Mar 12 17:49:17 2003 Received: from mail.tellurian.net (mail.tellurian.net [216.182.1.8]) by mycroft.greatcircle.com (Postfix) with ESMTP id F25F41963DE for ; Wed, 12 Mar 2003 17:49:13 -0800 (PST) Received: from walt99.betan.com (home.betandata.com [216.182.19.225]) by tellurian.com (Rockliffe SMTPRA 5.2.5) with ESMTP id for ; Wed, 12 Mar 2003 20:49:10 -0500 Message-Id: <5.1.1.5.2.20030312204808.00a7e090@popd.betan.net> X-Sender: walterbetanc@popd.betan.net X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Wed, 12 Mar 2003 20:48:56 -0500 To: majordomo-users@greatcircle.com From: Walt Subject: Re: Denying attachments In-Reply-To: <5.1.1.6.2.20030312165629.00abebc0@mail.esson.net> References: <3E6FD24A.8040108@sonny.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Archive-Number: 200303/76 X-Sequence-Number: 2947 An ugly footer, plainly stating no attachments might work. Walt At 08:04 PM 3/12/03, you wrote: >To add what Dan had to say, demime also prints a little notification at the end of the offending email that it stripped the attachment. > >The sender would then see that it got stripped, get mad at you, threaten to force a coup on whoever installed demime and question why he/she can't send those pictures to an email list.... > >Of course, your faq will plainly state that attachments will be stripped and should only be sent to private email addresses and only if requested. They will then tell you they never saw the faq even though it was asked of them to read it before posting to the list. > >"What intro email? I never saw any stinking intro email!! You mean that thing I got years ago that said don't delete? I deleted it!" > >And I got this sardonic after only administering half a dozen lists over the years.... > >}B->) > >Ed Kasky >Los Angeles, CA >. . . . . . . . >Growth for the sake of growth is the ideology of the cancer cell. > -John Nichols, novelist (1940- ) > >At 06:35 PM Wednesday, 3/12/2003, Daniel Liston wrote -=> > >>Since demime has the capability of stripping the attachments >>off the messages, email could still come to the list without >>requiring a notification to the sender about bouncing their >>message. If comments/complaints come in about the missing >>attachment, you can point them to your FAQ or AUA for that >>list. >> >>Adding these to the (global_)?taboo_headers section could help; >> >>/^Content-type: multipart/i >>/boundary=/i >> >>but they would not bounce to the sender, they would bounce to the >>owner or moderator. This person would then send out a notice that >>the attachment bearing message was denied distribution. With the >>proper filters in place, that notice could be automated as well. >> >>Dan Liston >> >>Christian Ready wrote: >>>Thanks for referring me to Demime. I don't think that's what I'm looking >>>for, though. >>>I was wondering if there was a config setting in majordomo that would send a >>>message back to the sender informing them that they are not allowed to send >>>messages to our list that have attachments. I know that there are some mime >>>types that I can deny, but I wanted to see if I can deny all mime types. >>>Is that possible? >>>Chris >>> >>>>-----Original Message----- >>>>From: majordomo-users-owner@greatcircle.com >>>>[mailto:majordomo-users-owner@greatcircle.com]On Behalf Of Daniel Liston >>>>Sent: Tuesday, March 11, 2003 1:59 PM >>>>To: Christian Ready; majordomo-users@greatcircle.com >>>>Subject: Re: Denying attachments >>>> >>>> >>>>Christian Ready wrote: >>>> >>>>>Greetings, >>>>> >>>>>I am considering making a change in my mailing list configurations. >>>>>I'd like to know if I can prevent attachments from being sent and if I >>>>>can have it set up such that if a user sends an attachment to the list, >>>>>it would reply back to them with a message that I would define >>>>>somewhere (e.g., "Your post was denied because you attached a file. >>>>>This is a no-no in our organization."). >>>>> >>>>>Does anyone know how this would be accomplished in majordomo 2.0? > > From majordomo-users-owner@greatcircle.com Thu Mar 13 09:29:38 2003 Received: from proteus.obantec.net (unknown [213.171.197.193]) by mycroft.greatcircle.com (Postfix) with ESMTP id 4E286195A74 for ; Thu, 13 Mar 2003 09:29:01 -0800 (PST) Received: from gamma (public1-leed4-5-cust15.leed.broadband.ntl.com [80.0.7.15]) (authenticated) by proteus.obantec.net (8.10.2/8.10.2) with ESMTP id h2DHSwN15370 for ; Thu, 13 Mar 2003 17:28:58 GMT Message-ID: <288c01c2e985$edbb6a40$0a01a8c0@gamma> From: "Obantec Support" To: Subject: fixed group writeable problem but now cannot open Date: Thu, 13 Mar 2003 17:28:09 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Archive-Number: 200303/77 X-Sequence-Number: 2948 Hi did some googling and fixed sendmail 8.12.6 on RH 7.2 (added dontblamegroupwriteable since removing world writeable caused cannot open error). now when i send an email with approved password to a list created with webmin i get (domain changed to protect the address). ----- The following addresses had permanent fatal errors ----- :include:/usr/local/majordomo/lists/0845users (expanded from: <0845users-list@somedomain.xyz>) ----- Transcript of session follows ----- 550 5.2.4 :include:/usr/local/majordomo/lists/0845users... Cannot open /usr/local/majordomo/lists/0845users: Permission denied i would have preferred to remove world writeable bits but could not get permissions right. majordomo is using user=majordomo group=daemon Mark -- Obantec Support www.obantec.net WebHosting and Domains Nominet UK Tag Holder From majordomo-users-owner@greatcircle.com Thu Mar 13 19:00:51 2003 Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101]) by mycroft.greatcircle.com (Postfix) with ESMTP id C164F195F6C for ; Thu, 13 Mar 2003 19:00:17 -0800 (PST) Received: from pobox.mot.com (pobox.mot.com [129.188.137.100]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id h2E30DPO025438 for ; Thu, 13 Mar 2003 20:00:13 -0700 (MST) Received: [from zch07exb01.corp.mot.com (zch07exb01.corp.mot.com [200.3.1.150]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id UAA19468 for ; Thu, 13 Mar 2003 20:00:11 -0700 (MST)] Received: by zch07exb01.corp.mot.com with Internet Mail Service (5.5.2656.59) id ; Fri, 14 Mar 2003 11:00:08 +0800 Message-ID: <1B2D9E22CDF7D611BD2200805FA7B779181C89@hou204.cig.mcel.mot.com> From: Chen Jervy-qch1408 To: Chen Jervy-qch1408 , "'Daniel Liston'" Cc: "'Majordomo-Users@greatcircle.com'" Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 Date: Fri, 14 Mar 2003 10:53:49 +0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain X-Archive-Number: 200303/78 X-Sequence-Number: 2949 Dan, Any idea will be appreciated , I tried it with many way but failed, thanks. Kind Regards Jervy Chen China TCSG-ITS * Fear can hold you prisoner * * Hope can set you free * -----Original Message----- From: Chen Jervy-qch1408 Sent: Monday, March 10, 2003 10:54 AM To: 'Daniel Liston' Cc: Majordomo-Users@greatcircle.com Subject: RE: majordomo problem after upgrading the sendmail to 8.12.8 Dan, Only one question remained, how to reconfigure the majorcool to run as the majordomo user and group (what configuration file)? I check the daemon status when I submitted the request on the web, "majorcool" daemon always run with nobody permission. Thanks a lot. > 4. Restart sendmail >Sendmail is definitely more strict on security than it used to be. You might have to reconfigure your majorcool to run as the majordomo user and group. Kind Regards Jervy Chen * Fear can hold you prisoner * * Hope can set you free * -----Original Message----- From: Daniel Liston [mailto:dliston@sonny.org] Sent: Friday, March 07, 2003 7:42 PM To: Chen Jervy-qch1408 Cc: Majordomo-Users@greatcircle.com Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 Chen Jervy-qch1408 wrote: > Dan, > > Thanks for your help, the following is answer, please try to give me more point form you. > 1. Upgrade majordomo to 1.94.5 (or higher) > This is my deadline to follow it. > 2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 > I use 8.12.8 sendmail.cf DZ8.12.8 > 3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf > I tried it but failed Please describe "failed". I use this successfully; O AliasFile=/etc/aliases,/etc/mail/majordomo.aliases The same could be written as two separate lines like; O AliasFile=/etc/aliases O AliasFile=/etc/mail/majordomo.aliases > 3a. Create a symbolic link from your majordomo_aliases to /etc/mail > It could not work anymore. I do not understand what you mean. Majordomo could not work, or sendmail? lrwxrwxrwx 1 root root 31 May 5 2002 /etc/mail/majordomo.aliases -> ../../var/lib/majordomo/aliases > 4. Restart sendmail > > > Now, I resolved some problems, I used "majordomo" account to replace "smmsp" in sendmail, so aliases can work as normal. > > But web interface (majorcool) could not work for all features, it always displayed permission error as the following messages in IE. > : ABORT > shlock: '/usr/majordomo/majordomo-1.94.4' is not writable by UID 60001 GID 60001 > > Recipient names must be specified > > #ls -ld /usr/majordomo/majordomo-1.94.4 > drwxr-xr-x 13 majordomomajordomo 2048 Mar 5 21:06 /usr/majordomo/majordomo-1.94.4 > > 60001 is "nobody" account & group, it seems that sendmail audit more strictly. Sendmail is definitely more strict on security than it used to be. You might have to reconfigure your majorcool to run as the majordomo user and group. Dan Liston > > Kind Regards > Jervy Chen > > * Fear can hold you prisoner * > * Hope can set you free * > > > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Thursday, March 06, 2003 2:33 AM > To: Chen Jervy-qch1408 > Cc: Majordomo-Users@greatcircle.com > Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 > > > Hi, > > Several points here, > > 1. Upgrade majordomo to 1.94.5 (or higher) > 2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 > 3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf > 3a. Create a symbolic link from your majordomo_aliases to /etc/mail > 4. Restart sendmail > > Dan Liston > > > Chen Jervy-qch1408 wrote: > >>Hello, guys, >> >>Could anybody help me to resolve the following problem? Any idea will be >>appreciated! >> >>I am majordomo admin and have a majordomo server (Sun Ultra 2), >>majordomo 1.94.4 and sendmail 8.8.5 installed on it, it works fine for 2 >>years already after I setup it. The following is my setting before in >>/etc/mail/sendmail.cf. >> >>OA/usr/majordomo/majordomo-1.94.4/majordomo_aliases >> >>Now, for the security reason, I have to upgrade sendmail from 8.8.5 to >>8.12.8, I finished it already and added the above line in sendmail.cf >>also but majordomo could not work as normal. The following is error >>message when I try to send mail to majordomo list but it can send email >>to normal user successfully. >> >>Mar 5 11:55:44 zchps01 sendmail[764]: h253tip9000764: SYSERR(root): dbm >>map "Alias0": unsafe map file >>/usr/majordomo/majordomo-1.94.4/majordomo_aliases: No such file or directory >> >>Here is the output when I try to send out majordomo list. >> >># /usr/lib/sendmail -v -bi >>WARNING: World writable directory /var/spool/mqueue >>/etc/mail/aliases: 9 aliases, longest 52 bytes, 294 bytes total >>WARNING: Group writable directory /usr/majordomo >>WARNING: Group writable directory /usr/majordomo/majordomo-1.94.4 >>newaliases: cannot open >>/usr/majordomo/majordomo-1.94.4/majordomo_aliases: Executable files not >>allowed >> >># /usr/lib/sendmail -v test >>. >>test... Connecting to [127.0.0.1] via relay... >>220 majordomo.motor.com ESMTP Sendmail 8.12.8/8.12.8; Wed, 5 Mar 2003 >>14:46:36 +0800 (CST) >> >>> EHLO majordomo.motor.com >>250-majordomo.motor.com Hello localhost [127.0.0.1], pleased to meet you >>250-ENHANCEDSTATUSCODES >>250-PIPELINING >>250-EXPN >>250-VERB >>250-8BITMIME >>250-SIZE >>250-DSN >>250-ETRN >>250-DELIVERBY >>250 HELP >> >>> MAIL From:> >>250 2.1.0 >>... Sender ok >> >>> RCPT To:> >> >>> DATA >>250 2.1.5 >>... Recipient ok (will queue) >>354 Enter mail, end with "." on a line by itself >> >>> . >>250 2.0.0 h256ka8v002492 Message accepted for delivery >>test... Sent (h256ka8v002492 Message accepted for delivery) >>Closing connection to [127.0.0.1] >> >>> QUIT >>221 2.0.0 majordomo.motor.com closing connection >> >># mailq >> /var/spool/mqueue (1 request) >>-----Q-ID----- --Size-- -----Q-Time----- >>------------Sender/Recipient----------- >>h256ka8v002492 0 Wed Mar 5 14:46 >> >> (dbm map "Alias1": unsafe map file >>/usr/majordomo/majordomo-1) >> >> >> Total requests: 1 >> >> >> >> >>Kind Regards >>Jervy Chen >>* Fear can hold you prisoner * >>* Hope can set you free * > From majordomo-users-owner@greatcircle.com Thu Mar 13 21:00:43 2003 Received: from illumen.com (unknown [64.207.29.198]) by mycroft.greatcircle.com (Postfix) with ESMTP id 0AB47195B1B for ; Thu, 13 Mar 2003 21:00:42 -0800 (PST) Received: from home by illumen.com with SMTP (MDaemon.PRO.v6.7.2.R) for ; Thu, 13 Mar 2003 22:01:33 -0700 From: "Daniel Ajoy" To: majordomo-users@greatcircle.com Date: Fri, 14 Mar 2003 00:01:26 -0500 MIME-Version: 1.0 Subject: problem with "newaliases" Reply-To: Daniel Ajoy Message-ID: <3E711BD6.28151.2290B0E@localhost> X-LINE1: ABCDEF0123456789 X-mailer: Pegasus Mail for Windows (v4.02) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Return-Path: dajoy@openworldlearning.org X-MDaemon-Deliver-To: majordomo-users@greatcircle.com X-Archive-Number: 200303/79 X-Sequence-Number: 2950 Hi, Can someone please help me solve this: I on a FreeBSD system so I had to put this line in the sendmail.cf file O AliasFile=/majordomo/majordomo.aliases but when I use newaliases I get: su-2.05# newaliases hash map "Alias0": unsafe map file /majordomo/majordomo.aliases.db: Permission denied WARNING: cannot open alias database /majordomo/majordomo.aliases Cannot create database for alias file /majordomo/majordomo.aliases /etc/mail/aliases: 22 aliases, longest 10 bytes, 213 bytes total total 249 -rw-rw---- 1 majordomo daemon 6 Mar 13 21:34 .majordomo_registration -rw-rw-r-- 1 majordomo daemon 0 Mar 13 21:30 Log drwxr-xr-x 2 majordomo daemon 512 Mar 13 21:23 Tools -rwxr-xr-x 1 majordomo daemon 5267 Mar 13 21:23 archive2.pl drwxr-xr-x 2 majordomo daemon 512 Mar 13 21:23 bin -rwxr-xr-x 1 majordomo daemon 2795 Mar 13 21:23 bounce-remind -rwxr-xr-x 1 majordomo daemon 10671 Mar 13 21:23 config-test -rwxr-xr-x 1 majordomo daemon 51130 Mar 13 21:23 config_parse.pl -rwxr-xr-x 1 majordomo daemon 14201 Mar 13 21:23 digest drwxrwx--- 2 majordomo daemon 512 Mar 13 21:38 lists -rwxr-xr-x 1 majordomo daemon 62511 Mar 13 21:23 majordomo -rw-r--r-- 1 majordomo daemon 89 Mar 13 21:41 majordomo.aliases -rw-r--r-- 1 majordomo daemon 0 Mar 13 21:46 majordomo.aliases.db -rw-r--r-- 1 majordomo daemon 10462 Mar 13 21:33 majordomo.cf -rwxr-xr-x 1 majordomo daemon 24381 Mar 13 21:23 majordomo.pl -rwxr-xr-x 1 majordomo daemon 137 Mar 13 21:23 majordomo_version.pl drwxr-xr-x 4 majordomo daemon 512 Mar 13 21:23 man -rwxr-xr-x 1 majordomo daemon 3791 Mar 13 21:23 request-answer -rwxr-xr-x 1 majordomo daemon 29919 Mar 13 21:23 resend -rw-r--r-- 1 majordomo daemon 10462 Mar 13 21:23 sample.cf -rwxr-xr-x 1 majordomo daemon 8060 Mar 13 21:23 shlock.pl -rwsr-xr-x 1 root daemon 7262 Mar 13 21:24 wrapper su-2.05# chmod g+w majordomo.aliases* su-2.05# newaliases newaliases: cannot open /majordomo/majordomo.aliases: Group writable file /etc/mail/aliases: 22 aliases, longest 10 bytes, 213 bytes total Daniel From majordomo-users-owner@greatcircle.com Fri Mar 14 06:20:19 2003 Received: from mail.innovativebusiness.net (mail.innovativebusiness.net [65.209.59.13]) by mycroft.greatcircle.com (Postfix) with ESMTP id A350C1959E9 for ; Fri, 14 Mar 2003 06:20:17 -0800 (PST) Received: from PETE (bastion.innovativebusiness.net [65.209.59.11]) by mail.innovativebusiness.net (8.12.2/8.12.2) with ESMTP id h2EEKG5s028692 for ; Fri, 14 Mar 2003 09:20:16 -0500 From: "Peter Dumpert" To: majordomo-users@greatcircle.com Date: Fri, 14 Mar 2003 09:23:26 -0500 MIME-Version: 1.0 Subject: Re: problem with "newaliases" Message-ID: <3E719F8E.21786.E1AD7@localhost> In-reply-to: <3E711BD6.28151.2290B0E@localhost> X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Archive-Number: 200303/80 X-Sequence-Number: 2951 Making the file group writable is going in the wrong direction. Check the permissions of the directory your .db file is in. If that directory - or any of its parent directories - is writable by group or other, that may be causing the "unsafe map file" condition. On 14 Mar 2003 at 0:01, Daniel Ajoy wrote: > Hi, > > Can someone please help me solve this: > > I on a FreeBSD system so I had to put this line in the sendmail.cf file > > O AliasFile=/majordomo/majordomo.aliases > > but when I use newaliases I get: > > su-2.05# newaliases > hash map "Alias0": unsafe map file /majordomo/majordomo.aliases.db: Permission denied > WARNING: cannot open alias database /majordomo/majordomo.aliases > Cannot create database for alias file /majordomo/majordomo.aliases > /etc/mail/aliases: 22 aliases, longest 10 bytes, 213 bytes total > > > total 249 > -rw-rw---- 1 majordomo daemon 6 Mar 13 21:34 .majordomo_registration > -rw-rw-r-- 1 majordomo daemon 0 Mar 13 21:30 Log > drwxr-xr-x 2 majordomo daemon 512 Mar 13 21:23 Tools > -rwxr-xr-x 1 majordomo daemon 5267 Mar 13 21:23 archive2.pl > drwxr-xr-x 2 majordomo daemon 512 Mar 13 21:23 bin > -rwxr-xr-x 1 majordomo daemon 2795 Mar 13 21:23 bounce-remind > -rwxr-xr-x 1 majordomo daemon 10671 Mar 13 21:23 config-test > -rwxr-xr-x 1 majordomo daemon 51130 Mar 13 21:23 config_parse.pl > -rwxr-xr-x 1 majordomo daemon 14201 Mar 13 21:23 digest > drwxrwx--- 2 majordomo daemon 512 Mar 13 21:38 lists > -rwxr-xr-x 1 majordomo daemon 62511 Mar 13 21:23 majordomo > -rw-r--r-- 1 majordomo daemon 89 Mar 13 21:41 majordomo.aliases > -rw-r--r-- 1 majordomo daemon 0 Mar 13 21:46 majordomo.aliases.db > -rw-r--r-- 1 majordomo daemon 10462 Mar 13 21:33 majordomo.cf > -rwxr-xr-x 1 majordomo daemon 24381 Mar 13 21:23 majordomo.pl > -rwxr-xr-x 1 majordomo daemon 137 Mar 13 21:23 majordomo_version.pl > drwxr-xr-x 4 majordomo daemon 512 Mar 13 21:23 man > -rwxr-xr-x 1 majordomo daemon 3791 Mar 13 21:23 request-answer > -rwxr-xr-x 1 majordomo daemon 29919 Mar 13 21:23 resend > -rw-r--r-- 1 majordomo daemon 10462 Mar 13 21:23 sample.cf > -rwxr-xr-x 1 majordomo daemon 8060 Mar 13 21:23 shlock.pl > -rwsr-xr-x 1 root daemon 7262 Mar 13 21:24 wrapper > > su-2.05# chmod g+w majordomo.aliases* > su-2.05# newaliases > newaliases: cannot open /majordomo/majordomo.aliases: Group writable file > /etc/mail/aliases: 22 aliases, longest 10 bytes, 213 bytes total > > Daniel > -- Peter A. Dumpert Innovative Computer Services LLC - web design/e-pubs/consulting Innovative BusinessNet - an ISP for Business www.innovativebusiness.net Phone: 732-683-0092 ext 102 Fax: 732-577-9390 From majordomo-users-owner@greatcircle.com Fri Mar 14 07:21:46 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 028C3195F87 for ; Fri, 14 Mar 2003 07:21:43 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2EFT1Et016796; Fri, 14 Mar 2003 09:29:01 -0600 Message-ID: <3E71F389.9020100@sonny.org> Date: Fri, 14 Mar 2003 09:21:45 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Ajoy Cc: majordomo-users@greatcircle.com Subject: Re: problem with "newaliases" References: <3E711BD6.28151.2290B0E@localhost> In-Reply-To: <3E711BD6.28151.2290B0E@localhost> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/81 X-Sequence-Number: 2952 Daniel Ajoy wrote: > Hi, > > Can someone please help me solve this: > > I on a FreeBSD system so I had to put this line in the sendmail.cf file > > O AliasFile=/majordomo/majordomo.aliases You did not "have to" put this in the sendmail.cf, you could use the /etc/mail/aliases file to house majordomo aliases instead of using a separate file for it. If you desire using separate aliases files, A better solution is to create a link to majordmo.aliases in the same directory as you existing aliases file, and point to that link in the sendmail.cf file. as root, ln -s /majordomo/majordomo.aliases /etc/mail/majordomo.aliases in sendmail.cf, O AliasFile=/etc/mail/majordomo.aliases > > but when I use newaliases I get: > > su-2.05# newaliases > hash map "Alias0": unsafe map file /majordomo/majordomo.aliases.db: Permission denied > WARNING: cannot open alias database /majordomo/majordomo.aliases > Cannot create database for alias file /majordomo/majordomo.aliases > /etc/mail/aliases: 22 aliases, longest 10 bytes, 213 bytes total Sendmail does not allow files or directories to have "loose" permissions by default. You have to tell sendmail to loosen up with "dontblame*" settings in the cf or abide by the new security rules it imposes on you. You are probably being caught by a group writable permission on the "/" or "/majordomo" directory, not any of the files inside those directories (yet). The "/majordomo/lists" is an example of loose permissions. It should have 750 or 751 permissions rather than the 770 it has now. > > > total 249 > -rw-rw---- 1 majordomo daemon 6 Mar 13 21:34 .majordomo_registration > -rw-rw-r-- 1 majordomo daemon 0 Mar 13 21:30 Log > drwxr-xr-x 2 majordomo daemon 512 Mar 13 21:23 Tools > -rwxr-xr-x 1 majordomo daemon 5267 Mar 13 21:23 archive2.pl > drwxr-xr-x 2 majordomo daemon 512 Mar 13 21:23 bin > -rwxr-xr-x 1 majordomo daemon 2795 Mar 13 21:23 bounce-remind > -rwxr-xr-x 1 majordomo daemon 10671 Mar 13 21:23 config-test > -rwxr-xr-x 1 majordomo daemon 51130 Mar 13 21:23 config_parse.pl > -rwxr-xr-x 1 majordomo daemon 14201 Mar 13 21:23 digest > drwxrwx--- 2 majordomo daemon 512 Mar 13 21:38 lists > -rwxr-xr-x 1 majordomo daemon 62511 Mar 13 21:23 majordomo > -rw-r--r-- 1 majordomo daemon 89 Mar 13 21:41 majordomo.aliases > -rw-r--r-- 1 majordomo daemon 0 Mar 13 21:46 majordomo.aliases.db > -rw-r--r-- 1 majordomo daemon 10462 Mar 13 21:33 majordomo.cf > -rwxr-xr-x 1 majordomo daemon 24381 Mar 13 21:23 majordomo.pl > -rwxr-xr-x 1 majordomo daemon 137 Mar 13 21:23 majordomo_version.pl > drwxr-xr-x 4 majordomo daemon 512 Mar 13 21:23 man > -rwxr-xr-x 1 majordomo daemon 3791 Mar 13 21:23 request-answer > -rwxr-xr-x 1 majordomo daemon 29919 Mar 13 21:23 resend > -rw-r--r-- 1 majordomo daemon 10462 Mar 13 21:23 sample.cf > -rwxr-xr-x 1 majordomo daemon 8060 Mar 13 21:23 shlock.pl > -rwsr-xr-x 1 root daemon 7262 Mar 13 21:24 wrapper > > su-2.05# chmod g+w majordomo.aliases* > su-2.05# newaliases > newaliases: cannot open /majordomo/majordomo.aliases: Group writable file > /etc/mail/aliases: 22 aliases, longest 10 bytes, 213 bytes total > > Daniel Sendmail is complaining about, not asking for, a group writable file. as root, in the majordomo directory, chmod g-w majordomo.aliases lists /majordomo / Dan Liston From majordomo-users-owner@greatcircle.com Fri Mar 14 08:39:31 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 713CB195A5F for ; Fri, 14 Mar 2003 08:39:27 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2EGkjEt017079; Fri, 14 Mar 2003 10:46:45 -0600 Message-ID: <3E7205C0.8090506@sonny.org> Date: Fri, 14 Mar 2003 10:39:28 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chen Jervy-qch1408 Cc: "'Majordomo-Users@greatcircle.com'" Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 References: <1B2D9E22CDF7D611BD2200805FA7B779181C89@hou204.cig.mcel.mot.com> In-Reply-To: <1B2D9E22CDF7D611BD2200805FA7B779181C89@hou204.cig.mcel.mot.com> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/82 X-Sequence-Number: 2953 I would have hoped a majorcool user/administrator could have jumped in by now to offer suggestions/advice on solving this for you. I do not know majorcool, it's requirements, or it's dependencies. I do all my majordomo via email commands or the unix shell. If that much is working, you have reached the limits of my knowledge. One other thought does come to mind though. If majorcool is running on Apache, perhaps you need to tell sendmail to trust Apache too. Sorry, I just don't know. Dan Liston Chen Jervy-qch1408 wrote: > Dan, > > Any idea will be appreciated , I tried it with many way but failed, thanks. > > Kind Regards > Jervy Chen > China TCSG-ITS > * Fear can hold you prisoner * > * Hope can set you free * > > > -----Original Message----- > From: Chen Jervy-qch1408 > Sent: Monday, March 10, 2003 10:54 AM > To: 'Daniel Liston' > Cc: Majordomo-Users@greatcircle.com > Subject: RE: majordomo problem after upgrading the sendmail to 8.12.8 > > > Dan, > > Only one question remained, how to reconfigure the majorcool to run as the majordomo user and group (what configuration file)? I check the daemon status when I submitted the request on the web, "majorcool" daemon always run with nobody permission. Thanks a lot. > > > >>4. Restart sendmail >>Sendmail is definitely more strict on security than it used to be. You might have to > > reconfigure your majorcool to run as the majordomo user and group. > > > Kind Regards > Jervy Chen > * Fear can hold you prisoner * > * Hope can set you free * > > > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Friday, March 07, 2003 7:42 PM > To: Chen Jervy-qch1408 > Cc: Majordomo-Users@greatcircle.com > Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 > > > > > Chen Jervy-qch1408 wrote: > >>Dan, >> >>Thanks for your help, the following is answer, please try to give me more point form you. >>1. Upgrade majordomo to 1.94.5 (or higher) >>This is my deadline to follow it. >>2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 >>I use 8.12.8 sendmail.cf > > > DZ8.12.8 > > >>3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf >>I tried it but failed > > > Please describe "failed". I use this successfully; > O AliasFile=/etc/aliases,/etc/mail/majordomo.aliases > > The same could be written as two separate lines like; > O AliasFile=/etc/aliases > O AliasFile=/etc/mail/majordomo.aliases > > > >>3a. Create a symbolic link from your majordomo_aliases to /etc/mail >>It could not work anymore. > > > I do not understand what you mean. Majordomo could not work, or sendmail? > lrwxrwxrwx 1 root root 31 May 5 2002 /etc/mail/majordomo.aliases -> ../../var/lib/majordomo/aliases > > >>4. Restart sendmail >> >> >>Now, I resolved some problems, I used "majordomo" account to replace "smmsp" in sendmail, so aliases can work as normal. >> >>But web interface (majorcool) could not work for all features, it always displayed permission error as the following messages in IE. >>: ABORT >>shlock: '/usr/majordomo/majordomo-1.94.4' is not writable by UID 60001 GID 60001 >> >>Recipient names must be specified >> >>#ls -ld /usr/majordomo/majordomo-1.94.4 >>drwxr-xr-x 13 majordomomajordomo 2048 Mar 5 21:06 /usr/majordomo/majordomo-1.94.4 >> >> 60001 is "nobody" account & group, it seems that sendmail audit more strictly. > > > Sendmail is definitely more strict on security than it used to be. You might have to > reconfigure your majorcool to run as the majordomo user and group. > > Dan Liston > > >>Kind Regards >>Jervy Chen >> >>* Fear can hold you prisoner * >>* Hope can set you free * >> >> >>-----Original Message----- >>From: Daniel Liston [mailto:dliston@sonny.org] >>Sent: Thursday, March 06, 2003 2:33 AM >>To: Chen Jervy-qch1408 >>Cc: Majordomo-Users@greatcircle.com >>Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 >> >> >>Hi, >> >>Several points here, >> >>1. Upgrade majordomo to 1.94.5 (or higher) >>2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 >>3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf >>3a. Create a symbolic link from your majordomo_aliases to /etc/mail >>4. Restart sendmail >> >>Dan Liston >> >> >>Chen Jervy-qch1408 wrote: >> >> >>>Hello, guys, >>> >>>Could anybody help me to resolve the following problem? Any idea will be >>>appreciated! >>> >>>I am majordomo admin and have a majordomo server (Sun Ultra 2), >>>majordomo 1.94.4 and sendmail 8.8.5 installed on it, it works fine for 2 >>>years already after I setup it. The following is my setting before in >>>/etc/mail/sendmail.cf. >>> >>>OA/usr/majordomo/majordomo-1.94.4/majordomo_aliases >>> >>>Now, for the security reason, I have to upgrade sendmail from 8.8.5 to >>>8.12.8, I finished it already and added the above line in sendmail.cf >>>also but majordomo could not work as normal. The following is error >>>message when I try to send mail to majordomo list but it can send email >>>to normal user successfully. >>> >>>Mar 5 11:55:44 zchps01 sendmail[764]: h253tip9000764: SYSERR(root): dbm >>>map "Alias0": unsafe map file >>>/usr/majordomo/majordomo-1.94.4/majordomo_aliases: No such file or directory >>> >>>Here is the output when I try to send out majordomo list. >>> >>># /usr/lib/sendmail -v -bi >>>WARNING: World writable directory /var/spool/mqueue >>>/etc/mail/aliases: 9 aliases, longest 52 bytes, 294 bytes total >>>WARNING: Group writable directory /usr/majordomo >>>WARNING: Group writable directory /usr/majordomo/majordomo-1.94.4 >>>newaliases: cannot open >>>/usr/majordomo/majordomo-1.94.4/majordomo_aliases: Executable files not >>>allowed >>> >>># /usr/lib/sendmail -v test >>>. >>>test... Connecting to [127.0.0.1] via relay... >>>220 majordomo.motor.com ESMTP Sendmail 8.12.8/8.12.8; Wed, 5 Mar 2003 >>>14:46:36 +0800 (CST) >>> >>>>>>EHLO majordomo.motor.com >>> >>>250-majordomo.motor.com Hello localhost [127.0.0.1], pleased to meet you >>>250-ENHANCEDSTATUSCODES >>>250-PIPELINING >>>250-EXPN >>>250-VERB >>>250-8BITMIME >>>250-SIZE >>>250-DSN >>>250-ETRN >>>250-DELIVERBY >>>250 HELP >>> >>>>>>MAIL From:> >>> >>>250 2.1.0 >>>... Sender ok >>> >>>>>>RCPT To:> >>>>>>DATA >>> >>>250 2.1.5 >>>... Recipient ok (will queue) >>>354 Enter mail, end with "." on a line by itself >>> >>>>>>. >>> >>>250 2.0.0 h256ka8v002492 Message accepted for delivery >>>test... Sent (h256ka8v002492 Message accepted for delivery) >>>Closing connection to [127.0.0.1] >>> >>>>>>QUIT >>> >>>221 2.0.0 majordomo.motor.com closing connection >>> >>># mailq >>> /var/spool/mqueue (1 request) >>>-----Q-ID----- --Size-- -----Q-Time----- >>>------------Sender/Recipient----------- >>>h256ka8v002492 0 Wed Mar 5 14:46 >>> >>> (dbm map "Alias1": unsafe map file >>>/usr/majordomo/majordomo-1) >>> >>> >>> Total requests: 1 >>> >>> >>> >>> >>>Kind Regards >>>Jervy Chen >>>* Fear can hold you prisoner * >>>* Hope can set you free * >> From majordomo-users-owner@greatcircle.com Fri Mar 14 11:31:05 2003 Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mycroft.greatcircle.com (Postfix) with ESMTP id 6FA6A1961B9 for ; Fri, 14 Mar 2003 11:31:04 -0800 (PST) Received: from bob (h00045aebda62.ne.client2.attbi.com[24.218.155.244]) by rwcrmhc52.attbi.com (rwcrmhc52) with SMTP id <200303141930580520001p11e>; Fri, 14 Mar 2003 19:30:58 +0000 Reply-To: From: "Bob Cohen" To: "'Majordomo-Users@Greatcircle. Com'" Subject: authentication Date: Fri, 14 Mar 2003 14:30:57 -0500 Organization: b.p.e.Creative Message-ID: <006601c2ea60$3cb59b90$6401a8c0@bob> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <3E2C2D87.6070901@sonny.org> X-Archive-Number: 200303/83 X-Sequence-Number: 2954 My logwatch reported the following message: ***Begin Quote*** Authentication warnings: majordomo set sender to Majordomo-Owner@narsil.nbtanet.org using -f: 1 Times(s) ***End Quote*** And I got a bounced mail in my in box that correspondes to this message. This has me concerned that I may have some sort of security hole. Any insight would be appreciated. Thanks. Bob Cohen b.p.e.Creative (Design and production services for the web) Put creative minds to work for you From majordomo-users-owner@greatcircle.com Fri Mar 14 13:07:10 2003 Received: from ourldsfamily.com (ourfam.dsl.xmission.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id 11B95196433 for ; Fri, 14 Mar 2003 13:07:07 -0800 (PST) Received: from localhost (karlp@localhost) by ourldsfamily.com (8.11.0/8.11.0) with ESMTP id h2EL74K17545 for ; Fri, 14 Mar 2003 14:07:04 -0700 Date: Fri, 14 Mar 2003 14:07:04 -0700 (MST) From: To: Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 In-Reply-To: <3E7205C0.8090506@sonny.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200303/84 X-Sequence-Number: 2955 Okay, I'll jump in... I've used Majorcool for a few years now without much problem. I don't allow the creation/deletion of lists. I use Dan's newlist2.pl, which I've modified to meet my own needs (default settings, etc.) to create lists, and I delete them using a short script I wrote and manually remove them from md.aliases (my name for that file). My solution to get Majorcool to work from the start was to make the owner/group the same as majordomo, which is also the same as apache. Yes, that's an interesting security thing to do, but it made the administration simple and completely permission-free. That's about all I had to do. Once done, everything kicked into place for me. -- Karl L. Pearson Senior Consulting Systems Analyst Senior Consulting Database Analyst karlp@ourldsfamily.com http://consulting.ourldsfamily.com My Thoughts on Terrorism In America: http://www.ourldsfamily.com/wtc.shtml On Fri, 14 Mar 2003, Daniel Liston wrote: > >I would have hoped a majorcool user/administrator could have jumped >in by now to offer suggestions/advice on solving this for you. I do >not know majorcool, it's requirements, or it's dependencies. I do >all my majordomo via email commands or the unix shell. If that much >is working, you have reached the limits of my knowledge. One other >thought does come to mind though. If majorcool is running on Apache, >perhaps you need to tell sendmail to trust Apache too. Sorry, I just >don't know. > >Dan Liston > >Chen Jervy-qch1408 wrote: >> Dan, >> >> Any idea will be appreciated , I tried it with many way but failed, thanks. >> >> Kind Regards >> Jervy Chen >> China TCSG-ITS >> * Fear can hold you prisoner * >> * Hope can set you free * >> >> >> -----Original Message----- >> From: Chen Jervy-qch1408 >> Sent: Monday, March 10, 2003 10:54 AM >> To: 'Daniel Liston' >> Cc: Majordomo-Users@greatcircle.com >> Subject: RE: majordomo problem after upgrading the sendmail to 8.12.8 >> >> >> Dan, >> >> Only one question remained, how to reconfigure the majorcool to run as the majordomo user and group (what configuration file)? I check the daemon status when I submitted the request on the web, "majorcool" daemon always run with nobody permission. Thanks a lot. >> >> >> >>>4. Restart sendmail >>>Sendmail is definitely more strict on security than it used to be. You might have to >> >> reconfigure your majorcool to run as the majordomo user and group. >> >> >> Kind Regards >> Jervy Chen >> * Fear can hold you prisoner * >> * Hope can set you free * >> >> >> -----Original Message----- >> From: Daniel Liston [mailto:dliston@sonny.org] >> Sent: Friday, March 07, 2003 7:42 PM >> To: Chen Jervy-qch1408 >> Cc: Majordomo-Users@greatcircle.com >> Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 >> >> >> >> >> Chen Jervy-qch1408 wrote: >> >>>Dan, >>> >>>Thanks for your help, the following is answer, please try to give me more point form you. >>>1. Upgrade majordomo to 1.94.5 (or higher) >>>This is my deadline to follow it. >>>2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 >>>I use 8.12.8 sendmail.cf >> >> >> DZ8.12.8 >> >> >>>3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf >>>I tried it but failed >> >> >> Please describe "failed". I use this successfully; >> O AliasFile=/etc/aliases,/etc/mail/majordomo.aliases >> >> The same could be written as two separate lines like; >> O AliasFile=/etc/aliases >> O AliasFile=/etc/mail/majordomo.aliases >> >> >> >>>3a. Create a symbolic link from your majordomo_aliases to /etc/mail >>>It could not work anymore. >> >> >> I do not understand what you mean. Majordomo could not work, or sendmail? >> lrwxrwxrwx 1 root root 31 May 5 2002 /etc/mail/majordomo.aliases -> ../../var/lib/majordomo/aliases >> >> >>>4. Restart sendmail >>> >>> >>>Now, I resolved some problems, I used "majordomo" account to replace "smmsp" in sendmail, so aliases can work as normal. >>> >>>But web interface (majorcool) could not work for all features, it always displayed permission error as the following messages in IE. >>>: ABORT >>>shlock: '/usr/majordomo/majordomo-1.94.4' is not writable by UID 60001 GID 60001 >>> >>>Recipient names must be specified >>> >>>#ls -ld /usr/majordomo/majordomo-1.94.4 >>>drwxr-xr-x 13 majordomomajordomo 2048 Mar 5 21:06 /usr/majordomo/majordomo-1.94.4 >>> >>> 60001 is "nobody" account & group, it seems that sendmail audit more strictly. >> >> >> Sendmail is definitely more strict on security than it used to be. You might have to >> reconfigure your majorcool to run as the majordomo user and group. >> >> Dan Liston >> >> >>>Kind Regards >>>Jervy Chen >>> >>>* Fear can hold you prisoner * >>>* Hope can set you free * >>> >>> >>>-----Original Message----- >>>From: Daniel Liston [mailto:dliston@sonny.org] >>>Sent: Thursday, March 06, 2003 2:33 AM >>>To: Chen Jervy-qch1408 >>>Cc: Majordomo-Users@greatcircle.com >>>Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 >>> >>> >>>Hi, >>> >>>Several points here, >>> >>>1. Upgrade majordomo to 1.94.5 (or higher) >>>2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 >>>3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf >>>3a. Create a symbolic link from your majordomo_aliases to /etc/mail >>>4. Restart sendmail >>> >>>Dan Liston >>> >>> >>>Chen Jervy-qch1408 wrote: >>> >>> >>>>Hello, guys, >>>> >>>>Could anybody help me to resolve the following problem? Any idea will be >>>>appreciated! >>>> >>>>I am majordomo admin and have a majordomo server (Sun Ultra 2), >>>>majordomo 1.94.4 and sendmail 8.8.5 installed on it, it works fine for 2 >>>>years already after I setup it. The following is my setting before in >>>>/etc/mail/sendmail.cf. >>>> >>>>OA/usr/majordomo/majordomo-1.94.4/majordomo_aliases >>>> >>>>Now, for the security reason, I have to upgrade sendmail from 8.8.5 to >>>>8.12.8, I finished it already and added the above line in sendmail.cf >>>>also but majordomo could not work as normal. The following is error >>>>message when I try to send mail to majordomo list but it can send email >>>>to normal user successfully. >>>> >>>>Mar 5 11:55:44 zchps01 sendmail[764]: h253tip9000764: SYSERR(root): dbm >>>>map "Alias0": unsafe map file >>>>/usr/majordomo/majordomo-1.94.4/majordomo_aliases: No such file or directory >>>> >>>>Here is the output when I try to send out majordomo list. >>>> >>>># /usr/lib/sendmail -v -bi >>>>WARNING: World writable directory /var/spool/mqueue >>>>/etc/mail/aliases: 9 aliases, longest 52 bytes, 294 bytes total >>>>WARNING: Group writable directory /usr/majordomo >>>>WARNING: Group writable directory /usr/majordomo/majordomo-1.94.4 >>>>newaliases: cannot open >>>>/usr/majordomo/majordomo-1.94.4/majordomo_aliases: Executable files not >>>>allowed >>>> >>>># /usr/lib/sendmail -v test >>>>. >>>>test... Connecting to [127.0.0.1] via relay... >>>>220 majordomo.motor.com ESMTP Sendmail 8.12.8/8.12.8; Wed, 5 Mar 2003 >>>>14:46:36 +0800 (CST) >>>> >>>>>>>EHLO majordomo.motor.com >>>> >>>>250-majordomo.motor.com Hello localhost [127.0.0.1], pleased to meet you >>>>250-ENHANCEDSTATUSCODES >>>>250-PIPELINING >>>>250-EXPN >>>>250-VERB >>>>250-8BITMIME >>>>250-SIZE >>>>250-DSN >>>>250-ETRN >>>>250-DELIVERBY >>>>250 HELP >>>> >>>>>>>MAIL From:> >>>> >>>>250 2.1.0 >>>>... Sender ok >>>> >>>>>>>RCPT To:> >>>>>>>DATA >>>> >>>>250 2.1.5 >>>>... Recipient ok (will queue) >>>>354 Enter mail, end with "." on a line by itself >>>> >>>>>>>. >>>> >>>>250 2.0.0 h256ka8v002492 Message accepted for delivery >>>>test... Sent (h256ka8v002492 Message accepted for delivery) >>>>Closing connection to [127.0.0.1] >>>> >>>>>>>QUIT >>>> >>>>221 2.0.0 majordomo.motor.com closing connection >>>> >>>># mailq >>>> /var/spool/mqueue (1 request) >>>>-----Q-ID----- --Size-- -----Q-Time----- >>>>------------Sender/Recipient----------- >>>>h256ka8v002492 0 Wed Mar 5 14:46 >>>> >>>> (dbm map "Alias1": unsafe map file >>>>/usr/majordomo/majordomo-1) >>>> >>>> >>>> Total requests: 1 >>>> >>>> >>>> >>>> >>>>Kind Regards >>>>Jervy Chen >>>>* Fear can hold you prisoner * >>>>* Hope can set you free * >>> > > From majordomo-users-owner@greatcircle.com Fri Mar 14 13:49:35 2003 Received: from mail.innovativebusiness.net (mail.innovativebusiness.net [65.209.59.13]) by mycroft.greatcircle.com (Postfix) with ESMTP id C2FAD195A84 for ; Fri, 14 Mar 2003 13:49:32 -0800 (PST) Received: from PETE (bastion.innovativebusiness.net [65.209.59.11]) by mail.innovativebusiness.net (8.12.2/8.12.2) with ESMTP id h2ELnP5s004353 for ; Fri, 14 Mar 2003 16:49:25 -0500 From: "Peter Dumpert" To: "'Majordomo-Users@Greatcircle. Com'" Date: Fri, 14 Mar 2003 16:52:36 -0500 MIME-Version: 1.0 Subject: Re: authentication Message-ID: <3E7208D4.32136.1A95291@localhost> In-reply-to: <006601c2ea60$3cb59b90$6401a8c0@bob> References: <3E2C2D87.6070901@sonny.org> X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Archive-Number: 200303/85 X-Sequence-Number: 2956 You need to make majordomo a trusted user. Only trusted users can send mail as someone else without generating a warning. If you have a sendmail.mc file, there should be a line similar to this: FEATURE(`use_ct_file') If you want to use something other than the default filename (/etc/sendmail.ct) you also need (as an example): define(`confCT_FILE', `/etc/mail/trusted-users') Then you put the usernames for your trusted users in the file, one per line. I think you have to restart sendmail for it to take effect. On 14 Mar 2003 at 14:30, Bob Cohen wrote: > My logwatch reported the following message: > > ***Begin Quote*** > Authentication warnings: > majordomo set sender to Majordomo-Owner@narsil.nbtanet.org using -f: > 1 Times(s) > ***End Quote*** > > And I got a bounced mail in my in box that correspondes to this message. > This has me concerned that I may have some sort of security hole. Any > insight would be appreciated. Thanks. > > Bob Cohen > b.p.e.Creative (Design and production services for the web) > Put creative minds to work for you > -- Peter A. Dumpert Innovative Computer Services LLC - web design/e-pubs/consulting Innovative BusinessNet - an ISP for Business www.innovativebusiness.net Phone: 732-683-0092 ext 102 Fax: 732-577-9390 From majordomo-users-owner@greatcircle.com Fri Mar 14 14:38:15 2003 Received: from wrenkasky.com (esson.net [216.102.129.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2D4AF195A3E for ; Fri, 14 Mar 2003 14:38:14 -0800 (PST) Received: from ekasky.wrenkasky.com (ekasky.priority.usc.edu [128.125.63.168]) by wrenkasky.com (8.12.5/8.12.5) with ESMTP id h2EMcF4f011291 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT) for ; Fri, 14 Mar 2003 14:38:15 -0800 Message-Id: <5.1.1.6.2.20030314142606.00aa8308@mail.esson.net> X-Sender: ed@mail.esson.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Fri, 14 Mar 2003 14:38:08 -0800 To: From: Ed Kasky Subject: Re: authentication In-Reply-To: <3E7208D4.32136.1A95291@localhost> References: <006601c2ea60$3cb59b90$6401a8c0@bob> <3E2C2D87.6070901@sonny.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200303/86 X-Sequence-Number: 2957 At 04:52 PM Friday, 3/14/2003, Peter Dumpert wrote -=> >You need to make majordomo a trusted user. Only trusted users >can send mail as someone else without generating a warning. > >If you have a sendmail.mc file, there should be a line similar to this: > FEATURE(`use_ct_file') Any time you make an addition to either sendmail.mc or submit mc, you need to run the m4 macro processor to make the new cf. This is the 'sendmail' recommended peocedure. ex: m4 ../m4/cf.m4 my-very-own.mc > /etc/mail/sendmail.cf >If you want to use something other than the default filename >(/etc/sendmail.ct) you also need (as an example): > define(`confCT_FILE', `/etc/mail/trusted-users') If you don't have a lot of users, I have found it easier to use the following in the mc: define(`confTRUSTED_USERS', `majordom mail otheruser')dnl If you are running 8.12.x and utilize the submit.cf, this or the settings for the ct file go in the submit.mc and then you build the cf in the same manner as you would for the sendmail.cf HTH Ed Kasky Los Angeles, CA . . . . . . . . It is a funny thing about life: if you refuse to accept anything but the best you very often get it. -William Somerset Maugham From majordomo-users-owner@greatcircle.com Mon Mar 17 01:05:30 2003 Received: from motgate.mot.com (motgate.mot.com [129.188.136.100]) by mycroft.greatcircle.com (Postfix) with ESMTP id 08C57195A42 for ; Mon, 17 Mar 2003 01:04:18 -0800 (PST) Received: from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate.mot.com (Motorola/Motgate) with ESMTP id h2H94HIG025930 for ; Mon, 17 Mar 2003 02:04:17 -0700 (MST) Received: [from zch07exb01.corp.mot.com (zch07exb01.corp.mot.com [200.3.1.150]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id CAA16094 for ; Mon, 17 Mar 2003 02:04:15 -0700 (MST)] Received: by zch07exb01.corp.mot.com with Internet Mail Service (5.5.2656.59) id ; Mon, 17 Mar 2003 17:04:14 +0800 Message-ID: <1B2D9E22CDF7D611BD2200805FA7B779181C97@hou204.cig.mcel.mot.com> From: Chen Jervy-qch1408 To: Chen Jervy-qch1408 Cc: Majordomo-Users@greatcircle.com Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 Date: Mon, 17 Mar 2003 17:04:00 +0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain X-Archive-Number: 200303/87 X-Sequence-Number: 2958 Dan, Bill, Ed, Karl, Thanks for your so warm assistance and suggestions, base on these idea, I resolved this problem after adding the SETUID permission on majordomo "wrapper"program. So this issue can be close now, hope to see your nice guys again. Kind Regards Jervy Chen China TCSG-ITS * Fear can hold you prisoner * * Hope can set you free * -----Original Message----- From: Daniel Liston [mailto:dliston@sonny.org] Sent: Saturday, March 15, 2003 12:39 AM To: Chen Jervy-qch1408 Cc: Majordomo-Users@greatcircle.com Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 I would have hoped a majorcool user/administrator could have jumped in by now to offer suggestions/advice on solving this for you. I do not know majorcool, it's requirements, or it's dependencies. I do all my majordomo via email commands or the unix shell. If that much is working, you have reached the limits of my knowledge. One other thought does come to mind though. If majorcool is running on Apache, perhaps you need to tell sendmail to trust Apache too. Sorry, I just don't know. Dan Liston Chen Jervy-qch1408 wrote: > Dan, > > Any idea will be appreciated , I tried it with many way but failed, thanks. > > Kind Regards > Jervy Chen > China TCSG-ITS > * Fear can hold you prisoner * > * Hope can set you free * > > > -----Original Message----- > From: Chen Jervy-qch1408 > Sent: Monday, March 10, 2003 10:54 AM > To: 'Daniel Liston' > Cc: Majordomo-Users@greatcircle.com > Subject: RE: majordomo problem after upgrading the sendmail to 8.12.8 > > > Dan, > > Only one question remained, how to reconfigure the majorcool to run as the majordomo user and group (what configuration file)? I check the daemon status when I submitted the request on the web, "majorcool" daemon always run with nobody permission. Thanks a lot. > > > >>4. Restart sendmail >>Sendmail is definitely more strict on security than it used to be. You might have to > > reconfigure your majorcool to run as the majordomo user and group. > > > Kind Regards > Jervy Chen > * Fear can hold you prisoner * > * Hope can set you free * > > > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Friday, March 07, 2003 7:42 PM > To: Chen Jervy-qch1408 > Cc: Majordomo-Users@greatcircle.com > Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 > > > > > Chen Jervy-qch1408 wrote: > >>Dan, >> >>Thanks for your help, the following is answer, please try to give me more point form you. >>1. Upgrade majordomo to 1.94.5 (or higher) >>This is my deadline to follow it. >>2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 >>I use 8.12.8 sendmail.cf > > > DZ8.12.8 > > >>3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf >>I tried it but failed > > > Please describe "failed". I use this successfully; > O AliasFile=/etc/aliases,/etc/mail/majordomo.aliases > > The same could be written as two separate lines like; > O AliasFile=/etc/aliases > O AliasFile=/etc/mail/majordomo.aliases > > > >>3a. Create a symbolic link from your majordomo_aliases to /etc/mail >>It could not work anymore. > > > I do not understand what you mean. Majordomo could not work, or sendmail? > lrwxrwxrwx 1 root root 31 May 5 2002 /etc/mail/majordomo.aliases -> ../../var/lib/majordomo/aliases > > >>4. Restart sendmail >> >> >>Now, I resolved some problems, I used "majordomo" account to replace "smmsp" in sendmail, so aliases can work as normal. >> >>But web interface (majorcool) could not work for all features, it always displayed permission error as the following messages in IE. >>: ABORT >>shlock: '/usr/majordomo/majordomo-1.94.4' is not writable by UID 60001 GID 60001 >> >>Recipient names must be specified >> >>#ls -ld /usr/majordomo/majordomo-1.94.4 >>drwxr-xr-x 13 majordomomajordomo 2048 Mar 5 21:06 /usr/majordomo/majordomo-1.94.4 >> >> 60001 is "nobody" account & group, it seems that sendmail audit more strictly. > > > Sendmail is definitely more strict on security than it used to be. You might have to > reconfigure your majorcool to run as the majordomo user and group. > > Dan Liston > > >>Kind Regards >>Jervy Chen >> >>* Fear can hold you prisoner * >>* Hope can set you free * >> >> >>-----Original Message----- >>From: Daniel Liston [mailto:dliston@sonny.org] >>Sent: Thursday, March 06, 2003 2:33 AM >>To: Chen Jervy-qch1408 >>Cc: Majordomo-Users@greatcircle.com >>Subject: Re: majordomo problem after upgrading the sendmail to 8.12.8 >> >> >>Hi, >> >>Several points here, >> >>1. Upgrade majordomo to 1.94.5 (or higher) >>2. You appear to be using a sendmail 8.8.5 config file with 8.12.8 >>3. Use "O AliasFile=/etc/mail/majordomo_aliases" in sendmail.cf >>3a. Create a symbolic link from your majordomo_aliases to /etc/mail >>4. Restart sendmail >> >>Dan Liston >> >> >>Chen Jervy-qch1408 wrote: >> >> >>>Hello, guys, >>> >>>Could anybody help me to resolve the following problem? Any idea will be >>>appreciated! >>> >>>I am majordomo admin and have a majordomo server (Sun Ultra 2), >>>majordomo 1.94.4 and sendmail 8.8.5 installed on it, it works fine for 2 >>>years already after I setup it. The following is my setting before in >>>/etc/mail/sendmail.cf. >>> >>>OA/usr/majordomo/majordomo-1.94.4/majordomo_aliases >>> >>>Now, for the security reason, I have to upgrade sendmail from 8.8.5 to >>>8.12.8, I finished it already and added the above line in sendmail.cf >>>also but majordomo could not work as normal. The following is error >>>message when I try to send mail to majordomo list but it can send email >>>to normal user successfully. >>> >>>Mar 5 11:55:44 zchps01 sendmail[764]: h253tip9000764: SYSERR(root): dbm >>>map "Alias0": unsafe map file >>>/usr/majordomo/majordomo-1.94.4/majordomo_aliases: No such file or directory >>> >>>Here is the output when I try to send out majordomo list. >>> >>># /usr/lib/sendmail -v -bi >>>WARNING: World writable directory /var/spool/mqueue >>>/etc/mail/aliases: 9 aliases, longest 52 bytes, 294 bytes total >>>WARNING: Group writable directory /usr/majordomo >>>WARNING: Group writable directory /usr/majordomo/majordomo-1.94.4 >>>newaliases: cannot open >>>/usr/majordomo/majordomo-1.94.4/majordomo_aliases: Executable files not >>>allowed >>> >>># /usr/lib/sendmail -v test >>>. >>>test... Connecting to [127.0.0.1] via relay... >>>220 majordomo.motor.com ESMTP Sendmail 8.12.8/8.12.8; Wed, 5 Mar 2003 >>>14:46:36 +0800 (CST) >>> >>>>>>EHLO majordomo.motor.com >>> >>>250-majordomo.motor.com Hello localhost [127.0.0.1], pleased to meet you >>>250-ENHANCEDSTATUSCODES >>>250-PIPELINING >>>250-EXPN >>>250-VERB >>>250-8BITMIME >>>250-SIZE >>>250-DSN >>>250-ETRN >>>250-DELIVERBY >>>250 HELP >>> >>>>>>MAIL From:> >>> >>>250 2.1.0 >>>... Sender ok >>> >>>>>>RCPT To:> >>>>>>DATA >>> >>>250 2.1.5 >>>... Recipient ok (will queue) >>>354 Enter mail, end with "." on a line by itself >>> >>>>>>. >>> >>>250 2.0.0 h256ka8v002492 Message accepted for delivery >>>test... Sent (h256ka8v002492 Message accepted for delivery) >>>Closing connection to [127.0.0.1] >>> >>>>>>QUIT >>> >>>221 2.0.0 majordomo.motor.com closing connection >>> >>># mailq >>> /var/spool/mqueue (1 request) >>>-----Q-ID----- --Size-- -----Q-Time----- >>>------------Sender/Recipient----------- >>>h256ka8v002492 0 Wed Mar 5 14:46 >>> >>> (dbm map "Alias1": unsafe map file >>>/usr/majordomo/majordomo-1) >>> >>> >>> Total requests: 1 >>> >>> >>> >>> >>>Kind Regards >>>Jervy Chen >>>* Fear can hold you prisoner * >>>* Hope can set you free * >> From majordomo-users-owner@greatcircle.com Mon Mar 17 13:17:14 2003 Received: from gateway.hns.com (unknown [208.236.67.14]) by mycroft.greatcircle.com (Postfix) with ESMTP id 684E4195A2B for ; Mon, 17 Mar 2003 13:17:12 -0800 (PST) Received: from excore1.hns.com (excore1.hns.com [139.85.52.104]) by gateway.hns.com (Switch-3.0.3/Switch-3.0.0) with ESMTP id h2HLH4nL028393 for ; Mon, 17 Mar 2003 16:17:05 -0500 (EST) Received: from hns.com (coresun3.md.hnsnet [10.32.12.200]) by excore1.hns.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h2HLGx802650 for ; Mon, 17 Mar 2003 16:16:59 -0500 (EST) Message-ID: <3E763B4A.60706@hns.com> Date: Mon, 17 Mar 2003 16:16:58 -0500 From: Jaysheel Mehd User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Problems with Majorcool References: <20030317211249.C4B99195F0B@mycroft.greatcircle.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms080902050500070600090007" X-Filtered: Sendmail MIME Filter v1.0.8 excore1.hns.com h2HLGx802650 X-Archive-Number: 200303/88 X-Sequence-Number: 2959 This is a cryptographically signed message in MIME format. --------------ms080902050500070600090007 Content-Type: multipart/alternative; boundary="------------010206070007020005030700" --------------010206070007020005030700 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi all, I am using Majordomo 1.94.5, majorcool v 1.3.2 and perl version 5.005_03 built for sun4-solaris. I am on Solaris 8 and sendmail version is 8.12.6. Now, I have installed Majordomo and the list is working pretty well. I tried to create the list through Majorcool and that also puts a config file. But the main cause is Majorcool sees just the test list and not any other lists Hence, I cannot modify, subscribe or do anything with any other lists. Any pointers to solve this will be very helpful Thanks --------------010206070007020005030700 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit
Hi all,

I am using Majordomo 1.94.5, majorcool v 1.3.2 and perl version 5.005_03 built for sun4-solaris.

I am on Solaris 8 and sendmail  version is 8.12.6.

Now, I have installed Majordomo and the list is working pretty well. I tried to create the list through Majorcool and that also puts a config file.

But the main cause is Majorcool sees just the test list and not any other lists
Hence, I cannot modify, subscribe or do anything with any other lists. Any pointers to solve this will be very helpful

Thanks
--------------010206070007020005030700-- --------------ms080902050500070600090007 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEH AQAAoIIMDDCCAy4wggKXoAMCAQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqG SIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwg SW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZp Y2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5 NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVy aVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5 ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1 YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0GCSqGSIb3DQEB AQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqd ufBou5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScK XbawNkIztW5UiE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdq yErICQbkmQIDAQABo3wwejARBglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAw PjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUFBwIBFh93d3cudmVyaXNpZ24u Y29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAwCwYDVR0PBAQD AgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bx ndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq +jPHvhnXU0zDvcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiS xVhqwY0DPOvDzQWikK5uMIIEaTCCA9KgAwIBAgIQfWzHfO+DvWIbj3LfU/z/ LTANBgkqhkiG9w0BAQQFADCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4x HzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3 dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBSZWYu LExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0Eg SW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZDAe Fw0wMjA0MTgwMDAwMDBaFw0wMzA0MTgyMzU5NTlaMIIBDTEXMBUGA1UEChMO VmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdv cmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEg SW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNv bmEgTm90IFZhbGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAx IC0gTmV0c2NhcGUgRnVsbCBTZXJ2aWNlMRYwFAYDVQQDFA1KYXlzaGVlbCBN ZWhkMRwwGgYJKoZIhvcNAQkBFg1qbWVoZEBobnMuY29tMIGfMA0GCSqGSIb3 DQEBAQUAA4GNADCBiQKBgQC5sIxeMk9dOcks0T3GE23ztjuHtD0O/hoWAxQr /7nD26C8EakcvcRsqneZYrHqJrsw6LIWNVbIDZIsCmkd26XkrVXarPsetVD5 HDBsBhvmYqvWpcQsBYMRbfzdA+HS30yAdF4vzdgV7kpcNXmG/ImLo+jASGVD ZGE4V+rTL4aRSQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGk MIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93 d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWdu LCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJl bmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQD AgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAAUyS3fwO4bqWOEVZSasz 8SqfWw4HAokPjT77hwREMpNPlvB1Hgv02eUMIT7TyzDCTt4/NLA4wIGLxDBT 4h8M4NWLSj2MPWtBciwI3Pycd3b1NCp9cNPAsiJ0TQxF1n3gES5IdfwJCFyX jW2SX5hprqchvp34oOb28o8ByE0dB/kwggRpMIID0qADAgECAhB9bMd874O9 YhuPct9T/P8tMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2ln biwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQG A1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAu IEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xh c3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs aWRhdGVkMB4XDTAyMDQxODAwMDAwMFoXDTAzMDQxODIzNTk1OVowggENMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0 b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UE CxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElE IENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxFjAUBgNVBAMUDUph eXNoZWVsIE1laGQxHDAaBgkqhkiG9w0BCQEWDWptZWhkQGhucy5jb20wgZ8w DQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALmwjF4yT105ySzRPcYTbfO2O4e0 PQ7+GhYDFCv/ucPboLwRqRy9xGyqd5liseomuzDoshY1VsgNkiwKaR3bpeSt Vdqs+x61UPkcMGwGG+Ziq9alxCwFgxFt/N0D4dLfTIB0Xi/N2BXuSlw1eYb8 iYuj6MBIZUNkYThX6tMvhpFJAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGs BgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxo dHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYO VmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBi eSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgB hvhCAQEEBAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJp c2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQABTJLd/A7h upY4RVlJqzPxKp9bDgcCiQ+NPvuHBEQyk0+W8HUeC/TZ5QwhPtPLMMJO3j80 sDjAgYvEMFPiHwzg1YtKPYw9a0FyLAjc/Jx3dvU0Kn1w08CyInRNDEXWfeAR Lkh1/AkIXJeNbZJfmGmupyG+nfig5vbyjwHITR0H+TGCAzQwggMwAgEBMIHh MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFI MEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNj cmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhB9bMd874O9YhuPct9T/P8t MAkGBSsOAwIaBQCgggGoMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJ KoZIhvcNAQkFMQ8XDTAzMDMxNzIxMTY1OFowIwYJKoZIhvcNAQkEMRYEFG7F FPYyPI4Zy416vWORkzYSKd1LMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcN AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0G CCqGSIb3DQMCAgEoMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUGA1UE ChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l dHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S UEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1Zl cmlTaWduIENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNv bmEgTm90IFZhbGlkYXRlZAIQfWzHfO+DvWIbj3LfU/z/LTANBgkqhkiG9w0B AQEFAASBgKeCqNLSHIkRVbrIzquz8bqeuTCotmUh64t3PJSgQuNi0aEGyVNq AZ2OrRfR5rudPLUq+khlQ8cldesPdYupIptfHA9dikcNbNVLFx3Dq1N1OOQU STc3taCRbMbKplQKFzcwX120NhbWiJnWWeM+iN1LNpaa2LrhfQSizK4u3PvQ AAAAAAAA --------------ms080902050500070600090007-- From majordomo-users-owner@greatcircle.com Mon Mar 17 13:47:18 2003 Received: from earth.msuotc.co.uk (81-86-125-15.dsl.pipex.com [81.86.125.15]) by mycroft.greatcircle.com (Postfix) with ESMTP id D6BBD195ADE for ; Mon, 17 Mar 2003 13:47:16 -0800 (PST) Received: from andybev.com ([192.168.0.50]) by earth.msuotc.co.uk (8.12.8/8.12.8) with ESMTP id h2HLlW3Q016463; Mon, 17 Mar 2003 21:47:33 GMT Message-ID: <3E7642E5.6070705@andybev.com> Date: Mon, 17 Mar 2003 21:49:25 +0000 From: Andrew Beverley User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jaysheel Mehd Cc: majordomo-users@greatcircle.com Subject: Re: Problems with Majorcool References: <20030317211249.C4B99195F0B@mycroft.greatcircle.com> <3E763B4A.60706@hns.com> In-Reply-To: <3E763B4A.60706@hns.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/89 X-Sequence-Number: 2960 You may have to run the following to update the cache of the lists. You need to run it from majordomo's home directory: ./wrapper mj_key_cache Andy Beverley Jaysheel Mehd wrote: > > Hi all, > > I am using Majordomo 1.94.5, majorcool v 1.3.2 and perl version 5.005_03 > built for sun4-solaris. > > I am on Solaris 8 and sendmail version is 8.12.6. > > Now, I have installed Majordomo and the list is working pretty well. I > tried to create the list through Majorcool and that also puts a config file. > > *But the main cause is Majorcool sees just the test list and not any > other lists > *Hence, I cannot modify, subscribe or do anything with any other lists. > Any pointers to solve this will be very helpful > > Thanks From majordomo-users-owner@greatcircle.com Mon Mar 17 16:28:48 2003 Received: from illumen.com (unknown [64.207.29.198]) by mycroft.greatcircle.com (Postfix) with ESMTP id 30C93195A2B for ; Mon, 17 Mar 2003 16:28:46 -0800 (PST) Received: from home by illumen.com with SMTP (MDaemon.PRO.v6.7.2.R) for ; Mon, 17 Mar 2003 17:29:45 -0700 From: "Daniel Ajoy" To: majordomo-users@greatcircle.com Date: Mon, 17 Mar 2003 19:29:26 -0500 MIME-Version: 1.0 Subject: Re: problem with "newaliases" Reply-To: Daniel Ajoy Message-ID: <3E762216.32401.27485@localhost> In-reply-to: <3E71F389.9020100@sonny.org> References: <3E711BD6.28151.2290B0E@localhost> X-mailer: Pegasus Mail for Windows (v4.02) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Return-Path: dajoy@openworldlearning.org X-MDaemon-Deliver-To: majordomo-users@greatcircle.com X-Archive-Number: 200303/90 X-Sequence-Number: 2961 On 14 Mar 2003 at 9:21, Daniel Liston wrote: > > You did not "have to" put this in the sendmail.cf, you could use the > /etc/mail/aliases file to house majordomo aliases instead of using a > separate file for it. If you desire using separate aliases files, > A better solution is to create a link to majordmo.aliases in the same > directory as you existing aliases file, and point to that link in > the sendmail.cf file. > > as root, > ln -s /majordomo/majordomo.aliases /etc/mail/majordomo.aliases > > in sendmail.cf, > O AliasFile=/etc/mail/majordomo.aliases thanks, that solved my problem. Daniel From majordomo-users-owner@greatcircle.com Mon Mar 17 20:14:31 2003 Received: from hawk.lamplightsoftware.com (ns1.lamplightsoftware.net [66.138.138.9]) by mycroft.greatcircle.com (Postfix) with ESMTP id 3DF3E195A2B for ; Mon, 17 Mar 2003 20:14:28 -0800 (PST) Received: from silas (dhcp101.lamplightsoftware.com [192.168.10.101]) by hawk.lamplightsoftware.com (8.12.7/8.12.7) with SMTP id h2I4BQLo004312 for ; Mon, 17 Mar 2003 22:11:26 -0600 (CST) From: "David E. Minor" To: Subject: ABORT Mailer problem Date: Mon, 17 Mar 2003 22:14:17 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Archive-Number: 200303/91 X-Sequence-Number: 2962 I recently upgraded to Majordomo 1.94.5, Solaris 9 and Sendmail 8.12.7. Whenever I try to send to any of my lists I receive the following message in majordomo.log and no mail is sent. Mar 11 01:23:50 awana-nct.org resend[28340] {awana-nct-leaders} ABORT Mailer /usr/lib/sendmail -oi -oee -fmissionary@awana-nct.org distrib-awana-nct-leaders exited unexpectedly with error 65535 Here is the output of the config-test: ------------------------------------------------------------ ---------------- Config-test for Majordomo ---------------- ------------------------------------------------------------ --------------------- Obvious things: --------------------- ------------------ environment variables ------------------ HOME=/opt/majordomo LOGNAME=root MAJORDOMO_CF=/opt/majordomo/majordomo.cf PATH=/bin:/usr/bin:/usr/ucb SHELL=/bin/sh TZ=US/Central --------------------- euid/egid checks --------------------- effective user = majordom (uid 1100) effective group = majordom daemon nuucp lp tty mail uucp adm sys bin root other (gid 120 12 9 8 7 6 5 4 3 2 0 1 ) ---------------------- uid/gid checks ---------------------- real user = majordom (uid 1100) real group = majordom daemon nuucp lp tty mail uucp adm sys bin root other (gid 120 12 9 8 7 6 5 4 3 2 0 1 ) ------------------------------------------------------------ Non obvious things that cause headaches: ------------------------------------------------------------ Good: 'require'd /opt/majordomo/majordomo.cf okay. Good: found ctime.pl okay. Good: found majordomo_version.pl okay. Good: found majordomo.pl okay. Good: found shlock.pl okay. Good: found config_parse.pl okay. You're running Majordomo Version 1.94.5. --==> Majordomo home directory is /opt/majordomo. ------------------- Include directories ------------------- /opt/majordomo /opt/perl/lib/5.8.0/sun4-solaris /opt/perl/lib/5.8.0 /opt/perl/lib/site_perl/5.8.0/sun4-solaris /opt/perl/lib/site_perl/5.8.0 /opt/perl/lib/site_perl . --------------------------- Home --------------------------- Good: changedir to /opt/majordomo succeeded. Good: Created a mock lock file. ---------------------- temp directory ---------------------- Good: Created a temp file in $TMPDIR (/var/tmp). ---------------------- list directory ---------------------- Good: list directory /opt/majordomo/lists has good permissions. --------------------------- log --------------------------- Good: logfile /opt/majordomo/majordomo.log exists and is writeable. ------------------------- Mailers ------------------------- You have defined a mailer for delivery. Attempting to verify that this is a valid mailer...looks okay. You have defined a mailer for delivering administrative messages. Attempting to verify that this is a valid mailer...looks okay. ------------------ Checking majordomo.cf ------------------ Checking to see if there are new variables that should be in your majordomo.cf file...Nope, none that I see. Have you configured where Majordomo is? $whereami is lamplightsoftware.com Good: yup! ----------------------- end of tests ----------------------- Nothing bad found! Majordomo _should_ work correctly. If it doesn't, check your configuration file (/opt/majordomo/majordomo.cf) closely, and if it still looks okay, consider asking the majordomo-users mailing list at "majordomo-users@greatcircle.com" for assistance. Be sure and fully specify what your problems are, and what type of machine (and operating system) you are using. Enjoy! Any help would be appreciated! -Dave Minor From majordomo-users-owner@greatcircle.com Mon Mar 17 23:56:33 2003 Received: from itfuture.dekundenserver.de (unknown [62.26.119.143]) by mycroft.greatcircle.com (Postfix) with ESMTP id 7823D195B22 for ; Mon, 17 Mar 2003 23:56:32 -0800 (PST) Received: from intra2 (unknown [213.217.101.98]) by itfuture.dekundenserver.de (Postfix) with ESMTP id AB9AE147A61 for ; Tue, 18 Mar 2003 08:56:31 +0100 (CET) Content-Type: text/plain; charset="iso-8859-1" From: Markus Tacker Organization: IT Future AG To: majordomo-users@greatcircle.com Subject: Variables available in info document Date: Tue, 18 Mar 2003 09:52:19 +0100 User-Agent: KMail/1.4.3 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200303171235.27074.mtacker@itfuture.de> X-Archive-Number: 200303/92 X-Sequence-Number: 2963 Hello List, I've read the docs, faq and a part of the archive but i=20 can't find a comprehensive list of variables (like $USER)=20 available in the different documents especially the info=20 document. Any hint? --=20 sincerely yours Markus Tacker From majordomo-users-owner@greatcircle.com Tue Mar 18 01:52:50 2003 Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.47]) by mycroft.greatcircle.com (Postfix) with ESMTP id B7CB5195F33 for ; Tue, 18 Mar 2003 01:52:44 -0800 (PST) Received: from esealnt611.al.sw.ericsson.se (alteon-nat4.sw.ericsson.se [153.88.254.121]) by penguin.wise.edt.ericsson.se (8.12.8/8.12.8/WIREfire-1.5) with ESMTP id h2I9qgwv021107 for ; Tue, 18 Mar 2003 10:52:43 +0100 (MET) Received: from esealnt135.al.sw.ericsson.se ([153.88.251.92]) by esealnt611.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55) id FDVPK4VD; Tue, 18 Mar 2003 10:52:42 +0100 Received: by esealnt135.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19) id ; Tue, 18 Mar 2003 10:48:16 +0100 Message-ID: <1254192C94D3D411B8060008C7E6AEEB075E029E@esealnt408> X-Sybari-Trust: 9c3413f8 9ffcebbb a5ee123c 00000138 From: =?iso-8859-1?Q?Torbj=F6rn_Sagen_=28PAC=29?= To: "'majordomo-users@greatcircle.com'" Subject: Trouble with config footer in HTML mails Date: Tue, 18 Mar 2003 10:49:33 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2ED33.ADA03D30" X-Archive-Number: 200303/93 X-Sequence-Number: 2964 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_01C2ED33.ADA03D30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi! =20 I have configured a mailing list to use a standard footer. In the config fi= le it looks like this: =20 message_footer << END ---------------------------------------------------------------------------= -- This is a footer text ---------------------------------------------------------------------------= -- END This footer follows nicely when sending out mails in plain text format (or = using rich text that will be converted to plain text) =20 However, it does not work when sending HTML mails. =20 I want my footer to work both with HTML and plain text mails. How can I ach= ieve this? =20 BR Torbj=F6rn ------_=_NextPart_001_01C2ED33.ADA03D30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi!
 
I have co= nfigured a=20 mailing list to use a standard footer. In the config file it looks like=20 this:
 
message_footer       =20 <<  =20 END
--------------------------------------------------------------------= ---------
This=20 is a footer text
------------------------------------------------------------------= -----------
END
This foot= er follows=20 nicely when sending out mails in plain text format (or using rich text that= will=20 be converted to plain text)
 
However, = it does not=20 work when sending HTML mails.
 
I want my= footer to=20 work both with HTML and plain text mails. How can I achieve=20 this?
 
BR
Torbj=F6rn
------_=_NextPart_001_01C2ED33.ADA03D30-- From majordomo-users-owner@greatcircle.com Tue Mar 18 07:15:17 2003 Received: from trip.mrball.net (66-214-180-43.la-cbi.charterpipeline.net [66.214.180.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 9EB3419608A for ; Tue, 18 Mar 2003 07:15:14 -0800 (PST) Received: by trip.mrball.net (Postfix, from userid 501) id 223022C0C4; Tue, 18 Mar 2003 10:15:09 -0500 (EST) Date: Tue, 18 Mar 2003 07:15:09 -0800 From: Todd Lyons To: "'majordomo-users@greatcircle.com'" Subject: Re: Trouble with config footer in HTML mails Message-ID: <20030318151509.GB17187@mrball.net> Mail-Followup-To: "'majordomo-users@greatcircle.com'" References: <1254192C94D3D411B8060008C7E6AEEB075E029E@esealnt408> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; x-action=pgp-signed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1254192C94D3D411B8060008C7E6AEEB075E029E@esealnt408> Organization: Progressive Linux Consultants X-mailer-flag: Outlook? Viral infections & bugs non-stop! Use another mailer if you value your data. User-Agent: Mutt/1.5.3i X-Archive-Number: 200303/94 X-Sequence-Number: 2965 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Torbjörn Sagen (PAC) wanted us to know: > This footer follows nicely when sending out mails in plain text format > (or using rich text that will be converted to plain text) > However, it does not work when sending HTML mails. > I want my footer to work both with HTML and plain text mails. How can > I achieve this? Rewrite majordomo is about the only way. It was made to work with plain text messages, not multipart messages. - -- Blue skies... Todd Public key: http://www.mrball.net/todd.asc P.S. Before I clicked 'send' on this composition I decided to consult the oracle, I mean Google, on the question of... --Clay Claiborne Linux kernel 2.4.19-24mdk 4 users, load average: 0.00, 0.01, 0.07 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: http://www.mrball.net/todd.asc iD8DBQE+dzf9IBT1264ScBURArlBAKCgx2GQdSq4QT8o1WVNmR1ALyuCwgCdFjxO 581ITAbmsUBauhvM6+2U6yo= =JKZh -----END PGP SIGNATURE----- From majordomo-users-owner@greatcircle.com Tue Mar 18 11:45:21 2003 Received: from LinuxIRC.com (wsip68-15-171-16.no.no.cox.net [68.15.171.16]) by mycroft.greatcircle.com (Postfix) with ESMTP id 97EDA195A1A for ; Tue, 18 Mar 2003 11:45:20 -0800 (PST) Received: from MyBox (tech447.com [68.15.171.17]) by LinuxIRC.com (8.12.8/8.12.8) with ESMTP id h2IJmBr9032300 for ; Tue, 18 Mar 2003 13:48:11 -0600 Subject: reply-to not working From: techie To: Majordomo-users@GreatCircle.COM Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 18 Mar 2003 14:18:16 -0500 Message-Id: <1048015096.22624.12.camel@MyBox> Mime-Version: 1.0 X-Archive-Number: 200303/95 X-Sequence-Number: 2966 im a using RH 8.0 with sendmail-8.12.8-1.80 and perl-5.8.0-55 i have set up the techtalk.config file to reply_to = techtalk@tech447.com but still not getting a reply to list in the email can anyone help? thanks From majordomo-users-owner@greatcircle.com Tue Mar 18 14:27:43 2003 Received: from gateway.hns.com (gateway.hns.com [208.236.67.13]) by mycroft.greatcircle.com (Postfix) with ESMTP id DF9A9195A34 for ; Tue, 18 Mar 2003 14:27:36 -0800 (PST) Received: from excore1.hns.com (excore1.hns.com [139.85.52.104]) by gateway.hns.com (Switch-3.0.3/Switch-3.0.0) with ESMTP id h2IMRXnL021658 for ; Tue, 18 Mar 2003 17:27:34 -0500 (EST) Received: from hns.com (coresun3.md.hnsnet [10.32.12.200]) by excore1.hns.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h2IMRS802013 for ; Tue, 18 Mar 2003 17:27:28 -0500 (EST) Message-ID: <3E779D4E.3010607@hns.com> Date: Tue, 18 Mar 2003 17:27:26 -0500 From: Jaysheel Mehd User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Majordomo-Users Subject: Majorcool and Archive Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090201050001010501010504" X-Filtered: Sendmail MIME Filter v1.0.8 excore1.hns.com h2IMRS802013 X-Archive-Number: 200303/96 X-Sequence-Number: 2967 This is a cryptographically signed message in MIME format. --------------ms090201050001010501010504 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi all, I am trying to implement list archiving and the search features through Majorcool. I am currently running archive on the server and the files are being listed over there. I want to these files to be displayed on web page. any clues? Thanks in advance Jaysheel --------------ms090201050001010501010504 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEH AQAAoIIMDDCCAy4wggKXoAMCAQICEQDSdi6NFAw9fbKoJV2v7g11MA0GCSqG SIb3DQEBAgUAMF8xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwg SW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZp Y2F0aW9uIEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5 NTlaMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVy aVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNv bS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5 ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1 YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0GCSqGSIb3DQEB AQUAA4GNADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqd ufBou5XZMUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScK XbawNkIztW5UiE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdq yErICQbkmQIDAQABo3wwejARBglghkgBhvhCAQEEBAMCAQYwRwYDVR0gBEAw PjA8BgtghkgBhvhFAQcBATAtMCsGCCsGAQUFBwIBFh93d3cudmVyaXNpZ24u Y29tL3JlcG9zaXRvcnkvUlBBMA8GA1UdEwQIMAYBAf8CAQAwCwYDVR0PBAQD AgEGMA0GCSqGSIb3DQEBAgUAA4GBAIi4Nzvd2pQ3AK2qn+GBAXEekmptL/bx ndPKZDjcG5gMB4ZbhRVqD7lJhaSV8Rd9Z7R/LSzdmkKewz60jqrlCwbe8lYq +jPHvhnXU0zDvcjjF7WkSUJj7MKmFw9dWBpJPJBcVaNlIAD9GCDlX4KmsaiS xVhqwY0DPOvDzQWikK5uMIIEaTCCA9KgAwIBAgIQfWzHfO+DvWIbj3LfU/z/ LTANBgkqhkiG9w0BAQQFADCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4x HzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3 dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3JwLiBCeSBSZWYu LExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEgQ0Eg SW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZDAe Fw0wMjA0MTgwMDAwMDBaFw0wMzA0MTgyMzU5NTlaMIIBDTEXMBUGA1UEChMO VmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdv cmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEg SW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNv bmEgTm90IFZhbGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAx IC0gTmV0c2NhcGUgRnVsbCBTZXJ2aWNlMRYwFAYDVQQDFA1KYXlzaGVlbCBN ZWhkMRwwGgYJKoZIhvcNAQkBFg1qbWVoZEBobnMuY29tMIGfMA0GCSqGSIb3 DQEBAQUAA4GNADCBiQKBgQC5sIxeMk9dOcks0T3GE23ztjuHtD0O/hoWAxQr /7nD26C8EakcvcRsqneZYrHqJrsw6LIWNVbIDZIsCmkd26XkrVXarPsetVD5 HDBsBhvmYqvWpcQsBYMRbfzdA+HS30yAdF4vzdgV7kpcNXmG/ImLo+jASGVD ZGE4V+rTL4aRSQIDAQABo4IBBjCCAQIwCQYDVR0TBAIwADCBrAYDVR0gBIGk MIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93 d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWdu LCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJl bmNlIGxpYWIuIGx0ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQD AgeAMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29t L2NsYXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAAUyS3fwO4bqWOEVZSasz 8SqfWw4HAokPjT77hwREMpNPlvB1Hgv02eUMIT7TyzDCTt4/NLA4wIGLxDBT 4h8M4NWLSj2MPWtBciwI3Pycd3b1NCp9cNPAsiJ0TQxF1n3gES5IdfwJCFyX jW2SX5hprqchvp34oOb28o8ByE0dB/kwggRpMIID0qADAgECAhB9bMd874O9 YhuPct9T/P8tMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2ln biwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQG A1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAu IEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xh c3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFs aWRhdGVkMB4XDTAyMDQxODAwMDAwMFoXDTAzMDQxODIzNTk1OVowggENMRcw FQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0 b3J5L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UE CxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElE IENsYXNzIDEgLSBOZXRzY2FwZSBGdWxsIFNlcnZpY2UxFjAUBgNVBAMUDUph eXNoZWVsIE1laGQxHDAaBgkqhkiG9w0BCQEWDWptZWhkQGhucy5jb20wgZ8w DQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALmwjF4yT105ySzRPcYTbfO2O4e0 PQ7+GhYDFCv/ucPboLwRqRy9xGyqd5liseomuzDoshY1VsgNkiwKaR3bpeSt Vdqs+x61UPkcMGwGG+Ziq9alxCwFgxFt/N0D4dLfTIB0Xi/N2BXuSlw1eYb8 iYuj6MBIZUNkYThX6tMvhpFJAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGs BgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxo dHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYO VmVyaVNpZ24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBi eSByZWZlcmVuY2UgbGlhYi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgB hvhCAQEEBAMCB4AwMwYDVR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJp c2lnbi5jb20vY2xhc3MxLmNybDANBgkqhkiG9w0BAQQFAAOBgQABTJLd/A7h upY4RVlJqzPxKp9bDgcCiQ+NPvuHBEQyk0+W8HUeC/TZ5QwhPtPLMMJO3j80 sDjAgYvEMFPiHwzg1YtKPYw9a0FyLAjc/Jx3dvU0Kn1w08CyInRNDEXWfeAR Lkh1/AkIXJeNbZJfmGmupyG+nfig5vbyjwHITR0H+TGCAzQwggMwAgEBMIHh MIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9y ZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFI MEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNj cmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkAhB9bMd874O9YhuPct9T/P8t MAkGBSsOAwIaBQCgggGoMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJ KoZIhvcNAQkFMQ8XDTAzMDMxODIyMjcyN1owIwYJKoZIhvcNAQkEMRYEFHm7 6trhprObef+KJQ2qbmzNzD2ZMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcN AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0G CCqGSIb3DQMCAgEoMIH0BgsqhkiG9w0BCRACCzGB5KCB4TCBzDEXMBUGA1UE ChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l dHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S UEEgSW5jb3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1Zl cmlTaWduIENsYXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNv bmEgTm90IFZhbGlkYXRlZAIQfWzHfO+DvWIbj3LfU/z/LTANBgkqhkiG9w0B AQEFAASBgFoMz66bvuk/l8qFyUDKwb3hSpc0u7gobH6+O7VKVn7vDaBayg7B wmbJbp2bNYABv5tlnZxCyKcGZHX8mm/gSRKZ3ZL6g0COzsbfbtOA8QPS6vIf xFyKPoSJO5ezv/PSmoD45zzZFJw5Ni2M6na3EAke541dr8ZkOb1aydXhodVT AAAAAAAA --------------ms090201050001010501010504-- From majordomo-users-owner@greatcircle.com Fri Mar 21 13:49:46 2003 Received: from lx2.colstate.edu (sub193206.ColState.EDU [168.26.193.206]) by mycroft.greatcircle.com (Postfix) with ESMTP id 6D7311961E3 for ; Fri, 21 Mar 2003 13:49:44 -0800 (PST) Received: from staffmail.colstate.edu (staffmail.ColState.EDU [168.26.193.34]) by lx2.colstate.edu (8.12.8/8.12.8) with ESMTP id h2LLnjKG012304 for ; Fri, 21 Mar 2003 16:49:45 -0500 Received: from WIND/SpoolDir by staffmail.colstate.edu (Mercury 1.48); 21 Mar 03 16:49:09 -0500 Received: from SpoolDir by WIND (Mercury 1.48); 21 Mar 03 16:48:53 -0500 From: "Mack" Organization: Columbus State Univ., Columbus, Ga To: majordomo-users@greatcircle.com Date: Fri, 21 Mar 2003 16:48:49 -0500 MIME-Version: 1.0 Subject: difference in archive and archive2.pl Message-ID: <3E7B4271.17304.5195472@localhost> X-mailer: Pegasus Mail for Windows (v4.02) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Archive-Number: 200303/97 X-Sequence-Number: 2968 Hi! Just wondering...what's the difference between the files "archive" and "archive2.pl"? I found these in my majordomo folder (/usr/local/majordomo-1.94.5). Thanks! mack From majordomo-users-owner@greatcircle.com Sat Mar 22 14:26:05 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 135D5195A5F for ; Sat, 22 Mar 2003 14:26:04 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2MMbYkc013176; Sat, 22 Mar 2003 16:37:34 -0600 Message-ID: <3E7CE306.9050304@sonny.org> Date: Sat, 22 Mar 2003 16:26:14 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mack Cc: majordomo-users@greatcircle.com Subject: Re: difference in archive and archive2.pl References: <3E7B4271.17304.5195472@localhost> In-Reply-To: <3E7B4271.17304.5195472@localhost> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/98 X-Sequence-Number: 2969 Are you sure "archive" is not a directory, and "archive2.pl" is the script that builds archives in that directory? I have archive2.pl in my majordomo directory and archive.pl in a subdirectory of majordomo called Tools. The archive2.pl script is newer and a bit more sophisticated than the older Tools/archive.pl script. Dan Liston Mack wrote: > Hi! > > Just wondering...what's the difference between the files "archive" and "archive2.pl"? > I found these in my majordomo folder (/usr/local/majordomo-1.94.5). > > Thanks! > mack From majordomo-users-owner@greatcircle.com Sun Mar 23 20:40:58 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 9B0C3196001 for ; Sun, 23 Mar 2003 20:40:55 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2O4r4kc001631; Sun, 23 Mar 2003 22:53:04 -0600 Message-ID: <3E7E8C7B.2040407@sonny.org> Date: Sun, 23 Mar 2003 22:41:31 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mack Ragan , Majordomo Users Subject: Re: difference in archive and archive2.pl References: <20030324041005.KVBJ28028.imf43bis.bellsouth.net@mail.bellsouth.net> In-Reply-To: <20030324041005.KVBJ28028.imf43bis.bellsouth.net@mail.bellsouth.net> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/99 X-Sequence-Number: 2970 The foldername.archive is a setting in the majordomo.cf file regarding archive location, $filedir and $filedir_suffix. You want to make sure these directories are owned by majordomo and are *not* group or world "writable". Dan Liston Mack Ragan wrote: > Yep, "archive2.pl" showed up after a default "clean" install of > Majordomo 1.94.5. I looked and found "archive" in a backup folder > of a previous install of Majordomo 1.94.5. But, the previous install > folder also included any changes made by Majorcool. So, maybe > Majorcool put "archive" there? Anyhow, I guess it's no big deal as > long as Majordomo 1.94.5 knows to use "archive2.pl" instead of "archive" > (which shows up in my /var/log/maillog, not "archive2.pl"). My > questions was prompted by my receiving emails about "foldername".archive > and permission denied on that folder. > > thanks, > mack > > > >> >> From: Daniel Liston >> Date: 2003/03/22 Sat PM 05:26:14 EST >> To: Mack >> CC: majordomo-users@greatcircle.com >> Subject: Re: difference in archive and archive2.pl >> >> Are you sure "archive" is not a directory, and "archive2.pl" is the >> script that builds archives in that directory? >> >> I have archive2.pl in my majordomo directory and archive.pl in a >> subdirectory of majordomo called Tools. The archive2.pl script is >> newer and a bit more sophisticated than the older Tools/archive.pl >> script. >> >> Dan Liston >> >> Mack wrote: >> > Hi! >> > >> > Just wondering...what's the difference between the files "archive" and "archive2.pl"? >> > I found these in my majordomo folder (/usr/local/majordomo-1.94.5). >> > >> > Thanks! >> > mack >> >> >> From majordomo-users-owner@greatcircle.com Mon Mar 24 12:11:36 2003 Received: from mailgate.intershop.de (mailgate.intershop.de [217.17.202.241]) by mycroft.greatcircle.com (Postfix) with ESMTP id 89393196243 for ; Mon, 24 Mar 2003 12:11:32 -0800 (PST) Received: from jahreskarenzabrechnungszeitraum.it.j.intershop.de ([10.0.88.129]) by mailgate.intershop.de (8.11.6/8.11.6) with ESMTP id h2OKBTr25636 for ; Mon, 24 Mar 2003 21:11:29 +0100 (MET) Received: from jahreskarenzabrechnungszeitraum.it.j.intershop.de (localhost [127.0.0.1]) by jahreskarenzabrechnungszeitraum.it.j.intershop.de (8.12.2+Sun/8.12.2) with ESMTP id h2OKBTAf007735 for ; Mon, 24 Mar 2003 21:11:29 +0100 (CET) Received: (from rainer@localhost) by jahreskarenzabrechnungszeitraum.it.j.intershop.de (8.12.2+Sun/8.12.2/Submit) id h2OKBSIn007734 for majordomo-users@greatcircle.com; Mon, 24 Mar 2003 21:11:28 +0100 (CET) Date: Mon, 24 Mar 2003 21:11:28 +0100 From: Rainer Sokoll To: majordomo-users@greatcircle.com Subject: Splitting outgoing mail in multiple instances? Message-ID: <20030324201128.GA7619@jahreskarenzabrechnungszeitraum.intershop.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Message-Flag: formatting your hard disk.... X-homepage: http://private.homepages.intershop.de/rainer X-pgp-fingerprint: A5 AC C6 70 DA 42 EB 8A 4F B3 65 31 28 C6 57 87 X-Geek-Code-1: -----BEGIN GEEK CODE BLOCK----- X-Geek-Code-2: Version: 3.1 X-Geek-Code-3: GCM$/C d- s: a C++ UL++++$ P->+++ L+++ E--- W+ N++ o-- K- w !O M- !V X-Geek-Code-4: PS+ PE Y+ PGP+ t- !5 X- R- tv- b+>+++ !DI D+ G e+++ h---- r+++ y+++ X-Geek-Code-5: ------END GEEK CODE BLOCK------ X-MimeOLE: Ole, Ole, Ole X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) X-Spam-Status: No, hits=-100.9 required=100.0 tests=SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_MUTT, USER_IN_WHITELIST version=2.44 X-Archive-Number: 200303/100 X-Sequence-Number: 2971 Hi there: my setup: Home ISP +-------------------------+ +----------+ | majordomo sendmail | | sendmail | | 1.94.5 <--> 8.12.6 | UUCP | 8.12.8 | +-------------------------+ +----------+ I have one list @home; it worked fine from the very beginning. But now, I get error messages by uucp@ISP, saying: ------8<----- Message from UUCP on jengate Mon Mar 24 20:00:09 2003 Execution request failed: rmail [lots of addresses] Standard error output was: rmail: /usr/lib/sendmail ------8<----- I think this happened when the subsciber's count crossed 150 or so. All these addresses seem to be in one RCPT-TO:-line. Now for my question: is it possible to force majordomo to generate multiple mails? Or is there another way to get the mails delivered? Unfortunatlaly, I cannot see where the real problem is: majordomo. sendmail or even rmail. Any help is highly welcome, Rainer From majordomo-users-owner@greatcircle.com Mon Mar 24 12:55:41 2003 Received: from fortuna.host4u.net (fortuna.host4u.net [216.71.64.64]) by mycroft.greatcircle.com (Postfix) with ESMTP id 35BAF1961F0 for ; Mon, 24 Mar 2003 12:54:40 -0800 (PST) Received: from MATT (cust-208-187-207-90.bbsc.net [208.187.207.90] (may be forged)) by fortuna.host4u.net (8.11.6/8.11.6) with ESMTP id h2OKnhd26536 for ; Mon, 24 Mar 2003 14:49:43 -0600 From: "Matt Mahoney" To: Subject: Permission Problems Date: Mon, 24 Mar 2003 13:54:33 -0700 Message-ID: <002f01c2f247$96f47c40$c80aa8c0@MATT> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Archive-Number: 200303/101 X-Sequence-Number: 2972 I have no clue what my Majordomo is doing. Here is a brief summary: > > 1 - Installed RPM > 2 - Setup the wrapper to work with Sendmail > 3 - Setup moderation and maintainer email address - mattm@ems-i.net > (which is the server and this forwards to my actual address > mattm@ems-i.com) > 4 - Setup maillist gms-l , sms-l and wms-l > 5 - Send subscription requests to majordomo@ems-i.net with subscribe > gms-l in the message body and sent it plain text. > 6 - I get the > message back saying somebody most likely you requested to subscribe > with an authorization code to send back to mattm@ems-i.com. > 7 - I send > it to mattm@ems-i.com I get the request to authorize for moderation > and I authorize it and it should be done. > > Problem: It doesn't write the address to the gms-l file in my > /var/lib/majordomo/lists folder. > > It used to be setup with 755 permissions with root as owner and > majordomo as the group. I changed the user to majordom like everything > I have read and it still will not write to the file. Matt Mahoney Web Developer mattm@ems-i.com ems-i.com 801-302-1400 Phone 801-302-1160 Fax From majordomo-users-owner@greatcircle.com Mon Mar 24 12:59:10 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 78198195A16 for ; Mon, 24 Mar 2003 12:59:09 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2OLBekc008623; Mon, 24 Mar 2003 15:11:40 -0600 Message-ID: <3E7F719D.108@sonny.org> Date: Mon, 24 Mar 2003 14:59:09 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rainer Sokoll Cc: majordomo-users@greatcircle.com Subject: Re: Splitting outgoing mail in multiple instances? References: <20030324201128.GA7619@jahreskarenzabrechnungszeitraum.intershop.de> X-Enigmail-Version: 0.63.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/102 X-Sequence-Number: 2973 Bulk_mailer can split your outgoing mail by domain and number of recipients. man bulk_mailer SYNOPSIS bulk_mailer [-comment comment] [-debugf] [-domain domainname] [-maxdomains maxdomains] [-maxsize maxsize] [-owner list-owner-address] [-precedence precedence-keyword] [-reply-to reply-address] [+reply-to reply-address] [-s] [-sendmail sendmail-flags] [-v] envelope-from recipient-list-file You can put this on your $list-outgoing alias like this, test-outgoing: "|/usr/sbin/bulk_mailer owner-test@DOMAIN.TLD /var/lib/majordomo/lists/test" but to break the envelope up by domains you also need "-maxdomains 1" before the owner address. Dan Liston Rainer Sokoll wrote: > Hi there: > > my setup: > > Home ISP > +-------------------------+ +----------+ > | majordomo sendmail | | sendmail | > | 1.94.5 <--> 8.12.6 | UUCP | 8.12.8 | > +-------------------------+ +----------+ > > I have one list @home; it worked fine from the very beginning. But now, > I get error messages by uucp@ISP, saying: > > ------8<----- > Message from UUCP on jengate Mon Mar 24 20:00:09 2003 > > Execution request failed: > rmail [lots of addresses] > Standard error output was: > rmail: /usr/lib/sendmail > ------8<----- > > I think this happened when the subsciber's count crossed 150 or so. All > these addresses seem to be in one RCPT-TO:-line. > Now for my question: is it possible to force majordomo to generate > multiple mails? Or is there another way to get the mails delivered? > Unfortunatlaly, I cannot see where the real problem is: majordomo. > sendmail or even rmail. > > Any help is highly welcome, > > Rainer From majordomo-users-owner@greatcircle.com Mon Mar 24 13:50:03 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id C0320195F8F for ; Mon, 24 Mar 2003 13:50:01 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2OM2Rkc008856; Mon, 24 Mar 2003 16:02:28 -0600 Message-ID: <3E7F7D84.90807@sonny.org> Date: Mon, 24 Mar 2003 15:49:56 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matt Mahoney Cc: majordomo-users@greatcircle.com Subject: Re: Permission Problems References: <002f01c2f247$96f47c40$c80aa8c0@MATT> In-Reply-To: <002f01c2f247$96f47c40$c80aa8c0@MATT> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/103 X-Sequence-Number: 2974 Matt Mahoney wrote: > I have no clue what my Majordomo is doing. Here is a brief summary: >> >> 1 - Installed RPM What version of rpm file did you use for installing majordomo? Can we assume 1.94.5-2? > >> 2 - Setup the wrapper to work with Sendmail What version of sendmail are you running? Is RedHat linux your OS? What version? > >> 3 - Setup moderation and maintainer email address - mattm@ems-i.net >> (which is the server and this forwards to my actual address >> mattm@ems-i.com) Exactly which settings in the config file did you use for these? > >> 4 - Setup maillist gms-l , sms-l and wms-l What do your aliases for these lists look like? Feel free to offer a generic look-alike set of aliases if you are worried about the security of your lists. > >> 5 - Send subscription requests to majordomo@ems-i.net with subscribe >> gms-l in the message body and sent it plain text. Sounds normal. > >> 6 - I get the >> message back saying somebody most likely you requested to subscribe >> with an authorization code to send back to mattm@ems-i.com. I think the authorization key should have been sent back to the majordomo address at ems-i.com rather than the moderator's address. > >> 7 - I send >> it to mattm@ems-i.com I get the request to authorize for moderation >> and I authorize it and it should be done. What command did you use to authorize the membership in the list? >> >> Problem: It doesn't write the address to the gms-l file in my >> /var/lib/majordomo/lists folder. >> >> It used to be setup with 755 permissions with root as owner and >> majordomo as the group. I changed the user to majordom like everything Are any of the directories before "lists" world or group writable? Are there any indicators of sendmail interferance in the maillog file? What about the /var/lib/majordomo/log file? Sorry if I seem anal. Specific information will help nail down the problem much quicker than a general summary. You did summarize quite well though. Dan Liston From majordomo-users-owner@greatcircle.com Tue Mar 25 10:01:43 2003 Received: from tecoma.mccc.edu (tecoma.mccc.edu [198.133.170.1]) by mycroft.greatcircle.com (Postfix) with ESMTP id 6C174195FCE for ; Tue, 25 Mar 2003 10:01:38 -0800 (PST) Received: from tecoma (tecoma [198.133.170.1]) by tecoma.mccc.edu (8.12.8/8.11.4) with ESMTP id h2PI1SpQ029353 for ; Tue, 25 Mar 2003 13:01:28 -0500 (EST) Date: Tue, 25 Mar 2003 13:01:28 -0500 (EST) From: Pete Holsberg To: majordomo-users@greatcircle.com Subject: Getting Help Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200303/104 X-Sequence-Number: 2975 I've posted a couple of messages to this address but they don't seem to come back to me nor do they appear in the archives. In fact, they seem to be going into a black hole! Pete From majordomo-users-owner@greatcircle.com Tue Mar 25 10:19:38 2003 Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by mycroft.greatcircle.com (Postfix) with ESMTP id 130F6196191 for ; Tue, 25 Mar 2003 10:19:38 -0800 (PST) Received: from h-69-3-76-32.phndaz91.covad.net ([69.3.76.32] helo=Vaio.earthlink.net) by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18xt1N-0006RF-00 for majordomo-users@greatcircle.com; Tue, 25 Mar 2003 10:19:37 -0800 Message-Id: <5.2.0.9.2.20030325111903.00bbb298@pop.earthlink.net> X-Sender: bobbish@pop.earthlink.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 25 Mar 2003 11:19:36 -0700 To: majordomo-users@greatcircle.com From: Bob Bish Subject: Re: Getting Help In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200303/105 X-Sequence-Number: 2976 At 11:01 AM 3/25/2003, Pete Holsberg wrote: >I've posted a couple of messages to this address but they >don't seem to come back to me nor do they appear in the >archives. > >In fact, they seem to be going into a black hole! I also posted a message several days ago which never appeared. Is this list moderated? ...Bob From majordomo-users-owner@greatcircle.com Tue Mar 25 10:38:44 2003 Received: from mail2.wfi.com (mail2.360.net [64.114.26.208]) by mycroft.greatcircle.com (Postfix) with SMTP id EA21A1962C3 for ; Tue, 25 Mar 2003 10:38:42 -0800 (PST) Received: from svbcexgr01.wfi.com(172.16.16.68) by mail2.wfi.com via csmap id 19293; Tue, 25 Mar 2003 10:28:16 -0800 (PST) Received: by svbcexgr01.wfi.com with Internet Mail Service (5.5.2653.19) id ; Tue, 25 Mar 2003 10:37:04 -0800 Message-ID: <2DB8F063662FD511A0C7006008F6D05B03CE01B5@SVBCEXMB01.wfi.com> From: Gary Thandi To: majordomo-users@greatcircle.com Subject: Re: Getting Help Date: Tue, 25 Mar 2003 10:37:04 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Archive-Number: 200303/106 X-Sequence-Number: 2977 I had a similar problem. what ended up being the issue was that I had some "command like" words in the email which majordomo didn't like and as a result sent to the moderator for approval. -----Original Message----- From: Bob Bish [mailto:bobbish@earthlink.net] Sent: Tuesday, March 25, 2003 10:20 AM To: majordomo-users@greatcircle.com Subject: Re: Getting Help At 11:01 AM 3/25/2003, Pete Holsberg wrote: >I've posted a couple of messages to this address but they >don't seem to come back to me nor do they appear in the >archives. > >In fact, they seem to be going into a black hole! I also posted a message several days ago which never appeared. Is this list moderated? ...Bob From majordomo-users-owner@greatcircle.com Tue Mar 25 10:51:23 2003 Received: from carcy02-04.allcovered.com (unknown [216.148.212.104]) by mycroft.greatcircle.com (Postfix) with ESMTP id E2E79195ADF for ; Tue, 25 Mar 2003 10:51:22 -0800 (PST) Received: from [10.10.2.117] (63-203-55-10.ded.pacbell.net [63.203.55.10]) (authenticated bits=0) by carcy02-04.allcovered.com (8.12.8/8.12.8) with ESMTP id h2PIteSV025124; Tue, 25 Mar 2003 10:55:41 -0800 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Tue, 25 Mar 2003 10:51:20 -0800 Subject: Re: Getting Help From: Mike Walt To: Bob Bish , "'Majordomo-Users@Greatcircle. Com'" Message-ID: In-Reply-To: <5.2.0.9.2.20030325111903.00bbb298@pop.earthlink.net> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Archive-Number: 200303/107 X-Sequence-Number: 2978 Bob, I got your message :) Mike On 3/25/03 10:19 AM, "Bob Bish" wrote: > At 11:01 AM 3/25/2003, Pete Holsberg wrote: >> I've posted a couple of messages to this address but they >> don't seem to come back to me nor do they appear in the >> archives. >> >> In fact, they seem to be going into a black hole! > > I also posted a message several days ago which never appeared. Is this > list moderated? > > ...Bob From majordomo-users-owner@greatcircle.com Tue Mar 25 11:04:28 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 92B6B195F66 for ; Tue, 25 Mar 2003 11:04:25 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2PJHOkc014147 for ; Tue, 25 Mar 2003 13:17:24 -0600 Message-ID: <3E80A868.1080004@sonny.org> Date: Tue, 25 Mar 2003 13:05:12 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Re: Getting Help References: <5.2.0.9.2.20030325111903.00bbb298@pop.earthlink.net> In-Reply-To: <5.2.0.9.2.20030325111903.00bbb298@pop.earthlink.net> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/108 X-Sequence-Number: 2979 This list is not "moderated" TTBOMK, but does have the administrivia filters enabled. If you are sending a message that contains a taboo word or phrase within the first 10 lines of the message, it will be rerouted for approval before getting posted to the list. These can take up to several days depending on the available free time of the list-owner. Dan Liston Bob Bish wrote: > At 11:01 AM 3/25/2003, Pete Holsberg wrote: >>I've posted a couple of messages to this address but they >>don't seem to come back to me nor do they appear in the >>archives. >> >>In fact, they seem to be going into a black hole! > > I also posted a message several days ago which never appeared. Is this > list moderated? > > ...Bob From majordomo-users-owner@greatcircle.com Tue Mar 25 11:08:27 2003 Received: from phyllis.cloop.com (mailhub.closedloop.com [63.106.115.10]) by mycroft.greatcircle.com (Postfix) with ESMTP id C63BF19663C for ; Tue, 25 Mar 2003 11:08:24 -0800 (PST) Received: by PHYLLIS with Internet Mail Service (5.5.2653.19) id ; Tue, 25 Mar 2003 11:07:06 -0800 Message-ID: <628A3F367450D711A0E500065BECD77C06476F@PHYLLIS> From: Sunita Rajagopal To: majordomo-users@greatcircle.com Subject: mail filtering Date: Tue, 25 Mar 2003 11:06:59 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2F301.B5D27260" X-Archive-Number: 200303/109 X-Sequence-Number: 2980 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_01C2F301.B5D27260 Content-Type: text/plain; charset="iso-8859-1" How can I prevent majordomo from not processing mails coming from a particular email addresses. Is there any ways I can also make majordomo accept mail messages only from one domain, or known domains. Thanks Sunita ------_=_NextPart_001_01C2F301.B5D27260 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
email addresses.
Is there any ways I can also make majordomo accept mail messa=
ges only from one
domain, or known domains.
=
Thanks
Sunita

 <= /span>

------_=_NextPart_001_01C2F301.B5D27260-- From majordomo-users-owner@greatcircle.com Tue Mar 25 17:04:45 2003 Received: from cloud.ccsf.cc.ca.us (cloud.ccsf.cc.ca.us [147.144.1.212]) by mycroft.greatcircle.com (Postfix) with ESMTP id 9B923196258 for ; Tue, 25 Mar 2003 17:04:43 -0800 (PST) Received: from localhost (jjah@localhost) by cloud.ccsf.cc.ca.us (8.11.6/8.11.2) with ESMTP id h2Q14gp27041; Tue, 25 Mar 2003 17:04:42 -0800 (PST) Date: Tue, 25 Mar 2003 17:04:42 -0800 (PST) From: "Joe R. Jah" To: Sunita Rajagopal Cc: majordomo-users@greatcircle.com Subject: Re: mail filtering In-Reply-To: <628A3F367450D711A0E500065BECD77C06476F@PHYLLIS> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200303/110 X-Sequence-Number: 2981 On Tue, 25 Mar 2003, Sunita Rajagopal wrote: > Date: Tue, 25 Mar 2003 11:06:59 -0800 > From: Sunita Rajagopal > To: majordomo-users@greatcircle.com > Subject: mail filtering > > How can I prevent majordomo from not processing mails coming from a > particular email addresses. Date: Tue, 24 Dec 2002 17:19:23 -0600 From: Daniel Liston To: Wolfgang Schneider Cc: "majordomo-users@greatcircle.com" Subject: Re: "reg expressions" (taboo_header / taboo_body) The address to moderate would go in the taboo_headers either in the list.config file or in the global majordomo.cf file like this; /abc\@junkyard\.de/i and the signature would be filtered with taboo_body in either location like this; /the badmouth specialist/i The "/" character indicates the beginning and ending of what string of characters you are trying to match. The "i" at the end means you are ignoring upper/lower case of the string to be matched. The "\" inside the match is an escape symbol, telling the regex engine to match the following character "exactly" rather than interpret it as a character with special meaning, like "wildcard" or "variable". Make sure you utilize "resend" in your list's alias, or anything you do in the .config file with be wasted time and effort. Dan Liston > Is there any ways I can also make majordomo accept mail messages only from > one domain, or known domains. Here is a patch that extends the function of restrict_post attribute, for Majordomo 1.94.5; it will allow you to make Majordomo accept mail messages only from domains that you specify: ftp://ftp.ccsf.org/majordomo-patches/1.94.5/restrict2domain.1 Read the patch for usage and/or installation information. Regards, Joe -- _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ _-\<,_ _/ _/ _/_/_/ _/ _/ ......(_)/ (_) _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us From majordomo-users-owner@greatcircle.com Wed Mar 26 06:57:15 2003 Received: from tecoma.mccc.edu (tecoma.mccc.edu [198.133.170.1]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1B687196221 for ; Wed, 26 Mar 2003 06:57:12 -0800 (PST) Received: from tecoma (tecoma [198.133.170.1]) by tecoma.mccc.edu (8.12.8/8.11.4) with ESMTP id h2QEv1pQ013276 for ; Wed, 26 Mar 2003 09:57:01 -0500 (EST) Date: Wed, 26 Mar 2003 09:57:00 -0500 (EST) From: Pete Holsberg To: majordomo-users@greatcircle.com Subject: Problem With A List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200303/111 X-Sequence-Number: 2982 My webhost company hosts a majordomo v1.94.4 mailing list for my community and it has been operating without problems for some time. Recently, it began acting strangely: messages would be sent to some of the list addresses and not to others. They claim that they cannot find anything wrong. Does anyone have any suggestions? Thanks, Pete From majordomo-users-owner@greatcircle.com Wed Mar 26 07:21:59 2003 Received: from skipper.averillpark.net (alb-24-194-112-77.nycap.rr.com [24.194.112.77]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2C9A3195A1E for ; Wed, 26 Mar 2003 07:21:58 -0800 (PST) Received: from rwelty by skipper.averillpark.net with local (Exim 4.10) id 18yCgG-0001HN-00 for majordomo-users@greatcircle.com; Wed, 26 Mar 2003 10:19:08 -0500 Date: Wed, 26 Mar 2003 10:19:07 -0500 (EST) From: Richard Welty Subject: Re: Problem With A List To: majordomo-users@greatcircle.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE References: In-Reply-To: X-Mailer: Mahogany 0.64 'Sparc', compiled for Linux 2.4.9-13 i686 Message-Id: X-Archive-Number: 200303/112 X-Sequence-Number: 2983 On Wed, 26 Mar 2003 09:57:00 -0500 (EST) Pete Holsberg wrote: > They claim that they cannot find anything wrong. > Does anyone have any suggestions? odds are it's an MTA problem and not a majordomo problem. you may also want to look at who is receiving and who is not receiving; it may be that one or more ISPs have spam blocking in place that is interfering with list delivery. presuming that your list is proper confirmed opt in, this would likely be collateral damage of one kind or another, or someone reporting non-spam as spam (which does happen from time to time.) richard -- Richard Welty rwelty@suespammers.org Averill Park Networking rwelty@averillpark.net Unix, Linux, IP Network Engineering, Security rwelty@krusty-motorsports.com 518-573-7592 From majordomo-users-owner@greatcircle.com Wed Mar 26 09:48:02 2003 Received: from phyllis.cloop.com (mailhub.closedloop.com [63.106.115.10]) by mycroft.greatcircle.com (Postfix) with ESMTP id 68805195A6B for ; Wed, 26 Mar 2003 09:44:43 -0800 (PST) Received: by PHYLLIS with Internet Mail Service (5.5.2653.19) id ; Wed, 26 Mar 2003 09:43:25 -0800 Message-ID: <628A3F367450D711A0E500065BECD77C064779@PHYLLIS> From: Sunita Rajagopal To: majordomo-users@greatcircle.com Subject: just have one email for subscription Date: Wed, 26 Mar 2003 09:43:16 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2F3BF.2E5E4BB0" X-Archive-Number: 200303/113 X-Sequence-Number: 2984 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_01C2F3BF.2E5E4BB0 Content-Type: text/plain; charset="iso-8859-1" Hi, Is there any ways that I could have just one email to confirm subscription, rather that have the user 1.send a message for subscription 2. send a 2nd message to confirm it. I would like to have just one email for request and confirming subscription.Users don't want to send 2 emails. Sunita ------_=_NextPart_001_01C2F3BF.2E5E4BB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,

Is there any ways that I could have just one email to confirm subscription, rather that have the user

1.send a message for subscription

2. send a 2nd message to confirm it.

 <= /span>

I would like to have just one email for request  and confirming subscription.Users= don’t want to send 2 emails.

Sunita

------_=_NextPart_001_01C2F3BF.2E5E4BB0-- From majordomo-users-owner@greatcircle.com Wed Mar 26 09:50:23 2003 Received: from tecoma.mccc.edu (tecoma.mccc.edu [198.133.170.1]) by mycroft.greatcircle.com (Postfix) with ESMTP id A32D019627F for ; Wed, 26 Mar 2003 09:50:08 -0800 (PST) Received: from tecoma (tecoma [198.133.170.1]) by tecoma.mccc.edu (8.12.8/8.11.4) with ESMTP id h2QHo7pQ026772; Wed, 26 Mar 2003 12:50:07 -0500 (EST) Date: Wed, 26 Mar 2003 12:50:07 -0500 (EST) From: Pete Holsberg To: Richard Welty Cc: majordomo-users@greatcircle.com Subject: Re: Problem With A List In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200303/114 X-Sequence-Number: 2985 On Wed, 26 Mar 2003, Richard Welty wrote: > On Wed, 26 Mar 2003 09:57:00 -0500 (EST) Pete Holsberg wrote: > > They claim that they cannot find anything wrong. > > > Does anyone have any suggestions? > > odds are it's an MTA problem and not a majordomo problem. The MTA is sendmail. Any suggestions as tohow to go about troubleshooting? > you may also want to look at who is receiving and who is > not receiving; it may be that one or more ISPs have spam > blocking in place that is interfering with list delivery. When I had about 300 names on the list, one of my two email addresses did not get mail and the other did. Now that I have reduced the number on the list to about 5, everyone gets mail. Can sendmail be configured to limit the number of recipients???? Thanks, Pete From majordomo-users-owner@greatcircle.com Wed Mar 26 10:25:00 2003 Received: from skipper.averillpark.net (alb-24-194-112-77.nycap.rr.com [24.194.112.77]) by mycroft.greatcircle.com (Postfix) with ESMTP id 91E2E1963D9 for ; Wed, 26 Mar 2003 10:24:58 -0800 (PST) Received: from rwelty by skipper.averillpark.net with local (Exim 4.10) id 18yFYp-0001Pj-00 for majordomo-users@greatcircle.com; Wed, 26 Mar 2003 13:23:39 -0500 Date: Wed, 26 Mar 2003 13:23:39 -0500 (EST) From: Richard Welty Subject: Re: Problem With A List To: majordomo-users@greatcircle.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE References: In-Reply-To: X-Mailer: Mahogany 0.64 'Sparc', compiled for Linux 2.4.9-13 i686 Message-Id: X-Archive-Number: 200303/115 X-Sequence-Number: 2986 On Wed, 26 Mar 2003 12:50:07 -0500 (EST) Pete Holsberg wrote: > > odds are it's an MTA problem and not a majordomo problem. > The MTA is sendmail. Any suggestions as tohow to go about > troubleshooting? it's been a long time since i used sendmail (6+ years now). i had problems similar to what you are having, but that was an old version, and the numbers on my lists were in the thousands, not hundreds. i seriously doubt my experience will be of any help. (the version of sendmail that was current 6 years ago had a very simple minded single threaded mail queue processing algorithm, and could stick on single problem email addresses for extended periods of time. bulk_mailer was one of the standard tools for mitigating this problem, and helped a lot, although it was/is far from perfect. i gather that the sendmail queuing problems have long since been addressed.) > > you may also want to look at who is receiving and who is > > not receiving; it may be that one or more ISPs have spam > > blocking in place that is interfering with list delivery. > When I had about 300 names on the list, one of my two > email addresses did not get mail and the other did. i should have been clearer. can you see patterns related to specific ISPs and mail service providers? (e.g., hotmail/msn has had some recent periods when certain servers were having trouble delivering to it lately.) also, you might want to hit one of the DNSBL lookup services and see if the IP address for the machine you're sending from is listed on any of them. richard -- Richard Welty rwelty@suespammers.org Averill Park Networking rwelty@averillpark.net Unix, Linux, IP Network Engineering, Security rwelty@krusty-motorsports.com 518-573-7592 From majordomo-users-owner@greatcircle.com Wed Mar 26 11:49:38 2003 Received: from web13308.mail.yahoo.com (web13308.mail.yahoo.com [216.136.175.44]) by mycroft.greatcircle.com (Postfix) with SMTP id E1B531959FF for ; Wed, 26 Mar 2003 11:49:36 -0800 (PST) Message-ID: <20030326194934.33273.qmail@web13308.mail.yahoo.com> Received: from [209.87.17.121] by web13308.mail.yahoo.com via HTTP; Wed, 26 Mar 2003 14:49:34 EST Date: Wed, 26 Mar 2003 14:49:34 -0500 (EST) From: Bob Henderson Subject: Re: Problem With A List To: rwelty@suespammers.org, pjh@mccc.edu, majordomo-users@greatcircle.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Archive-Number: 200303/116 X-Sequence-Number: 2987 We've come across exactly this same problem recently after upgrading sendmail. Here's what's been working fine for us: majordomo 1.94.5 Redhat Linux 7.2 sendmail-8.11.6-3.i386.rpm sendmail-cf-8.11.6-3.i386.rpm Then we upgraded sendmail to 8.11.6-23.i386.rpm/cf-8.11.6-23.i386.rpm to address a sendmail vulnerability and started having problems where although all posts were getting through to the digest, many were not making it to the list, and some were getting sent to some users and not others. We backed off to our original sendmail and the majordomo problems went away. We're looking now to upgrade sendmail to 8.12.8. I'm interested to hear from anyone who's upgraded their sendmail to 8.12.8....has it caused your majordomo any grief? Thanks, Bob -----Original Message-----From: Richard Welty [mailto:rwelty@suespammers.org]Sent: Wednesday, March 26, 2003 7:19 AMTo: majordomo-users@greatcircle.comSubject: Re: Problem With A ListOn Wed, 26 Mar 2003 09:57:00 -0500 (EST) Pete Holsberg wrote:> They claim that they cannot find anything wrong.> Does anyone have any suggestions?odds are it's an MTA problem and not a majordomo problem.you may also want to look at who is receiving and who is not receiving;it may be that one or more ISPs have spam blocking in place that isinterfering with list delivery. presuming that your list is properconfirmed opt in, this would likely be collateral damage of one kind oranother, or someone reporting non-spam as spam (which does happen from timeto time.)richard--Richard Weltyrwelty@suespammers.org Averill Park Networkingrwelty@averillpark.net Unix, Linux, IP Network Engineering, Securityrwelty@krusty-motorsports.com 518-573-7592 ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca From majordomo-users-owner@greatcircle.com Wed Mar 26 13:59:49 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 0B633195A89 for ; Wed, 26 Mar 2003 13:59:48 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2QLxk43021508; Wed, 26 Mar 2003 15:59:46 -0600 Message-ID: <3E8222D7.7060100@sonny.org> Date: Wed, 26 Mar 2003 15:59:51 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sunita Rajagopal Cc: majordomo-users@greatcircle.com Subject: Re: just have one email for subscription References: <628A3F367450D711A0E500065BECD77C064779@PHYLLIS> In-Reply-To: <628A3F367450D711A0E500065BECD77C064779@PHYLLIS> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Archive-Number: 200303/117 X-Sequence-Number: 2988 There is no concept of confirmation with just one email. The purpose of the 2nd (first and only confirmation) email is to verify that the address requesting membership to our list is valid/deliverable, and give the user a chance to change their mind about joining our list before adding them. If this does not serve your needs, just remove the +confirm from your list zubscribe_policy. Regardless of users not liking it, managing the lists will be much easier for _you_ long term if you leave it in. Dan Liston Sunita Rajagopal wrote: > Hi, > > Is there any ways that I could have just one email to confirm > subscription, rather that have the user > > 1.send a message for subscription > > 2. send a 2^nd message to confirm it. > > > > I would like to have just one email for request and confirming > subscription.Users don’t want to send 2 emails. > > Sunita > From majordomo-users-owner@greatcircle.com Wed Mar 26 22:18:22 2003 Received: from turkey.mail.pas.earthlink.net (turkey.mail.pas.earthlink.net [207.217.120.126]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2BEC4196045 for ; Wed, 26 Mar 2003 22:18:20 -0800 (PST) Received: from user-vcaum46.dsl.mindspring.com ([216.175.88.134] helo=queernet.org) by turkey.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18yQhz-0006Wd-00; Wed, 26 Mar 2003 22:17:51 -0800 Message-ID: <3E829791.2050808@queernet.org> Date: Wed, 26 Mar 2003 22:17:53 -0800 From: "Roger B.A. Klorese" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en, en-us, fr-be, fr-ca, fr-fr, fr-lu, fr-mc, fr-ch MIME-Version: 1.0 To: Daniel Liston Cc: Sunita Rajagopal , majordomo-users@greatcircle.com Subject: Re: just have one email for subscription References: <628A3F367450D711A0E500065BECD77C064779@PHYLLIS> <3E8222D7.7060100@sonny.org> In-Reply-To: <3E8222D7.7060100@sonny.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/118 X-Sequence-Number: 2989 Daniel Liston wrote: > > There is no concept of confirmation with just one email. The > purpose of the 2nd (first and only confirmation) email is to > verify that the address requesting membership to our list is > valid/deliverable, and give the user a chance to change their > mind about joining our list before adding them. If this does > not serve your needs, just remove the +confirm from your list > zubscribe_policy. Regardless of users not liking it, managing > the lists will be much easier for _you_ long term if you leave > it in. Let me explain this. Yes, your ACTUAL users don't like to send two messages. After all, they know they sent the first one. But how do the people whose enemies signed them up for 10,000 lists on the net without their acknowledgement by forging the From: line on the subscription requests feel about not having to confirm the subscription? If you're going to turn off confirmation, remember this: there are blacklists on the net for sites that don't do confirmation. You may have potential subscribers you're unable to send mail to at all because you don't require confirmation. From majordomo-users-owner@greatcircle.com Thu Mar 27 07:14:28 2003 Received: from mail.innovativebusiness.net (mail.innovativebusiness.net [65.209.59.13]) by mycroft.greatcircle.com (Postfix) with ESMTP id 68CE2195A01 for ; Thu, 27 Mar 2003 07:14:24 -0800 (PST) Received: from PETE (bastion.innovativebusiness.net [65.209.59.11]) by mail.innovativebusiness.net (8.12.2/8.12.2) with ESMTP id h2RFENRG017538 for ; Thu, 27 Mar 2003 10:14:23 -0500 From: "Peter Dumpert" To: majordomo-users@greatcircle.com Date: Thu, 27 Mar 2003 10:17:57 -0500 MIME-Version: 1.0 Subject: Re: Problem With A List Message-ID: <3E82CFD5.17516.3750C4@localhost> References: In-reply-to: X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/html; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Archive-Number: 200303/119 X-Sequence-Number: 2990


On 26 Mar 2003 at 12:50, Pete Holsberg wrote:

> When I had about 300 names on the list, one of my two
> email addresses did not get mail and the other did.
>
> Now that I have reduced the number on the list to about 5,
> everyone gets mail.
>
> Can sendmail be configured to limit the number of
> recipients????
>

Yes.  In your sendmail.mc file you do something like this:

            define(`confMAX_RCPTS_PER_MESSAGE', `100')dnl

Or if you're a masochist and like to tweak the .cf file,

            O MaxRecipientsPerMessage=100

If this isn't set, there is no limit.  It should be pretty easy to see if this is the case.  There would be a definite point in your list where no one after that point would have gotten the mail.

These days, a lot of spam masquerades as opt-in mailing lists. Filters are starting to look for opt-out instructions, disclaimers, etc. Ask some of your recipients who didn't get the mail whether their isp has spam filters.  If they do, there may be a way to configure it to let your list through.


--
Peter A. Dumpert
Innovative Computer Services LLC - web design/e-pubs/consulting
Innovative BusinessNet - an ISP for Business
www.innovativebusiness.net
Phone: 732-683-0092 ext 102  Fax: 732-577-9390
From majordomo-users-owner@greatcircle.com Thu Mar 27 14:30:29 2003 Received: from box1.vegas-hosting.com (box1.vegas-hosting.com [66.209.66.91]) by mycroft.greatcircle.com (Postfix) with ESMTP id 545FC19603D for ; Thu, 27 Mar 2003 14:30:28 -0800 (PST) Received: from CISLaptop (adsl-18-132-151.int.bellsouth.net [68.18.132.151]) (authenticated (0 bits)) by box1.vegas-hosting.com (8.11.6/8.11.6) with ESMTP id h2RMj3u21876 for ; Thu, 27 Mar 2003 14:45:03 -0800 Message-ID: <03a101c2f4b0$771a50f0$9601a8c0@CISLaptop> From: "Christopher Sparks" To: Subject: List Header Rewrite Date: Thu, 27 Mar 2003 17:30:25 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_039E_01C2F486.8DA570E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Archive-Number: 200303/120 X-Sequence-Number: 2991 This is a multi-part message in MIME format. ------=_NextPart_000_039E_01C2F486.8DA570E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am looking to replace the list name the name of the person getting the me= ssage. So the end user does not see the list name. Any ideas or suggestion= s? Example =46rom this From:Sparky@cniguru.com To:List@cniguru.com To This From:Sparky@cniguru.com To: joe@me.com TIA. ------=_NextPart_000_039E_01C2F486.8DA570E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I am looking to replace the list name the = name of=20 the person getting the message. So the end user does not see the list=20 name.  Any ideas or suggestions?
 
Example
From this
 
From:Sparky@cniguru.com
To:List@cniguru.com
 
To This
From:Sparky@cniguru.com
To: joe@me.com
 
TIA.
------=_NextPart_000_039E_01C2F486.8DA570E0-- From majordomo-users-owner@greatcircle.com Thu Mar 27 16:34:14 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id E421B19643C for ; Thu, 27 Mar 2003 16:34:12 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2S0Y743028626; Thu, 27 Mar 2003 18:34:10 -0600 Message-ID: <3E839888.8020803@sonny.org> Date: Thu, 27 Mar 2003 18:34:16 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christopher Sparks Cc: Majordomo-Users@greatcircle.com Subject: Re: List Header Rewrite References: <03a101c2f4b0$771a50f0$9601a8c0@CISLaptop> In-Reply-To: <03a101c2f4b0$771a50f0$9601a8c0@CISLaptop> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/121 X-Sequence-Number: 2992 Nope. You either have to rewrite code in majordomo, or use some other program that already does that. Dan Liston Christopher Sparks wrote: > I am looking to replace the list name the name of the person getting the > message. So the end user does not see the list name. Any ideas or > suggestions? > > Example > From this > > From:Sparky@cniguru.com > To:List@cniguru.com > > To This > From:Sparky@cniguru.com > To: joe@me.com > > TIA. From majordomo-users-owner@greatcircle.com Thu Mar 27 19:40:21 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 7DB8A195FD5 for ; Thu, 27 Mar 2003 19:40:19 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2S3eH43029559; Thu, 27 Mar 2003 21:40:17 -0600 Message-ID: <3E83C429.9050600@sonny.org> Date: Thu, 27 Mar 2003 21:40:25 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christopher Sparks , majordomo-users@greatcircle.com Subject: Re: List Header Rewrite References: <03a101c2f4b0$771a50f0$9601a8c0@CISLaptop> <3E839888.8020803@sonny.org> <000801c2f4cc$7fbeed80$fd00a8c0@sparkie> In-Reply-To: <000801c2f4cc$7fbeed80$fd00a8c0@sparkie> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/122 X-Sequence-Number: 2993 If I understand your query correctly, you need to rewrite the entire "resend" script. Currently it takes the entire contents of the list membership file and passes that with the message body to sendmail for delivery of a single message to many recipients. What you are trying to do is create a separate message for each recipient. You will need to parse the membership file, line by line, and generate a copy of the message for each recipient in order for the "To:" line to be the way you want it. Not to mention the RFCs you would be violating, the user that sent a message "To:" the list address probably would not appreciate having his message munged into separate personal messages to each member of the mailing list. Dan Liston Christopher Sparks wrote: > Could you give me any idea where to look in major domo to rewrite that code? > ----- Original Message ----- > From: "Daniel Liston" > To: "Christopher Sparks" > Cc: > Sent: Thursday, March 27, 2003 7:34 PM > Subject: Re: List Header Rewrite > > >> Nope. You either have to rewrite code in majordomo, or use some >> other program that already does that. >> >> Dan Liston >> >> Christopher Sparks wrote: >> > I am looking to replace the list name the name of the person getting the >> > message. So the end user does not see the list name. Any ideas or >> > suggestions? >> > >> > Example >> > From this >> > >> > From:Sparky@cniguru.com >> > To:List@cniguru.com >> > >> > To This >> > From:Sparky@cniguru.com >> > To: joe@me.com >> > >> > TIA. >> > From majordomo-users-owner@greatcircle.com Fri Mar 28 12:56:27 2003 Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by mycroft.greatcircle.com (Postfix) with ESMTP id 289B4196054 for ; Fri, 28 Mar 2003 12:56:26 -0800 (PST) Received: from h-69-3-76-244.phndaz91.covad.net ([69.3.76.244] helo=Vaio.earthlink.net) by harrier.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18z0tf-0004ij-00 for majordomo-users@greatcircle.com; Fri, 28 Mar 2003 12:56:19 -0800 Message-Id: <5.2.0.9.2.20030328131127.00ba17a0@pop.earthlink.net> X-Sender: bobbish@pop.earthlink.net X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Fri, 28 Mar 2003 13:56:16 -0700 To: majordomo-users@greatcircle.com From: Bob Bish Subject: Tying a web forum to a majordomo list Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200303/123 X-Sequence-Number: 2994 I'm looking at implementing a web forum which I would like to tie to the existing mailing list. The forum has e-mail capabilities for reading/posting/replying, but the e-mail side is minimal and feature-less. It would be great if I could run the e-mail side through majordomo (I'm using version 1.94.5). If I add the list posting address as a user of the web forum, then add the web forum as a member of the mailing list, a loop would be created. I'm thinking it might be possible to do this using two mailing lists, one for input and one for output. List A would have the web forum posting address as its only "member", so output would go to the forum. List B would have all the regular mailing list membership AND the posting address for List A. The posting address for List B would be a "user" of the web forum, so messages from the forum would be posted to List B and go out to members. Posts and replies from members would go to List A, and then to the web forum. Does anyone see any reason why this would not work? If so, might there be a better way to accomplish this? The web forum software in question has a patch available which will integrate it with existing mailing lists, and has been used with majordomo. It's a $289 patch, however, so if I can accomplish this without the patch it would be great. ...Bob From majordomo-users-owner@greatcircle.com Fri Mar 28 13:13:13 2003 Received: from planet.fef.com (unknown [166.90.172.7]) by mycroft.greatcircle.com (Postfix) with ESMTP id E412719634F for ; Fri, 28 Mar 2003 13:13:11 -0800 (PST) Received: from planet.fef.com (localhost.localdomain [127.0.0.1]) by planet.fef.com (8.12.8/8.12.8/check_local-5) with ESMTP id h2SLCimD010819; Fri, 28 Mar 2003 13:12:45 -0800 Received: (from alvin@localhost) by planet.fef.com (8.12.8/8.12.4/Submit) id h2SLCipW010818; Fri, 28 Mar 2003 13:12:44 -0800 From: Alvin Oga Message-Id: <200303282112.h2SLCipW010818@planet.fef.com> Subject: Re: Tying a web forum to a majordomo list To: bobbish@earthlink.net (Bob Bish) Date: Fri, 28 Mar 2003 13:12:44 -0800 (PST) Cc: majordomo-users@greatcircle.com In-Reply-To: <5.2.0.9.2.20030328131127.00ba17a0@pop.earthlink.net> from "Bob Bish" at Mar 28, 2003 01:56:16 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/124 X-Sequence-Number: 2995 hi ya bob i added a few lines to new-list so that i can maintain one RSVP list ... - they reply via email and it goes into one rsvp db - they reply via web and it goes into the same rsvp db new-list ( majordomo ) changes http://www.linux-consulting.com/Majordomo/new-list.rsvp - i use new-list as the autoresponder for ( send different *.info file for each autoresponder ) info@foo.com rsvp@foo.com map@foo.com - i see no point in web-gui for sending outgoing emails to a list... c ya alvin > Bob Bish wrote: > > I'm looking at implementing a web forum which I would like to tie to > the existing mailing list. The forum has e-mail capabilities for > reading/posting/replying, but the e-mail side is minimal and > feature-less. It would be great if I could run the e-mail side through > majordomo (I'm using version 1.94.5). > If I add the list posting address as a user of the web forum, then add > the web forum as a member of the mailing list, a loop would be created. > I'm thinking it might be possible to do this using two mailing lists, > one for input and one for output. List A would have the web forum posting > address as its only "member", so output would go to the forum. List B > would have all the regular mailing list membership AND the posting address > for List A. The posting address for List B would be a "user" of the web > forum, so messages from the forum would be posted to List B and go out to > members. Posts and replies from members would go to List A, and then to > the web forum. > Does anyone see any reason why this would not work? If so, might there > be a better way to accomplish this? > The web forum software in question has a patch available which will > integrate it with existing mailing lists, and has been used with > majordomo. It's a $289 patch, however, so if I can accomplish this without > the patch it would be great. > > ...Bob > From majordomo-users-owner@greatcircle.com Sat Mar 29 21:48:31 2003 Received: from trip.mrball.net (66-214-180-43.la-cbi.charterpipeline.net [66.214.180.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8AAC3195A58 for ; Sat, 29 Mar 2003 21:48:29 -0800 (PST) Received: by trip.mrball.net (Postfix, from userid 501) id D39492C09B; Sun, 30 Mar 2003 00:48:28 -0500 (EST) Date: Sat, 29 Mar 2003 21:48:28 -0800 From: Todd Lyons To: majordomo-users@greatcircle.com Subject: upgrade Message-ID: <20030330054828.GA19024@mrball.net> Mail-Followup-To: majordomo-users@greatcircle.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline Organization: Progressive Linux Consultants X-mailer-flag: Outlook? Viral infections & bugs non-stop! Use another mailer if you value your data. User-Agent: Mutt/1.5.3i X-Archive-Number: 200303/125 X-Sequence-Number: 2996 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just in case anybody missed it, there's another root exploit (local) for sendmail. Please upgrade your boxen before they're rooted. Note that this is less of an issue if you don't allow anybody to login to your box, but even still, don't wait too long to upgrade. Or switch to a different mailer. - -- Blue skies... Todd | Get a bigger hammer! | All vendors suck, but different ones | | http://www.mrball.net | suck less in different applications. | | http://faq.mrball.net | --Andy Walden on NANOG | Linux kernel 2.4.19-24mdk 7 users, load average: 0.06, 0.04, 0.06 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: http://www.mrball.net/todd.asc iD8DBQE+hoUsIBT1264ScBURArkHAJ9EjOROQ4I1mvnUEa2EMgSjOkLhqwCgotrf OBfLfav7tLUd+KPSixG+L+w= =f367 -----END PGP SIGNATURE----- From majordomo-users-owner@greatcircle.com Mon Mar 31 10:32:38 2003 Received: from web13303.mail.yahoo.com (web13303.mail.yahoo.com [216.136.175.39]) by mycroft.greatcircle.com (Postfix) with SMTP id 332F319624D for ; Mon, 31 Mar 2003 10:32:37 -0800 (PST) Message-ID: <20030331183236.52552.qmail@web13303.mail.yahoo.com> Received: from [209.87.17.121] by web13303.mail.yahoo.com via HTTP; Mon, 31 Mar 2003 13:32:36 EST Date: Mon, 31 Mar 2003 13:32:36 -0500 (EST) From: Bob Hendersen Subject: Re: upgrade To: Todd Lyons , majordomo-users@greatcircle.com In-Reply-To: <20030330054828.GA19024@mrball.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Archive-Number: 200303/126 X-Sequence-Number: 2997 A few weeks ago we upgraded the sendmail on our RH 7.2 machine (which runs majordomo 1.94.5) from 8.11.6-3.rpm to 8.11.6.23.rpm to get the buffer overflow fix. We immediately started having problems with our majordomo lists in that messages did not get sent to all list recipients. We reverted sendmail back to 8.11.6-3 and the problem went away. We'll be doing some testing with sendmail 8.12 before we upgrade specifically to test whether it breaks majordomo as the earlier patch did. I'll let folks know what we find. Has anyone on Linux 7.2 upgraded to sendmail 8.12x and found problems with majordomo? Bob --- Todd Lyons wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Just in case anybody missed it, there's another root > exploit (local) for > sendmail. Please upgrade your boxen before they're > rooted. Note that > this is less of an issue if you don't allow anybody > to login to your > box, but even still, don't wait too long to upgrade. > > Or switch to a different mailer. > - -- > Blue skies... Todd > | Get a bigger hammer! | All vendors suck, but > different ones | > | http://www.mrball.net | suck less in different > applications. | > | http://faq.mrball.net | --Andy > Walden on NANOG | > Linux kernel 2.4.19-24mdk 7 users, load average: > 0.06, 0.04, 0.06 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.7 (GNU/Linux) > Comment: http://www.mrball.net/todd.asc > > iD8DBQE+hoUsIBT1264ScBURArkHAJ9EjOROQ4I1mvnUEa2EMgSjOkLhqwCgotrf > OBfLfav7tLUd+KPSixG+L+w= > =f367 > -----END PGP SIGNATURE----- ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca From majordomo-users-owner@greatcircle.com Mon Mar 31 10:49:46 2003 Received: from mailserver2.strus.com (mailserver2.strus.com [65.204.54.3]) by mycroft.greatcircle.com (Postfix) with ESMTP id 93AD2196273 for ; Mon, 31 Mar 2003 10:49:41 -0800 (PST) Received: from BACKUP.STRUS.COM ([10.1.1.10]) by mailserver2.strus.com (8.12.8/8.12.8) with ESMTP id h2VInabq020575 for ; Mon, 31 Mar 2003 13:49:37 -0500 Received: by mailserver10.strus.com with Internet Mail Service (5.5.2656.59) id ; Mon, 31 Mar 2003 13:49:36 -0500 Message-ID: <67154518D2A4214FAD51120EA26BF0A30174A0A0@mailserver10.strus.com> From: "Kozloski, Matthew" To: majordomo-users@greatcircle.com Subject: Re: upgrade Date: Mon, 31 Mar 2003 13:49:23 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2F7B6.3F189780" X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) X-Archive-Number: 200303/127 X-Sequence-Number: 2998 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_01C2F7B6.3F189780 Content-Type: text/plain I am running Sendmail 8.12.8 with no problems. It is a hand-compiled version, so I can't speak for the rpm's. Matt -----Original Message----- From: Bob Hendersen [mailto:bobhendersen@yahoo.ca] Sent: Monday, March 31, 2003 1:33 PM To: Todd Lyons; majordomo-users@greatcircle.com Subject: Re: upgrade A few weeks ago we upgraded the sendmail on our RH 7.2 machine (which runs majordomo 1.94.5) from 8.11.6-3.rpm to 8.11.6.23.rpm to get the buffer overflow fix. We immediately started having problems with our majordomo lists in that messages did not get sent to all list recipients. We reverted sendmail back to 8.11.6-3 and the problem went away. We'll be doing some testing with sendmail 8.12 before we upgrade specifically to test whether it breaks majordomo as the earlier patch did. I'll let folks know what we find. Has anyone on Linux 7.2 upgraded to sendmail 8.12x and found problems with majordomo? Bob --- Todd Lyons wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Just in case anybody missed it, there's another root > exploit (local) for > sendmail. Please upgrade your boxen before they're > rooted. Note that > this is less of an issue if you don't allow anybody > to login to your > box, but even still, don't wait too long to upgrade. > > Or switch to a different mailer. > - -- > Blue skies... Todd > | Get a bigger hammer! | All vendors suck, but > different ones | > | http://www.mrball.net | suck less in different > applications. | > | http://faq.mrball.net | --Andy > Walden on NANOG | > Linux kernel 2.4.19-24mdk 7 users, load average: > 0.06, 0.04, 0.06 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.7 (GNU/Linux) > Comment: http://www.mrball.net/todd.asc > > iD8DBQE+hoUsIBT1264ScBURArkHAJ9EjOROQ4I1mvnUEa2EMgSjOkLhqwCgotrf > OBfLfav7tLUd+KPSixG+L+w= > =f367 > -----END PGP SIGNATURE----- ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca ------_=_NextPart_001_01C2F7B6.3F189780 Content-Type: text/html Content-Transfer-Encoding: quoted-printable Re: upgrade

I am running Sendmail 8.12.8 with no problems.  It i= s a hand-compiled version, so I can't speak for the rpm's.

Matt

-----Original Message-----
From: Bob Hendersen [mailto:bobhendersen@yahoo.ca]
Sent: Monday, March 31, 2003 1:33 PM
To: Todd Lyons; majordomo-users@greatcircle.com
Subject: Re: upgrade


A few weeks ago we upgraded the sendmail on our RH 7.2
machine (which runs majordomo 1.94.5) from
8.11.6-3.rpm to 8.11.6.23.rpm to get the buffer
overflow fix.  We immediately started having proble= ms
with our majordomo lists in that messages did not get
sent to all list recipients.  We reverted sendmail<= /FONT>
back to 8.11.6-3 and the problem went away.

We'll be doing some testing with sendmail 8.12 before
we upgrade specifically to test whether it breaks
majordomo as the earlier patch did.  I'll let folks=
know what we find.  Has anyone on Linux 7.2 upgrade= d
to sendmail 8.12x and found problems with majordomo?

Bob

 --- Todd Lyons <todd@mrball.net> wrote: > = -----BEGIN
PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Just in case anybody missed it, there's another roo= t
> exploit (local) for
> sendmail.  Please upgrade your boxen before th= ey're
> rooted.  Note that
> this is less of an issue if you don't allow anybody=
> to login to your
> box, but even still, don't wait too long to upgrade= .
>
> Or switch to a different mailer.
> - --
> Blue skies...       &= nbsp; Todd
> | Get a bigger hammer!   |  All vend= ors suck, but
> different ones  |
> | http://www.mrball.net  |  suck less in different
> applications.  |
> | http://faq.mrball.net  |      &nb= sp;         --Andy
> Walden on NANOG  |
> Linux kernel 2.4.19-24mdk   7 users, = ; load average:
> 0.06, 0.04, 0.06
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
> Comment: http://www.mrball.net/todd.asc
>
>
iD8DBQE+hoUsIBT1264ScBURArkHAJ9EjOROQ4I1mvnUEa2EMgSjOkLh= qwCgotrf
> OBfLfav7tLUd+KPSixG+L+w=3D
> =3Df367
> -----END PGP SIGNATURE-----

_________________________________________________________= _____________
Post your free ad now! http://personals.yahoo.ca

------_=_NextPart_001_01C2F7B6.3F189780-- From majordomo-users-owner@greatcircle.com Mon Mar 31 10:57:58 2003 Received: from planet.fef.com (unknown [166.90.172.7]) by mycroft.greatcircle.com (Postfix) with ESMTP id 9C1F51962E8 for ; Mon, 31 Mar 2003 10:57:57 -0800 (PST) Received: from planet.fef.com (localhost.localdomain [127.0.0.1]) by planet.fef.com (8.12.9/8.12.9/check_local-5) with ESMTP id h2VIvjTR024742; Mon, 31 Mar 2003 10:57:45 -0800 Received: (from alvin@localhost) by planet.fef.com (8.12.9/8.12.4/Submit) id h2VIvjSm024741; Mon, 31 Mar 2003 10:57:45 -0800 From: Alvin Oga Message-Id: <200303311857.h2VIvjSm024741@planet.fef.com> Subject: Re: upgrade - sendmail To: bobhendersen@yahoo.ca (Bob Hendersen) Date: Mon, 31 Mar 2003 10:57:45 -0800 (PST) Cc: majordomo-users@greatcircle.com In-Reply-To: <20030331183236.52552.qmail@web13303.mail.yahoo.com> from "Bob Hendersen" at Mar 31, 2003 01:32:36 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/128 X-Sequence-Number: 2999 hi ya bob sendmail-8.12.9 works fine for me w/ mj-1.94.5 on various flavors of linux and kernels rh-5.1 w/ 2.0.35 rh-6.1 w/ 2.2.14 rh-6.2 w/ 2.2.20 slack-8.1 w/ 2.4.20 slack-7.1 w/ 2.4.19 ... rh-7.0j w/ default kernel seems to be messy rh-7.x boxes are too much of a headache ... and upgraded to rh-8.x but the ones i play with does not host mj mailing lists - you dont want to know of the other still older boxes :-) sendmail install stuff http://www.Linux-Sec.net/Mail/Sendmail c ya alvin > A few weeks ago we upgraded the sendmail on our RH 7.2 > machine (which runs majordomo 1.94.5) from > 8.11.6-3.rpm to 8.11.6.23.rpm to get the buffer > overflow fix. We immediately started having problems > with our majordomo lists in that messages did not get > sent to all list recipients. We reverted sendmail > back to 8.11.6-3 and the problem went away. > > From majordomo-users-owner@greatcircle.com Mon Mar 31 11:09:50 2003 Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mycroft.greatcircle.com (Postfix) with ESMTP id 02E891962D7 for ; Mon, 31 Mar 2003 11:09:48 -0800 (PST) Received: from [192.168.1.101] (12-231-151-119.client.attbi.com[12.231.151.119]) by rwcrmhc51.attbi.com (rwcrmhc51) with SMTP id <2003033119094705100g92tme>; Mon, 31 Mar 2003 19:09:47 +0000 User-Agent: Microsoft-Entourage/10.1.1.2418 Date: Mon, 31 Mar 2003 11:10:14 -0800 Subject: Install help needed From: Adam Boettiger To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Archive-Number: 200303/129 X-Sequence-Number: 3000 I need some install help with the latest version of majordomo and majorcool. Is there anyone expert in both of these on this list that I can pay to do some troubleshooting? Pls contact me off-list at boettiger@pobox.com Thx Adam Boettiger From majordomo-users-owner@greatcircle.com Mon Mar 31 11:35:31 2003 Received: from wrenkasky.com (esson.net [216.102.129.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 129C41962F7 for ; Mon, 31 Mar 2003 11:35:28 -0800 (PST) Received: from ekasky.wrenkasky.com (ekasky.priority.usc.edu [128.125.63.168]) by wrenkasky.com (8.12.5/8.12.5) with ESMTP id h2VJZVIl025776 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT) for ; Mon, 31 Mar 2003 11:35:31 -0800 Message-Id: <5.1.1.6.2.20030331113239.00ab68e8@mail.esson.net> X-Sender: ed@mail.esson.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Mon, 31 Mar 2003 11:35:24 -0800 To: majordomo-users@greatcircle.com From: Ed Kasky Subject: Re: upgrade In-Reply-To: <67154518D2A4214FAD51120EA26BF0A30174A0A0@mailserver10.stru s.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200303/130 X-Sequence-Number: 3001 FWIW, I have to agree with Matt on this one. There are a few things I won't use rpm's for and sendmail is one of them. It takes a little extra time but definitely worth the flexibility and assurance that the binary will work properly... Ed Kasky Los Angeles, CA . . . . . . . . Genderplex: Trying to determine from the cutesy pictures which restroom to use. At 01:49 PM Monday, 3/31/2003, Kozloski, Matthew wrote -=> >I am running Sendmail 8.12.8 with no problems. It is a hand-compiled >version, so I can't speak for the rpm's. > >Matt > >-----Original Message----- >From: Bob Hendersen >[mailto:bobhendersen@yahoo.ca] >Sent: Monday, March 31, 2003 1:33 PM >To: Todd Lyons; majordomo-users@greatcircle.com >Subject: Re: upgrade > >A few weeks ago we upgraded the sendmail on our RH 7.2 >machine (which runs majordomo 1.94.5) from >8.11.6-3.rpm to 8.11.6.23.rpm to get the buffer >overflow fix. We immediately started having problems >with our majordomo lists in that messages did not get >sent to all list recipients. We reverted sendmail >back to 8.11.6-3 and the problem went away. > >We'll be doing some testing with sendmail 8.12 before >we upgrade specifically to test whether it breaks >majordomo as the earlier patch did. I'll let folks >know what we find. Has anyone on Linux 7.2 upgraded >to sendmail 8.12x and found problems with majordomo? > >Bob > > --- Todd Lyons wrote: > -----BEGIN >PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Just in case anybody missed it, there's another root > > exploit (local) for > > sendmail. Please upgrade your boxen before they're > > rooted. Note that > > this is less of an issue if you don't allow anybody > > to login to your > > box, but even still, don't wait too long to upgrade. > > > > Or switch to a different mailer. > > - -- > > Blue skies... Todd From majordomo-users-owner@greatcircle.com Mon Mar 31 13:02:48 2003 Received: from mepdc1.meplus.local (unknown [207.245.53.130]) by mycroft.greatcircle.com (Postfix) with ESMTP id A0030195FC0 for ; Mon, 31 Mar 2003 13:02:46 -0800 (PST) Subject: "Error unlinking temp files" error msg MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 31 Mar 2003 15:59:08 -0500 X-MIMEOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: "Error unlinking temp files" error msg Thread-Index: AcL3x1khp7U0mjRcRXmW2t1IJzcyRwAABSiw From: "Eric Sauvageau" To: X-Archive-Number: 200303/131 X-Sequence-Number: 3002 Hi, I just installed Majordomo on a Linux server for a customer. Have it configured with a test list and two users. Posting to the list works correctly: both users receive the message. However the administrator also receives this additional error message in an email: --- MAJORDOMO ABORT (mj_resend)!! Error unlinking temp files: No such file or directory --- I checked, I have majordomo.cf set to use /usr/tmp. Looking into this directory I see a pair of resend.????.in and .out files, which contain the email that was received by both users. Since both users did receive the mail I expect Majordomo does know where those files are and is able to access them. However once done with them, Majordomo is unable to remove those temp files, and generates this error message (right at the cleanup() routine I suppose). The file ahve the same user and group as Majordomo uses (majordomo.mail). Any suggestion? This is a Mandrake 8.2 system. Using Perl 5.601, Sendmail and Majordomo 1.94.5. I have a working setup on my own server (Mandrake 8.0 and Perl 5.8.0 tho), and everything works fine. Thanks in advance! --- Eric Sauvageau, Technicien Micro Expansion Plus From majordomo-users-owner@greatcircle.com Mon Mar 31 13:15:00 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 43B71196332 for ; Mon, 31 Mar 2003 13:14:58 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2VLEu43001112; Mon, 31 Mar 2003 15:14:57 -0600 Message-ID: <3E88AFD1.2040003@sonny.org> Date: Mon, 31 Mar 2003 15:14:57 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adam Boettiger Cc: majordomo-users@greatcircle.com Subject: Re: Install help needed References: In-Reply-To: X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/132 X-Sequence-Number: 3003 You might also want to post this request to majordomo-jobs@greatcircle.com. Please include what MTA (sendmail, postfix, qmail) you are using, and since you also want majorcool work done, what web server software you use. It is also useful to know what OS you are running too. Dan Liston Adam Boettiger wrote: > I need some install help with the latest version of majordomo and majorcool. > Is there anyone expert in both of these on this list that I can pay to do > some troubleshooting? > > Pls contact me off-list at boettiger@pobox.com > > Thx > > Adam Boettiger From majordomo-users-owner@greatcircle.com Mon Mar 31 13:49:34 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 6332119627E for ; Mon, 31 Mar 2003 13:49:30 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2VLnT43001341; Mon, 31 Mar 2003 15:49:30 -0600 Message-ID: <3E88B7EA.8050303@sonny.org> Date: Mon, 31 Mar 2003 15:49:30 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Sauvageau Cc: Majordomo-users@greatcircle.com Subject: Re: "Error unlinking temp files" error msg References: In-Reply-To: X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/133 X-Sequence-Number: 3004 What happens if you "su" to the majordomo user, "cd" into the /usr/tmp directory, and try to "rm" those files? You may find it beneficial and more secure to create a tmp directory dedicated to majordomo's use in the majordomo $HOME directory. su - majordomo mkdir tmp edit majordomo.cf so that $TMPDIR = "$homedir/tmp"; Dan Liston Eric Sauvageau wrote: > Hi, > > I just installed Majordomo on a Linux server for a customer. Have it > configured with a test list and two users. > > Posting to the list works correctly: both users receive the message. > However the administrator also receives this additional error message in > an email: > > --- > MAJORDOMO ABORT (mj_resend)!! > > Error unlinking temp files: No such file or directory > --- > > I checked, I have majordomo.cf set to use /usr/tmp. Looking into this > directory I see a pair of resend.????.in and .out files, which contain > the email that was received by both users. Since both users did receive > the mail I expect Majordomo does know where those files are and is able > to access them. However once done with them, Majordomo is unable to > remove those temp files, and generates this error message (right at the > cleanup() routine I suppose). The file ahve the same user and group as > Majordomo uses (majordomo.mail). > > > Any suggestion? > > This is a Mandrake 8.2 system. Using Perl 5.601, Sendmail and Majordomo > 1.94.5. I have a working setup on my own server (Mandrake 8.0 and Perl > 5.8.0 tho), and everything works fine. > > > Thanks in advance! > > > --- > Eric Sauvageau, > Technicien > Micro Expansion Plus From majordomo-users-owner@greatcircle.com Mon Mar 31 14:01:30 2003 Received: from mepdc1.meplus.local (unknown [207.245.53.130]) by mycroft.greatcircle.com (Postfix) with ESMTP id 60462196395 for ; Mon, 31 Mar 2003 14:01:29 -0800 (PST) Subject: FW: "Error unlinking temp files" error msg MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 31 Mar 2003 16:57:51 -0500 X-MIMEOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: "Error unlinking temp files" error msg Thread-Index: AcL3zuhCVk5g5SArQlePlDh71QNjSAAAJn8wAABAAcA= From: "Eric Sauvageau" To: X-Archive-Number: 200303/134 X-Sequence-Number: 3005 DOH! I expected the error message to be something like "permission denied" in the case of a permission issue, so I didn't thought about going further in this direction. majordomo user was indeed denied permission to access /usr/tmp, creating a temp dir in Majordomo's home dir solved it. Thanks for the quick solution :) --- Eric Sauvageau, Technicien Micro Expansion Plus -----Original Message----- From: Daniel Liston [mailto:dliston@sonny.org]=20 Sent: March 31, 2003 4:50 PM To: Eric Sauvageau Cc: Majordomo-users@greatcircle.com Subject: Re: "Error unlinking temp files" error msg What happens if you "su" to the majordomo user, "cd" into the /usr/tmp directory, and try to "rm" those files? You may find it beneficial and more secure to create a tmp directory dedicated to majordomo's use in the majordomo $HOME directory. su - majordomo mkdir tmp edit majordomo.cf so that $TMPDIR =3D "$homedir/tmp"; From majordomo-users-owner@greatcircle.com Mon Mar 31 15:18:42 2003 Received: from daniel.liston.nu (24-116-58-25.cpe.cableone.net [24.116.58.25]) by mycroft.greatcircle.com (Postfix) with ESMTP id 838E319626E for ; Mon, 31 Mar 2003 10:22:16 -0800 (PST) Received: from sonny.org (dad.liston.nu [192.168.1.60]) by daniel.liston.nu (8.12.8/8.12.5) with ESMTP id h2VIMF43000366; Mon, 31 Mar 2003 12:22:15 -0600 Message-ID: <3E888757.903@sonny.org> Date: Mon, 31 Mar 2003 12:22:15 -0600 From: Daniel Liston User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rob , majordomo-users@greatcircle.com Subject: Virtual hosting with majordomo - Was: (Re: bug? (double config files)) References: <200303311853.30378.rob@OhReally.com> In-Reply-To: <200303311853.30378.rob@OhReally.com> X-Enigmail-Version: 0.73.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/135 Hi Rob, I was not aware that virtual hosting samples were in the majordomo FAQ. Nope, just read it again, and that was not there. Perhaps you could provide a URL of where you are getting your config and setup information. The only time a new config file will be created is if you have a flat file by the same name in the lists directory, or somebody has tinkered with the majordomo scripts. In other words, majordomo found a file with the name example_com_list in the lists directory. This file should not exist any more than the example_com_list.config should. Delete them both. I authored this next snippet that you may find useful. New notes are appended to end for postfix and exim. I am still looking for qmail details. Here is the step by step recipe I recommend for virtual hosting of majordomo mailing lists with sendmail. I have posted this information a couple times without comment or criticism, so I have to assume those that have used it, found it to be accurate. Last posting was 11/24/2002. ASSUMPTIONS: Sendmail-8.8.8 and Majordomo-1.94.4 (I have used this recipe successfully into sendmail 8.12.8 and majordomo 1.94.5) Sendmail is working properly for the primary domain before hosting domains of any kind. The login ID for your majordomo user is "majordomo". Sendmail "Trusts" the majordomo user. Tmajordomo exists in sendmail.cf and/or submit.cf or you have majordomo on a line in sendmail.ct or /etc/mail/trusted-users Sendmail is NOT using "smrsh". If it is, you know where the directory is for creating links that allow sendmail to execute programs. Majordomo is working properly for the primary domain before hosting domains of any kind. Sendmail knows about any aliases files you may be using to support majordomo and/or virtual domains. You have "root" access to the server you are doing this configuration on. If the commands in the examples do not live in the same locations on your OS, you know where they are or what will work instead. The "root" user is responsible for maintaining all majordomo configurations for all virtual domains. Your primary domain is mydomain.com and you want to host your own lists plus example.net and sample.org. This implies that DNS MX records point to your host for all three domains. You want to allow each domain to have listnames that could collide with each other. Example; "test" test@mydomain.com, test@example.net, test@sample.org Your primary /etc/majordomo.cf contains; $whereami = "mydomain.com"; $homedir = "/usr/lib/majordomo"; $datadir = "/var/lib/majordomo"; $listdir = "$datadir/lists"; $digest_work_dir = "$datadir/digest"; $filedir = "$datadir/archive"; $filedir_suffix = ""; $log = "$datadir/Log"; STEPS: As "root" I. Configure sendmail for virtual hosting. http://www.sendmail.org/virtual-hosting.html 1. Your sendmail.cf supports /etc/mail/virtusertable 2. Your sendmail.cw (or local-host-names) contains mydomain.com example.net sample.org As "majordomo" II. Create directory trees and config information for your virtual domains. 1. cd /var/lib/majordomo a. mkdir -m 755 example.net sample.org 2. cd /var/lib/majordomo/example.net a. mkdir -m 755 lists digest archive b. touch Log c. cp /etc/majordomo.cf /var/lib/majordomo/example.net d. vi /var/lib/majordomo/example.net/majordomo.cf so that $whereami = "example.net"; $datadir = "/var/lib/majordomo/example.net"; 3. cd /var/lib/majordomo/sample.org a. mkdir -m 755 lists digest archive b. touch Log c. cp /etc/majordomo.cf /var/lib/majordomo/sample.org d. vi /var/lib/majordomo/sample.org/majordomo.cf so that $whereami = "sample.org"; $datadir = "/var/lib/majordomo/sample.org"; NOTE: If you have applied the .cf security patches to majordomo make sure to create links to the new majordomo.cf files in the /usr/lib/majordomo/config directory, and reference these *.cf files in your aliases rather than the .cf files in the actual hosted domain's directories. I would do something like this; As "root", ln -s /var/lib/majordomo/example.net/majordomo.cf /usr/lib/majordomo/config/example.cf ln -s /var/lib/majordomo/sample.org/majordomo.cf /usr/lib/majordomo/config/sample.cf As "root", then "majordomo", then some other "user", III. Test your new directories and majordomo.cf files. 1. cd /usr/lib/majordomo 2. ./wrapper config-test /var/lib/majordomo/example.net/majordomo.cf 3. ./wrapper config-test /var/lib/majordomo/sample.org/majordomo.cf 4. Fix any "bad things" found from steps 2 and 3 above. IV. To actually create lists called test for your own domain and for your hosted domains, using the same assumptions from above; As "majordomo" create a list called test in all domains 1. cd /var/lib/majordomo a. mkdir -m 755 archive/test archive/test-digest digest/test-digest b. touch lists/test lists/test-digest lists/test-post c. echo owner-test@mydomain.com > lists/test d. echo owner-test@mydomain.com > lists/test-digest e. echo owner-test@mydomain.com > lists/test-post 2. cd /var/lib/majordomo/example.net a. mkdir -m 755 archive/test archive/test-digest digest/test-digest b. touch lists/test lists/test-digest lists/test-post c. echo owner-test@example.net > lists/test d. echo owner-test@example.net > lists/test-digest e. echo owner-test@example.net > lists/test-post 3. cd /var/lib/majordomo/sample.org a. mkdir -m 755 archive/test archive/test-digest digest/test-digest b. touch lists/test lists/test-digest lists/test-post c. echo owner-test@sample.org > lists/test d. echo owner-test@sample.org > lists/test-digest e. echo owner-test@sample.org > lists/test-post As "root" 4. vi /etc/aliases # A majordomo user and owner would be good to have per domain. # This first one is for the primary or hosting domain. majordomo: "|/usr/lib/majordomo/wrapper majordomo" majordomo-owner: owner-majordomo owner-majordomo: real-person@anydomain.com, 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: real-person@anydomain.com, 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 # This section for example.net could live in a separate aliases file example.net-majordomo: "|/usr/lib/majordomo/wrapper majordomo -C /var/lib/majordomo/example.net/majordomo.cf" example.net-majordomo-owner: owner-majordomo owner-example.net-majordomo: real-person@anydomain.com, example.net-test: "|/usr/lib/majordomo/wrapper resend -C /var/lib/majordomo/example.net/majordomo.cf -l test -h example.net example.net-test-outgoing,nobody" example.net-test-outgoing: :include:/var/lib/majordomo/example.net/lists/test,example.net-test-digestify,example.net-test-archiver example.net-test-archiver: "|/usr/lib/majordomo/wrapper archive2.pl -C /var/lib/majordomo/example.net/majordomo.cf -f /var/lib/majordomo/example.net/archive/test/test -a -M" example.net-test-digestify: "|/usr/lib/majordomo/wrapper digest -r -C -c /var/lib/majordomo/example.net/majordomo.cf -l test-digest example.net-test-digest-outgoing,nobody" owner-example.com-test: real-person@anydomain.com, example.net-test-owner: owner-example.net-test example.net-test-digest: example.net-test example.net-test-digest-outgoing: :include:/var/lib/majordomo/example.net/lists/test-digest,nobody example.net-test-digest-owner: owner-example.net-test example.net-test-request: "|/usr/lib/majordomo/wrapper majordomo -C /var/lib/majordomo/example.net/majordomo.cf -l test" example.net-test-digest-request: "|/usr/lib/majordomo/wrapper majordomo -C /var/lib/majordomo/example.net/majordomo.cf -l test-digest" example.net-test-approval: owner-example.net-test example.net-test-digest-approval: owner-example.net-test # This section for sample.org could live in a separate aliases file sample.org-majordomo: "|/usr/lib/majordomo/wrapper majordomo -C /var/lib/majordomo/sample.org/majordomo.cf" sample.org-majordomo-owner: owner-majordomo owner-sample.org-majordomo: real-person@anydomain.com, sample.org-test: "|/usr/lib/majordomo/wrapper resend -C /var/lib/majordomo/sample.org/majordomo.cf -l test -h sample.org sample.org-test-outgoing,nobody" sample.org-test-outgoing: :include:/var/lib/majordomo/sample.org/lists/test,sample.org-test-digestify,sample.org-test-archiver sample.org-test-archiver: "|/usr/lib/majordomo/wrapper archive2.pl -C /var/lib/majordomo/sample.org/majordomo.cf -f /var/lib/majordomo/sample.org/archive/test/test -a -M" sample.org-test-digestify: "|/usr/lib/majordomo/wrapper digest -r -C -c /var/lib/majordomo/sample.org/majordomo.cf -l test-digest sample.org-test-digest-outgoing,nobody" owner-sample.org-test: real-person@anydomain.com, sample.org-test-owner: owner-sample.org-test sample.org-test-digest: sample.org-test sample.org-test-digest-outgoing: :include:/var/lib/majordomo/sample.org/lists/test-digest,nobody sample.org-test-digest-owner: owner-sample.org-test sample.org-test-request: "|/usr/lib/majordomo/wrapper majordomo -C /var/lib/majordomo/sample.org/majordomo.cf -l test" sample.org-test-digest-request: "|/usr/lib/majordomo/wrapper majordomo -C /var/lib/majordomo/sample.org/majordomo.cf -l test-digest" sample.org-test-approval: owner-sample.org-test sample.org-test-digest-approval: owner-sample.org-test # Don't forget to rebuild the aliases database by executing a. /usr/sbin/sendmail -bi or b. newaliases As "root" 5. vi /etc/mail/virtusertable #whitespace between columns must contain at least one tab character. #addresses for primary mydomain.com do not need to be listed here. #virtual test list for example.net majordomo@example.net example.net-majordomo owner-majordomo@example.net owner-example.net-majordomo majordomo-owner@example.net example.net-majordomo-owner test@example.net example.net-test owner-test@example.net owner-example.net-test test-owner@example.net example.net-test-owner test-request@example.net example.net-test-request test-approval@example.net example.net-test-approval test-digest@example.net example.net-test-digest owner-test-digest@example.net owner-example.net-test-digest test-digest-owner@example.net example.net-test-digest-owner test-digest-request@example.net example.net-test-digest-request test-digest-approval@example.net example.net-test-digest-approval #additional lists for example.net inserted /\above/\ this line #catchall for all other example.net addresses so they do not #accidentally go to the same name at mydomain.com \/below\/ @example.net error:nouser User unknown #virtual test list for sample.com majordomo@sample.org sample.org-majordomo owner-majordomo@sample.org owner-sample.org-majordomo majordomo-owner@sample.org sample.org-majordomo-owner test@sample.org sample.org-test owner-test@sample.org owner-sample.org-test test-owner@sample.org sample.org-test-owner test-request@sample.org sample.org-test-request test-approval@sample.org sample.org-test-approval test-digest@sample.org sample.org-test-digest owner-test-digest@sample.orgm owner-sample.org-test-digest test-digest-owner@sample.org sample.org-test-digest-owner test-digest-request@sample.org sample.org-test-digest-request test-digest-approval@sample.org sample.org-test-digest-approval #additional lists for sample.org inserted ^above^ this line #catchall for all other sample.org addresses so they do not #accidentally go to the same name at mydomain.com v-below-v @sample.org error:nouser User unknown #the following is added so spammers cannot easily get to my lists test-outgoing@mydomain.com error:nouser User unknown test-outgoing@localhost error:nouser User unknown test-outgoing@example.net error:nouser User unknown test-outgoing@sample.org error:nouser User unknown a. If you are not already there, cd /etc/mail and b. /usr/sbin/makemap hash virtusertable < virtusertable or c. /usr/sbin/makemap dbm virtusertable < virtusertable or possibly, depending on your "Makefile" d. make all V. Mail can now travel in and out of your lists from the internet. The test owners for each domain still need to configure their lists. 1. mailto:majordomo@mydomain.com?body=config%20test%20test.admin a. When the "majordomo results" get mailed to you, edit the config file to change the admin_passwd, and other settings regarding security, moderation, policies, etc. Make sure you do not change/cause any line wrapping during your edits. b. Send the modified config file back with a newconfig command. Make sure your email client does not line wrap when sending your config file back to majordomo or you will get errors. c. Use the newintro and newinfo commands for your list. 2. The owner of test@example.net does the same steps 1, 1a, 1b, 1c replacing mydomain.com with example.net. 3. The owner of test@sample.org does the same steps 1, 1a, 1b, 1c replacing mydomain.com with sample.org. Of course, if the list will NOT be archived or a digest version made available, the applicable virtusertable and aliases file entries can be skipped or commented out. The test.config files should make use of the "resend_host = applicable-domain" rather than using -h on the alias's resend line. A test-post file is not necessary, but available if the owner should decide their list is an announcement only type list, in which case the restrict_post = test-post setting should be used. If test-post is used, it can also be configured remoted via email commands, but does not require any entries in an aliases file. And finally, if the passwd command is expected to actually change the admin password for the list, the admin_passwd = should be left blank in the test.config file. Separate aliases files can be used for each domain, but must be preconfigured in sendmail.cf, and still follow the same format as if there were only one aliases file. Hint for archiving: Use the capital letter switches for Daily, Monthly, and Yearly archiving, so your filenames will have y2k compliant 4-digit years. See my recent post on Archive/Digest HOW-TO for a patch to archive2.pl if your version's file suffix stamp is off by 100 yrs. Hint for digests: If you want a periodic digest vs. a digest based on size or lines, and you do not want to wait for the next message to come in after this period to trigger the digest, you will need a crontab entry. This entry should NOT be owned or ran by, root or majordomo, and does not need to reside on the same host as majordomo. It may be preferable to use this cron from an alternate host so a fully qualified email address would be present for majordomo replies. SHELL=/bin/sh MAILTO="" # +---------- minute 0-59 # | +-------- hour 0-23 # | | +------ day 1-31 # | | | +---- month 1-12 or 3 letter month # | | | | +-- weekday 0-7 or 3 letter day (0=Sun) # | | | | | + here to % or EOL is field 6 for commands 59 23 * * * echo mkdigest listname listname-digest.passwd | mail majordomo@whatever.domain The above cron sends out the digest every day at 11:59PM and assumes your -outgoing alias is listname-digest-outgoing. If you do not use the -outgoing address for your delivery alias, the last line of cron would look like this; 59 23 * * * echo mkdigest listname listname-digest-delivery listname-digest.passwd | mail majordomo@whatever.domain If your majordomo does live on the same host as this cron job, you will also have to ensure that short names are accepted by majordomo, or that the mail command appends your domain to your username before it is seen by majordomo. Version 1.94.4 does not have this limitation, but 1.94.5 does. You might also be able to replace the mail command with "sendmail -f user@domain.com" if the cron belongs to a trusted user in the sendmail.cf file or sendmail.ct file. In most recent versions of sendmail, the filename is now /etc/mail/trusted-users. Another note on digests: If you do use cron, be sure your maxlength, digest_maxdays, and digest_maxlines are set high enough to allow your cron to execute before majordomo tries to do the job itself. Hint for modifying sendmail files and majordomo directories to support virtual mailing lists: Download, extract, read, possibly modify, and execute my interactive perl script at ftp://ftp.ccsf.org/majordomo-contrib/listadd.pl.gz (formerly newlist3.pl) Dan Liston PS. If anyone finds discrepancies in this recipe, please send me your comments via this mailing list at majordomo-users@greatcircle.com, and I will make changes or incorporate suggestions before reposting this again the next time someone asks about virtual hosting of lists. The same goes for use of the perl script for creating new lists too. POSTFIX: For postfix users, do not forget to execute `postalias aliases.database` and `postfix reload`, then this goes in your main.cf: allow_mail_to_files = include References to /etc/mail/virtusertable may be /etc/postfix/virtual and use the same format above. # DELIVERED-TO # # The prepend_delivered_header controls when Postfix should prepend # a Delivered-To: message header. # # By default, Postfix prepends a Delivered-To: header when forwarding # mail and when delivering to file (mailbox) and command. Turning off # the Delivered-To: header when forwarding mail is not recommended. # # prepend_delivered_header = command, file, forward # prepend_delivered_header = forward Please use the latter form of "prepend_delivered_header = forward" to prevent breaking the approve command in majordomo. To make up for removing the "Delivered-To:" header via postfix by making the change above, you can add it back in via the config file for each list's message_header section, or automate this by modifying the config_parse.pl script. /^Delivered-To: $LIST/ EXIM: For exim users, this goes in /etc/exim/exim.conf: #near the top trusted_users = exim:majordomo #after system_aliases director and before local_users director majordomo_aliases: driver = aliasfile pipe_transport = address_pipe file = /etc/aliases search_type = lsearch user = majordomo group = majordomo suffix = "+*" suffix_optional Rob wrote: > Hi, > > Let me first state that I have no experience with majordomo or other > mailinglists, so I may be doing something wrong... > > Having that said... I think I found a bug.... > > I just set up my first mailinglist (using Majordomo 1.94.5). > I have more then 1 domain on my server, so I used the virtual hosting example > from the faq. > > The list is list@example.com, and the line in virtusertable is > list@example.com example_com_list > > After setting it up, I typed 'echo "lists" | mail majordomo@example.com' to > generate list.config. This worked, so I edited it to my taste. > > But after sending a test message to the list (or after succesful subscription, > I didn't check), majordomo created a new .config file named > example_com_list.config (so it used the alias name in stead of the list > name). > Some variables (like admin_passwd) are now taken from list.config, and others > (like reply_to) are taken from example_com_list.config. > > I'm sorry I just dump this here, but at this moment I really don't have time > to get into the code to provide a solution. > Mail me if you need more info. > > TIA > Rob >