From majordomo-users-owner@greatcircle.com Sun Jan 3 05:20:14 2010 Received: from mail-yw0-f191.google.com (mail-yw0-f191.google.com [209.85.211.191]) by mycroft.greatcircle.com (Postfix) with ESMTP id EFD9159010B for ; Sun, 3 Jan 2010 05:20:12 -0800 (PST) Received: by ywh29 with SMTP id 29so17874619ywh.32 for ; Sun, 03 Jan 2010 05:20:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Fo3puQyzdKCjLfrrN+MhmXX/MKFKhZfk6ilS8wdLrC8=; b=stOkr1X7rdjxJPpQjkYYUXxbN3Iy2EYzlCKTAY8WuZav0VaS8ByckW0Eu7Mx95Z9NW ClW5qnTU4DjrLJUH5grrZnVJntrAScX6Wpz2x/EYkB9JSeAiqiULpvbAthLVHBj5sFBd F2jnTAxm3jZmYf64AJkRRzV5m/VLeg8HS4WP4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=hk8jRaIfGilox0qVSaj1FwTVOQ79aIvjXW9eI9vnXCYbfMNmICYElBEPfhUbr24OaS dJ0P/5vFCo+RsIvQhrM1X0RXN3ciibEBmV26Oytm78KUNfJWAPhkHGIH8NU5uJsVbTWe dBTqc1YnnOoYNfoz8cIPjsWmTPTg4v9V19K64= MIME-Version: 1.0 Received: by 10.91.161.31 with SMTP id n31mr3022628ago.96.1262524812054; Sun, 03 Jan 2010 05:20:12 -0800 (PST) Date: Sun, 3 Jan 2010 22:20:12 +0900 Message-ID: <99079c361001030520s5cff8738g5f3d04a4209e7c00@mail.gmail.com> Subject: From: "me ." To: majordomo-users@greatcircle.com Content-Type: text/plain; charset=ISO-8859-1 X-Archive-Number: 201001/1 X-Sequence-Number: 5906 On Dec 24 2009 13:47:32 I got the following error in my majordomo.log WARNING Failed to open temp file '/usr/tmp/resend.5590.out', it exists ABORT resend: Can't open /usr/tmp/resend.5590.out: Illegal seek I checked the resend.5590.out file in /usr/tmp and can see that it was created in Dec 1 2009 22:16 and also realized that there is a resend.5590.in file present. I dont really know the meaning or causes of the error. and would be glad if someone could explain it to me Also the difference between resend.xxx.out and resend.xxx.in files and the reason why they are created. Info about the majordomo I'm using majordomo-1.94.5 perl v5.8.5 Linux (Redhat) Qmail I am new to majordomo and would be glad to have some information on this matter. Thanks in advance From majordomo-users-owner@greatcircle.com Mon Jan 4 13:51:07 2010 X-Greylist: delayed 2789 seconds by postgrey-1.24 at mycroft; Mon, 04 Jan 2010 13:51:07 PST Received: from s5.cableone.net (s5.cableone.net [24.116.0.231]) by mycroft.greatcircle.com (Postfix) with ESMTP id 679F869005B for ; Mon, 4 Jan 2010 13:51:07 -0800 (PST) Received: from [192.168.1.28] (unverified [24.117.88.177]) by s5.cableone.net (CableOne SMTP Service s5) with ESMTP id 27487970-1872270 for multiple; Mon, 04 Jan 2010 14:04:35 -0700 Message-ID: <4B4257D0.70001@sonny.org> Date: Mon, 04 Jan 2010 15:04:16 -0600 From: Daniel Liston User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: majordomo-users@greatcircle.com CC: "me ." Subject: Re: (no subject) References: <99079c361001030520s5cff8738g5f3d04a4209e7c00@mail.gmail.com> In-Reply-To: <99079c361001030520s5cff8738g5f3d04a4209e7c00@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Vpipe: Scanner said ok (av_avast) X-IP-stats: Incoming Last 0, First 45, in=5, out=0, spam=0 ip=24.117.88.177 X-Originating-IP: 24.117.88.177 X-Abuse-Info: Send abuse complaints to abuse@cableone.net X-Archive-Number: 201001/2 X-Sequence-Number: 5907 I have never used qmail myself, but I know it is different from and has unique requirements to configure use with majordomo. Several questions come to mind... Does the date in your majordomo.log entry match the timestamp of the tmp file? If not, something (qmail?) did not clean up the files last time they were used, and you should remove them manually. If the files actually contain message(s) from "Dec 01, 2009", do you have the qmail and majordomo logs that match the timestamp? Do you have more than one list? Does this happen every time you send messages through majordomo, or just a specific list? Or has this not happened at all since 1 Dec 09? If you can't tell, I am thinking this is probably something to do with the way qmail does things vs. a problem with majordomo. With sendmail I do not see *.in or *.out files in my tmp directory. Dan Liston > On Dec 24 2009 13:47:32 I got the following error in my majordomo.log > > WARNING Failed to open temp file '/usr/tmp/resend.5590.out', it exists > ABORT resend: Can't open /usr/tmp/resend.5590.out: Illegal seek > > I checked the resend.5590.out file in /usr/tmp and can see that it was > created in Dec 1 2009 22:16 and also realized that there is a > resend.5590.in file present. > > I dont really know the meaning or causes of the error. > and would be glad if someone could explain it to me > > Also the difference between resend.xxx.out and resend.xxx.in files and > the reason why they are created. > > Info about the majordomo I'm using > majordomo-1.94.5 > perl v5.8.5 > Linux (Redhat) > Qmail > > I am new to majordomo and would be glad to have some information on this matter. > Thanks in advance From majordomo-users-owner@greatcircle.com Mon Jan 4 21:42:55 2010 X-Greylist: delayed 63 seconds by postgrey-1.24 at mycroft; Mon, 04 Jan 2010 21:42:54 PST Received: from kdtc.net (177.122.103.218.static.netvigator.com [218.103.122.177]) by mycroft.greatcircle.com (Postfix) with ESMTP id 6150E69002E for ; Mon, 4 Jan 2010 21:42:54 -0800 (PST) Received: from [192.168.8.28] (crazycat [192.168.8.28]) (authenticated bits=0) by kdtc.net (8.14.3/8.14.3) with ESMTP id o055j24R007421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 5 Jan 2010 13:45:07 +0800 X-Authentication-Warning: kdtc.net: Host crazycat [192.168.8.28] claimed to be [192.168.8.28] Message-ID: <4B42CD09.8000409@kdtc.net> Date: Tue, 05 Jan 2010 13:24:25 +0800 From: CC User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090410 SeaMonkey/1.1.16 MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: confused with moderating a list Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.57 on 192.168.8.27 X-Archive-Number: 201001/3 X-Sequence-Number: 5908 Hi, I'm trying to set up a moderated list with Majordomo. I've setup the configuration file with moderated set to yes, and the approve_password set to the password. As far as I can understand from the FAQ and Googled topics, the process of moderating is the following: 1) Someone sends an e-mail to, say, thislist@mydomain.com. 2) The moderator receives the message: BOUNCE: thislist@mydomain.com Approval required: 3) Moderator replies with the following (using a mail client the client will quote the message to be moderated. The moderator must delete the quote marks): From this: > From - someone@anotherdoamin.com > Received: .... > .... > Received: ... > .... > Dear All > > To this: Approved: Received: ... ... Received: ... .... Dear All 4) Message is to be sent to the thislist@mydomain.com. I've removed the "Precedence" and "Sender" headers because they are always being appended to the end of the message. i.e. Dear All Precendence: bulk Sender: mylist@mydomain.com Which is wrong. Have I gotten the right procedure down? The reason why I'm asking is that no matter what I do, approving the message would often screw up the outgoing message format. i.e. instead of: Dear All I have made a test to this e-mail list. Please confirm if you get this message. All messages should go here. Moderator I get the following: Dear All I have made a test to this e-mail list. Please confirm if you get this message. All messages should go here. Moderator Sender: owner-list@mydomain.com What exactly am I doing wrong? Any clarifications appreciated. Thanks. Edmund From majordomo-users-owner@greatcircle.com Mon Jan 11 18:14:16 2010 Received: from s1.cableone.net (s1.cableone.net [24.116.0.227]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8E3C769009E for ; Mon, 11 Jan 2010 18:14:14 -0800 (PST) Received: from [192.168.1.28] (unverified [24.117.88.177]) by s1.cableone.net (CableOne SMTP Service s1) with ESMTP id 26357412-1872270 for multiple; Mon, 11 Jan 2010 19:14:11 -0700 Message-ID: <4B4BDAF2.20807@sonny.org> Date: Mon, 11 Jan 2010 20:14:10 -0600 From: Daniel Liston User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: CC CC: majordomo-users@greatcircle.com Subject: Re: confused with moderating a list References: <4B42CD09.8000409@kdtc.net> In-Reply-To: <4B42CD09.8000409@kdtc.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Vpipe: Scanner said ok (av_avast) X-IP-stats: Incoming Last 31, First 170, in=30, out=0, spam=0 ip=24.117.88.177 X-Originating-IP: 24.117.88.177 X-Abuse-Info: Send abuse complaints to abuse@cableone.net X-Archive-Number: 201001/4 X-Sequence-Number: 5909 My mail server's hard drive crashed while I was out of town last week, so first let me apologize for a week long delay to send your reply. I think you are very close to having the process correct and complete with one exception; All mail is really two (or more) pieces of information. You have an envelope which exposes sender and receiver, postage and a postmark, as well as any irrelevant comments. Inside the envelope is the bill, newsletter, bank statement, or a combination of them all. In other words, the message body. I could get into attachments and MIME parts, but they all really count as message body contents anyway. So the piece you are missing in your process to moderate a mailing list is simply a separation of envelope and message. This is a blank line. Since you don't really need the postage, postmark, or comments in the distributed message, you can send an approval like this; (cut from the list-owner-info text file included with majordomo) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> From: majordomo@list.server \ To: your-list-approval@list.server | Don't want these headers Subject: BOUNCE: approval required / - Blank line >From list-member@her.site date \ Received: some long routing info | Headers of original message; From: list-member@her.site | You want these. It's OK if you To: your-list@list.server | don't have the first line. Subject: Just a message / - Blank line, you _must_ have this! Hello. I'm just writing to \ consume some bandwidth and | Message body; include all of take up space in your mail | this. spool! / <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Technically, you only care about the To: From: Subject: and perhaps even the Date: fields of the envelope, but these must be preceded with the keyword Approved: followed by the appropriate password. What you send back to your list, not majordomo now looks like this; >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Approved: secret pass code >From: list-member@her.site To: your-list@list.server Subject: Just a message Hello. I'm just writing to consume some bandwidth and take up space in your mail spool! <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Notice you are allowed to use MORE than one blank line to separate the headers from the body. The crucial factor is that your email client does not introduce any blank lines above your approved line, and that the blank line that is used to separate the body from the header is truly a blank line, not some non-printable whitespace character. Final note: Some MTAs enforce the rfc822 requirement to use CR/LF as a line termination sequence in email. If you have one of these, you need to check the documentation of your MTA for relaxing the restriction, or put a line of perl code in majordomo.pl and resend so it can strip the extra character to recognize and call the line "blank". ***majordomo.pl 59c59,60 < s/\n\s+/ /g; --- > s/[\^M]//g; # strip DOS from lines > s/\n\s+/ /g; # unfold wrapped headers The ^M is a single character created by typing ctrl-v then ctrl-m. ***resend 591c591 < --- > s/[\^M]//g; # strip DOS from end of lines If you are familiar with unix patch or diff, the above line is inserted at line 59 in majordomo.pl, and replaces a blank line 591 in resend. Another solution, instead of stripping out the carriage return would be to actually accept ^M or CR/LF as an acceptable line termination sequence. The above line numbering assumes you have an unpatched 1.94.5 version of majordomo. If not, you may need some help to locate the actual place to insert the modification. Happy New Year, Dan Liston From majordomo-users-owner@greatcircle.com Mon Jan 18 19:47:57 2010 X-Greylist: delayed 65 seconds by postgrey-1.24 at mycroft; Mon, 18 Jan 2010 19:47:55 PST Received: from belfordhk.com (www.belfordhk.com [210.3.42.178]) by mycroft.greatcircle.com (Postfix) with ESMTP id EAB01690081 for ; Mon, 18 Jan 2010 19:47:55 -0800 (PST) Received: from [192.168.0.27] (it [192.168.0.27]) (authenticated bits=0) by belfordhk.com (8.14.3/8.14.2) with ESMTP id o0J3klWA022130; Tue, 19 Jan 2010 11:46:48 +0800 X-Authentication-Warning: belfordhk.com: Host it [192.168.0.27] claimed to be [192.168.0.27] Message-ID: <4B552B19.2060809@belfordhk.com> Date: Tue, 19 Jan 2010 11:46:33 +0800 From: Edmund User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18 MIME-Version: 1.0 To: Daniel Liston CC: majordomo-users@greatcircle.com Subject: Re: confused with moderating a list References: <4B42CD09.8000409@kdtc.net> <4B4BDAF2.20807@sonny.org> In-Reply-To: <4B4BDAF2.20807@sonny.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 192.168.9.21 X-Archive-Number: 201001/5 X-Sequence-Number: 5910 Daniel Liston wrote: > I think you are very close to having the process correct and complete > with one exception; > > All mail is really two (or more) pieces of information. You have an > envelope which exposes sender and receiver, postage and a postmark, > as well as any irrelevant comments. Inside the envelope is the bill, > newsletter, bank statement, or a combination of them all. In other > words, the message body. I could get into attachments and MIME parts, > but they all really count as message body contents anyway. > > So the piece you are missing in your process to moderate a mailing > list is simply a separation of envelope and message. This is a blank > line. Hi Daniel, Sorry for the delay. Been following your message at work and gave up since I didn't have much time to spend on this issue. Now that I have some time, I figured I'd do a test mailing list. At this moment, I got it working provided I remove the quotes. Here's what I mean. 1) I receive the BOUNCE message. 2) I click on reply (using Seamonkey). 3) It quotes everything in the post. 4) I remove the top part up to but not including the initial From: header. 5) I remove the "> " from the post. 6) I add the blank line and then Approved: after the blank line and before the message. 7) I send. If I don't remove the quotes, it obviously doesn't know the subject and from, so it posts an empty subject message with the whole quoted message and then the From: and To:. Is this by design? Thanks Edmund > > Since you don't really need the postage, postmark, or comments in the > distributed message, you can send an approval like this; (cut from the > list-owner-info text file included with majordomo) > > From: majordomo@list.server \ > To: your-list-approval@list.server | Don't want these headers > Subject: BOUNCE: approval required / > - Blank line >>From list-member@her.site date \ > Received: some long routing info | Headers of original message; > From: list-member@her.site | You want these. It's OK if you > To: your-list@list.server | don't have the first line. > Subject: Just a message / > - Blank line, you _must_ have this! > Hello. I'm just writing to \ > consume some bandwidth and | Message body; include all of > take up space in your mail | this. > spool! / > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > > Technically, you only care about the To: From: Subject: and perhaps > even the Date: fields of the envelope, but these must be preceded > with the keyword Approved: followed by the appropriate password. > > What you send back to your list, not majordomo now looks like this; > > Approved: secret pass code >> From: list-member@her.site > To: your-list@list.server > Subject: Just a message > > > Hello. I'm just writing to > consume some bandwidth and > take up space in your mail > spool! > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > > Notice you are allowed to use MORE than one blank line to > separate the headers from the body. The crucial factor is > that your email client does not introduce any blank lines > above your approved line, and that the blank line that is > used to separate the body from the header is truly a blank > line, not some non-printable whitespace character. > > Final note: Some MTAs enforce the rfc822 requirement to > use CR/LF as a line termination sequence in email. If you > have one of these, you need to check the documentation of > your MTA for relaxing the restriction, or put a line of > perl code in majordomo.pl and resend so it can strip the > extra character to recognize and call the line "blank". > > ***majordomo.pl > 59c59,60 > < s/\n\s+/ /g; > --- >> s/[\^M]//g; # strip DOS from lines >> s/\n\s+/ /g; # unfold wrapped headers > > The ^M is a single character created by typing ctrl-v then ctrl-m. > > ***resend > 591c591 > < > --- >> s/[\^M]//g; # strip DOS from end of lines > > If you are familiar with unix patch or diff, the above line is > inserted at line 59 in majordomo.pl, and replaces a blank line > 591 in resend. Another solution, instead of stripping out the > carriage return would be to actually accept ^M or CR/LF as an > acceptable line termination sequence. > > The above line numbering assumes you have an unpatched 1.94.5 > version of majordomo. If not, you may need some help to locate > the actual place to insert the modification. > > Happy New Year, > Dan Liston > From majordomo-users-owner@greatcircle.com Thu Jan 21 22:17:00 2010 X-Greylist: delayed 335 seconds by postgrey-1.24 at mycroft; Thu, 21 Jan 2010 22:16:58 PST Received: from www2.mrbrklyn.com (www2.mrbrklyn.com [96.57.23.82]) by mycroft.greatcircle.com (Postfix) with ESMTP id CAFD169005E for ; Thu, 21 Jan 2010 22:16:58 -0800 (PST) Received: from [96.57.23.82] (www2.mrbrklyn.com [96.57.23.82]) by www2.mrbrklyn.com (Postfix) with ESMTP id ED1739C31D for ; Fri, 22 Jan 2010 01:09:50 -0500 (EST) Message-ID: <4B59412E.8010105@mrbrklyn.com> Date: Fri, 22 Jan 2010 01:09:50 -0500 From: Ruben Safir User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091130 SUSE/3.0.0-1.1.1 Thunderbird/3.0 MIME-Version: 1.0 To: Majordomo-Users@GreatCircle.COM Subject: majordomo postfix - status=deferred (temporary failure) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archive-Number: 201001/6 X-Sequence-Number: 5911 Hello I have this puzzle that I can't figure out. I had my mailing list working on openSuSE 11.2 with postfix and majordomo. I've been using majordomo on sendmailf or years with no trouble. I moved to postfix with no trouble and now, suddenly I'm getting nothing through to my lists. Everything says status=deferred(temporary failure). I have no idea what is happening. I've done a shake out with post fix and it seems to be relaying through the aliases fine. So, I think I might have somehow messed up my majordomo set up, but I can't find anything for the life of me. Aliases look like this majordomo: "|/usr/lib/majordomo/wrapper majordomo" #majordomo: "|/tmp/tmp_mail" owner-majordomo: root, majordomo-owner: root, # sample entry for a majordomo mailing-list called "test" # read /usr/doc/packages/majordomo/README.linux for more information # replace "test" with a new name and put the administrator into # the "owner-test" alias instead of "root". # #test: "|/usr/lib/majordomo/wrapper resend -l test test-outgoing" hangout: "|/usr/lib/majordomo/wrapper resend -l hangout hangout-outgoing" #test-outgoing: :include:/var/lib/majordomo/lists/test hangout-outgoing: :include:/var/lib/majordomo/lists/hangout #test-request: "|/usr/lib/majordomo/wrapper majordomo -l test" hangout-request: "|/usr/lib/majordomo/wrapper majordomo -l hangout" #test-approval: owner-test, hangout-approval: owner-hangout, #owner-test-outgoing: owner-test, owner-hangout-outgoing: owner-hangout, #owner-test-request: owner-test, owner-hangout-request: owner-hangout, #owner-test: root, owner-hangout: ruben, The /etc/majordomo file show this # $log -- Where do I write my log? # $log = "/var/lib/majordomo/Log"; But there is no log and nothing under /var/lib/majordomo/tmp of use either I have the following file permisions www2:/usr/lib/majordomo # ls -al total 360 drwxr-xr-x 3 mdom mdom 472 Dec 19 17:02 . drwxr-xr-x 272 root root 109640 Jan 12 00:38 .. drwxr-xr-x 2 root root 264 Dec 19 17:02 Tools -rwxr-xr-x 1 root root 5267 Oct 19 11:24 archive2.pl -rwxr-xr-x 1 root root 2796 Oct 19 11:24 bounce-remind -rwxr-xr-x 1 root root 10693 Oct 19 11:24 config-test -rwxr-xr-x 1 root root 51130 Oct 19 11:24 config_parse.pl -rwxr-xr-x 1 root root 14215 Oct 19 11:24 digest -rwxr-xr-x 1 root root 62513 Oct 19 11:24 majordomo -rwxr-xr-x 1 root root 24613 Oct 19 11:24 majordomo.pl -rwxr-xr-x 1 root root 137 Oct 19 11:24 majordomo_version.pl -rwxr-xr-x 1 root root 3793 Oct 19 11:24 request-answer -rwxr-xr-x 1 root root 29949 Oct 19 11:24 resend -rw-r--r-- 1 root root 10561 Oct 19 11:24 sample.cf -rwxr-xr-x 1 root root 8060 Oct 19 11:24 shlock.pl -rwsr-xr-x 1 root daemon 5896 Oct 19 11:24 wrapper config-test runs as a normal user ruben@www2:/usr/lib/majordomo> ./wrapper config-test ------------------------------------------------------------ ---------------- Config-test for Majordomo ---------------- ------------------------------------------------------------ --------------------- Obvious things: --------------------- ------------------ environment variables ------------------ HOME=/usr/lib/majordomo LOGNAME=ruben MAJORDOMO_CF=/etc/majordomo.cf PATH=/bin:/usr/bin SHELL=/bin/sh USER=ruben --------------------- euid/egid checks --------------------- effective user = mdom (uid 28) effective group = mdom audio video games users gdm (gid 28 17 33 40 100 117 ) ---------------------- uid/gid checks ---------------------- real user = mdom (uid 28) real group = mdom audio video games users gdm (gid 28 17 33 40 100 117 ) ------------------------------------------------------------ Non obvious things that cause headaches: ------------------------------------------------------------ This is permisions for the list locations ruben@www2:/var/lib> ls -al |grep maj drwxr-xr-x 6 mdom mdom 232 2010-01-22 00:59 majordomo ruben@www2:/var/lib/majordomo> ls -al total 22 drwxr-xr-x 6 mdom mdom 232 2010-01-22 00:59 . drwxr-xr-x 60 root root 1560 2010-01-12 00:38 .. drwxr-xr-x 2 mdom mdom 48 2009-10-19 11:24 archive drwxr-xr-x 2 mdom mdom 48 2009-10-19 11:24 digest drwxr-xr-x 2 mdom mdom 704 2010-01-21 21:40 lists -rw-rw-r-- 1 mdom mdom 0 2010-01-22 00:59 Log -rw------- 1 mdom mdom 10504 2010-01-01 14:03 majordomo.cf -rwx------ 1 mdom mdom 8060 2005-05-19 03:52 shlock.pl drwxr-xr-x 2 mdom mdom 48 2010-01-21 21:51 tmp ruben@www2:/var/lib/majordomo/lists> ls -al total 269 drwxr-xr-x 2 mdom mdom 704 2010-01-21 21:40 . drwxr-xr-x 6 mdom mdom 232 2010-01-22 00:59 .. -rwx------ 1 mdom mdom 57 2005-07-16 12:05 break.pl -rw-r--r-- 1 mdom mdom 106 2009-07-29 22:23 freedom_it -rw-r--r-- 1 mdom mdom 17392 2007-10-10 03:10 freedom_it.admin -rw-r--r-- 1 mdom mdom 16690 2007-10-10 03:09 freedom_it.config -rw-r--r-- 1 mdom mdom 2943 2009-11-17 18:56 hangout -rw-r--r-- 1 mdom mdom 17389 2007-12-08 12:25 hangout.admin -rw-r--r-- 1 mdom mdom 9025 2005-05-19 03:52 hangout.archive.200504 -rw-r--r-- 1 mdom mdom 16584 2009-12-22 06:42 hangout.config -rw-r--r-- 1 mdom mdom 16570 2005-05-19 03:52 hangout-digest.config -rw-r--r-- 1 mdom mdom 5 2005-05-19 03:52 hangout-digest.config.LOCK -rw-r--r-- 1 mdom mdom 5534 2008-04-19 14:36 hangout.intro -rw-r--r-- 1 mdom mdom 2303 2005-08-28 11:59 mikanrecro -rw-r--r-- 1 mdom mdom 17392 2005-07-17 06:21 mikanrecro.admin -rw-r--r-- 1 mdom mdom 16644 2005-07-25 19:37 mikanrecro.config -rw-r--r-- 1 mdom mdom 59 2008-02-15 09:09 natureny -rw-r--r-- 1 mdom mdom 17389 2008-02-15 09:07 natureny.admin -rw-r--r-- 1 mdom mdom 16551 2008-02-15 09:09 natureny.config -rw-r--r-- 1 mdom mdom 40 2007-12-17 13:26 pharmacy -rw-r--r-- 1 mdom mdom 17392 2007-12-17 13:26 pharmacy.admin -rw-r--r-- 1 mdom mdom 16703 2007-12-17 13:34 pharmacy.config I can use some advise on how to fix this ... Ruben From majordomo-users-owner@greatcircle.com Tue Jan 26 13:21:33 2010 X-Greylist: delayed 163 seconds by postgrey-1.24 at mycroft; Tue, 26 Jan 2010 13:21:32 PST Received: from m1.cnet.wnec.edu (m1.cnet.wnec.edu [205.246.4.21]) by mycroft.greatcircle.com (Postfix) with ESMTP id F1FE969005A for ; Tue, 26 Jan 2010 13:21:32 -0800 (PST) Received: from m1.cnet.wnec.edu (localhost [127.0.0.1]) by m1.cnet.wnec.edu (8.14.2/8.14.2) with ESMTP id o0QLIrd4003014 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 26 Jan 2010 16:18:53 -0500 Received: (from pszaban@localhost) by m1.cnet.wnec.edu (8.14.2/8.14.2/Submit) id o0QLIrrE003006 for Majordomo-Users@GreatCircle.COM; Tue, 26 Jan 2010 16:18:53 -0500 Date: Tue, 26 Jan 2010 16:18:53 -0500 From: Peter Szaban To: Majordomo-Users@GreatCircle.COM Subject: majordomo postfix - status=deferred (temporary failure) Message-ID: <20100126211853.GB13557@m1.cnet.wnec.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="neYutvxvOLaeuPCA" Content-Disposition: inline X-PGP-Key: http://homepage.wnec.edu/~pszaban/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: clamav-milter 0.95.3 at m1 X-Virus-Status: Clean X-Archive-Number: 201001/7 X-Sequence-Number: 5912 --neYutvxvOLaeuPCA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Ruben, You *MAY* be experiencing the same thing that happened to us when we upgraded to SuSE11.2. We're using sendmail instead of postfix, but were seeing error messages in logfiles similar to: $* is no longer supported at /usr/local/lib/majordomo/digest line xxx $* is no longer supported at /usr/local/lib/majordomo/majordomo.pl line= xxx My understanding is that the majordomo.pl Perl script was written in "old-style" Perl, using the deprecated function "$*". SuSE11.2 includes Pe= rl 5.10, which no longer supports "$*". Note that I never tried using the version of Majordomo that comes with OpenSuSE 11.2. You might want to give the OpenSuSE supplied .rpm a whirl; = they may have already fixed this problem. Someone else did a better job explaining how they got around the issue than I ever could. They even created a patch for majordomo.pl. See: http://www.mail-archive.com/misc@openbsd.org/msg69481.html Date: Fri, 22 Jan 2010 01:09:50 -0500 =46rom: Ruben Safir To: Majordomo-Users@GreatCircle.COM Subject: majordomo postfix - status=3Ddeferred (temporary failure) Message-ID: <4B59412E.8010105@mrbrklyn.com> Hello I have this puzzle that I can't figure out. I had my mailing list working on openSuSE 11.2 with postfix and majordomo. I've been using majordomo on sendmailf or years with no trouble. I moved to postfix with no trouble and now, suddenly I'm getting nothing through to my lists. Everything says status=3Ddeferred(temporary failure). I have no idea what is happening. I've done a shake out with post fix and it seems to be relaying through the aliases fine. So, I think I might have somehow messed up my majordomo set up, but I can't find anything for the life of me. --neYutvxvOLaeuPCA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iD8DBQFLX1w9Wevpz4y9CYsRAljIAJ0SSmygXovmGKMkwcBw/enZ0ha/EACeKrIu Q0kbK3ksCNzS1PQ2S9Zr7IM= =6QMC -----END PGP SIGNATURE----- --neYutvxvOLaeuPCA--