All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tommy McNeely <Tommy.McNeely@Sun.COM>
To: Ian Batterbee <ian.batterbee@aut.ac.nz>, netfilter@lists.netfilter.org
Cc: Athan <netfilter@miggy.org>, Carol Anne Ogdin <caogdin@deepwoods.com>
Subject: Re: Subject: Re: Making this list more readable
Date: Wed, 08 Jan 2003 17:52:42 -0700	[thread overview]
Message-ID: <90760000.1042073562@leverage> (raw)
In-Reply-To: <3E1CB63C.9090602@aut.ac.nz>

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



  reply	other threads:[~2003-01-09  0:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 23:37 Subject: Re: Making this list more readable Ian Batterbee
2003-01-09  0:52 ` Tommy McNeely [this message]
2003-01-09  1:27 ` Athan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=90760000.1042073562@leverage \
    --to=tommy.mcneely@sun.com \
    --cc=caogdin@deepwoods.com \
    --cc=ian.batterbee@aut.ac.nz \
    --cc=netfilter@lists.netfilter.org \
    --cc=netfilter@miggy.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.