From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 760426DE0119 for ; Thu, 16 Nov 2017 11:48:55 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.311 X-Spam-Level: X-Spam-Status: No, score=0.311 tagged_above=-999 required=5 tests=[AWL=-0.378, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.211, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u9roNqf3Bfb1 for ; Thu, 16 Nov 2017 11:48:53 -0800 (PST) Received: from mail-wr0-f179.google.com (mail-wr0-f179.google.com [209.85.128.179]) by arlo.cworth.org (Postfix) with ESMTPS id 5D02C6DE00D4 for ; Thu, 16 Nov 2017 11:48:53 -0800 (PST) Received: by mail-wr0-f179.google.com with SMTP id u97so163312wrc.1 for ; Thu, 16 Nov 2017 11:48:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:in-reply-to:references:date:message-id:mime-version; bh=1ggMAJSxehw2TO+oHJjjzc4T5MmmJPLektw7IXkBsnA=; b=WXSz3q1kZy729hPM5nA2izuj81I6LKp84lgy2GNzRLw4ijjlsHAsp3KOw8AXRA2RJy nL24VVgs+eLX8pDOdUzDkvoy9/IBoO1BmiNjIVQjQq5gMoPF7WOeUEaLg8Za7mOyT0NC 99rND2WmvGpuU4sO4Fw8QBpGeM7kKRC3JHhrzMqpE4NEgM16R9y5VpeBGaSsW3zrIalV nBfLPHIOSGiyd/EbpEAj/8OEzGy83WcnEbF25fMMwbcetPTtImyaNIfHwix/IFxw2Qjl jYHqgojSfMRab9AHEJ4tqDRnfXNOgYanF8NCnLiGVND+RWHxyjhccyCUAMfcupWqRIBt BagA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version; bh=1ggMAJSxehw2TO+oHJjjzc4T5MmmJPLektw7IXkBsnA=; b=EYIm19iTxE21kmQ57YBkKqsZ9XQaKbULdCALAz6n2ZBYzZz/r7osFp3s5ufCheyOAD /67Bf2RzpkSq2Wg172fcZuUo2aATsgdWTfA38YAMDmvInY+wZno5PHst9/JSVt4QtC// 2W18+Fk6F84Na6FP/FcHfG07IlS/Fpxl2Nop07Pu5g5U4+m6l8iH0adfpve662743C+K tBtFfJloj7eX3EySOd4fy9QQGe9qJo7k5jD0IwjaIbPgNB/h3ujt7nURec1Op7uFor5Q CNzV66k/XR+TJXbMzz0vrxEFarNviAWFft1vll5NdGz4+NvLrbLm0TIUzJXYdFytNVxY 3AYQ== X-Gm-Message-State: AJaThX4PWrcMMX/tici9ITnM2cw6TWYsrSS3DAZQsLzxEEGCgISSdtOv WBXSCLScDgZ+/mr12qu/VckufCcS X-Google-Smtp-Source: AGs4zMYsx5TXhu5UQ93NTx7k7eQTfrcWjTJ7D7a9N53y7ZozaqsweYrnOvxwhOPANukmMDlJmGm3XA== X-Received: by 10.223.170.150 with SMTP id h22mr2391222wrc.26.1510861730790; Thu, 16 Nov 2017 11:48:50 -0800 (PST) Received: from nix230 (port-92-196-46-141.dynamic.qsc.de. [92.196.46.141]) by smtp.gmail.com with ESMTPSA id 138sm3012931wmf.21.2017.11.16.11.48.49 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 16 Nov 2017 11:48:49 -0800 (PST) From: Kai Harries To: David Bremner , notmuch@notmuchmail.org Subject: Re: bounce/forward not working due to CR at line end In-Reply-To: <877eur5i33.fsf@tesseract.cs.unb.ca> References: <87d14ri436.fsf@x230.kaiha.invalid> <877euraf0e.fsf@tethera.net> <87fu9f45e1.fsf@x230.kaiha.invalid> <877eur5i33.fsf@tesseract.cs.unb.ca> Date: Thu, 16 Nov 2017 20:48:48 +0100 Message-ID: <87shdeovhb.fsf@x230.kaiha.invalid> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 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: Thu, 16 Nov 2017 19:48:55 -0000 David Bremner writes: > Kai Harries writes: > >> David Bremner writes: >> >>> During off-list discussion, Kai mentioned id:87a7zsm5ol.fsf@gmail.com as >>> a message that he cannot bounce (and also not forward?). For me this >>> forwards fine, but does not bounce because it has a corrupted Cc header, >>> and my MTA rejects it. That doesn't sound related to the original >>> problem report (nothing about line endings). >> >> Can you please evaluate the following on your system: >> >> (call-process "notmuch" nil t nil "show" "--format=raw" "id:87a7zsm5ol.fsf@gmail.com") >> >> If I do this on my system, then the text that is inserted into the >> buffer has ^M (CR) at the line endings. Is this expected? > > No ^M line endings for me. Can you check the file on disk? Maybe "od -a" > lacking a better idea. `od -a` does also show that the lines are ending with 'cr' and 'nl' this is correct according to RFC 2822 [1]. According to this [2] Emacs normally converts line endings to only 'nl' (newline) when opening a DOS file. This works on my system, if I open the file from disk no carriage-return (^M) is shown. Not working is inserting the output of `notmuch show` into a buffer. If I do this, then the carriage-return (^M) is shown. David, I assume your system is also a Linux, does notmuch show --format=raw id:1472041345236.7014@de.bosch.com | od -a also show 'cr' and 'nl' as line ending? If No, then my `notmuch show` behaves different. If Yes, then my Emacs behaves different when inserting text with DOS line endings into a buffer. [1] https://tools.ietf.org/html/rfc2822#section-2.2 [2] https://www.gnu.org/software/emacs/manual/html_mono/emacs.html#Coding-Systems