From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id QA/HAuqN52L3XAAAbAwnHQ (envelope-from ) for ; Mon, 01 Aug 2022 10:25:14 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id GMLTAeqN52Lv9wAAG6o9tA (envelope-from ) for ; Mon, 01 Aug 2022 10:25:14 +0200 Received: from mail.notmuchmail.org (yantan.tethera.net [135.181.149.255]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 9F5383830 for ; Mon, 1 Aug 2022 10:25:13 +0200 (CEST) Received: from yantan.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id B3FF75F371; Mon, 1 Aug 2022 08:18:03 +0000 (UTC) Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) by mail.notmuchmail.org (Postfix) with ESMTPS id BEE745E54B for ; Mon, 1 Aug 2022 08:18:00 +0000 (UTC) Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 212BA240104 for ; Mon, 1 Aug 2022 10:18:00 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1659341880; bh=+Co+q3if/lMJnEO0+DPFBg6con4mP/wbls/duRAtdUQ=; h=From:To:Cc:Subject:Date:From; b=GW7eNQDjCtHfNZg38QNyWmu3SK3sFZrqOP/uVfwKKTnafY2zzAkTTKBvbTnam21BO 5x/CCJ/RSKtEUipbhmIwWPdshtKxcn4rXZ8oX8QmCMSWKSsR2pKbsGu9A3vfk3/W8+ fbp7xyIUhWDLvl7seSeGoVv8IWQj8pm2NmwFaUgWfEKKVO2BwogbnTG6YVCm1Tpp7g XuP5fuuYa1JMSJWkiiuODjd3M2GTaEEyZVrqp/RyrZ9N2y8v4Rk3fMXujEVc4dlFtl AW4MFh+NQ2b+7TKFOIjw5OMy+4EY3VhPAPMUm06uuqQVfekov4ODpeD5hh8cWhAsa+ NjPx6vTH4AOzQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Lx9wl2RnHz9rxN; Mon, 1 Aug 2022 10:17:59 +0200 (CEST) From: Dan =?utf-8?B?xIxlcm3DoWs=?= To: Justus Winter Subject: Re: Sending mail succeeded but signaled failure In-Reply-To: <87edy2ia4m.fsf@thinkbox> References: <87k080jgx8.fsf@thinkbox> <87bktc3r2t.fsf@tethera.net> <87edy2ia4m.fsf@thinkbox> Date: Mon, 01 Aug 2022 08:17:58 +0000 Message-ID: <87les88jih.fsf@cgc-instruments.com> MIME-Version: 1.0 Message-ID-Hash: G4WMSEK72Y2BWXA26HBEVBCA6Y6YXZ2G X-Message-ID-Hash: G4WMSEK72Y2BWXA26HBEVBCA6Y6YXZ2G X-MailFrom: dan.cermak@posteo.net X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: notmuch@notmuchmail.org X-Mailman-Version: 3.3.3 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: DE ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1659342313; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-owner:list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=A8zWBWeqeg1OAr9II3zTHM7WouC4cVvByXgSxU5BI1Y=; b=rOiT/W6652bD5WaJm+7RGAGC2DTCHYgNfp/JekNMstrwrsFHZ9ILhOsuizi8oFvC7/AF1k wEXi8ENeBoai0YjVjupGlfKxEGp9HAl5n+Latp0x+jO9QlIYfAoTZSHnzMDOP1NNJP2aDN 9lM5pvWRjQotokPZU146PjkgSMUI21NXDoUCbIiAKCI5G2eg1/ccemds7EZ+rmSt1X20Yf pCPhC6JuEqqV3NTUr1+NA3/QPjctI4eDZxn8oIp0QxHVY7Q7V6AGnY2N3t8NwkjB4hU6LT CObOOQb1gtHOn+4NqIm5qjaXYaMNpcBNVCJDZ7YnbzR8rCxU7e/yI8RwrvCCVg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1659342313; a=rsa-sha256; cv=none; b=lYR9OCFx/vEb/DSLstCTRoMsEDF7rdEgHIJOWam9QzEv6kDGZfQhRnkSRt0svCujGlR3om B1ARomwPjCnd2ayUpbm/K4spE0SgOGuBqAViqJY0mXkbpIc2GwEtXNv5TouL5eHxcVxdaj 3zjzF4QOvIOY4EV9wc+rgUmW1bXgoMD8hPxU/KgYqH7v7OoYBDV8AppWTAyhlL/4f45rZW LhT585uOZ+onD2XbVCSgA89bSnqUqRzLIoa6TskseukhzOC255l4/QV5UEC3yU12iBcnbW yQv+Ykp4BRk/HVlH+g7y15W0Gy8bSSHBcHKqGjg8d31r0SdAOOcnIHkqoYIK/A== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=posteo.net header.s=2017 header.b=GW7eNQDj; dmarc=fail reason="SPF not aligned (strict)" header.from=posteo.net (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 135.181.149.255 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Spam-Score: 6.54 Authentication-Results: aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=posteo.net header.s=2017 header.b=GW7eNQDj; dmarc=fail reason="SPF not aligned (strict)" header.from=posteo.net (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 135.181.149.255 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Migadu-Queue-Id: 9F5383830 X-Spam-Score: 6.54 X-Migadu-Scanner: scn1.migadu.com X-TUID: 8V4G7Ip9mUe4 Justus Winter writes: > David Bremner writes: > >> Justus Winter writes: >> >>> Hello, >>> >>> I just embarrassed myself a little by sending the same mail over and >>> over again. The reason for that is that notmuch-emacs signaled failure, >>> i.e. it displayed an error message in the status buffer and didn't close >>> the compose buffer, yet it did in fact send the mail. >>> >>> I suspect that my configuration has to do with that and someone is >>> trying to be helpful. So I use msmtp with the authentication password >>> encrypted using OpenPGP. Then, I use 'gpg --no-tty -q -d ...' as >>> msmtp's passwordeval function. Now, my OpenPGP key has expired, but >>> that doesn't stop GnuPG from decrypting the secret, and in fact it >>> returns the status code 0. It also prints >>> >>> gpg: Note: secret key 08CC70F8D8CC765A expired at Mon 25 Jul 2022 05:31:26 PM CEST >>> >>> to stderr, which is picked up by notmuch-emacs, it says >>> >>> sending...failed to gpg: Note: secret key 08CC70F8D8CC765A expired at Mon 25 Jul 2022 05:31:26 PM CEST >>> >>> in the status buffer while the compose buffer stays open. >>> >>> I suspect that this is not notmuch's fault, but I don't know where else >>> to turn to with this bug report. >> >> I guess the first step is to see if you can duplicate the problem with >> plain M-x message-mode. The mechanics of sending should be identical in >> notmuch-message-mode unless (surprise!) I misremember something. > > It does indeed happen with the plain message mode. And I think I have > identified the code in emacs that turns any output, stdout and stderr, > into errors: > > % cat -n emacs/lisp/mail/sendmail.el > [...] > 1343 (exit-value (apply #'call-process-region args))) > 1344 (cond ((or (null exit-value) (eq 0 exit-value))) > 1345 ((numberp exit-value) > 1346 (setq error t) > 1347 (error "Sending...failed with exit value %d" exit-value)) > 1348 ((stringp exit-value) > 1349 (setq error t) > 1350 (error "Sending...terminated by signal: %s" exit-value)) > 1351 (t > 1352 (setq error t) > 1353 (error "SENDMAIL-SEND-IT -- fall through: %S" exit-value)))) > 1354 (or fcc-was-found > 1355 (error "No recipients"))) > 1356 (if mail-interactive > 1357 (with-current-buffer errbuf > 1358 (goto-char (point-min)) > 1359 (while (re-search-forward "\n\n* *" nil t) > 1360 (replace-match "; ")) > 1361 (unless (zerop (buffer-size)) > 1362 (setq error t) > 1363 (error "Sending...failed to %s" > 1364 (buffer-substring (point-min) (point-max))))))) > > Apparently, that behavior goes back to the initial checkin of that > file. I refuse to believe that Dan and me are the only ones having > problems with that in 30 years... I'll report it upstream. Can you paste the upstream bug number here as well please? Thanks, Dan