Regarding the issue of listserve postings being uuencoded, I received the response below from the listserve folks.
-----Original Message-----
From: SPSSX(r) Discussion <
[hidden email]>
To:
[hidden email] <
[hidden email]>
Sent: Mon Sep 22 16:07:23 2008
Subject: [SPSSX-L] UTF-8 in digests/archives
We received a note a few days ago:
I have found that utf-8 encoded messages sent to the
_LISTNAME_ listserve are appearing uuencoded in
digests and the archives. Can this be fixed?
utf-8 is such a standard that it ought not to cause
a problem these days.
good point.
Eric Thomas (the Listserv guy) has sent this response:
If you are reading NOMIME digests, the only supported
message type is plain ASCII with no encoding. You have
to switch to MIME digests if you want to read anything
other than that.
Many mail clients default to non-text mail, and you have to check the options to find how this may be sent in any other form. For many, plain ASCII is old fashioned and not how they send mail.
this option may be toggled with the listserver commands:
set _LISTNAME_ mime
set _LISTNAME_ nomime
-- Joe Kelley
[hidden email]
ps Eric added in a subsequent post that some changes were planned for NOMIME that should allow this. This is for a future release.
=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD
Locked
