From f1bb5d17cee115c48df00efa6920b8c7a1683942 Mon Sep 17 00:00:00 2001 From: Patrick Totzke Date: Sun, 27 Oct 2013 13:23:53 +0000 Subject: [PATCH] Re: How about these: -- CR & NL char in rfc2047-encoded header... --- 8b/b42b400e7bbe5ecbcff2aaaf86a8bc929cb121 | 119 ++++++++++++++++++++++ 1 file changed, 119 insertions(+) create mode 100644 8b/b42b400e7bbe5ecbcff2aaaf86a8bc929cb121 diff --git a/8b/b42b400e7bbe5ecbcff2aaaf86a8bc929cb121 b/8b/b42b400e7bbe5ecbcff2aaaf86a8bc929cb121 new file mode 100644 index 000000000..d25852327 --- /dev/null +++ b/8b/b42b400e7bbe5ecbcff2aaaf86a8bc929cb121 @@ -0,0 +1,119 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id ED787429E4B + for ; Sun, 27 Oct 2013 06:24:05 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -0.799 +X-Spam-Level: +X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 + tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, + FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id iTu456B-bH7K for ; + Sun, 27 Oct 2013 06:24:00 -0700 (PDT) +Received: from mail-we0-f170.google.com (mail-we0-f170.google.com + [74.125.82.170]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 064E7431FDC + for ; Sun, 27 Oct 2013 06:23:59 -0700 (PDT) +Received: by mail-we0-f170.google.com with SMTP id u57so5615501wes.1 + for ; Sun, 27 Oct 2013 06:23:57 -0700 (PDT) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; + h=content-type:mime-version:content-disposition:from:user-agent:to + :references:in-reply-to:message-id:subject:date; + bh=hm9W7pObtnFL31qss8Twn+yiexV0XiyBMnzIkMobsd0=; + b=dEV4o9w0QEfpeWUueA36Y+NtFfBcCT1nl6UGgfyIO3OXk7Ay4Cg2nUlH+rkyFSBVjN + Am72EqkZ9rINikZbrPiwAEPsrZTQBjvwyix2xj8XL1vTOa4GFC87ofa81M7Dyng9Q6Qn + ORdmr5bzj6W03Mbtc6G2V7AXyL8F7Q3/LP7LYDhJnJeX1wDiIT9/dM3gUbxUYisqXm3c + 5konUZZln9q1A2pM5CgezhtZZhLiUJ5qdFmiZ+pD2ISwOZL2dVaufLRb0KCN3cJqRJjC + UuwPYaEiztoBzMbkVZXN//MrshBc/eO/0VmGSYErcqlYRePIMyjUCvYqIQewutt6VO1a + Ok5w== +X-Received: by 10.180.211.71 with SMTP id na7mr5442494wic.5.1382880234949; + Sun, 27 Oct 2013 06:23:54 -0700 (PDT) +Received: from localhost (cpc14-sgyl28-2-0-cust332.18-2.cable.virginm.net. + [82.39.85.77]) by mx.google.com with ESMTPSA id + ft19sm25713258wic.5.2013.10.27.06.23.54 for + (version=TLSv1.2 cipher=RC4-SHA bits=128/128); + Sun, 27 Oct 2013 06:23:54 -0700 (PDT) +Content-Type: multipart/signed; protocol="application/pgp-signature"; + micalg="pgp-sha1"; boundary="===============2022887196568602547==" +MIME-Version: 1.0 +Content-Disposition: inline +From: Patrick Totzke +User-Agent: alot/0.3.5+ +To: David Bremner , tomi.ollila@iki.fi, + notmuch@notmuchmail.org +References: <1374606929.hand.crafted.4.sendmail@guru.guru-group.fi> + <87hac23mnb.fsf@zancas.localnet> +In-Reply-To: <87hac23mnb.fsf@zancas.localnet> +Message-ID: <20131027132353.5125.14023@brick> +Subject: Re: How about these: -- CR & NL char in rfc2047-encoded header... +Date: Sun, 27 Oct 2013 13:23:53 +0000 +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +Precedence: list +List-Id: "Use and development of the notmuch mail system." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Sun, 27 Oct 2013 13:24:06 -0000 + +--===============2022887196568602547== +Content-Type: text/plain; charset="utf-8" +MIME-Version: 1.0 +Content-Transfer-Encoding: quoted-printable + +Quoting David Bremner (2013-10-27 12:48:24) +> tomi.ollila@iki.fi writes: +> = + +> > In thread starting from id:08cb1dcd-c5db-4e33-8b09-7730cb3d59a2@gmail.c= +om +> > David wondered in id:87y58xv71x.fsf@zancas.localnet what filtering +> > is done by CLI and what by lib. +> > +> > But where should the "problem" presented in the Subject: header should +> > be handled. I did some hacks to emacs client to drop the ^J (newline) +> > characters from Subject: and From: headers but should these be filtered +> > in CLI (or in lib) instead? +> > +> = + +> Eventually we decided this was a front-end isssue. The emacs front-end +> fixed this with commit 0.16-111-ga7964c8 + + +I agree that this should be an issue for the MUA. +FYI: alot also normalizes newlines and tabs in subject lines.. +https://github.com/pazz/alot/blob/master/alot/db/utils.py#L369 +I cannot reproduce the original issue with the escaped UTF8 header not bein= +g interpreted. +This works fine for me in alot. + +Best, +/p + +--===============2022887196568602547== +MIME-Version: 1.0 +Content-Transfer-Encoding: 7bit +Content-Description: signature +Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii" + +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v2.0.20 (GNU/Linux) + +iEYEABECAAYFAlJtE+kACgkQlDQDZ9fWxaqq4ACfXq9YfOQnT5g4U5StYY5xbm/v +vUcAn3BCQrEV5XIzVb4U3eC/78/eljRd +=CHQd +-----END PGP SIGNATURE----- + +--===============2022887196568602547==-- -- 2.26.2