--- /dev/null
+Return-Path: <fauno@ponape.com.ar>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 3D0126DE17A1\r
+ for <notmuch@notmuchmail.org>; Wed, 30 Dec 2015 06:14:22 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.618\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.618 tagged_above=-999 required=5 tests=[AWL=0.034,\r
+ DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.55,\r
+ SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id oClMr9Lzc2J0 for <notmuch@notmuchmail.org>;\r
+ Wed, 30 Dec 2015 06:14:20 -0800 (PST)\r
+Received: from ponape.com.ar (ponape.com.ar [190.104.249.150])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id A77D26DE179F\r
+ for <notmuch@notmuchmail.org>; Wed, 30 Dec 2015 06:14:19 -0800 (PST)\r
+Received: by [127.0.0.1] (localhost [127.0.0.1])\r
+ id 2363CC64F7; Wed, 30 Dec 2015 11:14:13 -0300 (ART)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kiwwwi.com.ar;\r
+ s=ponape; t=1451484853;\r
+ bh=TLiUgcqiRJlKyCSkjYYpJNgRYZJT33iv+Z6K4MFPVc0=;\r
+ h=From:To:Subject:In-Reply-To:References:Date;\r
+ b=mBw0hk3IyZd6pO1J6ytpNldNqdLqRDTMVKQ3ZJ6DzoKupp6tB8ZO9v302tlFCnUmw\r
+ O9Pu/iIv8MjVOAiW81HgH0XzbdErHm6Sm7z1BDPiMgR8hCH0AolxVF6EqjHE2nedn/\r
+ fx35k/w+byNnVI4eryMG+EmvlMUfcdsCu8bcRujEsBQC33axEAL2ahfNCFwqcN5QdB\r
+ IUir9NXwHgXUIaIah0NPsrhXNgvQfErGmb1ABGo8WuIJz4HivC/D7kaTXkV68+SCwm\r
+ ejh9k4659GlCEnWQ8kN3jtmXsrfNwljkijI5kh29lipi4eUsfOW11ghZ+4cRI/sS1U\r
+ hhVrGMsQHpLyw==\r
+From: fauno <fauno@kiwwwi.com.ar>\r
+To: notmuch@notmuchmail.org\r
+Subject: notmuch-mua and jl-encrypt (was: file-error "not a regular file")\r
+In-Reply-To: <8737ukcm41.fsf@steelpick.2x.cz>\r
+References:\r
+ <CAE+_6Tw18LY954NZt+koH-mn=nniubVdk4tR8TSitDy_6wJB2Q@mail.gmail.com>\r
+ <87wprzb4sj.fsf@endefensadelsl.org> <87ege6d41j.fsf@zancas.localnet>\r
+ <878u4e9jkx.fsf@endefensadelsl.org> <8737ukcm41.fsf@steelpick.2x.cz>\r
+Mail-Followup-To: notmuch@notmuchmail.org\r
+Date: Wed, 30 Dec 2015 11:14:12 -0300\r
+Message-ID: <87k2nw6n2j.fsf@endefensadelsl.org>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+ micalg=pgp-sha512; protocol="application/pgp-signature"\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 30 Dec 2015 14:14:22 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+Michal Sojka <sojkam1@fel.cvut.cz> writes:\r
+> can you share more details about how do you use jl-encrypt and which\r
+> functions do not work? Recently, I posted a few patches that fix some\r
+> problems related to the replacing message-mode with\r
+> notmuch-message-mode. Maybe, there is more what we can do to not break\r
+> user's setups.\r
+\r
+i've been using jl-encrypt unmodified with notmuch for a while now. i\r
+just require it on my .emacs\r
+\r
+since 0.21, i had to rebind notmuch-message-mode C-c C-c and C-s C-s\r
+keys:\r
+\r
+(define-key notmuch-message-mode-map (kbd "C-c C-c") 'jl-message-send-and-e=\r
+xit)\r
+(define-key notmuch-message-mode-map (kbd "C-c C-s") 'jl-message-send)\r
+\r
+and solved the issue of fcc by setting notmuch-fcc-dirs to nil and\r
+making my mta send me bcc of my own email.\r
+\r
+this has worked correctly for the last week.\r
+\r
+> From a brief look at jl-encrypt, it seems it is tightly bound to gnus,\r
+> because it uses gnus-message-setup-hook. Maybe it will work again with\r
+> notmuch if you use my patch [1] and run\r
+>\r
+> (add-hook 'message-setup-hook 'jl-encrypt-if-possible)\r
+\r
+i applied your patch to the 0.21 release and byte-compiled notmuch-mua.el\r
+\r
+the message is sent unencrypted unless i rebind C-c C-c as before. the\r
+email is encrypted but it asks for the recipient, which i'm guessing\r
+emacs can't figure out for itself anymore?\r
+\r
+also tested with `emacs -q` and loading this file, and jl-encrypt never\r
+asks to encrypt the email when possible:\r
+\r
+# /tmp/emacs\r
+\r
+(require 'notmuch)\r
+(add-to-list 'load-path "~/.emacs.d/lisp/")\r
+(require 'jl-encrypt)\r
+(add-hook 'message-setup-hook 'jl-encrypt-if-possible)\r
+(add-hook 'message-setup-hook 'mml-secure-message-sign-pgpmime)\r
+\r
+by adding the C-c C-c rebind, it gets to encrypt, but asks for recipient\r
+again.\r
+\r
+i hope this info is useful :)\r
+\r
+> -Michal\r
+>\r
+> [1] id:1450690875-2111-2-git-send-email-sojkam1@fel.cvut.cz\r
+\r
+=2D-=20\r
+:D\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature; name="signature.asc"\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+\r
+iQF8BAEBCgBmBQJWg+a0XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w\r
+ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0OUY3MDdBMUNCMzY2QzU4MEU2MjVCM0M0\r
+NTYwMzJENzE3QTRDRDlDAAoJEEVgMtcXpM2cMIcH/RwnnJLA1khr9CUx59TMec/t\r
+nLQy6pqpv2FIArrq1Bp2UXJb2Ths2O50WnSYHxLTiA6un4nZB+ePk60JFnwTr9nv\r
+zLSo3yu2fXdOhAReBE/6Lg5LwQnUxXTCICeOxpCuSuxhwE01z9q/Fm4cX54DUQXR\r
+LTNqHcXgAevp//2yMDnuP+swMLcmJBUFNIlXjOWncwN7Bum5E1cnedIDLZU/Eh/g\r
+CGU0QM+dgvgDEXBKJSkoso0r+d8NcQqBVSGa84tUwvDAUpHy9SeS5tcdv2tcxa2K\r
+WWC3RlnhGKKIZAFWBSMzj0uhK0N8q6w+wmcw70AWznVU043YE3j6MuGk+vVI7iE=\r
+=Hye6\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r
projects / notmuch-archives.git / commitdiff