>>>>YC
>>>>YC I'm a new user of majordomo-1.94.3. We put it on an AIX 4.0 machine.
>>>>YC It worked pretty well for the first couple of days. But just a few
>>>>YC days ago we noticed that our list owner was getting tons of mails
>>>>YC reading:
>>>>YC ----------
>>>>YC To: majordom
>>>>YC --- The transcript of the session follows ---
>>>>YC --- The unsent message follows ---
>>>>YC Received: by snowball.nctr.fda.gov (AIX 4.1/UCB 5.64/4.03)
>>>>YC id AA23818; Mon, 15 Sep 1997 09:16:36 -0500
>>>>YC Date: Mon, 15 Sep 1997 09:16:36 -0500
>>>>YC Message-Id: <9709151416.AA23818@listserv.nctr.fda.gov>
>>>>YC To: majordomo@snowball.nctr.fda.gov
>>>>YC From: majordomo@snowball.nctr.fda.gov
>>>>YC Subject: MAJORDOMO ABORT (mj_majordomo)
>>>>YC Reply-To: majordomo@snowball.nctr.fda.gov
>>>>YC --
>>>>YC MAJORDOMO ABORT (mj_majordomo)!!
>>>>YC majordomo@snowball.nctr.fda.gov punting to avoid mail loop.
-------------
What are your list.config parameters "Reply_to" an "sender" set to?
Try:
Reply_to = $SENDER
sender = owner-list
I had a simular problem and used the above settings and now get
diagnostics, like "headers to long > 1024".
"sender" is a required parameter with mj 1.94.3, I think, but if you
leave it undefined things go to never-never-where-ever.
I asked majordom-users for help as UNCLE? but got no response.
======================================================
Robert E. Davis Sandia National Laboratories Org-04911
E-mail Team and MajorDomo Distribution Lists
redavis@sandia.gov (505)844-6817 FAX(505)844-8335
======================================================
|
|
