Paul Phillips said:
> rouilj> Do you have an example bounce message that you are receiving.
>
> Sample bounce message:
> >>>
> Date: Tue, 24 May 1994 12:15:39 -0700
> From: owner-sample@is.internic.net
> To: owner-sample@is.internic.net
> Subject: BOUNCE sample@is.internic.net: Approval required
This subject line indicated that the list is being
moderated. Somewhere you have set moderate to yes, or have provided an
opt_a flag.
=== This is where your approved header line should go
> >From owner-sample Tue May 24 12:15:37 1994
> Received: (from paulp@localhost) by is.internic.net (8.6.8/8.6.6) id
> MAA04456;
> Tue, 24 May 1994 12:15:37 -0700
> Date: Tue, 24 May 1994 12:15:37 -0700 (PDT)
> From: Paul Phillips <paulp@is.internic.net>
> Subject: New release
> To: sample@is.internic.net
> Message-ID: <Pine.3.89.9405241222.A4265-0100000@is.internic.net>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
{{{{ Do not put the approved header line here }}}}
>
> Announcement... etc, etc, etc.
> Sending this back to the list with an "Approved" line first does send it
> out, but the new message has no subject and other problems that seem to
> be due to the header (everyone from the same domain appears on the To:
> line, for example.)
> rouilj> bounced. Is the list moderated? Are you using the
> rouilj> approve(1) command to approve the bounced messages, or are
> rouilj> you doing it by hand. If you are doing it by hand, are you
> rouilj> keeping all of the original headers that are encapsulated in
> rouilj> the bounce message?
>
> I was doing the approval by hand, at the bottom of the enclosed bounced
> message header.
Check the example above. I this looks like you problem, the approved
header MUST come before the headers encapsulated in the message
otherwise all of those headers will be lost.
> In case the problem lies here, the /etc/aliases section looks like this:
> sample: "|/infoguide/majordomo-1.90/wrapper resend -l sample -h
> is.internic.net -s sample-outgoing"
> sample-digest: sample
> owner-sample-outgoing: owner-sample
> sample-outgoing: :include:/infoguide/majordomo-1.90/lists/sample,
> "|/infoguide/majordomo-1.90/wrapper digest -r -C -l sample-digest sample-digest-outgoing"
>
Don't use -s on the command line for resend in the aliases file. As
documented int he README, the only flags that should be used when
using resend with majordomo are -l and -h. See below for more info.
> It appears that certain aspects of the list can be controlled with
> command line options to resend as well as in the config file (for
> example, moderated = yes vs. -A.) Is this because the software is
> evolving and/or is there a preferred way to control these?
Resend is meant to be used with or without the rest of majordomo. If
used WITHOUT majordomo you would use the command line flags.
If used with majordomo, ONLY the -h <hostname> and -l <listname>
flags should be used, otherwise the defaults listed in the
configuration file may not be correct leading to confusion.
Just a note, I think I broke the ability to use resend without
majordomo in the 1.90 release. I will fix it for 1.91.
-- John
John Rouillard
Senior Systems Consultant (SERL Project) University of Massachusetts at Boston
rouilj@cs.umb.edu (preferred) Boston, MA, (617) 287-6480
==============================================================================
My employers don't acknowledge my existence much less my opinions.
|
|
