Out of town for the weekend, thus the delay...
On Sat, 21 May 1994, John P. Rouillard wrote:
> You haven't given us a heck of a lot to go on.
>
> 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
>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
Announcement... etc, etc, etc.
-PSP
>>>
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.)
The driving force behind fixing this is that the many subscribers of the
list are rather irked to have lost their subject headers. Any quick fix
that would return that would give me some time to figure out the rest,
but it appears that it's all codependent.
> The subject line of the bounced message says why it is being
> bounced. Is the list moderated? Are you using the approve(1) command
> to approve the bounced messages, or are you doing it by hand. If you
> are doing it by hand, are you keeping all of the original headers that
> are encapsulated in the bounce message?
The subject line just says "Approval required" which according to the
docs (?) should do:
The requests for approval that Majordomo generates all start with
"APPROVE" in the "Subject:" line.
I was doing the approval by hand, at the bottom of the enclosed bounced
message header.
In case the problem lies here, the /etc/aliases section looks like this:
>>>
owner-sample: paulp@is.internic.net
sample-approval: paulp@is.internic.net
owner-sample-digest: owner-sample
sample-digest-approval: sample-approval
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"
owner-sample-digest-outgoing: owner-sample
sample-digest-outgoing:
:include:/infoguide/majordomo-1.90/lists/sample-digest
owner-sample-request: owner-sample
sample-request: "|/infoguide/majordomo-1.90/wrapper majordomo -l sample"
owner-sample-digest-request: sample-digest-owner
sample-digest-request: "|/infoguide/majordomo-1.90/wrapper majordomo -l
sample-digest"
>>>
I do apologize if this is easy stuff, but I have no experience with
mailing lists, and the obvious may be non-obvious to me right now.
---
Paul Phillips | EMAIL: paulp@is.internic.net |
InterNIC Information Services | WWW: http://www.internic.net/~paulp/ |
InfoGuide Administrator | PHONE: 619-455-4626 FAX: 619-455-4640 |
References:
|
|
