On Feb 19, 11:35pm, David Cornwell wrote:
}
} After investigation by both us and the ISP we have identified the fact that
} my copy of Outlook 97 (8.02.4212) is sending messages as a multi-part Mime
} message. The footer is being added as a base-64-encoded file (I have _no_
} idea what this means!). My simple understanding is that Majordomo appears
} to add the subject pre-fix and footer as another mime part which is
} automatically stripped out by Outlook.
[This is a total guess, with no real Outlook experience to back it up.]
Outlook/Exchange, unless otherwise configured, sends a duplicate
copy of its text-only mail as a "rich text" base64 attachment. I think
what is happening is that Majordomo produces the following based on
what you send in:
From: you
To: list
Subject: [prefix] subject
------ =_NextPart_000_01BD3D8F.54DF9B40
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
This is the body of the message being sent.
------ =_NextPart_000_01BD3D8F.54DF9B40
Content-Type: application/ms-tnef
Content-Transfer-Encoding: base64
Q0ZheIMPrYQROIYgHjR3iMAuI1DiYycQcmwubiGGZQWw3mcfkx
------ =_NextPart_000_01BD3D8F.54DF9B40--
[Majordomo attaches footer here.]
Since the "trailer" portion has no MIME type or body part
delineation, Outlook ignores it (ie, will not display it) when
read back. But it is still probably there.
This would explain the missing footer problem. As for the missing
subject prefix, the only thing I can think of is that maybe there
is a copy of the headers included in the main body part; Majordomo
will be modifying the Subject in the envelope but not the body
part, and Outlook will ignore the envelope Subject in deference
to the MIME body.
} Has anyone come across this and if so are there any solutions - a majordomo
} config issue perhaps.
Since it works for everyone but you w/Outlook, why would you think
it is a Majordomo config issue? This is clearly an Outlook/MIME
problem. Turn off your Rich Text. Stop sending MIME.
--bill
|
|
