Re: Problem posting to listserve

Gary Handman (ghandman@library.berkeley.edu)
Fri, 8 Nov 2002 11:58:04 -0800 (PST)

--=====================_13654015==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

> Sorry I can't be more helpful, Rick. I do my best on the tech end of
> things, but at this level, it's really not in my control.

I think the work-around is to use a messaging product other than one
produced/supported by MicroSoft (if I read my systems department
correctly). Pine, Eudora, Webmail...etc. The problem really has nothing
to do with your service provider...

>Gary--
>
>With all due respect, your maven's answer to this problem was not helpful.
>The question is not "why does this happen?" The question is "How can we
>correct it?" I.e. the best solution would be to be able, on your end, to
>correct the problem. The second-best solution would be to give us, your
>list-serve subscribers, simple work-arounds to circumvent the problem. I am
>no software or internet guru, but from those "mavens" on your end, a few
>simple sentences like, "If you're on AOL..." or "if you get a message that
>originated on MS Word..." or whatever (from your maven's message below I have
>no idea where the problem originates-- what are "Microsoft mailers"-- are
>they part of the server, the word-processing software, what? is the problem
>in my email sending program or receiving program?), and then "here's what you
>can do as a workaround...." would be helpful.
>
>Thanks for your attention to this extremely annoying problem.
>
>Rick Goldsmith
>
>In a message dated 11/7/2002 5:23:54 PM Pacific Standard Time,
>ghandman@library.berkeley.edu writes:
>
>
> >
> > Hello all:
> >
> > I've continued to get perplexed and wistful messages from various
> > subscribers to the videolib and videonews lists regarding the receipt of
> > messages from the list that look like they're HTML encoded. I've asked
> UCB
> > Library's system mavens to explain--below is what they have to say. Blame
> > it on Bill Gates, I guess.
> >
> > Gary
> >
> >
> > >
> > >Gary -
> > >
> > > I think I responded to this once before, but I'd forgotten the
> > >answer as well, so here goes.
> > >
> > > Microsoft mailers by default send all emails as multipart, with
> > >the first part being MS-DOS text and the second part being HTML. Listproc
> > >doesn't handle multipart messages well, specifically, it doesn't copy the
> > >headers identifying the email as multipart, or specifying the content type
> > >of the parts, correctly. The result is that the receiving mail client
> > >assumes that the email it is receiving is a single part, plain text
> > >message (note that it cannot even do the conversion from MS-DOS text to
> > >Unix text) and displays it accordingly.
> > >
> > > With some digging, I understand that it is possible to stop
> > >Microsoft products from making all messages multi-part. That is about the
> > >only thing that will help, apart from changing list server software.
> >
> > Gary Handman
> > Director
> > Media Resources Center
> > Moffitt Library
> > UC Berkeley
> > ghandman@library.berkeley.edu
> > http://www.lib.berkeley.edu/MRC
> >
>
>
>
>--part1_23.2737d5a8.2afd5f63_boundary
>Content-Type: text/html; charset="US-ASCII"
>Content-Transfer-Encoding: 7bit
>
>Gary--
>
>With all due respect, your maven's answer to this problem was not
>helpful. The question is not "why does this happen?" The question is
>"How can we correct it?" I.e. the best solution would be to be able, on
>your end, to correct the problem. The second-best solution would be to
>give us, your list-serve subscribers, simple work-arounds to circumvent
>the problem. I am no software or internet guru, but from those "mavens"
>on your end, a few simple sentences like, "If you're on AOL..." or "if you
>get a message that originated on MS Word..." or whatever (from your
>maven's message below I have no idea where the problem originates-- what
>are "Microsoft mailers"-- are they part of the server, the word-processing
>software, what? is the problem in my email sending program or receiving
>program?), and then "here's what you can do as a workaround...." would be
>helpful.
>
>Thanks for your attention to this extremely annoying problem.
>
>Rick Goldsmith
>
>In a message dated 11/7/2002 5:23:54 PM Pacific Standard Time,
>ghandman@library.berkeley.edu writes:
>
>
>>
>>Hello all:
>>
>>I've continued to get perplexed and wistful messages from various
>>subscribers to the videolib and videonews lists regarding the receipt of
>>messages from the list that look like they're HTML encoded. I've asked UCB
>>Library's system mavens to explain--below is what they have to say. Blame
>>it on Bill Gates, I guess.
>>
>>Gary
>>
>>
>> >
>> >Gary -
>> >
>> > I think I responded to this once before, but I'd forgotten the
>> >answer as well, so here goes.
>> >
>> > Microsoft mailers by default send all emails as multipart, with
>> >the first part being MS-DOS text and the second part being HTML. Listproc
>> >doesn't handle multipart messages well, specifically, it doesn't copy the
>> >headers identifying the email as multipart, or specifying the content type
>> >of the parts, correctly. The result is that the receiving mail client
>> >assumes that the email it is receiving is a single part, plain text
>> >message (note that it cannot even do the conversion from MS-DOS text to
>> >Unix text) and displays it accordingly.
>> >
>> > With some digging, I understand that it is possible to stop
>> >Microsoft products from making all messages multi-part. That is about the
>> >only thing that will help, apart from changing list server software.
>>
>>Gary Handman
>>Director
>>Media Resources Center
>>Moffitt Library
>>UC Berkeley
>>ghandman@library.berkeley.edu
>>http://www.lib.berkeley.edu/MRC
>
>
>
>--part1_23.2737d5a8.2afd5f63_boundary--

