# testing vger handling of charsets (part 1) 6 messages from 2007-05-15 to 2007-05-15. Participants: Jeff King, Karl Hasselström, J. Bruce Fields, Jan Hudec, Alex Riesen, David Kågedal. Thread: https://gitlist.dev/t/8161 ## Jeff King, 2007-05-15 07:12 Subject: testing vger handling of charsets (part 1) Message-ID: <20070515test.1@coredump.intra.peff.net> URL: https://gitlist.dev/e/20070515test.1%40coredump.intra.peff.net ``` This is a test message to check how vger reacts to seeing 8bit characters (like Hasselström) in a message without the right mime header. Previous attempts were eaten by the list because of a lack of a message id. If your mail server doesn't advertise the 8BITMIME extensions, I expect this message to be corrupted to iso8859-1 during the smtp conversation between vger and your server, because it lacks a mime version header. ``` ## Karl Hasselström, 2007-05-15 08:32 Subject: Re: testing vger handling of charsets (part 1) Message-ID: <20070515083235.GE9096@diana.vm.bytemark.co.uk> URL: https://gitlist.dev/e/20070515083235.GE9096%40diana.vm.bytemark.co.uk In-Reply-To: <20070515test.1@coredump.intra.peff.net> ``` On 2007-05-15 03:12:05 -0400, Jeff King wrote: > This is a test message to check how vger reacts to seeing 8bit > characters (like Hasselström) in a message without the right mime > header. Previous attempts were eaten by the list because of a lack > of a message id. This was broken when I got it via the list, but looked good when I got it directly. -- Karl Hasselström, kha@treskal.com www.treskal.com/kalle ``` ## J. Bruce Fields, 2007-05-15 14:58 Subject: Re: testing vger handling of charsets (part 1) Message-ID: <20070515145853.GA6794@fieldses.org> URL: https://gitlist.dev/e/20070515145853.GA6794%40fieldses.org In-Reply-To: <20070515083235.GE9096@diana.vm.bytemark.co.uk> ``` On Tue, May 15, 2007 at 10:32:35AM +0200, Karl Hasselström wrote: > On 2007-05-15 03:12:05 -0400, Jeff King wrote: > > > This is a test message to check how vger reacts to seeing 8bit > > characters (like Hasselström) in a message without the right mime > > header. Previous attempts were eaten by the list because of a lack > > of a message id. > > This was broken when I got it via the list, but looked good when I got > it directly. Ditto here. And the copy from the list had the same big warning as before in the headers. --b. ``` ## Jan Hudec, 2007-05-15 18:12 Subject: Re: testing vger handling of charsets (part 1) Message-ID: <20070515181207.GC3653@efreet.light.src> URL: https://gitlist.dev/e/20070515181207.GC3653%40efreet.light.src In-Reply-To: <20070515test.1@coredump.intra.peff.net> ``` On Tue, May 15, 2007 at 03:12:05 -0400, Jeff King wrote: > This is a test message to check how vger reacts to seeing 8bit > characters (like Hasselström) in a message without the right mime > header. Previous attempts were eaten by the list because of a lack of a > message id. > > If your mail server doesn't advertise the 8BITMIME extensions, I expect > this message to be corrupted to iso8859-1 during the smtp conversation > between vger and your server, because it lacks a mime version header. To me it arrived via vger only, including the ö, with Content-Type: text/plain; charset=utf-8 -- Jan 'Bulb' Hudec ``` ## Alex Riesen, 2007-05-15 18:42 Subject: Re: testing vger handling of charsets (part 1) Message-ID: <20070515184258.GA2407@steel.home> URL: https://gitlist.dev/e/20070515184258.GA2407%40steel.home In-Reply-To: <20070515test.1@coredump.intra.peff.net> ``` Jeff King, Tue, May 15, 2007 09:12:05 +0200: > This is a test message to check how vger reacts to seeing 8bit > characters (like Hasselström) in a message without the right mime > header. Previous attempts were eaten by the list because of a lack of a > message id. ok here. Headers: Received: from googlemail-pop.l.google.com [66.249.93.16] by steel.home with POP3 (fetchmail-6.3.6 polling pop.googlemail.com account raa.lkml) for (single-drop); Tue, 15 May 2007 09:21:24 +0200 (CEST) Received: by 10.100.225.3 with SMTP id x3cs2418606ang; Tue, 15 May 2007 00:13:44 -0700 (PDT) Received: by 10.82.177.3 with SMTP id z3mr3288934bue.1179213217602; Tue, 15 May 2007 00:13:37 -0700 (PDT) Return-Path: Received: from vger.kernel.org (vger.kernel.org [209.132.176.167]) by mx.google.com with ESMTP id j2si425607mue.2007.05.15.00.13.05; Tue, 15 May 2007 00:13:37 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of git-owner@vger.kernel.org designates 209.132.176.167 as permitted sender) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754566AbXEOHMI (ORCPT + 56 others); Tue, 15 May 2007 03:12:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754600AbXEOHMI (ORCPT ); Tue, 15 May 2007 03:12:08 -0400 Received: from 66-23-211-5.clients.speedfactory.net ([66.23.211.5]:3083 "EHLO peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754566AbXEOHMH (ORCPT ); Tue, 15 May 2007 03:12:07 -0400 Received: (qmail 26461 invoked from network); 15 May 2007 07:12:07 -0000 Received: from coredump.intra.peff.net (10.0.0.2) by peff.net with (DHE-RSA-AES128-SHA encrypted) SMTP; 15 May 2007 07:12:07 -0000 Received: by coredump.intra.peff.net (sSMTP sendmail emulation); Tue, 15 May 2007 03:12:05 -0400 Date: Tue, 15 May 2007 03:12:05 -0400 From: Jeff King To: git@vger.kernel.org cc: kha@treskal.com, peff@peff.net, bfields@fieldses.org Subject: testing vger handling of charsets (part 1) Message-ID: <20070515test.1@coredump.intra.peff.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Status: RO Content-Length: 614 ``` ## David Kågedal, 2007-05-15 22:05 Subject: Re: testing vger handling of charsets (part 1) Message-ID: <87646teo8o.fsf@morpheus.local> URL: https://gitlist.dev/e/87646teo8o.fsf%40morpheus.local In-Reply-To: <20070515test.1@coredump.intra.peff.net> ``` Jeff King writes: > This is a test message to check how vger reacts to seeing 8bit > characters (like Hasselström) in a message without the right mime > header. Previous attempts were eaten by the list because of a lack of a > message id. This is broken when reading over NNTP from GMANE. -- David Kågedal ```