MAJORDOMO ABORT (mj

From majordomo-users-owner@greatcircle.com Tue Aug 4 05:14:53 2009 X-Greylist: delayed 661 seconds by postgrey-1.24 at mycroft; Tue, 04 Aug 2009 05:14:52 PDT Received: from rpc7149.teradata.com (nat13.teradata.com [153.65.16.13]) by mycroft.greatcircle.com (Postfix) with ESMTP id 26A56690064 for ; Tue, 4 Aug 2009 05:14:51 -0700 (PDT) Received: from susday7659.TD.teradata.com (localhost.localdomain [127.0.0.1]) by rpc7149.teradata.com (8.13.8/8.13.8) with ESMTP id n74C3nPb010578 for ; Tue, 4 Aug 2009 08:03:49 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA14FB.A06672A9" Subject: MAJORDOMO ABORT (mj_majordomo) Date: Tue, 4 Aug 2009 08:03:47 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MAJORDOMO ABORT (mj_majordomo) Thread-Index: AcoU+589/VxlwwOaSr6cC66ucg6BTw== From: "Sharma, Vikas" To: X-TM-AS-Product-Ver: IMSS-7.0.0.3346-5.6.0.1016-16804.006 X-TM-AS-Result: No--14.374-5.0-31-1 X-imss-scan-details: No--14.374-5.0-31-1;No--14.374-5.0-31-1 X-TM-AS-User-Approved-Sender: No;No X-TM-AS-User-Blocked-Sender: No X-Archive-Number: 200908/1 X-Sequence-Number: 5859 This is a multi-part message in MIME format. ------_=_NextPart_001_01CA14FB.A06672A9 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I have started getting the below error: ------------------------------------------------------- MAJORDOMO ABORT (mj_majordomo)!! Majordomo@lists.majordomo.com : not replying to MAILER-DAEMON to avoid mail loop. --------------------------------------------------------- Can someone please help me what is the problem? > thanks and=20 > regards,=20 > Vikas=20 >=20 >=20 ------_=_NextPart_001_01CA14FB.A06672A9 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MAJORDOMO ABORT (mj_majordomo)

Hi,

I have started getting the below = error:

-------------------------------------------------------
MAJORDOMO ABORT (mj_majordomo)!!

Majordomo@lists.majordomo.com: not replying to MAILER-DAEMON to avoid mail = loop.
---------------------------------------------------------

Can someone please help me what is the = problem?

thanks = and
regards,=20
Vikas

------_=_NextPart_001_01CA14FB.A06672A9-- From majordomo-users-owner@greatcircle.com Tue Aug 4 07:22:38 2009 Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mycroft.greatcircle.com (Postfix) with ESMTP id AD32E69006F for ; Tue, 4 Aug 2009 07:22:36 -0700 (PDT) Received: from park.js.berklix.net (p549A3ABA.dip.t-dialin.net [84.154.58.186]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id n74EMUXI059285; Tue, 4 Aug 2009 14:22:31 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id n74EMLWC025842; Tue, 4 Aug 2009 16:22:21 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id n74ENp1N047448; Tue, 4 Aug 2009 16:23:56 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200908041423.n74ENp1N047448@fire.js.berklix.net> To: "Sharma, Vikas" cc: majordomo-users@greatcircle.com Subject: Re: MAJORDOMO ABORT (mj_majordomo) From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Tue, 04 Aug 2009 08:03:47 EDT." Date: Tue, 04 Aug 2009 16:23:51 +0200 X-Archive-Number: 200908/2 X-Sequence-Number: 5860 > Hi, > I have started getting the below error: > ------------------------------------------------------- > MAJORDOMO ABORT (mj_majordomo)!! > Majordomo@lists.majordomo.com : > not replying to MAILER-DAEMON to avoid mail loop. > --------------------------------------------------------- > Can someone please help me what is the problem? Normal error here: I run lists with hundreds of people, most of whom are Very Far from being computer professionals, most of them run Microsoft on their PCs, periodically their email archives get harvested by viruses. Over years spammers learn mail list & majordomo addresses. The message tells you majordomo saved you from a mail explosion - This Time. Imagine if your majordomo@ got in a dialogue with some other domain's mailer daemon or other mail list robot: each would react to the other, appending progresively more noise. How would such a deadly embrace start ? Could be a malicious set up or accident, but normally a spammer by chance faking one address to the other address. BUT majordomo default config failed to save me 2 days ago: The server of @suedbau-ing.de (not on any of my lists, & didnt know it existed before) flooded my majordomo@berklix, unfortunately not from eg MAILER-DAEMON@suedbau-ing.de but from postmaster@suedbau-ing.de what @suedbau-ing.de did wrong, others can & will & we should be prepared for, The flood I got was painful. I've since added postmaster to majordomo_dont_reply in majordomo.cf, see a trimmed patch below for comment of others on list. (OK line numbers trimmed/mangled, & not All lines needed, it's for comment not patching blind-folded :-) ] *** majordomo-1.94.5.cf.generic Mon Aug 3 18:25:01 2009 ] --- majordomo.cf Tue Aug 4 14:27:24 2009 ] *************** ] *** 278,283 **** ] --- 288,295 ---- ] ] # taboo headers to catch ] # ] $global_taboo_headers = <<'END'; ] /^subject: ndn: /i ] /^subject:\s*RCPT:/i ] *************** ] *** 290,297 **** ] --- 302,329 ---- ] /^subject:\s*unable to deliver mail\b/i ] /^subject:\s.*\baway from my mail\b/i ] /^subject:\s*Autoreply/i ] + /^content\-type: multipart\/report; report\-type=delivery\-status;/i ] + /^deferred:/i ] + /^subject:\s*=\?koi8\-r\/i ] + /^subject:\s*Autoreply/i ] + /^subject:\s*Benachrichtung/i ] + /^subject:\s*Subject:\s*no\-reply/i ] + /^to:\s*undisclosed\-recipients/i ] + /charset=\"koi8\-r\"/i ] + /policy rejection\- please try later\./i ] + /recipient address rejected/i ] END ] ] # Taboo body contents to catch and forward to the approval address ] # ] # For example: ] *************** ] *** 301,315 **** ] # END ] # NOTE! Using ' instead of " in the next line is VERY IMPORTANT!!! ] # ] $global_taboo_body = <<'END'; ] END ] ] # Majordomo will not send replies to addresses which match this. ] # The match is done case-insensitively. ] ! $majordomo_dont_reply = '(mailer-daemon|uucp|listserv|majordomo|listproc)\@'; ] ] 1; ] # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.34 1997/08/27 15:00:31 cwilson Exp $ ] ] --- 333,405 ---- ] # END ] # NOTE! Using ' instead of " in the next line is VERY IMPORTANT!!! ] # ] + # Pre 2009_08_03 was empty global_taboo_body, ] + # I think this list of taboos will only protect lists ] + # & not prevent private recursive flood between local majordomo ] + # & remote robot (JJLATER vi -c/global_taboo_headers resend ). ] $global_taboo_body = <<'END'; ] + /dies\s*ist\s*eine\s*automatisch\s*erstellte\s*benachrichtigung/i ] + /this\s*is\s*an\s*automaticaly\s*generated/i ] END ] ] # Majordomo will not send replies to addresses which match this. ] # The match is done case-insensitively. ] ! # $majordomo_dont_reply = '(mailer-daemon|uucp|listserv|majordomo|listproc)\@'; ] ! # Should - in mailer-daemon be escaped ? JJLATER Read code & decide. ] ! $majordomo_dont_reply = '(_dhcp|_pflogd|abuse|admin|apache|avahi|bind|bin|copyright|cups|cyrus|daemon|dhcpd|dumper|exmh-bug-master|faxmanager|faxmaster|fetchmail|ftp-admin|ftp-bugs|ftpmaster|ftp|games|haldaemon|hostmaster|kmem|listproc|listserv|mailer-daemon|mailman|mailnull|majordomo-h|majordomo-owner|majordomo1|majordomo2|majordomo3|majordomo|majordom|man|messagebus|msgs|nagios|newsmaster|news|nobody|null-notify|operator|owner-majordomo|polkit|pop|postmaster|proxy|release|root|saned|smmsp|squid|sshd|subscribe|system|toor|tty|usenet|uucp|webmaster|www-test|www|xten)\@'; ] ! # 2009_08_03 jhs added postmaster to majordomo_dont_reply ] ! # Although ] ! # - in theory there's no reason why a postmaster ] ! # should not subscribe a list, ] ! # - a postmaster might want to legitimately ] ! # test majordomo with eg "help" or "lists" ] ! # It's too dangerous. eg majordomo got into a deadly embrace ] ! # as postmaster@suedbau-ing.de was not a human but a robot. ] ! # I also blocked some other likely addresses (all system addreses from ] ! # /etc/passwd & /etc/mail/aliases) spammers might fake & trigger a ] ! # storm, eg 'subscribe' (which I then saw reported next morning as: ] ! # MAJORDOMO ABORT (mj_majordomo)!! ] ! # majordomo@berklix.org: not replying to subscribe to avoid mail loop. ] ] + # I jhs@ suspect next line "^1;" may be an error ? ] + # But it is also in majordomo-1.94.5.cf.generic (from FreeBSD-7.1). ] 1; ] # $Header: /sources/cvsrepos/majordomo/sample.cf,v 1.34 1997/08/27 15:00:31 cwilson Exp $ Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail ASCII plain text not HTML & Base64. http://asciiribbon.org Virused Microsoft PCs cause spam. http://berklix.com/free/ From majordomo-users-owner@greatcircle.com Tue Aug 4 07:33:55 2009 Received: from rpc7152.teradata.com (nat13.teradata.com [153.65.16.13]) by mycroft.greatcircle.com (Postfix) with ESMTP id 19235590003 for ; Tue, 4 Aug 2009 07:33:54 -0700 (PDT) Received: from susday7659.TD.teradata.com (localhost.localdomain [127.0.0.1]) by rpc7152.teradata.com (8.13.8/8.13.8) with ESMTP id n74EXrVY006053; Tue, 4 Aug 2009 10:33:53 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: MAJORDOMO ABORT (mj_majordomo) Date: Tue, 4 Aug 2009 10:33:52 -0400 Message-ID: In-Reply-To: <4A784384.9090104@sonny.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MAJORDOMO ABORT (mj_majordomo) Thread-Index: AcoVDsxlNWM8+kZFTNu0kc5DOSWp4AAAYatw From: "Sharma, Vikas" To: "Daniel Liston" Cc: X-TM-AS-Product-Ver: IMSS-7.0.0.3346-5.6.0.1016-16804.007 X-TM-AS-Result: No--10.977-5.0-31-1 X-imss-scan-details: No--10.977-5.0-31-1;No--10.977-5.0-31-1 X-TM-AS-User-Approved-Sender: No;No X-TM-AS-User-Blocked-Sender: No X-Archive-Number: 200908/3 X-Sequence-Number: 5861 Daniel, I have not changed anything in majordomo. I'm using sendmail with majordomo. I have several lists in majordomo for many users. But I started getting these messages just now. I'm not sure if my list have a subscriber named root@ or postmaster@ address. Can I check it by some script? >Vikas=20 -----Original Message----- From: Daniel Liston [mailto:dliston@sonny.org]=20 Sent: Tuesday, August 04, 2009 10:20 AM To: Sharma, Vikas Cc: majordomo-users@greatcircle.com Subject: Re: MAJORDOMO ABORT (mj_majordomo) Sharma, Vikas wrote: > Hi, >=20 > I have started getting the below error: >=20 > ------------------------------------------------------- > MAJORDOMO ABORT (mj_majordomo)!! >=20 > _Majordomo@lists.majordomo.com_ : > not replying to MAILER-DAEMON to avoid mail loop. > --------------------------------------------------------- >=20 > Can someone please help me what is the problem? >=20 >=20 There are possibilities of one or more of several problems. Have you changed anything recently? What mailer (MTA) do you have majordomo configured with? If you google on "MAJORDOMO ABORT" or MAILER-DAEMON and "mail loop"... Do you have more than one list? Does this happen on just one of them? Does your list have a subscriber named root@ or postmaster@ address? These days, with 90-95% of all email on the internet being spam, you probably received a bounce message to your majordomo address. Check your sendmail logs and your majordomo/Log for entries with the same or near the same time stamp as your abort message to confirm. Dan Liston From majordomo-users-owner@greatcircle.com Tue Aug 4 08:26:20 2009 X-Greylist: delayed 3924 seconds by postgrey-1.24 at mycroft; Tue, 04 Aug 2009 08:26:19 PDT Received: from mail.sonny.com (unknown [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8E7FD590015 for ; Tue, 4 Aug 2009 08:26:19 -0700 (PDT) Received: from [192.168.1.28] (daniel.sonny.com [192.168.1.28]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTPA id <0KNU0090FYVMG2@mail.sonny.com> for majordomo-users@greatcircle.com; Tue, 04 Aug 2009 10:26:10 -0500 (CDT) Date: Tue, 04 Aug 2009 10:25:12 -0500 From: Daniel Liston Subject: Re: MAJORDOMO ABORT (mj_majordomo) In-reply-to: To: "Sharma, Vikas" Cc: majordomo-users@greatcircle.com Message-id: <4A7852D8.5020308@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) References: X-Archive-Number: 200908/4 X-Sequence-Number: 5862 I will assume based on your reply that you are new to unix/sendmail/majordomo, and you don't know how to google. Did you mention this is happening on just one, or all of your lists? Narrowing the problem down makes it easier to solve. If you log on to your majordomo server, and run "uname -a" what is output? Assuming the GNU version of "grep" is available on your OS, this script should help. If your lists are not in /var/lib/majordomo/lists, change to match your environment. ------------------------>%cut here%<------------------------------------------- #!/bin/sh listdir=/var/lib/majordomo/lists /bin/grep -i "mailer-daemon" $listdir/* /bin/grep -i "postmaster" $listdir/* /bin/grep -i "root" $listdir/* | grep -v config ------------------------>%cut here%<------------------------------------------- If you get any output from the above script, you have a problem. Another place to look is your /etc/aliases file. /bin/grep -i postmaster /etc/aliases You should see something like: mailer-daemon: postmaster postmaster: root info: postmaster marketing: postmaster sales: postmaster support: postmaster To top this off, you should have a "root" alias here that points to a real address, like; root: you@your.domain As mentioned previously, the most likely answer is that a spammer forged your majordomo address in the from header of their junk mail. Some of the emails they sent are undeliverable/bouncing to the return address of your majordomo. These bounces are "from" mailer-daemon or postmaster, and the default majordomo configuration refuses to reply, which is a good thing. If majordomo did respond, you would end up in two robots auto-responding to each other for infinity. Be glad majordomo aborted, but check your /var/lib/majordomo/Log file and maybe /var/log/maillog to see what else is reported. Maybe you can block the "blowback" spam, and make certain that your server is not the cause of the problem. Dan Liston Sharma, Vikas wrote: > Daniel, > > I have not changed anything in majordomo. > I'm using sendmail with majordomo. I have several lists in majordomo for > many users. > But I started getting these messages just now. I'm not sure if my list > have a subscriber named root@ or postmaster@ address. Can I check it by > some script? > > >> Vikas > > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Tuesday, August 04, 2009 10:20 AM > To: Sharma, Vikas > Cc: majordomo-users@greatcircle.com > Subject: Re: MAJORDOMO ABORT (mj_majordomo) > > Sharma, Vikas wrote: >> Hi, >> >> I have started getting the below error: >> >> ------------------------------------------------------- >> MAJORDOMO ABORT (mj_majordomo)!! >> >> _Majordomo@lists.majordomo.com_ : >> not replying to MAILER-DAEMON to avoid mail loop. >> --------------------------------------------------------- >> >> Can someone please help me what is the problem? >> >> > > There are possibilities of one or more of several problems. Have you > changed anything recently? What mailer (MTA) do you have majordomo > configured with? > > If you google on "MAJORDOMO ABORT" or MAILER-DAEMON and "mail loop"... > > Do you have more than one list? Does this happen on just one of them? > Does your list have a subscriber named root@ or postmaster@ address? > > These days, with 90-95% of all email on the internet being spam, you > probably received a bounce message to your majordomo address. Check your > sendmail logs and your majordomo/Log for entries with the same or near > the same time stamp as your abort message to confirm. > > Dan Liston > From majordomo-users-owner@greatcircle.com Tue Aug 4 08:33:13 2009 Received: from rpc7152.teradata.com (nat13.teradata.com [153.65.16.13]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1AEA4590015 for ; Tue, 4 Aug 2009 08:33:12 -0700 (PDT) Received: from susday7659.TD.teradata.com (localhost.localdomain [127.0.0.1]) by rpc7152.teradata.com (8.13.8/8.13.8) with ESMTP id n74FXBeC022925; Tue, 4 Aug 2009 11:33:12 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: MAJORDOMO ABORT (mj_majordomo) Date: Tue, 4 Aug 2009 11:33:09 -0400 Message-ID: In-Reply-To: <4A7852D8.5020308@sonny.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MAJORDOMO ABORT (mj_majordomo) Thread-Index: AcoVF+/SDgEbjb4KTdyVE6Do+9bwPQAANH4A From: "Sharma, Vikas" To: "Daniel Liston" Cc: X-TM-AS-Product-Ver: IMSS-7.0.0.3346-5.6.0.1016-16804.007 X-TM-AS-Result: No--16.066-5.0-31-1 X-imss-scan-details: No--16.066-5.0-31-1;No--16.066-5.0-31-1 X-TM-AS-User-Approved-Sender: No;No X-TM-AS-User-Blocked-Sender: No X-Archive-Number: 200908/5 X-Sequence-Number: 5863 Your assumption is correct ;) I'm new to these technology. Thanks for your brief process. I'll follow and let you confirm.=20 >Vikas=20 -----Original Message----- From: Daniel Liston [mailto:dliston@sonny.org]=20 Sent: Tuesday, August 04, 2009 11:25 AM To: Sharma, Vikas Cc: majordomo-users@greatcircle.com Subject: Re: MAJORDOMO ABORT (mj_majordomo) I will assume based on your reply that you are new to unix/sendmail/majordomo, and you don't know how to google. Did you mention this is happening on just one, or all of your lists? Narrowing the problem down makes it easier to solve. If you log on to your majordomo server, and run "uname -a" what is output? Assuming the GNU version of "grep" is available on your OS, this script should help. If your lists are not in /var/lib/majordomo/lists, change to match your environment. ------------------------>%cut=20 ------------------------>here%<----------------------------------------- ------------------------>-- #!/bin/sh listdir=3D/var/lib/majordomo/lists /bin/grep -i "mailer-daemon" $listdir/* /bin/grep -i "postmaster" $listdir/* /bin/grep -i "root" $listdir/* | grep -v config ------------------------>%cut=20 ------------------------>here%<----------------------------------------- ------------------------>-- If you get any output from the above script, you have a problem. Another place to look is your /etc/aliases file. /bin/grep -i postmaster /etc/aliases You should see something like: mailer-daemon: postmaster postmaster: root info: postmaster marketing: postmaster sales: postmaster support: postmaster To top this off, you should have a "root" alias here that points to a real address, like; root: you@your.domain As mentioned previously, the most likely answer is that a spammer forged your majordomo address in the from header of their junk mail. Some of the emails they sent are undeliverable/bouncing to the return address of your majordomo. These bounces are "from" mailer-daemon or postmaster, and the default majordomo configuration refuses to reply, which is a good thing. If majordomo did respond, you would end up in two robots auto-responding to each other for infinity. Be glad majordomo aborted, but check your /var/lib/majordomo/Log file and maybe /var/log/maillog to see what else is reported. Maybe you can block the "blowback" spam, and make certain that your server is not the cause of the problem. Dan Liston Sharma, Vikas wrote: > Daniel, >=20 > I have not changed anything in majordomo. > I'm using sendmail with majordomo. I have several lists in majordomo=20 > for many users. > But I started getting these messages just now. I'm not sure if my list > have a subscriber named root@ or postmaster@ address. Can I check it=20 > by some script? >=20 >=20 >> Vikas >=20 > -----Original Message----- > From: Daniel Liston [mailto:dliston@sonny.org] > Sent: Tuesday, August 04, 2009 10:20 AM > To: Sharma, Vikas > Cc: majordomo-users@greatcircle.com > Subject: Re: MAJORDOMO ABORT (mj_majordomo) >=20 > Sharma, Vikas wrote: >> Hi, >> >> I have started getting the below error: >> >> ------------------------------------------------------- >> MAJORDOMO ABORT (mj_majordomo)!! >> >> _Majordomo@lists.majordomo.com_ : >> not replying to MAILER-DAEMON to avoid mail loop. >> --------------------------------------------------------- >> >> Can someone please help me what is the problem? >> >> >=20 > There are possibilities of one or more of several problems. Have you=20 > changed anything recently? What mailer (MTA) do you have majordomo=20 > configured with? >=20 > If you google on "MAJORDOMO ABORT" or MAILER-DAEMON and "mail loop"... >=20 > Do you have more than one list? Does this happen on just one of them? > Does your list have a subscriber named root@ or postmaster@ address? >=20 > These days, with 90-95% of all email on the internet being spam, you=20 > probably received a bounce message to your majordomo address. Check=20 > your sendmail logs and your majordomo/Log for entries with the same or > near the same time stamp as your abort message to confirm. >=20 > Dan Liston >=20 From majordomo-users-owner@greatcircle.com Tue Aug 4 09:20:58 2009 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id D78DD69006E for ; Tue, 4 Aug 2009 09:20:57 -0700 (PDT) Received: from [192.168.1.28] (daniel.sonny.com [192.168.1.28]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTPA id <0KNU0090AVUOF7@mail.sonny.com> for majordomo-users@greatcircle.com; Tue, 04 Aug 2009 09:20:48 -0500 (CDT) Date: Tue, 04 Aug 2009 09:19:48 -0500 From: Daniel Liston Subject: Re: MAJORDOMO ABORT (mj_majordomo) In-reply-to: To: "Sharma, Vikas" Cc: majordomo-users@greatcircle.com Message-id: <4A784384.9090104@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) References: X-Archive-Number: 200908/6 X-Sequence-Number: 5864 Sharma, Vikas wrote: > Hi, > > I have started getting the below error: > > ------------------------------------------------------- > MAJORDOMO ABORT (mj_majordomo)!! > > _Majordomo@lists.majordomo.com_ : > not replying to MAILER-DAEMON to avoid mail loop. > --------------------------------------------------------- > > Can someone please help me what is the problem? > > There are possibilities of one or more of several problems. Have you changed anything recently? What mailer (MTA) do you have majordomo configured with? If you google on "MAJORDOMO ABORT" or MAILER-DAEMON and "mail loop"... Do you have more than one list? Does this happen on just one of them? Does your list have a subscriber named root@ or postmaster@ address? These days, with 90-95% of all email on the internet being spam, you probably received a bounce message to your majordomo address. Check your sendmail logs and your majordomo/Log for entries with the same or near the same time stamp as your abort message to confirm. Dan Liston From majordomo-users-owner@greatcircle.com Tue Aug 11 06:09:51 2009 X-Greylist: delayed 2455 seconds by postgrey-1.24 at mycroft; Tue, 11 Aug 2009 06:09:50 PDT Received: from isls-mx10.wmin.ac.uk (isls-mx10.wmin.ac.uk [161.74.14.112]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2EA4B5901A9 for ; Tue, 11 Aug 2009 06:09:50 -0700 (PDT) Received: from [161.74.14.1] (helo=isls-exch-be-1.intranet.wmin.ac.uk) by isls-mx10.wmin.ac.uk with esmtp (Exim 4.60) (envelope-from ) id 1MaqTG-0003Qc-Mj for majordomo-users@greatcircle.com; Tue, 11 Aug 2009 13:28:54 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA1A7F.4A545759" Subject: auto reply to provide message for closed list Date: Tue, 11 Aug 2009 13:28:54 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: auto reply to provide message for closed list Thread-Index: Acoaf0pRrPfYiseyRW6GAFc9KfsZTw== From: "Malcolm Bodger" To: X-Archive-Number: 200908/7 X-Sequence-Number: 5865 This is a multi-part message in MIME format. ------_=_NextPart_001_01CA1A7F.4A545759 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable All I want to do is close a list and give anyone sending email to the = list an automated message to say this list is now closed etc, etc. How = can I do this? =20 Thanks, Malcolm. -- The University of Westminster is a charity and a company limited by guarantee. Registration number: 977818 England. Registered Office: 309 Regent Street, London W1B 2UW, UK. ------_=_NextPart_001_01CA1A7F.4A545759 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= =0A= =0A= =0A=

All I want to do is = close a list and give anyone sending email to the list an automated = message to say this list is now closed etc, etc. How can I do = this?

=0A=

Thanks,

=0A=

Malcolm.

The University of Westminster is a charity and a company limited by guarantee. Registration number: 977818 England. Registered Office: 309 Regent Street, London W1B 2UW.

= ------_=_NextPart_001_01CA1A7F.4A545759-- From majordomo-users-owner@greatcircle.com Tue Aug 11 07:33:51 2009 Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mycroft.greatcircle.com (Postfix) with ESMTP id F35D4590353 for ; Tue, 11 Aug 2009 07:33:49 -0700 (PDT) Received: from park.js.berklix.net (p549A6AF1.dip.t-dialin.net [84.154.106.241]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id n7BEYJYj007644; Tue, 11 Aug 2009 14:34:21 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id n7BEXeHW089237; Tue, 11 Aug 2009 16:33:40 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id n7BEZoPJ078364; Tue, 11 Aug 2009 16:35:55 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200908111435.n7BEZoPJ078364@fire.js.berklix.net> To: "Malcolm Bodger" cc: majordomo-users@greatcircle.com Subject: Re: auto reply to provide message for closed list From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Tue, 11 Aug 2009 13:28:54 BST." Date: Tue, 11 Aug 2009 16:35:50 +0200 X-Archive-Number: 200908/8 X-Sequence-Number: 5866 > All I want to do is close a list and give anyone sending email to the = > list an automated message to say this list is now closed etc, etc. How = > can I do this? Not supported by majordomo as such. I'd suggest: vi /etc/mail/aliases # delete line for that list newaliases man adduser create a dummy user called name of list man vacation set up auto responder man crontab vi /etc/crontab set up a periodic truncate script eg cp /dev/null /var/mail/list-name Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail ASCII plain text not HTML & Base64. http://asciiribbon.org Virused Microsoft PCs cause spam. http://berklix.com/free/ From majordomo-users-owner@greatcircle.com Tue Aug 11 07:37:01 2009 Received: from isls-mx10.wmin.ac.uk (isls-mx10.wmin.ac.uk [161.74.14.112]) by mycroft.greatcircle.com (Postfix) with ESMTP id D3EE15903E3 for ; Tue, 11 Aug 2009 07:37:00 -0700 (PDT) Received: from [161.74.14.1] (helo=isls-exch-be-1.intranet.wmin.ac.uk) by isls-mx10.wmin.ac.uk with esmtp (Exim 4.60) (envelope-from ) id 1MasTD-0003xi-Ld for majordomo-users@greatcircle.com; Tue, 11 Aug 2009 15:36:59 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA1A91.2F071D80" Subject: Re: auto reply to provide message for closed list Date: Tue, 11 Aug 2009 15:36:03 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: auto reply to provide message for closed list Thread-Index: AcoakMZCuD2w25vNQAWS/p103f2rWgAAEdrH References: <200908111435.n7BEZoPJ078364@fire.js.berklix.net> From: "Malcolm Bodger" To: "Julian H. Stacey" , "Malcolm Bodger" Cc: X-Archive-Number: 200908/9 X-Sequence-Number: 5867 This is a multi-part message in MIME format. ------_=_NextPart_001_01CA1A91.2F071D80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks Julian - I'll give it a try. =20 Regards, Malcolm. ________________________________ From: Julian H. Stacey [mailto:jhs@berklix.com] Sent: Tue 11/08/2009 15:35 To: Malcolm Bodger Cc: majordomo-users@greatcircle.com Subject: Re: auto reply to provide message for closed list=20 > All I want to do is close a list and give anyone sending email to the = =3D > list an automated message to say this list is now closed etc, etc. How = =3D > can I do this? Not supported by majordomo as such. I'd suggest: vi /etc/mail/aliases # delete line for that list newaliases man adduser create a dummy user called name of list man vacation set up auto responder man crontab vi /etc/crontab set up a periodic truncate script eg cp /dev/null /var/mail/list-name Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich = http://berklix.com =20 Mail ASCII plain text not HTML & Base64. http://asciiribbon.org = =20 Virused Microsoft PCs cause spam. http://berklix.com/free/ -- The University of Westminster is a charity and a company limited by guarantee. Registration number: 977818 England. Registered Office: 309 Regent Street, London W1B 2UW, UK. ------_=_NextPart_001_01CA1A91.2F071D80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: auto reply to provide message for = closed list=0A= =0A= =0A= =0A=

=0A=

Thanks Julian = - I'll give it a try.

=0A=

Regards,

=0A=

Malcolm.

=0A=

=0A= From: Julian H. Stacey = [mailto:jhs@berklix.com]
Sent: Tue 11/08/2009 = 15:35
To: Malcolm Bodger
Cc: = majordomo-users@greatcircle.com
Subject: Re: auto reply to = provide message for closed list

=0A=

> All I want to do is close a list and give anyone = sending email to the =3D
> list an automated message to say this = list is now closed etc, etc. How =3D
> can I do this?

Not = supported by majordomo as such. I'd = suggest:
        vi = /etc/mail/aliases # delete line for that = list
        = newaliases
        man = adduser
        =         create a dummy user called = name of list
        man = vacation
        =         set up auto = responder
        man = crontab
        vi = /etc/crontab
        =         set up a periodic truncate = script eg
        =         =         cp /dev/null = /var/mail/list-name

Cheers,
Julian
--
Julian Stacey: BSD = Unix Linux C Sys Eng Consultants Munich http://berklix.com
Mail ASCII = plain text not HTML & Base64.      http://asciiribbon.org
= Virused Microsoft PCs cause = spam.           &n= bsp; http://berklix.com/free/
=

The University of Westminster is a charity and a company limited by guarantee. Registration number: 977818 England. Registered Office: 309 Regent Street, London W1B 2UW.

= ------_=_NextPart_001_01CA1A91.2F071D80-- From majordomo-users-owner@greatcircle.com Tue Aug 11 08:50:23 2009 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id B782A5902A5 for ; Tue, 11 Aug 2009 08:50:22 -0700 (PDT) Received: from [192.168.1.28] (daniel.sonny.com [192.168.1.28]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTPA id <0KO700H02YNPAP@mail.sonny.com> for majordomo-users@greatcircle.com; Tue, 11 Aug 2009 10:50:13 -0500 (CDT) Date: Tue, 11 Aug 2009 10:50:10 -0500 From: Daniel Liston Subject: Re: auto reply to provide message for closed list In-reply-to: To: Malcolm Bodger Cc: majordomo-users@greatcircle.com Message-id: <4A819332.2060801@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) References: X-Archive-Number: 200908/10 X-Sequence-Number: 5868 Malcolm Bodger wrote: > All I want to do is close a list and give anyone sending email to the > list an automated message to say this list is now closed etc, etc. How > can I do this? > > Thanks, > Malcolm. > > The University of Westminster is a charity and a company > limited by guarantee. Registration number: 977818 England. > Registered Office: 309 Regent Street, London W1B 2UW. > > First off, auto-reply is considered poor netiquette any more. What would be easiest, is using the list to send notifications that the list is shutting down. (A closed list means closed to new subscribers, a restricted list is one where only members are allowed to post.) If necessary, add the moderator capability for a month, and just collect addresses for a moderated reply rather than auto reply once per week. After four weeks, start bouncing or discarding messages to the list's old address. If you are actually closing vs. shutting down, meaning you will still have an active list that does not accept new subscribers, simply restrict-post to your existing members or even a subset of those users. Dan Liston From majordomo-users-owner@greatcircle.com Wed Aug 12 01:28:43 2009 Received: from isls-mx10.wmin.ac.uk (isls-mx10.wmin.ac.uk [161.74.14.112]) by mycroft.greatcircle.com (Postfix) with ESMTP id A5BFD69000A for ; Wed, 12 Aug 2009 01:28:41 -0700 (PDT) Received: from [161.74.14.1] (helo=isls-exch-be-1.intranet.wmin.ac.uk) by isls-mx10.wmin.ac.uk with esmtp (Exim 4.60) (envelope-from ) id 1Mb9CK-00078G-6x for majordomo-users@greatcircle.com; Wed, 12 Aug 2009 09:28:40 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA1B26.E4DE41ED" Subject: Re: auto reply to provide message for closed list Date: Wed, 12 Aug 2009 09:28:39 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: auto reply to provide message for closed list Thread-Index: AcoaoRsLENikSHPdSfqyFWT+2XdkNAAhKeV7 References: <4A819CAE.5070101@sonny.org> From: "Malcolm Bodger" To: "Daniel Liston" , "Malcolm Bodger" Cc: X-Archive-Number: 200908/11 X-Sequence-Number: 5869 This is a multi-part message in MIME format. ------_=_NextPart_001_01CA1B26.E4DE41ED Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Daniel, =20 Thanks for this.=20 The list is owned by the University undergraduate office and I believe = it's used for student enquiries and is to be replaced. Unfortunately, we = have to provide where possible what the business user requires. I will = forward your suggestion and at least I can now confirm that this is not = an available option with Majordomo. =20 Regards, Malcolm. ________________________________ From: Daniel Liston [mailto:dliston@sonny.org] Sent: Tue 11/08/2009 17:30 To: Malcolm Bodger Cc: majordomo-users@greatcircle.com Subject: Re: auto reply to provide message for closed list Malcolm Bodger wrote: > All I want to do is close a list and give anyone sending email to the > list an automated message to say this list is now closed etc, etc. How > can I do this? >=20 > Thanks, > Malcolm. > > The University of Westminster is a charity and a company > limited by guarantee. Registration number: 977818 England. > Registered Office: 309 Regent Street, London W1B 2UW. > > First off, auto-reply is considered poor netiquette any more. Too easy for spammer to take advantage of... What would be easiest, is using the list to send notifications that the list is shutting down. (A closed list means closed to new subscribers, a restricted list is one where only members are allowed to post.) If necessary, add the moderator capability for a month, and just collect addresses for a moderated reply rather than auto reply once per week. After four weeks, start bouncing or discarding messages to the list's old address. This can be done by simply removing the list aliases from /etc/aliases and/or replacing the right hand side with /dev/null or the local user's email that will be managing the shut down. If you are actually closing vs. shutting down, meaning you will still have an active list that does not accept new subscribers, simply restrict-post to your existing members or even a subset of those users. Dan Liston -- The University of Westminster is a charity and a company limited by guarantee. Registration number: 977818 England. Registered Office: 309 Regent Street, London W1B 2UW, UK. ------_=_NextPart_001_01CA1B26.E4DE41ED Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: auto reply to provide message for = closed list=0A= =0A= =0A= =0A=

=0A=

Hi = Daniel,

=0A=

Thanks for this.

=0A=

The list is owned by the = University undergraduate office and I believe it's used for student = enquiries and is to be replaced. Unfortunately, we have to provide where = possible what the business user requires. I will forward your suggestion = and at least I can now confirm that this is not an available option with = Majordomo.

=0A=

Regards,

=0A=

Malcolm.

=0A=

From: Daniel Liston = [mailto:dliston@sonny.org]
Sent: Tue 11/08/2009 = 17:30
To: Malcolm Bodger
Cc: = majordomo-users@greatcircle.com
Subject: Re: auto reply to = provide message for closed list

=0A=

Malcolm Bodger wrote:
> All I want to do is = close a list and give anyone sending email to the
> list an = automated message to say this list is now closed etc, etc. How
> = can I do this?
>
> Thanks,
> = Malcolm.
>
> The University of Westminster is a charity and = a company
> limited by guarantee. Registration number: 977818 = England.
> Registered Office: 309 Regent Street, London W1B = 2UW.
>
>

First off, auto-reply is considered poor = netiquette any more.
Too easy for spammer to take advantage = of...

What would be easiest, is using the list to send = notifications
that the list is shutting down. (A closed list means = closed to
new subscribers, a restricted list is one where only = members are
allowed to post.) If necessary, add the moderator = capability
for a month, and just collect addresses for a moderated = reply
rather than auto reply once per week. After four weeks, = start
bouncing or discarding messages to the list's old = address. This
can be done by simply removing the list aliases = from /etc/aliases
and/or replacing the right hand side with /dev/null = or the local
user's email that will be managing the shut = down.

If you are actually closing vs. shutting down, meaning you = will
still have an active list that does not accept new = subscribers,
simply restrict-post to your existing members or even a = subset
of those users.

Dan = Liston

The University of Westminster is a charity and a company limited by guarantee. Registration number: 977818 England. Registered Office: 309 Regent Street, London W1B 2UW.

= ------_=_NextPart_001_01CA1B26.E4DE41ED-- From majordomo-users-owner@greatcircle.com Wed Aug 12 10:36:21 2009 X-Greylist: delayed 300 seconds by postgrey-1.24 at mycroft; Wed, 12 Aug 2009 10:36:19 PDT Received: from ncrx1.ncr.int.ec.gc.ca (fwncr1-2.ncr.ec.gc.ca [199.212.18.131]) by mycroft.greatcircle.com (Postfix) with ESMTP id DC06C590012 for ; Wed, 12 Aug 2009 10:36:19 -0700 (PDT) Received: from ncrx7.ncr.int.ec.gc.ca ([142.135.209.110]) by ncrx1.ncr.int.ec.gc.ca with Microsoft SMTPSVC(6.0.3790.3959); Wed, 12 Aug 2009 13:31:17 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA1B72.B335B522" Subject: Government Firewall Security and Free Hosting Date: Wed, 12 Aug 2009 13:31:18 -0400 Message-ID: <4F8BB2B3A0405C44B8DBD1C0D44489D106199310@ncrx7.ncr.int.ec.gc.ca> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Government Firewall Security and Free Hosting Thread-Index: AcobcrMbk7d0v6HzTC+Chdk+ILtZFA== From: "Saper,Ron [NCR]" To: X-OriginalArrivalTime: 12 Aug 2009 17:31:17.0894 (UTC) FILETIME=[B3204A60:01CA1B72] X-Archive-Number: 200908/12 X-Sequence-Number: 5870 This is a multi-part message in MIME format. ------_=_NextPart_001_01CA1B72.B335B522 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, I am working as a temporary with the Canadian federal government on a project that involves collaboration with other departments and non-government entities. Turns out the security policies are quite tight and they do not run majodomo in the department or allow anything like that. I want to arrange an email discussion list that works just like this list (I think). Anyone have experience in similar situations? Did it work to use an external hosting service and are there any good free (or nearly free) ones? =20 ------_=_NextPart_001_01CA1B72.B335B522 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Government Firewall Security and Free Hosting

Hello,

I am working as a = temporary with the Canadian federal government on a project that = involves collaboration with other departments and non-government = entities. Turns out the security policies are quite tight and they = do not run majodomo in the department or allow anything like = that.

I want to arrange = an email discussion list that works just like this list (I = think).

Anyone have = experience in similar situations? Did it work to use an external = hosting service and are there any good free (or nearly free) = ones?

------_=_NextPart_001_01CA1B72.B335B522-- From majordomo-users-owner@greatcircle.com Tue Aug 18 09:59:52 2009 X-Greylist: delayed 3604 seconds by postgrey-1.24 at mycroft; Tue, 18 Aug 2009 09:59:50 PDT Received: from vms173009pub.verizon.net (vms173009pub.verizon.net [206.46.173.9]) by mycroft.greatcircle.com (Postfix) with ESMTP id E3FF769006D for ; Tue, 18 Aug 2009 09:59:50 -0700 (PDT) Received: from astratech-1 ([70.110.49.245]) by vms173009.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KOK006T8XRG2V74@vms173009.mailsrvcs.net> for Majordomo-Users@GreatCircle.COM; Tue, 18 Aug 2009 10:59:41 -0500 (CDT) From: "Kenneth G. Gordon" To: Majordomo-Users@GreatCircle.COM Date: Tue, 18 Aug 2009 08:59:41 -0700 MIME-version: 1.0 Subject: Possible ownership/permissions issue? Reply-to: kgordon2006@verizon.net Message-id: <4A8A6D7D.24186.16BB0271@localhost> X-Mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Archive-Number: 200908/13 X-Sequence-Number: 5871 I have run an earlier version of Majordomo on one of my systems over the past 10 years or so, and had very little problem setting it up and getting it operating. Recently, my main server crashed with a catastrophic hardware failure, and I am in the process of rebuilding my system and adding a backup system. The machines are HP servers, running HP-UX 11.11 with all updates. I also installed gcc and other software needed by it, and bash, pine, pico, Apache, etc. Sendmail is version 8.13.X E-mail is working fine as is the web server. I tried to set up Majordomo 1.94.5 according to the most recent documentation, but am having difficulty. The setup is as follows: userID: majordom group: daemon majordomo home directory: /opt/majordomo permissions on $home: 0770 permissions IN /opt/majordomo/lists: 664 In the aliases file at /etc/aliases, I have setup the first alias as majordom : majordomo in addition to those listed in the majordomo.alias file. I can mail to majordomo@foo.somewhere.edu from root or a local user and it works fine. I get the proper responses, etc. However, when I attempt to mail to my list@foo.somewhere.edu, I receive several messages at the list manager as follows: "The original message was received at Mon, 17 Aug 2009 22:09:02 - 0700 (PDT) from daemon@localhost ----- The following addresses had permanent fatal errors ----- :include:/opt/majordomo/lists/ (expanded from: -list) ----- Transcript of session follows ----- 550 5.2.4 :include:/opt/majordomo/lists/... Cannot open /opt/majordomo/lists/: Group writable directory [ Part 2: "Delivery Status" ] Reporting-MTA: dns; foo.somewhere.edu Arrival-Date: Mon, 17 Aug 2009 22:09:02 -0700 (PDT) Final-Recipient: RFC822; -list@foo.somewhere.edu X-Actual-Recipient: rfc822;/opt/majordomo/lists/@foo.somewhere.edu Action: failed Status: 5.2.4 Last-Attempt-Date: Mon, 17 Aug 2009 22:09:02 -0700 (PDT)" Will/can someone please tell me what the heck is going on? What is this "Group writable directory" business? As far as I can see, the directory in question MUST be "group writable". I am confused...which is not an unusual state for me. :-( Kenneth G. Gordon Electronic Instrument Specialist, Sr. University of Idaho College of Science Moscow, Idaho 83844-3025 From majordomo-users-owner@greatcircle.com Tue Aug 18 10:23:17 2009 X-Greylist: delayed 372 seconds by postgrey-1.24 at mycroft; Tue, 18 Aug 2009 10:23:16 PDT Received: from fmailhost01.isp.att.net (fmailhost01.isp.att.net [207.115.11.51]) by mycroft.greatcircle.com (Postfix) with ESMTP id A18E269007B for ; Tue, 18 Aug 2009 10:23:16 -0700 (PDT) Received: from [127.0.0.1] (adsl-068-209-223-242.sip.jan.bellsouth.net[68.209.223.242]) by isp.att.net (frfwmhc01) with ESMTP id <20090818171703H0100h7akde>; Tue, 18 Aug 2009 17:17:04 +0000 X-Originating-IP: [68.209.223.242] Message-ID: <4A8AE22A.9040206@bellsouth.net> Date: Tue, 18 Aug 2009 12:17:30 -0500 From: Adam Williams User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) MIME-Version: 1.0 To: kgordon2006@verizon.net CC: Majordomo-Users@GreatCircle.COM Subject: Re: Possible ownership/permissions issue? References: <4A8A6D7D.24186.16BB0271@localhost> In-Reply-To: <4A8A6D7D.24186.16BB0271@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200908/14 X-Sequence-Number: 5872 chmod g-w /opt/majordomo/lists Kenneth G. Gordon wrote: > I have run an earlier version of Majordomo on one of my systems over > the past 10 years or so, and had very little problem setting it up and > getting it operating. > > Recently, my main server crashed with a catastrophic hardware failure, > and I am in the process of rebuilding my system and adding a backup > system. > > The machines are HP servers, running HP-UX 11.11 with all updates. I > also installed gcc and other software needed by it, and bash, pine, pico, > Apache, etc. Sendmail is version 8.13.X > > E-mail is working fine as is the web server. > > I tried to set up Majordomo 1.94.5 according to the most recent > documentation, but am having difficulty. > > The setup is as follows: > userID: majordom > group: daemon > majordomo home directory: /opt/majordomo > permissions on $home: 0770 > permissions IN /opt/majordomo/lists: 664 > > In the aliases file at /etc/aliases, I have setup the first alias as > > majordom : majordomo > > in addition to those listed in the majordomo.alias file. > > I can mail to majordomo@foo.somewhere.edu from root or a local user > and it works fine. I get the proper responses, etc. > > However, when I attempt to mail to my list@foo.somewhere.edu, I > receive several messages at the list manager as follows: > > "The original message was received at Mon, 17 Aug 2009 22:09:02 - > 0700 (PDT) from daemon@localhost > > ----- The following addresses had permanent fatal errors ----- > :include:/opt/majordomo/lists/ > (expanded from: -list) > > ----- Transcript of session follows ----- > 550 5.2.4 :include:/opt/majordomo/lists/... Cannot open > /opt/majordomo/lists/: Group writable directory > > [ Part 2: "Delivery Status" ] > > Reporting-MTA: dns; foo.somewhere.edu > Arrival-Date: Mon, 17 Aug 2009 22:09:02 -0700 (PDT) > > Final-Recipient: RFC822; -list@foo.somewhere.edu > X-Actual-Recipient: > rfc822;/opt/majordomo/lists/@foo.somewhere.edu > Action: failed > Status: 5.2.4 > Last-Attempt-Date: Mon, 17 Aug 2009 22:09:02 -0700 (PDT)" > > Will/can someone please tell me what the heck is going on? > > What is this "Group writable directory" business? As far as I can see, the > directory in question MUST be "group writable". > > I am confused...which is not an unusual state for me. :-( > > Kenneth G. Gordon > Electronic Instrument Specialist, Sr. > University of Idaho > College of Science > Moscow, Idaho 83844-3025 > > > From majordomo-users-owner@greatcircle.com Tue Aug 18 10:26:35 2009 X-Greylist: delayed 136 seconds by postgrey-1.24 at mycroft; Tue, 18 Aug 2009 10:26:35 PDT Received: from mail.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id 07C8169007B for ; Tue, 18 Aug 2009 10:26:34 -0700 (PDT) Received: from webmail.ourldsfamily.com (localhost [127.0.0.1]) by mail.ourldsfamily.com (8.14.2/8.14.2) with ESMTP id n7IHOIXh005001; Tue, 18 Aug 2009 11:24:18 -0600 Received: from ammon ([172.20.20.1]) (SquirrelMail authenticated user karlp) by webmail.ourldsfamily.com with HTTP; Tue, 18 Aug 2009 11:24:19 -0600 Message-ID: <9b266f46debdb24027d54c3bc31de4f6.squirrel@webmail.ourldsfamily.com> In-Reply-To: <4A8A6D7D.24186.16BB0271@localhost> References: <4A8A6D7D.24186.16BB0271@localhost> Date: Tue, 18 Aug 2009 11:24:19 -0600 Subject: Re: Possible ownership/permissions issue? From: "Karl Pearson" To: kgordon2006@verizon.net Cc: Majordomo-Users@greatcircle.com User-Agent: SquirrelMail/1.4.19 MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: clamav-milter 0.95.2 at mail.ourldsfamily.com X-Virus-Status: Clean X-Archive-Number: 200908/15 X-Sequence-Number: 5873 Permissions have to be 751 or 750 and 640 or 644, not 770 or 664. Karl On Tue, August 18, 2009 9:59 am, Kenneth G. Gordon wrote: > I have run an earlier version of Majordomo on one of my systems over > the past 10 years or so, and had very little problem setting it up and > getting it operating. > > Recently, my main server crashed with a catastrophic hardware failure, > and I am in the process of rebuilding my system and adding a backup > system. > > The machines are HP servers, running HP-UX 11.11 with all updates. I > also installed gcc and other software needed by it, and bash, pine, > pico, > Apache, etc. Sendmail is version 8.13.X > > E-mail is working fine as is the web server. > > I tried to set up Majordomo 1.94.5 according to the most recent > documentation, but am having difficulty. > > The setup is as follows: > userID: majordom > group: daemon > majordomo home directory: /opt/majordomo > permissions on $home: 0770 > permissions IN /opt/majordomo/lists: 664 > > In the aliases file at /etc/aliases, I have setup the first alias as > > majordom : majordomo > > in addition to those listed in the majordomo.alias file. > > I can mail to majordomo@foo.somewhere.edu from root or a local user > and it works fine. I get the proper responses, etc. > > However, when I attempt to mail to my list@foo.somewhere.edu, I > receive several messages at the list manager as follows: > > "The original message was received at Mon, 17 Aug 2009 22:09:02 - > 0700 (PDT) from daemon@localhost > > ----- The following addresses had permanent fatal errors ----- > :include:/opt/majordomo/lists/ > (expanded from: -list) > > ----- Transcript of session follows ----- > 550 5.2.4 :include:/opt/majordomo/lists/... Cannot open > /opt/majordomo/lists/: Group writable directory > > [ Part 2: "Delivery Status" ] > > Reporting-MTA: dns; foo.somewhere.edu > Arrival-Date: Mon, 17 Aug 2009 22:09:02 -0700 (PDT) > > Final-Recipient: RFC822; -list@foo.somewhere.edu > X-Actual-Recipient: > rfc822;/opt/majordomo/lists/@foo.somewhere.edu > Action: failed > Status: 5.2.4 > Last-Attempt-Date: Mon, 17 Aug 2009 22:09:02 -0700 (PDT)" > > Will/can someone please tell me what the heck is going on? > > What is this "Group writable directory" business? As far as I can see, > the > directory in question MUST be "group writable". > > I am confused...which is not an unusual state for me. :-( > > Kenneth G. Gordon > Electronic Instrument Specialist, Sr. > University of Idaho > College of Science > Moscow, Idaho 83844-3025 > --- Karl Pearson Karlp@ourldsfamily.com Owner/Administrator of the sites at http://ourldsfamily.com --- "To mess up your Linux PC, you have to really work at it; to mess up a microsoft PC you just have to work on it." --- Democracy is two wolves and a lamb voting on what to have for lunch. Liberty is a well-armed lamb contesting the vote. --Benjamin Franklin --- From majordomo-users-owner@greatcircle.com Tue Aug 18 11:05:45 2009 X-Greylist: delayed 915 seconds by postgrey-1.24 at mycroft; Tue, 18 Aug 2009 11:05:45 PDT Received: from mx3.uidaho.edu (mx3.uidaho.edu [129.101.155.247]) by mycroft.greatcircle.com (Postfix) with ESMTP id 1424A690079 for ; Tue, 18 Aug 2009 11:05:44 -0700 (PDT) Received: from gordon-xw8600 (GordonXW8600.mines.uidaho.edu [129.101.10.145]) by mx3.uidaho.edu (8.14.1/8.14.1) with ESMTP id n7II5hKT002653 for ; Tue, 18 Aug 2009 11:05:43 -0700 From: "Kenneth G. Gordon" To: Majordomo-Users@GreatCircle.COM Date: Tue, 18 Aug 2009 11:05:54 -0700 MIME-Version: 1.0 Subject: More on possible permission/ownership issue Reply-to: kgordon2006@verizon.net Message-ID: <4A8A8B12.6343.209AEB28@localhost> X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5,1.2.40,4.0.166 definitions=2009-08-18_13:2009-08-11,2009-08-18,2009-08-18 signatures=0 X-SpamDetails: rule=notspam policy=default score=2 spamscore=2 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0907200000 definitions=main-0908180118 X-SpamBar: * X-SpamScore: 2 X-Archive-Number: 200908/16 X-Sequence-Number: 5874 OK. Now I get: "MAJORDOMO ABORT (mj_resend)!! shlock: '/opt/majordomo/lists' is not writable by UID 1 GID 1" Ken "Still Confused" Gordon University of Idaho From majordomo-users-owner@greatcircle.com Tue Aug 18 11:27:50 2009 Received: from mail.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id 76A38690079 for ; Tue, 18 Aug 2009 11:27:49 -0700 (PDT) Received: from webmail.ourldsfamily.com (localhost [127.0.0.1]) by mail.ourldsfamily.com (8.14.2/8.14.2) with ESMTP id n7IIRlPt018968; Tue, 18 Aug 2009 12:27:48 -0600 Received: from ammon ([172.20.20.1]) (SquirrelMail authenticated user karlp) by webmail.ourldsfamily.com with HTTP; Tue, 18 Aug 2009 12:27:48 -0600 Message-ID: <680587529036d5fde5cd95b76150f562.squirrel@webmail.ourldsfamily.com> In-Reply-To: <4A8A8B12.6343.209AEB28@localhost> References: <4A8A8B12.6343.209AEB28@localhost> Date: Tue, 18 Aug 2009 12:27:48 -0600 Subject: Re: More on possible permission/ownership issue From: "Karl Pearson" To: kgordon2006@verizon.net Cc: Majordomo-Users@greatcircle.com User-Agent: SquirrelMail/1.4.19 MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: clamav-milter 0.95.2 at mail.ourldsfamily.com X-Virus-Status: Clean X-Archive-Number: 200908/17 X-Sequence-Number: 5875 The owner/groups much match the majordomo use in /etc/passwd, space 2 and 3. Hope that helps. Karl On Tue, August 18, 2009 12:05 pm, Kenneth G. Gordon wrote: > OK. > > Now I get: > > "MAJORDOMO ABORT (mj_resend)!! > > shlock: '/opt/majordomo/lists' is not writable by UID 1 GID 1" > > Ken "Still Confused" Gordon > University of Idaho > --- Karl Pearson Karlp@ourldsfamily.com Owner/Administrator of the sites at http://ourldsfamily.com --- "To mess up your Linux PC, you have to really work at it; to mess up a microsoft PC you just have to work on it." --- Democracy is two wolves and a lamb voting on what to have for lunch. Liberty is a well-armed lamb contesting the vote. --Benjamin Franklin --- From majordomo-users-owner@greatcircle.com Tue Aug 18 12:13:13 2009 Received: from mx2.uidaho.edu (mx2.uidaho.edu [129.101.155.249]) by mycroft.greatcircle.com (Postfix) with ESMTP id ADA4A690079 for ; Tue, 18 Aug 2009 12:13:12 -0700 (PDT) Received: from gordon-xw8600 (GordonXW8600.mines.uidaho.edu [129.101.10.145]) by mx2.uidaho.edu (8.14.1/8.14.1) with ESMTP id n7IJDAZn006809 for ; Tue, 18 Aug 2009 12:13:11 -0700 From: "Kenneth G. Gordon" To: Majordomo-Users@GreatCircle.COM Date: Tue, 18 Aug 2009 12:13:21 -0700 MIME-Version: 1.0 Subject: Weird result Reply-to: kgordon2006@verizon.net Message-ID: <4A8A9AE1.20408.20D8ACE9@localhost> X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5,1.2.40,4.0.166 definitions=2009-08-18_13:2009-08-11,2009-08-18,2009-08-18 signatures=0 X-SpamDetails: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0907200000 definitions=main-0908180134 X-SpamBar: X-SpamScore: 0 X-Archive-Number: 200908/18 X-Sequence-Number: 5876 When I do this: chmod g-w $list_dir or this chmod 6751 $list_dir I get this "shlock: $list_dir is not writable by UID 1 GID 1" Yet if I do this: chmod 0770 $list_dir or this chmod 6770 $list_dir I get this: "550 5.2.4 :include:$list_dir/list... Cannot open $list_dir/list: Group writable directory" The second and third entries in /etc/passwd are 2) daemon and 3) bin The userID majordom is a member of the group daemon AND of the group majordom. Furthermore, if I run as a non-root user ./wrapper config-test, I get even more confusing messages...especially, "$list_dir has bad permissions." unless I make them 770, in which case config-test tells me everything is wonderful...which it isn't... As I said...I am still confused. Help...?!?? Ken Gordon University of Idaho From majordomo-users-owner@greatcircle.com Tue Aug 18 12:16:19 2009 Received: from mx2.uidaho.edu (mx2.uidaho.edu [129.101.155.249]) by mycroft.greatcircle.com (Postfix) with ESMTP id ABF71690096 for ; Tue, 18 Aug 2009 12:16:18 -0700 (PDT) Received: from gordon-xw8600 (GordonXW8600.mines.uidaho.edu [129.101.10.145]) by mx2.uidaho.edu (8.14.1/8.14.1) with ESMTP id n7IJGHUV009164 for ; Tue, 18 Aug 2009 12:16:17 -0700 From: "Kenneth G. Gordon" To: Majordomo-Users@GreatCircle.COM Date: Tue, 18 Aug 2009 12:16:28 -0700 MIME-Version: 1.0 Subject: More permissions issue Reply-to: kgordon2006@verizon.net Message-ID: <4A8A9B9C.28280.20DB86F3@localhost> X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5,1.2.40,4.0.166 definitions=2009-08-18_13:2009-08-11,2009-08-18,2009-08-18 signatures=0 X-SpamDetails: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0907200000 definitions=main-0908180134 X-SpamBar: X-SpamScore: 0 X-Archive-Number: 200908/19 X-Sequence-Number: 5877 And now, my Majordomo-owner (root) is getting this: "MAJORDOMO ABORT (mj_majordomo)!! While running with an effective uid of 1 and an effective gid of 1 1 5, Majordomo ran into the following problems: Unable to write to list directory $listdir, check permissions on /opt/majordomo/lists" So, what the heck is going on? I am almost totally confused by now..... Ken Gordon From majordomo-users-owner@greatcircle.com Tue Aug 18 12:24:03 2009 Received: from fmailhost06.isp.att.net (fmailhost06.isp.att.net [207.115.11.56]) by mycroft.greatcircle.com (Postfix) with ESMTP id 07C0C690079 for ; Tue, 18 Aug 2009 12:24:02 -0700 (PDT) Received: from [127.0.0.1] (adsl-068-209-223-242.sip.jan.bellsouth.net[68.209.223.242]) by isp.att.net (frfwmhc06) with ESMTP id <20090818192402H0600hbfj9e>; Tue, 18 Aug 2009 19:24:02 +0000 X-Originating-IP: [68.209.223.242] Message-ID: <4A8AFFEB.4060809@bellsouth.net> Date: Tue, 18 Aug 2009 14:24:27 -0500 From: Adam Williams User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) MIME-Version: 1.0 To: kgordon2006@verizon.net CC: Majordomo-Users@GreatCircle.COM Subject: Re: More permissions issue References: <4A8A9B9C.28280.20DB86F3@localhost> In-Reply-To: <4A8A9B9C.28280.20DB86F3@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200908/20 X-Sequence-Number: 5878 paste the output of: ls -al /opt/majordomo/lists and cat /etc/passwd|grep majordomo Kenneth G. Gordon wrote: > And now, my Majordomo-owner (root) is getting this: > > "MAJORDOMO ABORT (mj_majordomo)!! > > While running with an effective uid of 1 and an effective gid of 1 1 5, > Majordomo > ran into the following problems: > Unable to write to list directory $listdir, check permissions on > /opt/majordomo/lists" > > So, what the heck is going on? > > I am almost totally confused by now..... > > Ken Gordon > > > From majordomo-users-owner@greatcircle.com Tue Aug 18 15:32:02 2009 Received: from mail.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id EABD26900B0 for ; Tue, 18 Aug 2009 15:32:00 -0700 (PDT) Received: from lehi.local (lehi172 [172.20.20.100]) by mail.ourldsfamily.com (8.14.2/8.14.2) with ESMTP id n7IMVsQo003922; Tue, 18 Aug 2009 16:31:54 -0600 Date: Tue, 18 Aug 2009 16:31:54 -0600 (MDT) From: Karl Pearson X-X-Sender: karlp@lehi To: "Kenneth G. Gordon" cc: Majordomo-Users@greatcircle.com Subject: Re: Weird result In-Reply-To: <4A8A9AE1.20408.20D8ACE9@localhost> Message-ID: References: <4A8A9AE1.20408.20D8ACE9@localhost> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: clamav-milter 0.95.2 at mail.ourldsfamily.com X-Virus-Status: Clean X-Archive-Number: 200908/21 X-Sequence-Number: 5879 I think it sounds like an smrsh issue at this point. Check to be sure there's a soft link in /etc/smrsh to majordomo-1.94.5/wrapper, and any other program majordomo needs. I also use bulk_mailer, so there's a link to it's location in /usr/local/bin, too. cd /etc/smrsh ls -la should give this: wrapper -> /opt/majordomo-1.94.5/wrapper If you get that there, then setting the directories to 751 and the lists to 644 should make the system happy. Karl On Tue, 18 Aug 2009, Kenneth G. Gordon wrote: > When I do this: > > chmod g-w $list_dir > > or this > > chmod 6751 $list_dir > > I get this > > "shlock: $list_dir is not writable by UID 1 GID 1" > > Yet if I do this: > > chmod 0770 $list_dir > > or this > > chmod 6770 $list_dir > > I get this: > > "550 5.2.4 :include:$list_dir/list... Cannot open > $list_dir/list: Group writable directory" > > The second and third entries in /etc/passwd are 2) daemon and 3) > bin > > The userID majordom is a member of the group daemon AND of > the group majordom. > > Furthermore, if I run as a non-root user ./wrapper config-test, I get > even more confusing messages...especially, "$list_dir has bad > permissions." unless I make them 770, in which case config-test > tells me everything is wonderful...which it isn't... > > As I said...I am still confused. > > Help...?!?? > > Ken Gordon > University of Idaho > --- _/ _/ _/ _/_/_/ ____________ __o _/ _/ _/ _/ _/ ____________ _-\\<._ _/_/ _/ _/_/_/ (_)/ (_) _/ _/ _/ _/ ...................... _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com --- http://consulting.ourldsfamily.com --- "Our Constitution was made only for a moral and religious people. It is wholly inadequate to the government of any other." --John Quincy Adams --- Do not handicap your children by making their lives easy. -- Robert Heinlein --- Democracy is two wolves and a lamb voting on what to have for lunch. Liberty is a well-armed lamb contesting the vote. -- Benjamin Franklin --- "To mess up your Linux PC, you have to really work at it; to mess up a microsoft PC you just have to work on it." --- From majordomo-users-owner@greatcircle.com Tue Aug 18 16:43:01 2009 Received: from mx2.uidaho.edu (mx2.uidaho.edu [129.101.155.249]) by mycroft.greatcircle.com (Postfix) with ESMTP id A93C56900B0 for ; Tue, 18 Aug 2009 16:43:00 -0700 (PDT) Received: from gordon-xw8600 (GordonXW8600.mines.uidaho.edu [129.101.10.145]) by mx2.uidaho.edu (8.14.1/8.14.1) with ESMTP id n7INgxjP015284; Tue, 18 Aug 2009 16:42:59 -0700 From: "Kenneth G. Gordon" To: Karl Pearson Date: Tue, 18 Aug 2009 16:43:10 -0700 MIME-Version: 1.0 Subject: Re: Weird result Reply-to: kgordon2006@verizon.net CC: Majordomo-Users@GreatCircle.COM Message-ID: <4A8ADA1E.7476.21CFB062@localhost> In-reply-to: References: <4A8AD25C.20091.21B16282@localhost> X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5,1.2.40,4.0.166 definitions=2009-08-18_15:2009-08-11,2009-08-18,2009-08-18 signatures=0 X-SpamDetails: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0907200000 definitions=main-0908180192 X-SpamBar: X-SpamScore: 0 X-Archive-Number: 200908/22 X-Sequence-Number: 5880 On 18 Aug 2009 at 17:34, Karl Pearson wrote: > It typically is part of the sendmail configuration. You may do a > search at root for smrsh > > cd /;find . -name smrsh -print > > and see what comes back. Perhaps it in /usr/share/etc on HPUX It turns out that I had to add majordom as a Trusted user to the sendmail.cf file. Otherwise, sendmail would not read the $list_dir/list files All fixed now. S'mazing!!!!!!!! Ken From majordomo-users-owner@greatcircle.com Tue Aug 18 16:45:05 2009 Received: from mail.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id 995356900B3 for ; Tue, 18 Aug 2009 16:45:04 -0700 (PDT) Received: from webmail.ourldsfamily.com (localhost [127.0.0.1]) by mail.ourldsfamily.com (8.14.2/8.14.2) with ESMTP id n7INj3Yb022476; Tue, 18 Aug 2009 17:45:03 -0600 Received: from ammon ([172.20.20.1]) (SquirrelMail authenticated user karlp) by webmail.ourldsfamily.com with HTTP; Tue, 18 Aug 2009 17:45:03 -0600 Message-ID: In-Reply-To: <4A8ADA1E.7476.21CFB062@localhost> References: <4A8AD25C.20091.21B16282@localhost> <4A8ADA1E.7476.21CFB062@localhost> Date: Tue, 18 Aug 2009 17:45:03 -0600 Subject: Re: Weird result From: "Karl Pearson" To: kgordon2006@verizon.net Cc: Majordomo-Users@greatcircle.com User-Agent: SquirrelMail/1.4.19 MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: clamav-milter 0.95.2 at mail.ourldsfamily.com X-Virus-Status: Clean X-Archive-Number: 200908/23 X-Sequence-Number: 5881 On Tue, August 18, 2009 5:43 pm, Kenneth G. Gordon wrote: > On 18 Aug 2009 at 17:34, Karl Pearson wrote: > >> It typically is part of the sendmail configuration. You may do a >> search at root for smrsh >> >> cd /;find . -name smrsh -print >> >> and see what comes back. Perhaps it in /usr/share/etc on HPUX > > It turns out that I had to add majordom as a Trusted user to the > sendmail.cf file. > > Otherwise, sendmail would not read the $list_dir/list files > > All fixed now. > > S'mazing!!!!!!!! > > Ken > Nice sleuthing job Karl From majordomo-users-owner@greatcircle.com Tue Aug 18 18:48:43 2009 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id C15076900BC for ; Tue, 18 Aug 2009 18:48:41 -0700 (PDT) Received: from [192.168.1.14] (solara.sonny.com [192.168.1.14]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTPA id <0KOL00406P0YKL@mail.sonny.com> for Majordomo-Users@GreatCircle.COM; Tue, 18 Aug 2009 20:48:34 -0500 (CDT) Date: Tue, 18 Aug 2009 20:48:44 -0500 From: Daniel Liston Subject: Re: More permissions issue In-reply-to: <4A8A9B9C.28280.20DB86F3@localhost> To: kgordon2006@verizon.net Cc: Majordomo-Users@GreatCircle.COM Message-id: <4A8B59FC.80808@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) References: <4A8A9B9C.28280.20DB86F3@localhost> X-Archive-Number: 200908/24 X-Sequence-Number: 5882 Root should not be the majordomo owner. if majordomo is "majordom:x:91:91:List Manager:/opt/majordomo:/bin/sh" NOTE: do not use csh|ksh|zsh for the shell, bash is ok. make sure there is either a group 91 for majordomo to belong to, or make the group the same number as mail, not daemon. Make sure the wrapper is compiled to match settings (uid:gid) of the majordomo user. Take your time and get it right. First sendmail has to work, then the aliases for sendmail, then list expansion, then piping to other programs like majordomo's wrapper. Dan Liston Kenneth G. Gordon wrote: > And now, my Majordomo-owner (root) is getting this: > > "MAJORDOMO ABORT (mj_majordomo)!! > > While running with an effective uid of 1 and an effective gid of 1 1 5, > Majordomo > ran into the following problems: > Unable to write to list directory $listdir, check permissions on > /opt/majordomo/lists" > > So, what the heck is going on? > > I am almost totally confused by now..... > > Ken Gordon From majordomo-users-owner@greatcircle.com Thu Aug 20 11:25:34 2009 Received: from vms173011pub.verizon.net (vms173011pub.verizon.net [206.46.173.11]) by mycroft.greatcircle.com (Postfix) with ESMTP id 492966900FC for ; Thu, 20 Aug 2009 11:25:33 -0700 (PDT) Received: from dell600m ([70.110.49.245]) by vms173011.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KOO00GIXTU4IN46@vms173011.mailsrvcs.net> for Majordomo-Users@greatcircle.com; Thu, 20 Aug 2009 13:25:17 -0500 (CDT) From: "Kenneth G. Gordon" To: Majordomo-Users@greatcircle.com Date: Thu, 20 Aug 2009 11:25:15 -0700 MIME-version: 1.0 Subject: Headers and footers not appearing on list messages Message-id: <4A8D329B.24095.2726E5EF@localhost> X-Mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Archive-Number: 200908/25 X-Sequence-Number: 5883 I think the following has something to do with sendmail's security features, but am not sure: In the $list.config files for some of my lists, there are both headers and footers that are intended to be included in each e-mail. However, if I set ALL files in the majordomo/lists director to mode 644, neither the header nor the footer appears on any list message. The above leads me to believe that the $list.config files are not even being used at all with the present mode. Shouldn't some of those files be executable? Which ones? Executable by whom? If I do not set at least the $list file to mode 644, I get an error message from sendmail that the file is group writeable and it won't read it. Thus, none of the list administrators can edit their $list files unless they su majordom, or unless I make all the files associated with a particular list owned by the list administrator. The first method has, to my mind, security issues. The second is somewhat "unhandy" to root. I have added majordom to the list of Trusted users in my sendmail.cf, which allows sendmail to read the $list files at all, but what do I do about the other files, especially the $list.config files? Solution(s)? Ken Gordon From majordomo-users-owner@greatcircle.com Thu Aug 20 11:57:07 2009 Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mycroft.greatcircle.com (Postfix) with ESMTP id A981F690067 for ; Thu, 20 Aug 2009 11:57:06 -0700 (PDT) Received: from park.js.berklix.net (p549A398A.dip.t-dialin.net [84.154.57.138]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id n7KIv4Hf060472; Thu, 20 Aug 2009 18:57:04 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id n7KIrYYr064215; Thu, 20 Aug 2009 20:53:34 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id n7KItL4M065524; Thu, 20 Aug 2009 20:55:26 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200908201855.n7KItL4M065524@fire.js.berklix.net> To: "Kenneth G. Gordon" cc: Majordomo-Users@greatcircle.com Subject: Re: Headers and footers not appearing on list messages From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Thu, 20 Aug 2009 11:25:15 PDT." <4A8D329B.24095.2726E5EF@localhost> Date: Thu, 20 Aug 2009 20:55:21 +0200 X-Archive-Number: 200908/26 X-Sequence-Number: 5884 ... > neither the header nor the footer appears on any list message. Caution: majordomo is old & ignorant of MIME enclosures, so if people post HTML + Ascii, majordomo doesnt append a MIME delimeter before footer, & footer not visible , though it's there. > Thus, none of the list administrators can edit their $list files unless they su > majordom, or unless I make all the files associated with a particular list > owned by the list administrator. Not true, 4rd option exists: list owners can mail updates in via majordomo using list password. man majordomo Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail ASCII plain text not HTML & Base64. http://asciiribbon.org Virused Microsoft PCs cause spam. http://berklix.com/free/ From majordomo-users-owner@greatcircle.com Thu Aug 20 16:07:21 2009 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id E7EB0590120 for ; Thu, 20 Aug 2009 16:07:19 -0700 (PDT) Received: from [192.168.1.28] (daniel.sonny.com [192.168.1.28]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTPA id <0KOP0060P6W2KK@mail.sonny.com> for Majordomo-Users@greatcircle.com; Thu, 20 Aug 2009 18:07:14 -0500 (CDT) Date: Thu, 20 Aug 2009 18:06:07 -0500 From: Daniel Liston Subject: Re: Headers and footers not appearing on list messages In-reply-to: <4A8D329B.24095.2726E5EF@localhost> To: "Kenneth G. Gordon" Cc: Majordomo-Users@greatcircle.com Message-id: <4A8DD6DF.9030508@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) References: <4A8D329B.24095.2726E5EF@localhost> X-Archive-Number: 200908/27 X-Sequence-Number: 5885 Kenneth G. Gordon wrote: > I think the following has something to do with sendmail's security features, > but am not sure: > > In the $list.config files for some of my lists, there are both headers and > footers that are intended to be included in each e-mail. > > However, if I set ALL files in the majordomo/lists director to mode 644, > neither the header nor the footer appears on any list message. Are you sure they are not in the message? Or are they hidden by MIME/HTML message bodies? CTRL-U in netscape/mozilla/thunderbird to see pieces of the message hidden by the client. I am not sure of equivalent outlook/eudora/other clients keys, but they do have this ability too. > > The above leads me to believe that the $list.config files are not even being > used at all with the present mode. This depends on the answer to the above, and whether "resend" is being used on the alias that directs messages for your list. > > Shouldn't some of those files be executable? ABSOLUTELY NOT!!! > > Which ones? Executable by whom? None. The only executables are in/under your majordomo $HOME directory. My *.config files are 660 and my lists are 644. My list, digest, and archive directories are all 750. Then again, my majordomo user has it's own group, and mail is a member of majordomo and majordomo is trusted. > > If I do not set at least the $list file to mode 644, I get an error message from > sendmail that the file is group writeable and it won't read it. Sendmail security can be reduced to allow group writable files, but this is not necessary either. As this is not in majordomo's control, but sendmail's, I offer; http://www.sendmail.org/tips/dontBlameSendmail > > Thus, none of the list administrators can edit their $list files unless they su > majordom, or unless I make all the files associated with a particular list > owned by the list administrator. Incorrect! Admins do not have to manipulate the files locally, or even have a login on your majordomo/sendmail server. Lists and their configs can be managed remotely through email commands to majordomo. To add or remove addresses from a list, they simply send one line for each command in the body of a message to your majordomo alias. approve list-password [un]subscribe listname email@address approve list-password [un]subscribe listname other@email.address The above method means list owners do not need permission to manipulate files in the majordomo lists directory, as majordomo is the user making changes. [approve list-password] who listname will retrieve the entire subscriber file SEE ALSO: config listname list-password newconfig listname list-password writeconfig listname list-password > > The first method has, to my mind, security issues. The second is somewhat > "unhandy" to root. > > I have added majordom to the list of Trusted users in my sendmail.cf, which > allows sendmail to read the $list files at all, but what do I do about the other > files, especially the $list.config files? Adding majordom as a Trusted user does not do what you describe above, but it may seem like it. A trusted user is one that sendmail will not issue warnings about setting the from address to something other than it's own login name. It may have a side effect of trusting directories/files owned by that user as well. You should really be following majordomo documentation for managing majordomo, then if sendmail security is restricting your majordomo actions, you can relax sendmail accordingly. This might be helpful, with lots of good troubleshooting/debugging information; http://www.greatcircle.com/majordomo/README > > Solution(s)? > > Ken Gordon From majordomo-users-owner@greatcircle.com Thu Aug 20 16:34:52 2009 Received: from mx3.uidaho.edu (mx3.uidaho.edu [129.101.155.247]) by mycroft.greatcircle.com (Postfix) with ESMTP id 36036590120 for ; Thu, 20 Aug 2009 16:34:50 -0700 (PDT) Received: from gordon-xw8600 (GordonXW8600.mines.uidaho.edu [129.101.10.145]) by mx3.uidaho.edu (8.14.1/8.14.1) with ESMTP id n7KNYnv0032477; Thu, 20 Aug 2009 16:34:49 -0700 From: "Kenneth G. Gordon" To: "Daniel Liston" Date: Thu, 20 Aug 2009 16:35:01 -0700 MIME-Version: 1.0 Subject: Re: Headers and footers not appearing on list messages Reply-to: kgordon2006@verizon.net CC: Majordomo-Users@GreatCircle.COM Message-ID: <4A8D7B35.5648.2C14F2E6@localhost> In-reply-to: <4A8DD6DF.9030508@sonny.org> References: <4A8D329B.24095.2726E5EF@localhost> X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5,1.2.40,4.0.166 definitions=2009-08-21_01:2009-08-11,2009-08-21,2009-08-20 signatures=0 X-SpamDetails: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0907200000 definitions=main-0908200119 X-SpamBar: X-SpamScore: 0 X-Archive-Number: 200908/28 X-Sequence-Number: 5886 On 20 Aug 2009 at 18:06, Daniel Liston wrote: > > However, if I set ALL files in the majordomo/lists director to mode > > 644, neither the header nor the footer appears on any list message. > > Are you sure they are not in the message? Yes. Absolutely. They are not even there when I use PINE to view those e-mails, nor in Pegasus, even when I look at the RAW file. They are simply not there. > Or are they hidden by > MIME/HTML message bodies? CTRL-U in netscape/mozilla/thunderbird to > see pieces of the message hidden by the client. I am not sure of > equivalent outlook/eudora/other clients keys, but they do have this > ability too. NONE of this applies in this case. > > The above leads me to believe that the $list.config files are not > > even being used at all with the present mode. > > This depends on the answer to the above, and whether "resend" is being > used on the alias that directs messages for your list. It is. > > Shouldn't some of those files be executable? > > ABSOLUTELY NOT!!! I assumed as much. > None. The only executables are in/under your majordomo $HOME > directory. My *.config files are 660 and my lists are 644. Ah HA! WHICH *..config files? Where? This is the question I am asking.... > My list, > digest, and archive directories are all 750. As are mine....although I think my list directory is 4750...since it is owned by majordom > Then again, my majordomo > user has it's own group, and mail is a member of majordomo and > majordomo is trusted. So is mine...actually, majordom is a member of mail. I suppose I should reverse that... > > If I do not set at least the $list file to mode 644, I get an error > > message from sendmail that the file is group writeable and it won't > > read it. > > Sendmail security can be reduced to allow group writable files, but > this is not necessary either. And I do not want to do that either! > As this is not in majordomo's control, > but sendmail's, Yes. I know. > I offer; > > http://www.sendmail.org/tips/dontBlameSendmail I have already read that....so many times my eyes are tired. > > Thus, none of the list administrators can edit their $list files > > unless they su majordom, or unless I make all the files associated > > with a particular list owned by the list administrator. > > Incorrect! Admins do not have to manipulate the files locally, or > even have a login on your majordomo/sendmail server. Lists and their > configs can be managed remotely through email commands to majordomo. I know that. I HAVE read the Majordomo documentation, after all, although it may seem as though I haven't. However, most of my list managers prefer to use SSH or similar rather than the e-mail management method. > To add or remove addresses from a list, they simply send one line for > each command in the body of a message to your majordomo alias. > > approve list-password [un]subscribe listname email@address > approve list-password [un]subscribe listname other@email.address > > The above method means list owners do not need permission to > manipulate files in the majordomo lists directory, as majordomo is the > user making changes. > > [approve list-password] who listname > will retrieve the entire subscriber file Yes. I know all that, thanks. As I said, most of my list managers are reluctant to use that method. They prefer something they are used to using....SSH/telnet. After all, they have been using their preferred method for nigh onto 10 years... > > SEE ALSO: > config listname list-password > newconfig listname list-password > writeconfig listname list-password I have read all that. As I said... > > I have added majordom to the list of Trusted users in my > > sendmail.cf, which allows sendmail to read the $list files at all, > > but what do I do about the other files, especially the $list.config > > files? > > Adding majordom as a Trusted user does not do what you describe above, > but it may seem like it. A trusted user is one that sendmail will not > issue warnings about setting the from address to something other than > it's own login name. It may have a side effect of trusting > directories/files owned by that user as well. You should really be > following majordomo documentation for managing majordomo, then if > sendmail security is restricting your majordomo actions, you can relax > sendmail accordingly. That last, relaxing sendmail's security, I do NOT want to do. I have had too much trouble with hackers to even suggest making it any easier for those scum-of-the-earth. > > This might be helpful, with lots of good troubleshooting/debugging > information; > > http://www.greatcircle.com/majordomo/README I have read that, repeatedly, and have printed it off several times. To provide another clue, I have the following files in my lists directory. $list $list.config $list.info $list.save $list.strip ALL $list files are 644 If I make $list.config 644, it does not get "read" or applied. I HAVE to set that file, at least, as 664 in order for it to work. I do not yet know if the others are effected as well. However, you say above that your *.config files are 664, so again, I ask WHICH *.,config files? Those dealing with majordomo itself, those associated with each list, those over in the directory where I did Make and Install? Which? Am I correct in assuming that when you said *.config, you meant ONLY those in the lists directory? Thank for all the time and help, BTW. Ken Gordon From majordomo-users-owner@greatcircle.com Fri Aug 21 22:46:06 2009 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 34ADF69004F for ; Fri, 21 Aug 2009 22:46:02 -0700 (PDT) Received: from [192.168.1.28] (daniel.sonny.com [192.168.1.28]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTPA id <0KOR00702K0GJT@mail.sonny.com> for Majordomo-Users@GreatCircle.COM; Sat, 22 Aug 2009 00:45:52 -0500 (CDT) Date: Sat, 22 Aug 2009 00:44:41 -0500 From: Daniel Liston Subject: Re: Headers and footers not appearing on list messages In-reply-to: <4A8D7B35.5648.2C14F2E6@localhost> To: kgordon2006@verizon.net Cc: Majordomo-Users@GreatCircle.COM Message-id: <4A8F85C9.7020607@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) References: <4A8D329B.24095.2726E5EF@localhost> <4A8D7B35.5648.2C14F2E6@localhost> X-Archive-Number: 200908/29 X-Sequence-Number: 5887 Let's review: Your old server crashed and you had to reinstall majordomo on a newer one with\out identical OS, perl, sendmail, or other applications. You installed majordomo, but you are getting permission warnings/errors. From the top, FIRST sendmail must work. You can receive mail to users on the machine, and those users can use sendmail to get mail out of the system to other users on the internet, and an alias can expand to a local or remote address with successful delivery. If this does not work, do not proceed to the next step. SECOND, sendmail allows aliases that use :include: files in directories that are not owned by sendmail. These files are also not owned by sendmail. THIRD, sendmail can write messages to a file in a directory that it does not own. (something has to tell sendmail these files/directories are safe) Notice: majordomo is not participating yet FORTH, sendmail must be able to pipe messages to other programs for delivery (or further processing) and trust that program. Notice: sendmail was able to do all these things on your old server Were you able to capture sendmail.cf from the old machine? It should still work with the newer version. Once you have the prerequisites above achieved, you can introduce majordomo to the environment. For security reasons, majordomo should not use the same uid or gid as root, daemon, postmaster, mailer-daemon, or sendmail for that matter. Since you can't have your cake, and eat it too, you have to make some hard decisions on allowing your 10 year users to continue in their old habits of editing files at the command shell, or relaxing the newer versions of sendmail security. Lastly, yes. I was referring *.config files as only those in my lists directory, and they are owner:group majordomo:majordomo (I run linux). Relaxing sendmail security at the file system level does not make it easier for hackers to get into your system or to use your sendmail service. (unless one of your list owners is the hacker) Remember, you are only allowing what sendmail always allowed in your previous version, and you can be specific about the directories that you are telling sendmail to consider "safe". Ultimately, majordomo and sendmail are only secure/safe if there are no human users on your system. Even then, you still have to take more precautions to protect these services from the outside world too. Let us know what you decide. Dan Liston Kenneth G. Gordon wrote: > On 20 Aug 2009 at 18:06, Daniel Liston wrote: > >>> However, if I set ALL files in the majordomo/lists director to mode >>> 644, neither the header nor the footer appears on any list message. >> Are you sure they are not in the message? > > Yes. Absolutely. They are not even there when I use PINE to view > those e-mails, nor in Pegasus, even when I look at the RAW file. > They are simply not there. > >> Or are they hidden by >> MIME/HTML message bodies? CTRL-U in netscape/mozilla/thunderbird to >> see pieces of the message hidden by the client. I am not sure of >> equivalent outlook/eudora/other clients keys, but they do have this >> ability too. > > NONE of this applies in this case. > >>> The above leads me to believe that the $list.config files are not >>> even being used at all with the present mode. >> This depends on the answer to the above, and whether "resend" is being >> used on the alias that directs messages for your list. > > It is. > >>> Shouldn't some of those files be executable? >> ABSOLUTELY NOT!!! > > I assumed as much. > >> None. The only executables are in/under your majordomo $HOME >> directory. My *.config files are 660 and my lists are 644. > > Ah HA! WHICH *..config files? Where? This is the question I am > asking.... > >> My list, >> digest, and archive directories are all 750. > > As are mine....although I think my list directory is 4750...since it is > owned by majordom > >> Then again, my majordomo >> user has it's own group, and mail is a member of majordomo and >> majordomo is trusted. > > So is mine...actually, majordom is a member of mail. I suppose I > should reverse that... > >>> If I do not set at least the $list file to mode 644, I get an error >>> message from sendmail that the file is group writeable and it won't >>> read it. >> Sendmail security can be reduced to allow group writable files, but >> this is not necessary either. > > And I do not want to do that either! > >> As this is not in majordomo's control, >> but sendmail's, > > Yes. I know. > >> I offer; >> >> http://www.sendmail.org/tips/dontBlameSendmail > > I have already read that....so many times my eyes are tired. > >>> Thus, none of the list administrators can edit their $list files >>> unless they su majordom, or unless I make all the files associated >>> with a particular list owned by the list administrator. >> Incorrect! Admins do not have to manipulate the files locally, or >> even have a login on your majordomo/sendmail server. Lists and their >> configs can be managed remotely through email commands to majordomo. > > I know that. I HAVE read the Majordomo documentation, after all, > although it may seem as though I haven't. However, most of my list > managers prefer to use SSH or similar rather than the e-mail > management method. > >> To add or remove addresses from a list, they simply send one line for >> each command in the body of a message to your majordomo alias. >> >> approve list-password [un]subscribe listname email@address >> approve list-password [un]subscribe listname other@email.address >> >> The above method means list owners do not need permission to >> manipulate files in the majordomo lists directory, as majordomo is the >> user making changes. >> >> [approve list-password] who listname >> will retrieve the entire subscriber file > > Yes. I know all that, thanks. As I said, most of my list managers are > reluctant to use that method. They prefer something they are used > to using....SSH/telnet. After all, they have been using their preferred > method for nigh onto 10 years... > >> SEE ALSO: >> config listname list-password >> newconfig listname list-password >> writeconfig listname list-password > > I have read all that. As I said... > >>> I have added majordom to the list of Trusted users in my >>> sendmail.cf, which allows sendmail to read the $list files at all, >>> but what do I do about the other files, especially the $list.config >>> files? >> Adding majordom as a Trusted user does not do what you describe above, >> but it may seem like it. A trusted user is one that sendmail will not >> issue warnings about setting the from address to something other than >> it's own login name. It may have a side effect of trusting >> directories/files owned by that user as well. You should really be >> following majordomo documentation for managing majordomo, then if >> sendmail security is restricting your majordomo actions, you can relax >> sendmail accordingly. > > That last, relaxing sendmail's security, I do NOT want to do. I have > had too much trouble with hackers to even suggest making it any > easier for those scum-of-the-earth. > >> This might be helpful, with lots of good troubleshooting/debugging >> information; >> >> http://www.greatcircle.com/majordomo/README > > I have read that, repeatedly, and have printed it off several times. > > To provide another clue, I have the following files in my lists > directory. > > $list > $list.config > $list.info > $list.save > $list.strip > > ALL $list files are 644 > > If I make $list.config 644, it does not get "read" or applied. I HAVE > to set that file, at least, as 664 in order for it to work. > > I do not yet know if the others are effected as well. > > However, you say above that your *.config files are 664, so again, I > ask WHICH *.,config files? Those dealing with majordomo itself, > those associated with each list, those over in the directory where I > did Make and Install? Which? > > Am I correct in assuming that when you said *.config, you meant > ONLY those in the lists directory? > > Thank for all the time and help, BTW. > > Ken Gordon