It doesn't seem to, for two reasons:
1) At least as majordomo is configured for my list, I am not getting an
approval "template". Even if it did,
2) The message as stripped by majordomo contains no MIME
version no., content-type, or content-transfer-encoding lines to inform
the subscriber's MUA that it should be converted back, once approved.
After considerable experimentation, I have been able to get the list to
work as it should, but only by sending the Approval line in the body of
the text as submitted, rather than in a two-step approval process. (I had
previously used the two-step process to check appearance before sending
the message to list subscribers.)
I observe that if a blank line after the approval line is OMITTED, the
entire message is thrown into QP-visible characters, the Subject line is
omitted, and the "outgoing" mail address appears in the "To" field.
On Thu, 31 Dec 1998, Jeffrey Kaplan wrote:
> When the message comes in for moderation, the headers that denote that
> the message is in QP are in the body of the message. The headers for
> the bounce (from Majordomo) are in us-ascii, thus the QP artifacts.
> When the message is approved and the Major generated "wrapping" bounce
> is stripped away (leaving just the original message and its headers),
> wouldn't the QP artifacts then be translated back to their respective
> characters, if the reader's mail client handles QP?
> Jeffrey Kaplan <*> I'm set up for PGP. Are you?
> SF in New England: www.world.std.com/~gordol/sfne/
> "I was so obsessed with fixing other peoples problems because I was afraid
> to face my own. I don't think I have that luxury anymore." (Dr. Franklin,
> B5 "Interludes and Examinations")
> On Wed, 30 Dec 1998, Mats Dufberg wrote:
> >> I manage a moderated majordomo list which frequently has the occasion to
> >> include Spanish or French texts -- in other words, ASCII characters above
> >> 128. When I send these texts to the list, I USUALLY (not always) get back
> >> quoted-printable characters where "=20" ends each line, "=E9" is an accented
> >> e (é), etc.
> >I would guess that you damage the header fields when you approve the
> >messages. A header field should be on one physical line OR on serveral
> >lines where each continuation line has to start with space or tab. Before
> >approving, break a long header fields and add space in begining of
> >continuation lines.
> >Correct header fields are necessary for correct interpretaion of codes in
> >MIME mail.