Binary attachments such as images, documents, and executables must be encoded
by the sender's email client before the message is sent, to ensure that the
attachments do not become corrupted during transit. The encoding is done by
the sender's email client, not by LISTSERV. LISTSERV does not encode or decode
any attachments.

The material you included below the paragraph describing the problem appears
to have been extracted from the raw source of a multi-part MIME message. The
material contains two MIME boundaries and all or part of the content of each
MIME part.

The first MIME part contains a single line of unencoded 7-bit ASCII text.

        Language= Exchange, Attachments=All

The second MIME part appears to be the first few lines from an image file
which was encoded using the BASE64 encoding scheme.

It appears that you (or the sender of the message) sent a message to the list
address with the 'Language=' and 'Attachments=' keywords in the body of the
message, and an image attached to the message. These keyword statements must
appear on separate lines in the list header, not in the body of a message sent
to the list. Furthermode, the 'Attachments=' keyword does not support the
operand 'All'. The valid forms of the 'Attachments=' keyword are:

        Attachments= Yes
        Attachments= No
        Attachments= No,filter
        Attachments= [list of acceptable MIME types]

See <http://www.lsoft.com/manuals/1.8d/owner/appendb.html#keyAttachments> for
additional information about the 'Attachments=' keyword.

--
Paul Russell
Senior Systems Administrator
University of Notre Dame