On Tue, 22 Jan 2002 15:27:53 -0600, "Gladish, Christopher W."
<[log in to unmask]> wrote:

>IA0KDQoJDQoJRnJvbTogQ2FsdmluLCBDaGFybGVzIEQuIFttYWlsdG86Q0NhbHZpbkBmYWVncmUu
>Y29tXSANCgkNCglJIGZpbmQgdGhpcyBkZWNpc2lvbiB0cm91YmxpbmcgZnJvbSBhIHByb2NlZHVy
>YWwgc3RhbmRwb2ludCwgaWYgaXQncyB0cnVlDQoJdGhhdCB0aGUgbGltaXRlZCBwYXJ0bmVycyBh
>cmUgcHJlY2x1ZGVkIGZyb20gcmVsaXRpZ2F0aW5nIGlzc3VlcyBkZWNpZGVkIGluDQoJYW4gYWN0

This is Base64 encoding.  It is used in email in a number of circumstances.
Conor suggested an encrypted or digitally signed message.  This is possible.
Also possible is simply a special character set (e.g. a document copied from
Word).   In any event the issue is related to the originator/author of the
message (probably some settings set incorrectly in their email program).  It
is not a problem caused by LISTSERV.