I looked through the RFC2257 document, and I don't think the listserv HTML digest complies.  As I said, the file doesn't work in my browser.  Looking at the raw html, I would expect to see some Content:ID and Content-Type: lines in the file.  There are none.  I can see nothing in the file that would tell anyone where to go to find the text that relates to the "cid:2847@lists.psu.edu" string.  Shall I include the raw html digest here so we can all see it?

>Eudora (like most mail clients; Pegasus is a notable exception) doesn't
>properly handle HTML digests.  You have to use MIME digests instead.
>
>If I'm not mistaken, this is a failure on the part of the client to handle
>MIME-encapsulated aggregate documents with imbedded Content-ID (cid:) URIs
>(see RFC2557 chapter 4.2).
>
>Nathan
>
>At 10:16 AM 5/9/2003 -0400, Bill Verity wrote:
>>I use Eudora to read my mail.  I subscribe to a list in Digest mode and
>>have SET HTML as an option.  None of the digest links work.  If I open the
>>mail in a browser, Mozilla, it looks a lot like our archive pages, but it
>>still doesn't work properly.  The links look like <a
>>href="cid:2847@LISTS.PSU.EDU">.
>>The list is on a 1.8d server.
>>

--
Why is "abbreviated" such a long word?
Why isn't "phonics" spelled the way it sounds?

Bill Verity - 814-865-4758  Fax: 814-863-7049
215A Computer Building - Information Technology Services, Penn State University
At the office - on my Mac, of course ;-)