A subscriber to my MOHICKOR list says he is getting the following type messages. I checked with the others on the list and no one else is having this problem. Does anyone have an answer? Thank you. Linda Crawford Part 1.1 Type: Plain Text (text/plain) Encoding: quoted-printable

Hi, Sure, the answer dates back to 1993 when the Internet Engineering Task Force (IETF) approved Request For Comments (RFC) 1521 titled: "MIME (Multipurpose Internet Mail Extensions Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies." More helpful to your technical staff would be for them to visit section 5.1 of the subject RFC, which is titled: "Quoted-Printable Content-Transfer-Encoding." It is a fairly lengthy description with lots of semantic syntax examples. I would need to see an example message to tell you specifically if there is an encoding error or not. Better still, I'm sure the staff at rootsweb would enjoy doing that. One thought is that if someone tries to send a binary file (e.g., a photograph) as a quoted-printable content transfer encoded message to the listserve the result will be a bombed message since the listserve does not handle photographs. So long as the encoding follows the RFC "quoted-printable" is a valid and often used transfer encoding. Jason Linda Crawford wrote: > A subscriber to my MOHICKOR list says he is getting the following type messages. I checked with the others on the list and no one else is having this problem. Does anyone have an answer? Thank you. Linda Crawford > > Part 1.1 Type: Plain Text (text/plain) > Encoding: quoted-printable > > ============================== > Create a FREE family website at MyFamily.com! > http://www.myfamily.com/banner.asp?ID=RWLIST2