Hello Ian,
> No other help on this issue? There's no way for Majordomo to bounce
> a file attachment
> as a file attachment instead of just included MIME-encoded text?
That's right. Majordomo knows nothing at all about MIME. When
Majordomo bounces a message, the bounce is a plain non-MIME message
that contains the original message (headers plus body) as the body part
of the bounce notification. The fact that the original's MIME headers
are now part of the bounce body means that the content is no longer
recognisable as a MIME message.
However, if you're careful about the way you approve the message then
it's perfectly possible to reinstate the MIME-ness of the message by
arranging for the original MIME headers to be restored by Majordomo
when it distributes the approved message to the list. All of the
original parts will then be recognised by MIME-aware mail readers.
When the bounce arrives in your mailbox its body will look something
like this:
Received: from mailhub.example.com (mailhub.example.com [842.154.333.21])
by trantor.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA07551;
Sat, 15 Jul 2000 08:15:05 -0700 (PDT)
Received: from Beispiel (ppp15-global4.example.com [213.627.19.266])
by mailhub.example.com (8.9.3/8.9.3) with SMTP id RAA15220;
Sat, 15 Jul 2000 17:15:03 +0200 (CEST)
Message-ID: <0022bfee6f$50b080$0fc3d5@beispiel>
From: A Subscriber <a.subscriber@example.com>
To: "your list" <your-list@sun.com>
Subject: A message with an HTML attachment
Date: Sat, 15 Jul 2000 17:13:18 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_001C_01BFEE7F.F88CD660"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Length: 2591
This is a multi-part message in MIME format.
------=_NextPart_000_001C_01BFEE7F.F88CD660
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello everybody.
------=_NextPart_000_001C_01BFEE7F.F88CD660
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
</HEAD>
<BODY>
Hello everybody.
</BODY></HTML>
------=_NextPart_000_001C_01BFEE7F.F88CD660--
All you have to do is to place your 'Approved:' header on top of the
original headers and send the entire bounce body, including the
message's original headers, back to to Majordomo. I'd also remove the
'Content-Length:' header line from the original headers, in case the
message has picked up an extra blank line or other whitespace that
might render the old content-length incorrect and confuse some MTA's or
mail clients. Don't change any of the original message body.
If Majordomo sees an 'Approved:' header as the first line of the body
of a message then it uses the following lines, up to the next blank
line, as the headers of the outgoing message. So if you add your
'Approved:' header and password and send this as the body
of the approval message to Majordomo:
Approved: Your-Approval-Password
Received: from mailhub.example.com (mailhub.example.com [842.154.333.21])
by trantor.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA07551;
Sat, 15 Jul 2000 08:15:05 -0700 (PDT)
Received: from Beispiel (ppp15-global4.example.com [213.627.19.266])
by mailhub.example.com (8.9.3/8.9.3) with SMTP id RAA15220;
Sat, 15 Jul 2000 17:15:03 +0200 (CEST)
Message-ID: <0022bfee6f$50b080$0fc3d5@beispiel>
From: A Subscriber <a.subscriber@example.com>
To: "your list" <your-list@sun.com>
Subject: A message with an HTML attachment
Date: Sat, 15 Jul 2000 17:13:18 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_001C_01BFEE7F.F88CD660"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Content-Length: 2591
This is a multi-part message in MIME format.
------=_NextPart_000_001C_01BFEE7F.F88CD660
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello everybody.
------=_NextPart_000_001C_01BFEE7F.F88CD660
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
</HEAD>
<BODY>
Hello everybody.
</BODY></HTML>
------=_NextPart_000_001C_01BFEE7F.F88CD660--
then the end result is that original MIME headers will be recycled into
the message that gets distributed on the list and your subscribers will
see it as a MIME message.
One thing to watch out for is that, depending on how you create the
approval message from the bounce notification, your mail client might
insert quoting characters at the start of each line of the approval
message body. Obviously you need to remove those quoting characters
from the approval.
Good luck, Mike.
--
mike.oliver@eng.sun.com
|
|
