Subject: Re: Making this list more readable

Subject: Re: Making this list more readable

[Ian Batterbee]

>
>
>Content-Type: text/plain; charset=us-ascii
>Content-Disposition: inline
>Content-Transfer-Encoding: quoted-printable
>
>On Wed, Jan 08, 2003 at 08:59:16AM -0800, Carol Anne Ogdin wrote:
>  
>
>>>    Is there any way to change the listserv so it doesn't convert control
>>>    characters (e.g., tabs, quotes and spaces at ends of lines) to '=3Dxx'
>>>    form of hex characters.  It's hard to read.  (I read the digest, so
>>>    perhaps the problem lies there, and not in the main listserv?)
>>>    Does your listserv software have a conversion table you can set that
>>>    will make things more readable?
>>    
>>
>
>  I don't see this, and I'm getting the list direct.  The =3DXX thing is
>"Quoted Printable" encoding.  Probably an option on the listserv to turn
>it on/off for the digest.
>
I see the problem as well.. I think it's caused by the fact that many of 
the individual messages in the  are content-transfer-encoding: 
quoted-printable, but the digest has no content-transfer-encoding in the 
header, so the quoted-printable data inside the messages included in the 
digest is treated as plain text and incorrectly formatted.

If we know that ALL messages contained in the digest are 
quoted-printable, then it would just be a matter of changing the 
content-type of the digest, but I've noticed the problem doesn't occur 
on all messages.. some are fine.. so...  I guess people's mailers are 
simply posting as quoted-printable, and the digest process is just 
including the message body as-is

Re: Subject: Re: Making this list more readable

[Tommy McNeely]

All those Mic*ft mailers that send that html email :p maybe the listserv 
could reject it :) or at the very least, select the ascii attachment (that 
usually comes along with it)..



--On Thursday, January 09, 2003 12:37:32 PM +1300 Ian Batterbee 
<ian.batterbee@aut.ac.nz> wrote:

>>
>>
>> Content-Type: text/plain; charset=us-ascii
>> Content-Disposition: inline
>> Content-Transfer-Encoding: quoted-printable
>>
>> On Wed, Jan 08, 2003 at 08:59:16AM -0800, Carol Anne Ogdin wrote:
>>
>>
>>>>    Is there any way to change the listserv so it doesn't convert
>>>>    control characters (e.g., tabs, quotes and spaces at ends of lines)
>>>>    to '=3Dxx' form of hex characters.  It's hard to read.  (I read the
>>>>    digest, so perhaps the problem lies there, and not in the main
>>>>    listserv?) Does your listserv software have a conversion table you
>>>>    can set that will make things more readable?
>>>
>>>
>>
>>  I don't see this, and I'm getting the list direct.  The =3DXX thing is
>> "Quoted Printable" encoding.  Probably an option on the listserv to turn
>> it on/off for the digest.
>>
> I see the problem as well.. I think it's caused by the fact that many of
> the individual messages in the  are content-transfer-encoding:
> quoted-printable, but the digest has no content-transfer-encoding in the
> header, so the quoted-printable data inside the messages included in the
> digest is treated as plain text and incorrectly formatted.
>
> If we know that ALL messages contained in the digest are
> quoted-printable, then it would just be a matter of changing the
> content-type of the digest, but I've noticed the problem doesn't occur on
> all messages.. some are fine.. so...  I guess people's mailers are simply
> posting as quoted-printable, and the digest process is just including the
> message body as-is
>
>
>
>



--
Tommy McNeely         --        Tommy.McNeely@Sun.COM
Sun Microsystems - IT Ops - Broomfield Campus Support
Phone:  x50888 / 303-464-4888  --  Fax:  720-566-3168

Re: Subject: Re: Making this list more readable

[Athan]

[-- Attachment #1: Type: text/plain, Size: 1599 bytes --]

On Thu, Jan 09, 2003 at 12:37:32PM +1300, Ian Batterbee wrote:
> I see the problem as well.. I think it's caused by the fact that many of 
> the individual messages in the  are content-transfer-encoding: 
> quoted-printable, but the digest has no content-transfer-encoding in the 
> header, so the quoted-printable data inside the messages included in the 
> digest is treated as plain text and incorrectly formatted.
> 
> If we know that ALL messages contained in the digest are 
> quoted-printable, then it would just be a matter of changing the 
> content-type of the digest, but I've noticed the problem doesn't occur 
> on all messages.. some are fine.. so...  I guess people's mailers are 
> simply posting as quoted-printable, and the digest process is just 
> including the message body as-is

  Having checked and found this list is run with mailman, and then
checked the options for a list I have admin access to the solution is to
just make the digests 'plain' rather than 'mime'.  I presume the former
means you get one big file in mbox style, which may cause some people
problems too I guess.  This list is mailman 2.0.11, the one I checked is
2.0.12, so there's not going to be any extra options in this list's
config for it.

  Of course you could just read it in normal mode rather than digest ;).

-Ath
-- 
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
                  Finger athan(at)fysh.org for PGP key
	   "And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]