From: Linus Torvalds <torvalds@osdl.org>
To: Andy Whitcroft <apw@shadowen.org>
Cc: "Karl Hasselström" <kha@treskal.com>,
"Catalin Marinas" <catalin.marinas@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Allow hand-editing of patches before sending
Date: Fri, 3 Nov 2006 10:48:49 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0611031034520.25218@g5.osdl.org> (raw)
In-Reply-To: <454B4C43.2040607@shadowen.org>
On Fri, 3 Nov 2006, Andy Whitcroft wrote:
>
> Heh, well the copy thunderbird wrote directly to my mailbox is also
> 8bit. And thinking about it I've seen talk of MTA's not supporting 8bit
> xfers between themselves, so thats probabally when it gets switched.
If your ISP mailer doesn't answer with "8BITMIME" to your EHLO, your mail
client is supposed to downgrade to a 7-bit format (or the same thing can
happen anywhere in between on one of the other hops). Of course, that
would be a really old and broken mailer, and if you find one of those at
the ISP you use, you should probably switch ISPs.
Some other mailers have other issues, and qmail for example is apparently
totally broken (it accepts 8-bit input, but cannot forward it properly to
somebody who wants it converted to 7-bit).
And some of us use "fetchmail" and ask it do do mimedecode for us, so that
even if it arrived as 7-bit crud, we don't have to see it. So the fact
that some people see it as 8-bit can be because the hops to them didn't
involve a broken remailer, but it could also be because something in
between (like fetchmail) tries to fix it up after the fact.
That said: it tends to be unusual to see true 7-bit mailer setups these
days.
So the most _likely_ cause of unnecessary 7-bit QP crud is not in fact a
7-bit mailserver, but usually just the mail client that is just lazy and
just sends out everything as 7-bit because it's too bothersome to even
look at whether the mail server supports 8-bit data. Check your
Thunderbird settings - it's quite possible that there's a flag there
somewhere to turn on 8-bit mail transfers.
next prev parent reply other threads:[~2006-11-03 18:49 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 9:00 [PATCH] Allow hand-editing of patches before sending Karl Hasselström
2006-11-02 10:32 ` Catalin Marinas
2006-11-02 11:36 ` Karl Hasselström
2006-11-03 9:39 ` Catalin Marinas
2006-11-03 9:58 ` Karl Hasselström
2006-11-03 10:01 ` Karl Hasselström
2006-11-03 10:21 ` Petr Baudis
2006-11-03 10:31 ` Robin Rosenberg
2006-11-03 10:36 ` Andreas Ericsson
2006-11-03 10:53 ` Karl Hasselström
2006-11-03 11:21 ` Junio C Hamano
2006-11-03 11:35 ` Karl Hasselström
2006-11-03 12:56 ` Catalin Marinas
2006-11-03 12:07 ` Andy Whitcroft
2006-11-03 12:36 ` Karl Hasselström
2006-11-03 14:03 ` Andy Whitcroft
2006-11-03 18:48 ` Linus Torvalds [this message]
2006-11-05 11:43 ` Karl Hasselström
2006-11-05 16:44 ` Linus Torvalds
2006-11-05 19:04 ` Karl Hasselström
2006-11-05 19:29 ` Jakub Narebski
2006-11-06 7:45 ` [PATCH] Add a MIME-Version header to e-mails Karl Hasselström
2006-11-06 7:56 ` Karl Hasselström
2006-11-07 9:53 ` Catalin Marinas
2006-11-07 19:09 ` Catalin Marinas
2006-11-08 8:40 ` Karl Hasselström
2006-11-08 9:41 ` Catalin Marinas
2006-11-08 10:01 ` Karl Hasselström
2006-11-08 10:12 ` Catalin Marinas
2006-11-12 21:14 ` [StGIT PATCH 0/2] mail and import tests Karl Hasselström
2006-11-12 21:15 ` [StGIT PATCH 1/2] Regression test for "stg import" Karl Hasselström
2006-11-12 21:15 ` [StGIT PATCH 2/2] Regression test for "stg mail" Karl Hasselström
2006-11-11 12:24 ` [PATCH] Add a MIME-Version header to e-mails Karl Hasselström
2006-11-16 17:24 ` Catalin Marinas
2006-11-03 12:44 ` [PATCH] Allow hand-editing of patches before sending Catalin Marinas
2006-11-03 13:02 ` Karl Hasselström
2006-11-03 13:16 ` Catalin Marinas
2006-11-03 13:25 ` Karl Hasselström
2006-11-03 13:25 ` Catalin Marinas
2006-11-03 13:33 ` Karl Hasselström
2006-11-03 13:42 ` Karl Hasselström
2006-11-03 13:56 ` Catalin Marinas
2006-11-03 14:37 ` Catalin Marinas
2006-11-03 13:39 ` Petr Baudis
2006-11-03 14:01 ` Catalin Marinas
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=Pine.LNX.4.64.0611031034520.25218@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=apw@shadowen.org \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/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 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).