[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

MIME and "weird" conversions (TAB -> =09)



[ This question is likely to have wider audience, thus I will Cc: it to
  the  zmailer@nic.funet.fi  as well ]

....
> > 
> > =09Sure, but Solaris 2.3 diff doesn't have those switches..
> > =09(Now I installed there GNU diff, so I could do it..)
> 
> Is converting TABs to =09 desired behavior?


	Yes, if you had looked wider, you would have noticed some other
	QP-coded characters on (most likely) Matthias Ulrichs signature.
	Even one such 8-bit character will cause QP encoding, when the
	message is transferred to non-8-bit-transparent MTAs.
	(Isn't the MIME lovely ?)

	This message you are reading now should not become converted, and
	the  charset= will likely report  US-ASCII  (it should, anyway),
	because all the characters in the message are in range 0..127.
	I do originate all of my email in 8-bit and charset=ISO-8859-1,
	but the machine has liberty to convert it to  7-bit charset=US-ASCII
	when transporting (because the low-128 are the same on both.)


	I will insert some comments below into the headers -- "time reversed",
	like the Received lines are..

Have a look into these headers you so gratituously copied here:

> Matti Aarnio writes:
> > From kiae!kiae!nic.funet.fi!zmailer-owner Fri Jan  6 14:41:27 1995
> > Received: from kiae by harpy.skfgvc.pyatigorsk.su with UUCP id <178294(2)>;
> >   Fri, 6 Jan 1995 14:41:21 +0300

	I see that HARPY runs pretty old version of ZMailer because of the
	spool-id is of the format from 2.2.1.
	Had you been running my recent MIMEmified versions, you would not
	have noticed the QP-coding at all, because the  mailbox  decodes it..
	(Your email-exchange parthers might notice, though..)

> > Received: from nic.funet.fi by sequent.kiae.su with SMTP id AA00652
> >   (5.65.kiae-2  for <zmailer-readers@skfgvc.pyatigorsk.su>);
> >   Fri, 6 Jan 1995 14:02:19 +0300

	That SEQUENT is running pretty old sendmail..  Perhaps 8-bit
	transparent, but without announcing it in any way. (Not in
	ESMTP/MIME anyway..)

> > Received: from castor.cc.utu.fi ([130.232.1.14]) by nic.funet.fi
> >   with ESMTP id <92722-3> convert rfc822-to-quoted-printable;
> >   Fri, 6 Jan 1995 13:01:18 +0200

	Here it states that  nic.funet.fi  did convert the 8-bit encoded
	email (because it had some 8-bit char in it) to QP when it noticed
	that   sequent.kiae.su  does not support pure transparent 8BITMIME
	transport.

> > Received: by utu.fi id <166530-1>; Fri, 6 Jan 1995 13:01:05 +0200

	Here is no conversion clause for two reasons:
		- UTU.FI -> NIC.FUNET.FI is 8BITMIME transparent
		- I originate my texts in 8-bit

> > Subject: Re: Version 2.99.7 is out
> > From: Matti Aarnio <mea@utu.fi>
> > To: urlichs@noris.de (Matthias Urlichs)
> > Date: Fri, 6 Jan 1995 14:01:01 +0300
> > Cc: zmailer@nic.funet.fi
> > In-Reply-To: <3eieq4$a5j@smurf.noris.de> from "Matthias Urlichs" at Jan 5, 95 10:52:36 pm
> > Mime-Version: 1.0
> > Content-Type: text/plain; charset=ISO-8859-1
> > Content-Transfer-Encoding: QUOTED-PRINTABLE
> > Content-Length: 372       
> > Message-Id: <95Jan6.130105+0200_eet.166530-1+38@utu.fi>

> []
> -- 
> /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
> Joint stock company "GVC Energeticy", North-Caucasian Branch, Pyatigorsk
> Andrew Petrovich Kokarev, postmaster         andrew@skfgvc.pyatigorsk.su


	I am curious, how do you solve the 8-bit character problem in the
	Russian ?  "Just-send-8-bit" or are there any plans to jump to the
	MIME-bandvagon ?


	If you want to use the ZMailer like in the old-days of unannounced
	methods, run the channel programs with "-8" option, and you get
	ALMOAST the same behaviour.  ("Almoast", because QP-coded email
	will become decoded, when transported to next-hop..)


	/Matti Aarnio	<mea@utu.fi>