Index: [Article Count Order] [Thread]

Date:  Tue, 09 Aug 2005 06:16:28 +0200
From:  Trond =?ISO-8859-1?Q?Hus=F8?= <tr-huso (at mark) online.no>
Subject:  [coba-e:02670] Re: majordomo error email
To:  coba-e (at mark) bluequartz.org
Message-Id:  <1123560988.3195.71.camel (at mark) evon160.safranmedia.com>
In-Reply-To:  <1123267566.18292.228.camel (at mark) fred.sf.pfinders.com>
References:  <1123267566.18292.228.camel (at mark) fred.sf.pfinders.com>
X-Mail-Count: 02670

Hi Herb/List

You can avoid it by doing this:
$admin_body = <<'END';
END

That part works perfectly on my end.


I do however get this message when I send to any list on our sites:

----- The following addresses had permanent fatal errors -----
bogusname
    (reason: 553 5.3.0 <bogusname (at mark) www.bogusdomain.com>... No such user
here)
    (expanded from: bogusname)

   ----- Transcript of session follows -----
... while talking to [127.0.0.1]:
>>> DATA
<<< 553 5.3.0 <bogusname (at mark) www.bogusdomain.com>... No such user here
550 5.1.1 bogusname... User unknown



-trond-




On Fri, 2005-08-05 at 11:46 -0700, Herb Rubin wrote:
> Hi,
> 
> I keep getting this emailed to me from majordomo:
> 
>   MAJORDOMO WARNING (mj_resend)!!
> 
>   resend:  $admin_body not defined in  
> /usr/local/majordomo/sites/site12/majordomo.cf !!
>   Majordomo will only catch "subscribe" and "unsubscribe" in
>   the body.
> 
> So, I looked in the file majordomo.cf and saw this:
> 
> # Disable body command detection for Cobalt Linux
> $admin_body = undef;
> 
> Can I avoid getting the emails with this:
> 
> $admin_body = "";
> 
> or is there a reason to have it undefined for Blue Quartz?
> 
> Herb
>