Gary Handman
Director
Media Resources Center
Moffitt Library
UC Berkeley
ghandman@library.berkeley.edu
http://www.lib.berkeley.edu/MRC
--=====================_13654015==_.ALT
Content-Type: text/html; charset="us-ascii"

 Sorry I can't be more helpful, Rick.  I do my best on the tech end of things, but at this level, it's really not in my control.

I think the work-around is to use a messaging product other than one produced/supported by MicroSoft (if I read my systems department correctly).  Pine, Eudora, Webmail...etc.  The problem really has nothing to do with your service provider...

Gary--

With all due respect, your maven's answer to this problem was not helpful. 
The question is not "why does this happen?"  The question is "How can we
correct it?"  I.e. the best solution would be to be able, on your end, to
correct the problem.  The second-best solution would be to give us, your
list-serve subscribers, simple work-arounds to circumvent the problem.  I am
no software or internet guru, but from those "mavens" on your end, a few
simple sentences like, "If you're on AOL..." or "if you get a message that
originated on MS Word..." or whatever (from your maven's message below I have
no idea where the problem originates-- what are "Microsoft mailers"-- are
they part of the server, the word-processing software, what? is the problem
in my email sending program or receiving program?), and then "here's what you
can do as a workaround...." would be helpful. 

Thanks for your attention to this extremely annoying problem.

Rick Goldsmith

In a message dated 11/7/2002 5:23:54 PM Pacific Standard Time,
ghandman@library.berkeley.edu writes:


>
> Hello all:
>
> I've continued to get perplexed and wistful messages from various
> subscribers to the videolib and videonews lists regarding the receipt of
> messages from the list that look like they're HTML encoded.  I've asked UCB
> Library's system mavens to explain--below is what they have to say.  Blame
> it on Bill Gates, I guess.
>
> Gary
>
>
> >
> >Gary -
> >
> >         I think I responded to this once before, but I'd forgotten the
> >answer as well, so here goes.
> >
> >         Microsoft mailers by default send all emails as multipart, with
> >the first part being MS-DOS text and the second part being HTML. Listproc
> >doesn't handle multipart messages well, specifically, it doesn't copy the
> >headers identifying the email as multipart, or specifying the content type
> >of the parts, correctly. The result is that the receiving mail client
> >assumes that the email it is receiving is a single part, plain text
> >message (note that it cannot even do the conversion from MS-DOS text to
> >Unix text) and displays it accordingly.
> >
> >         With some digging, I understand that it is possible to stop
> >Microsoft products from making all messages multi-part. That is about the
> >only thing that will help, apart from changing list server software.
>
> Gary Handman
> Director
> Media Resources Center
> Moffitt Library
> UC Berkeley
> ghandman@library.berkeley.edu
> http://www.lib.berkeley.edu/MRC
>



--part1_23.2737d5a8.2afd5f63_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Gary--

With all due respect, your maven's answer to this problem was not helpful.  The question is not "why does this happen?"  The question is "How can we correct it?"  I.e. the best solution would be to be able, on your end, to correct the problem.  The second-best solution would be to give us, your list-serve subscribers, simple work-arounds to circumvent the problem.  I am no software or internet guru, but from those "mavens" on your end, a few simple sentences like, "If you're on AOL..." or "if you get a message that originated on MS Word..." or whatever (from your maven's message below I have no idea where the problem originates-- what are "Microsoft mailers"-- are they part of the server, the word-processing software, what? is the problem in my email sending program or receiving program?), and then "here's what you can do as a workaround...." would be helpful.  

Thanks for your attention to this extremely annoying problem.

Rick Goldsmith

In a message dated 11/7/2002 5:23:54 PM Pacific Standard Time, ghandman@library.berkeley.edu writes:



Hello all:

I've continued to get perplexed and wistful messages from various
subscribers to the videolib and videonews lists regarding the receipt of
messages from the list that look like they're HTML encoded.  I've asked UCB
Library's system mavens to explain--below is what they have to say.  Blame
it on Bill Gates, I guess.

Gary


>
>Gary -
>
>         I think I responded to this once before, but I'd forgotten the
>answer as well, so here goes.
>
>         Microsoft mailers by default send all emails as multipart, with
>the first part being MS-DOS text and the second part being HTML. Listproc
>doesn't handle multipart messages well, specifically, it doesn't copy the
>headers identifying the email as multipart, or specifying the content type
>of the parts, correctly. The result is that the receiving mail client
>assumes that the email it is receiving is a single part, plain text
>message (note that it cannot even do the conversion from MS-DOS text to
>Unix text) and displays it accordingly.
>
>         With some digging, I understand that it is possible to stop
>Microsoft products from making all messages multi-part. That is about the
>only thing that will help, apart from changing list server software.

Gary Handman
Director
Media Resources Center
Moffitt Library
UC Berkeley
ghandman@library.berkeley.edu
http://www.lib.berkeley.edu/MRC



--part1_23.2737d5a8.2afd5f63_boundary--

Gary Handman
Director
Media Resources Center
Moffitt Library
UC Berkeley
ghandman@library.berkeley.edu
http://www.lib.berkeley.edu/MRC

--=====================_13654015==_.ALT--