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 5E6D86DE0C69 for ; Wed, 25 Jan 2017 07:17:25 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.555 X-Spam-Level: X-Spam-Status: No, score=-0.555 tagged_above=-999 required=5 tests=[AWL=0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 qExxtaU2hn2G for ; Wed, 25 Jan 2017 07:17:24 -0800 (PST) Received: from mail-pf0-f170.google.com (mail-pf0-f170.google.com [209.85.192.170]) by arlo.cworth.org (Postfix) with ESMTPS id CBB2E6DE0ABE for ; Wed, 25 Jan 2017 07:17:24 -0800 (PST) Received: by mail-pf0-f170.google.com with SMTP id f144so58990734pfa.2 for ; Wed, 25 Jan 2017 07:17:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:user-agent:date :message-id:mime-version; bh=ArIOGBTtUjeFJyyjpyLrHuNkAyav/nrwYcgZ9Vpd/J4=; b=SuMX0dPMHjfjZCPwhXwrHXt7e1l+ZpmiBZJZmEQgJpXNWoHgC7KA/kQcyMnAPsy/DK XLjNinY5qRvEd3qjRb6Th9U0AvyjC52xtnnJ65o3qP9LGn3CE1HBhyev56aGgKeCptr8 NQLlWcF4ZIYCDVo/3MpWAwWz3HKFr1nHMQQbaInBpYn9ls6jLcKjIx7LvAo0ZLpSBWU/ kMGkj0aya0Obc0sskPNWlJ28EN6rrJAdu7wpcF9loHBG9+872RgvlBuOnYUUiwK3ZFfb fIZgCbEGvS3vaN/3pEXwqujEL5PUusE3ORYBIO/RI+k0/ZDjjJVrADoO0B3leACKB19Q e1xA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references :user-agent:date:message-id:mime-version; bh=ArIOGBTtUjeFJyyjpyLrHuNkAyav/nrwYcgZ9Vpd/J4=; b=fhRbWlcX2znegU+mXaQ+4xADQpidqJWRixe/LU+Ip2H37haxnpArf8DYmhqErlL3jd IvYLylkIoGtGkkl0UTdTof0h0tfpAbp65l9WC6qtyLfMwCrLW0OGNq6MJjUm9MrfITHb 9SjBxyRs3z9ywrUvNCm5vVGSzPlp8aHW4KlVzQy/7XCeL7hSZ/2sB4ATqzJwR6KFqY5p qqah0xu+P9GR9O45c0Nsa4BSHaLK8SnACkcNhyuTB7v3lm39c8RzsAiLb91UueJAwYi0 NDEDgXo/No8IkWzeD2x4Qub82xOjOq/H0Z6qPL8aGBgCFVTLkjNCJQfQBaFVM3jhwRjR VnVQ== X-Gm-Message-State: AIkVDXKv1JyTh9BRbPsuFZKf7xKpTbwJBZGbIB5CWdCJ3CehUr3HtSEiDBNDpAu1tVc/Xg== X-Received: by 10.98.61.207 with SMTP id x76mr46680932pfj.152.1485357444209; Wed, 25 Jan 2017 07:17:24 -0800 (PST) Received: from localhost ([59.182.151.219]) by smtp.gmail.com with ESMTPSA id o18sm2030260pgn.36.2017.01.25.07.17.21 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 25 Jan 2017 07:17:22 -0800 (PST) From: Vishal Belsare To: notmuch@notmuchmail.org, Mark Walters Subject: Re: Q: notmuch emacs, fcc, maildir, notmuch insert and message-kill-buffer-on-exit In-Reply-To: <877f5j47h8.fsf@qmul.ac.uk> References: <87efzrgxwx.fsf@gmail.com> <877f5j47h8.fsf@qmul.ac.uk> User-Agent: Notmuch/0.23.5 (https://notmuchmail.org) Emacs/25.1.1 (x86_64-unknown-linux-gnu) Date: Wed, 25 Jan 2017 20:44:45 +0530 Message-ID: <878tpzgoii.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 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: Wed, 25 Jan 2017 15:17:25 -0000 Mark Walters writes: > Hi > > I am not sure what the full problem is (I will try and have a better > look later), but I think the main problem is that the sending mail part > is returning an error. The "Sending...failed to" is coming from emacs, > and I think the "mail for [ -oi -t > ] : send was successful; " from > msmtp/msmptq. Could it be that because the sent messages get queued to msmtpq, it is picked up as an 'error'? If it might help, I can try switching to using msmtp instead of msmtpq and see whether the fcc notmuch insert works and the message buffer is killed. > > The insert is done after the send, so since this returns an error the > insert is never attempted. If that is the case, then perhaps both (1) the insert not happening and (2) the message buffer not being killed after the message being sent, are probably tied to the same underlying issue. Vishal > > Best wishes > > Mark > > -- Vishal Belsare GPG Fingerprint: 9ACC F873 D04E CF71 11DD 4598 28FD 5DF6 BCC8 CB43