Complete.Org: Mailing Lists: Archives: discussion: December 2007:
[aclug-L] Re: Tonight's meeting

[aclug-L] Re: Tonight's meeting

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: discussion@xxxxxxxxx
Subject: [aclug-L] Re: Tonight's meeting
From: Chris Owen <owenc@xxxxxxxxxx>
Date: Tue, 11 Dec 2007 09:41:19 -0600
Reply-to: discussion@xxxxxxxxx

Hash: SHA1

On Dec 10, 2007, at 11:59 PM, Bruce Bales wrote:

> On Monday 10 December 2007 15:29:38 Bruce Bales wrote:
>> Doesn't look like a good night for me, either. =3DA0It's 31=3D3DB0 =
and =20
>> raining
>> righ=3D3D t=3D3D20
>> now. =3D3D20
>> bruce
> Doesn't matter a whole lot, but when the message above left here
> the "=3D3DB0" was a nice, neat xmodmap degree sign and the=3D20
> "righ=3D3Dt=3D3D20" was "right" followed by a newline.
> If I send a degree sign to myself, it stays a degree sign.
> Strange. =3D20
> bruce=3D20

This is a fairly old issue with Ecartis and one that come up here =20
every couple of years.  I'm not sure if its been fixed in newer =20
versions of Ecartis or not since the Ecartis we site seems to be MIA.

My guess is you are sending email with 7bit encoding.  Your mail =20
client will then attach a header of "Content-Transfer-Encoding: 7bit" =20=

to let clients on the other end know how the message was encoded.  =20
Those clients then are smart enough to back off all the encoding on =20
the high bit characters (and the =3D sign which is not high bit but is =20=

reserved because it is used in the encoding).

The problem is that when Ecartis processes the mail it replaces your =20
7bit header with an 8bit header.  That's fine I suppose if it is =20
sending out 8bit emails but it isn't converting your email to 8bit.  =20
That means when the clients on the other end get it they see the 8bit =20=

header and don't do any of the magic decoding of the high bit =20
characters (which are now their encoded 7bit equivalents).  So instead =20=

of equal sign you see =3D3D.

The only way you could fix this is set your mail client to send mail =20
with 8bit encoding.  This may cause you issues other places though.

The real solution would be for Ecartis to either:

1) Honor the original emails encoding and pass that on when forwarding =20=

the message


2) Convert the 7bit message to 8bit before resending

The problem may be more complicated than that too because I send mail =20=

to the list as 7bit and it is fine so there may be more going on.


Test: =3D ' " % =95

Chris Owen         ~ Garden City (620) 275-1900 ~  Lottery (noun):
President          ~ Wichita     (316) 858-3000 ~    A stupidity tax
Hubris Communications Inc

Version: GnuPG v1.4.7 (Darwin)
Comment: Public Key:
Comment: Public Key ID: 0xB513D9DD


-- This is the discussion@xxxxxxxxx list.  To unsubscribe,

[Prev in Thread] Current Thread [Next in Thread]