Aloha Ken,
I ran it manually. However, the issue still persists.
-Rashid
At 09:45 AM 10/6/2006, you wrote:
>From: "Abdul-Rashid Abdullah" <webmaster (at mark) muntada.com>
>
>>Aloha,
>>
>>It seems sometime yesterday majordomo flat broke on me. Here is the
>>situation. Let's say I have a mailing list of family (at mark) muntada.com. I get an
>>undelivered message to the moderator address for the list when I send to it
>>from any address (I used gmail in my example below):
>>
>>The original message was received at Fri, 6 Oct 2006 08:59:24 -1000
>>from mail@localhost
>>
>> ----- The following addresses had permanent fatal errors -----
>>165-family-list
>> (reason: 550 5.1.1 <165-family-list (at mark) baraka.muntadanet.com>... User
>>unknown)
>> (expanded from: 165-family-list)
>>nobody
>> (reason: 550 5.1.1 <nobody (at mark) baraka.muntadanet.com>... User unknown)
>> (expanded from: nobody)
>>
>> ----- Transcript of session follows -----
>>... while talking to [127.0.0.1]:
>>>>>DATA
>><<< 550 5.1.1 <nobody (at mark) baraka.muntadanet.com>... User unknown
>>550 5.1.1 nobody... User unknown
>><<< 550 5.1.1 <165-family-list (at mark) baraka.muntadanet.com>... User unknown
>>550 5.1.1 165-family-list... User unknown
>><<< 503 5.0.0 Need RCPT (recipient)
>>
>>Reporting-MTA: dns; baraka.muntadanet.com
>>Arrival-Date: Fri, 6 Oct 2006 08:59:24 -1000
>>
>>Final-Recipient: RFC822; 165-family-list (at mark) baraka.muntadanet.com
>>Action: failed
>>Status: 5.1.1
>>Remote-MTA: DNS; [127.0.0.1]
>>Diagnostic-Code: SMTP; 550 5.1.1 <165-family-list (at mark) baraka.muntadanet.com>...
>>User unknown
>>Last-Attempt-Date: Fri, 6 Oct 2006 08:59:24 -1000
>>
>>Final-Recipient: RFC822; nobody (at mark) baraka.muntadanet.com
>>Action: failed
>>Status: 5.1.1
>>Remote-MTA: DNS; [127.0.0.1]
>>Diagnostic-Code: SMTP; 550 5.1.1 <nobody (at mark) baraka.muntadanet.com>... User
>>unknown
>>Last-Attempt-Date: Fri, 6 Oct 2006 08:59:24 -1000
>>
>>Return-Path: <owner-family (at mark) www.muntada.com>
>>Received: (from mail@localhost)
>> by baraka.muntadanet.com (8.13.1/8.13.1/Submit) id k96IxOWD008999;
>> Fri, 6 Oct 2006 08:59:24 -1000
>>X-Authentication-Warning: baraka.muntadanet.com: mail set sender to
>>owner-family (at mark) www.muntada.com using -f
>>Received: from py-out-1112.google.com (py-out-1112.google.com
>>[64.233.166.176])
>> by baraka.muntadanet.com (8.13.1/8.13.1) with ESMTP id k96IxNrA008995
>> for <family (at mark) muntada.com>; Fri, 6 Oct 2006 08:59:23 -1000
>>Received: by py-out-1112.google.com with SMTP id i49so1063152pyi
>> for <family (at mark) muntada.com>; Fri, 06 Oct 2006 11:59:19 -0700 (PDT)
>>DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
>> s=beta; d=gmail.com;
>>
>>h=received:message-id:date:from:to:subject:mime-version:content-type;
>>
>>b=oDrKQL86bZ3mTxUHQTIRsMr+mFe8L4axQOHpaxQMcuB/5Cs5YYlIEZN0GiG+AyzClrkph/HbAj
>>L2/iqqG4DiagIiqKYPRWWRccuGC0VmkpLHM0hmVLaBjatESkExMSKFOok79Hc6dcij1w+uUBgJsa
>>mY8g5Q2glYieUGS4VpGOM=
>>Received: by 10.64.184.14 with SMTP id h14mr4836574qbf;
>> Fri, 06 Oct 2006 11:59:19 -0700 (PDT)
>>Received: by 10.64.243.1 with HTTP; Fri, 6 Oct 2006 11:59:18 -0700 (PDT)
>>Message-ID: <a082d83f0610061159lb586983n259f0fed504cb314 (at mark) mail.gmail.com>
>>Date: Fri, 6 Oct 2006 08:59:18 -1000
>>From: "Abdul Rashid Abdullah" <abdulrashid.abdullah (at mark) gmail.com>
>>To: family (at mark) muntada.com
>>Subject: [family] Test 3
>>MIME-Version: 1.0
>>Content-Type: multipart/alternative;
>> boundary="----=_Part_8863_7312776.1160161158997"
>>Sender: owner-family (at mark) www.muntada.com
>>Precedence: bulk
>>Reply-To: "Abdul Rashid Abdullah" <abdulrashid.abdullah (at mark) gmail.com>
>>X-Majordomo-Version: 1.94.4
>>
>>
>>When I look at the file list under
>>/usr/local/majordomo/sites/site87/lists/family
>>I have all the accounts listed. Then I look at the aliases.majordomo file
>>in /etc/mail. That is what I find strange:
>>
>>1592-alert: "|/usr/local/majordomo/wrapper resend -l alert -r
>>alert (at mark) www.hawaiifamilyforum.org -C
>>/usr/local/majordomo/sites/site25/majordomo.cf 1592-alert-list, nobody"
>>165-family-approval: muntada
>>165-family-request: "|/usr/local/majordomo/wrapper request-answer
>>family"
>>owner-165-family: muntada
>>165-family: "|/usr/local/majordomo/wrapper resend -l family -C
>>/usr/local/majordomo/sites/site87/majordomo.cf 165-family-list, nobody"
>>165-family-list:
>>:include:/usr/local/majordomo/sites/site87/lists/family, 165-family-archival
>>165-family-archival: /dev/null
>>165-family-owner: muntada
>>
>>I want to emphasize that I found all the lists looking like this. Any
>>ideas?
>>
>>-Rashid
>
>You might try this:
>http://www.blue-quartz.com/majordomo/
>http://www.blue-quartz.com/majordomo/fix_majordomo.tar.gz
>
>
>
>
>----
>Ken Marcus
>Precision Web Hosting, Inc.
>http://www.precisionweb.net
>
>
>
*****************************************************************
MuntadaNet Web Hosting and Web Design Services
http://www.muntada.com
Sales - sales (at mark) muntada.com
Support - support (at mark) muntada.com
Billing - billing (at mark) muntada.com
Main Office - 808-689-6092
Fax - (808) 356-0279
*****************************************************************