Great Circle Associates Majordomo-Workers
(August 1998)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Two MJ2 questions
From: "William R. Dickson" <wrd @ awenet . com>
Date: Fri, 14 Aug 1998 10:15:21 -0700 (PDT)
To: Jason L Tibbitts III <tibbs @ hpc . uh . edu>
Cc: majordomo-workers @ greatcircle . com
In-reply-to: <ufau33fo608.fsf@sina.hpc.uh.edu>

On 14 Aug 1998, Jason L Tibbitts III wrote:

> >>>>> "WRD" == William R Dickson <wrd@awenet.com> writes:
> 
> WRD> I _am_ left with one final problem, and have scoured the documentation
> WRD> but can't find any reason for it.  Namely, mj_email fails and I get an
> WRD> "unknown mailer 255" error when mail is sent to
> WRD> majordomo-owner. listname-owner addresses work just fine.
> 
> First, check the debug logs or do something like
> 
> echo "hello" | mail -v majordomo-owner

The mail -v results in the following:

[Awenet]:/usr/users/wrd> echo "hello" | mail -v majordomo-owner
majordomo-owner... aliased to "|/usr/local/libexec/majordomo/bin/mj_email
-o -d awenet.com"
"|/usr/local/libexec/majordomo/bin/mj_email -o -d awenet.com"...
Connecting to prog...
"|/usr/local/libexec/majordomo/bin/mj_email -o -d awenet.com"... unknown
mailer error 255
/usr/users/wrd/.forward: line 1: forwarding to wrd@awenet.com
/usr/users/wrd/dead.letter... Saved message in /usr/users/wrd/dead.letter

The debug log for that session contains:

[29630]Majordomo Email client - Fri Aug 14 10:02:51 1998
[29630].Compilation took 14.94s, 5.48u
[29630].Majordomo::new: /usr/local/libexec/majordomo/lists, awenet.com
[29630].Majordomo::new..done, took 1.50 sec
[29630].Majordomo::connect: owner
[29630].Majordomo::connect..done, took 0.46 sec
[29630].Majordomo::dispatch: owner_start
[29630]..Mj::MailOut::owner_start: GLOBAL
[29630]..Mj::MailOut::owner_start..done, took 0.23 sec
[29630].Majordomo::dispatch..done, took 0.54 sec
[29630].Majordomo::dispatch: owner_done
[29630]..Mj::MailOut::owner_done: GLOBAL
--== Use of uninitialized value at
/usr/local/libexec/majordomo/lib/auto/Mj/Mail
Out/mail_message.al line 10, <STDIN> chunk 10.
[29630]...Mj::MailOut::mail_message:
/usr/local/libexec/majordomo/tmp/post.29630.AAA, 
[29630].....Sending unaddressed envelope
Sending unaddressed envelope at /usr/local/libexec/majordomo/lib/Mj/Log.pm
line 
378
        Log::In::abort('Log::In=HASH(0x56dc58)', 'Sending unaddressed
envelope')
 called at /usr/local/libexec/majordomo/lib/Mj/Deliver/Envelope.pm line
201

Mj::Deliver::Envelope::send('Mj::Deliver::Envelope=HASH(0x2cac88)') call
ed at /usr/local/libexec/majordomo/lib/auto/Mj/MailOut/mail_message.al
line 21
        Mj::MailOut::mail_message('Majordomo=HASH(0x54b388)',
'majordomo-owner@a
wenet.com', '/usr/local/libexec/majordomo/tmp/post.29630.AAA') called at
/usr/local/libexec/majordomo/lib/auto/Mj/MailOut/owner_done.al line 19
        Mj::MailOut::owner_done('Majordomo=HASH(0x54b388)', '', '', '',
'owner', '(message to GLOBAL-owner)', '', 'GLOBAL', ...) called at
/usr/local/libexec/majordomo/lib/Majordomo.pm line 323
        Majordomo::dispatch('Majordomo=HASH(0x54b388)', 'owner_done', '',
'', '', 'owner', '(message to GLOBAL-owner)', '', ...) called at
/usr/local/libexec/majordomo/bin/.mj_email line 188
        main::forward_to_owner('Majordomo=HASH(0x54b388)', 'GLOBAL')
called at /usr/local/libexec/majordomo/bin/.mj_email line 149
[29630]...Mj::MailOut::mail_message..done, took 3.07 sec
[29630]..Mj::MailOut::owner_done..done, took 3.16 sec
[29630].Majordomo::dispatch..done, took 3.25 sec

(I apologize for the wrapping; pine may not be the best choice for sending
things like this)

> My guess is that I've hosed something with owner processing or that the
> 'owners' variable for GLOBAL did not properly get set (which should not
> happen, really, since postinstall should to a createlist GLOBAL which sets
> that variable).  Current sources run OK on my setup (which runs the latest
> snapshot).

configset GLOBAL owners << ENDAAI
ENDAAI

...is what I see in configedit GLOBAL.  I'll try putting my email address
in there and see if it makes a difference.  (Same problem occurred on this
setup at home (NetBSD 1.3.2) and my setup at work (Digital Unix, not sure
of version offhand).  Both setups using perl 5.004.04.

> WRD> This problem appears to cause the failure of token approvals.
> 
> Are you sure it isn't just the notification message that's failing?  In any
> case, things haven't adequately recovered from the big owner change and
> there are bound to be bugs there.

Well, no, I'm not sure...I do know both are failing, but I guess I can't
say the owner problem is causing the other failure.  I'll make that change
and see what happens.

-Bill

-- 
 William R. Dickson -- Consuming the Earth's limited resources since 1968
 wrd@awenet.com  <>  http://www.awenet.com/~wrd/  <>  VNB3T, VSC1T, VSX1T

                   "Give 'em hell, Pike!"

                                            - Dutch, _The Wild Bunch_




Follow-Ups:
References:
Indexed By Date Previous: Re: majordomo2 accounting?
From: "William R. Dickson -- System Administration" <wdickson@nwnexus.net>
Next: Re: Two MJ2 questions
From: "William R. Dickson" <wrd@awenet.com>
Indexed By Thread Previous: Re: Two MJ2 questions
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>
Next: Re: Two MJ2 questions
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>

Google
 
Search Internet Search www.greatcircle.com