The how-to I wrote for approving messages back in 2000 still applies
today. Mostly, the instructions just explain this section of the
list-owner-info file in a bit more detail. I was using the Netscape
mail client when I wrote the doc, but mozilla and thunderbird under
linux should still work. Honestly, unless you use this on a regular
basis, you can forget it pretty easily. I have not tried this in
evolution, but faintly recall this also working in pine, mutt, and
elm too.
Here we go;
First and formost, you MUST use plain text to author your message.
First and formost, you MUST use plain text to author your message.
First and formost, you MUST use plain text to author your message.
NO HTML!!!
The approval piece is identical, whether it needs approved due
to attachment, administrivia, or just a plain moderated list.
Preparation;
Mozilla based mail clients default to HTML message authoring, and
automatically wrapping lines longer than 72 characters. These features
need to be turned off. Use plain text and set line wrap to 255. Pine
does plain text and has long enough line wrap by default.
You also want to view all headers, so they are included in the body of
your message when you hit forward or reply. Without this, you might
also consider using ctrl-u to see the complete message with headers
and any attachments, then ctrl-a to select all and ctrl-c to copy the
selected text for pasting with ctrl-v into your approval message body.
Pine has ctrl-h for viewing headers with the message body.
Finally, an example (with comments)
Assume the bounced message you received is between the lines of @@@:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Received: (from mj1945@localhost) by example.com (8.8.8/8.8.8) id RAA21062; Thu, 14 Sep 2000 17:00:10 -0500 (CDT)
Date: Thu, 14 Sep 2000 17:00:10 -0500 (CDT)
From: owner-test@example.com
Message-ID: <200009142200.RAA21062@example.com>
To: list-approval@example.com
Subject: BOUNCE test@example.com: global taboo header: /^content-type:\s.*multi/i
>From owner-test Thu Sep 14 16:59:58 2000
Received: from netscape.com (h-205-217-228-106.netscape.com [205.217.228.106]) by example.com
(8.8.8/8.8.3) with ESMTP id QAA21048 for <test@example.com>; Thu, 14 Sep 2000 16:59:51 -0500 (CDT)
Message-ID: <39C14A49.71900C77@netscape.com>
Date: Thu, 14 Sep 2000 16:59:37 -0500
From: Dan Liston <myaddress@netscape.com>
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: test@example.com
Subject: attachments
Content-Type: multipart/mixed;
boundary="------------74FF034AC5DFC92E73DFBCF9"
This is a multi-part message in MIME format.
--------------74FF034AC5DFC92E73DFBCF9
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Approved: test.password
This is only a test to see if I can attach a file (smaller than 40k).
Dan
Forth try. Sending message to test@example.com now.
Fifth try. Removed taboo setting from majordomo.cf.
--------------74FF034AC5DFC92E73DFBCF9
Content-Type: application/x-zip-compressed;
name="somefile.zip"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="somefile.zip"
UEsDBBQAAgAIAGGqmSg9r8I9Ew4AACYyAAAIABUAQ09SRS5ORk9VVAkAA6XvBTml7wU5VXgE
[Snipped more of these kind of lines.....]
ICAgICAgICAgICAgICAgICAgICAgICAgICAgR2VuZXNpcyAtLy0gUE5UaVNPIC0vLSBCU2lT
Tw==
--------------74FF034AC5DFC92E73DFBCF9--
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
This is the text of the message body that you would send to your list;
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
Approved: test.password
>From owner-test Thu Sep 14 16:59:58 2000
Message-ID: <39C14A49.71900C77@netscape.com>
Date: Thu, 14 Sep 2000 16:59:37 -0500
From: Dan Liston <myaddress@netscape.com>
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: test@example.com
Subject: attachments
Content-Type: multipart/mixed;
boundary="------------74FF034AC5DFC92E73DFBCF9"
This is a multi-part message in MIME format.
--------------74FF034AC5DFC92E73DFBCF9
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
This is only a test to see if I can attach a file (smaller than 40k).
Dan
Forth try. Sending message to test@example.com now.
Fifth try. Removed taboo setting from majordomo.cf.
--------------74FF034AC5DFC92E73DFBCF9
Content-Type: application/x-zip-compressed;
name="somefile.zip"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="somefile.zip"
UEsDBBQAAgAIAGGqmSg9r8I9Ew4AACYyAAAIABUAQ09SRS5ORk9VVAkAA6XvBTml7wU5VXgE
[snipped all the compressed file information again]
ICAgICAgICAgICAgICAgICAgICAgICAgICAgR2VuZXNpcyAtLy0gUE5UaVNPIC0vLSBCU2lT
Tw==
--------------74FF034AC5DFC92E73DFBCF9--
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
Notice, when forwarding the message with the attachment back into the list address, I
made the "Approved: test.password" the first line, purged all Received: lines, removed
the blank line between boundry= and "This is a multi-", and I removed the old Approved:
line deeper down in the message so that the first line following the first blank space
was actually message content.
Dan Liston
Steve wrote:
> Hi;
>
> I run a majordomo list where a persistent disruptive individual had to
> be banned.
>
> Rather then moderating every post I used the taboo_body tag to bounce
> emails with certain phrases in it.
>
> This has been very effective. However about once every two weeks a
> mistake happens creating the need to "approve" a post. For various
> reasons having the server owner implement a perl script as suggested in
> the docs is not going to happen.
>
> I need to use an email client that will let me insert "From:" and other
> headers to make "approved" posts look as they would have looked if they
> did not bounce.
>
> Can anyone recommend such a client? My only requirement is that the
> client should run on at least gnu/linux. If it has a low learning
> curve that would be a bonus, but not a requirement.
>
> Thanks much in advance for any info.
>
> Steve
Follow-Ups:
References:
|
|
