Great Circle Associates Majordomo-Workers
(May 1998)
 

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

Subject: Re: Problem with Majordomo 2.0 installation
From: rms39 @ columbia . edu (Russell Steinthal)
Date: Fri, 08 May 1998 00:49:17 -0300
To: majordomo-workers @ greatcircle . com
Cc: Jason L Tibbitts III <tibbs @ hpc . uh . edu>
In-reply-to: Your message of "07 May 1998 23:27:27 CDT." <ufa4sz19ykw.fsf@sina.hpc.uh.edu>

We now join an exchange between Jason and myself already in progress, the 
earlier bug report due to emerge from majordomo-worker's administrivia filters 
in a few days or so. :)

Jason wrote:

> It tried to talk to your mail server (probably localhost) and failed.
> Without full debugging info I can't say much more, as the debugging info
> includes the full SMTP trace.  The rest of the message is a backtrace; you
> experienced a catastrophic failure and the mail sending function aborted.
> 
> You might like to try a run with debugging, and also telnet localhost 25
> and fake an SMTP transaction if you know how to do this.

Here's what I assume is the relevant portion of the debugging output 
(everything to this point succeeds):

[2256].........Mj::MailOut::mail_message: /f15/majordomo/tmp/mj-tmp.2256.AAB, 
rms39@columbia.edu
[2256]..........Mj::Deliver::Envelope::new: localhost
[2256]...........Mj::Deliver::SMTP::getresp
[2256]............<<<220 eagle.avnet.org ESMTP
[2256]...........Mj::Deliver::SMTP::getresp..done, took 0.07 sec
[2256]...........>>>HELO eagle.avnet.org
[2256]...........Mj::Deliver::SMTP::getresp
[2256]............<<<250-eagle.avnet.org
--== Timed out getting response? at /f15/majordomo/lib/Mj/Deliver/SMTP.pm line 
119, <GEN20> chunk 2.
[2256]...........Mj::Deliver::SMTP::getresp..done, took 60.00 sec
[2256]..........Mj::Deliver::Envelope::new..done, took 60.19 sec
[2256]..........Failed to build envelope for mailing.
[2256].........Mj::MailOut::mail_message..done, took 60.26 sec
[2256]........Mj::MailOut::mail_entity..done, took 60.74 sec
[2256].......Mj::Token::confirm..done, took 61.44 sec
[2256]......Mj::Access::_d_subscribe..done, took 62.54 sec
[2256].....Mj::Access::_a_default..done, took 62.56 sec
[2256]....Mj::Access::list_access_check..done, took 62.75 sec
[2256]...Majordomo::subscribe..done, took 62.97 sec
[2256]..Majordomo::dispatch..done, took 62.99 sec
[2256].Mj::TextOutput::subscribe..done, took 63.01 sec

I can forge mail to the SMTP port without a problem (other than being a bit 
rusty on SMTP syntax).

System information for the host in question: Solaris 2.5.1, qmail 1.01, Perl 
5.004_04, running on a Sparc 20.

If you need more of the debugging output than I included above, let me know; I 
didn't think it was worth burdening the list with a string of success returns.

-Russell



-- 
Russell Steinthal
<rms39@columbia.edu>		Columbia College Class of 1999
<steintr@avnet.org>		System Administrator, AV-Network





Follow-Ups:
Indexed By Date Previous: Independent Price Survey of 175 Life Insurance Companies
From: majordomo-workers-owner@GreatCircle.COM
Next: Re: Single-command addresses
From: Norbert Bollow <bollow@math.ethz.ch>
Indexed By Thread Previous: Independent Price Survey of 175 Life Insurance Companies
From: majordomo-workers-owner@GreatCircle.COM
Next: Re: Problem with Majordomo 2.0 installation
From: Jason L Tibbitts III <tibbs@hpc.uh.edu>

Google
 
Search Internet Search www.greatcircle.com