zsh-workers
 help / color / mirror / code / Atom feed
From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: schaefer@nbn.com
Cc: A.Main@dcs.warwick.ac.uk, zsh-workers@math.gatech.edu
Subject: Re: bug in zsh 3.0-pre6?
Date: Tue, 13 Aug 1996 22:22:12 +0200 (MET DST)	[thread overview]
Message-ID: <199608132022.WAA02231@bolyai.cs.elte.hu> (raw)
In-Reply-To: <960813125931.ZM2257@candle.brasslantern.com> from Bart Schaefer at "Aug 13, 96 12:59:31 pm"

> I didn't get any lossage ... the problem appears to be that Zoltan
> is sending out
> 
> Content-Transfer-Encoding: 8bit
> 
> which isn't necessary (his message is all 7bit) but which causes "smart"
> ESMTP agents to convert to quoted-printable when gatewaying to an old
> SMTP (not 8-bit-clean) agent.
> 
> Zoltan didn't do the encoding; it happened along the way somewhere.
> But Zoltan could have prevented it by using 7bit as his C-T-E, if he
> has that level of control over his mail client.

There was a letter `é' in the message I quoted.  My mail client
(elm-2.4ME+) scans the message for characters with 8th bit set and if it
finds one it automatically uses 8bit, quoted-printable or base64 encoding
(it uses quoted-printable only if I tell it during compile time that my MTA
does not support 8bit, and it uses base64 if more the percentage of 8th bit
set characters is high).

When I read a message, quoted-printable or base64 is seemlessly converted
on the fly by elm.

Zoltan


  parent reply	other threads:[~1996-08-13 20:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-08-13 17:09 Tomas Gradin
1996-08-13 18:34 ` Zoltan Hidvegi
1996-08-13 19:11   ` Zefram
1996-08-13 19:59     ` Bart Schaefer
1996-08-13 20:06       ` Richard Coleman
1996-08-13 20:22       ` Zoltan Hidvegi [this message]
1996-08-13 20:37         ` Zefram
1996-08-13 20:45           ` Zoltan Hidvegi
1996-08-13 20:15     ` Zoltan Hidvegi

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=199608132022.WAA02231@bolyai.cs.elte.hu \
    --to=hzoli@cs.elte.hu \
    --cc=A.Main@dcs.warwick.ac.uk \
    --cc=schaefer@nbn.com \
    --cc=zsh-workers@math.gatech.edu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).