Inline-encryption, encryption failure when storing sent mails

Simon Hirscher writes: > Hey there, > > I'm quite new to notmuch and have two questions regarding the state of > mail encryption: > > 1. Support for inline-encryption As far as I can see, so far only > encrypted mails with PGP/MIME are supported. Couldn't notmuch also > support text/plain

Inline-encryption, encryption failure when storing sent mails

On Fri, Aug 16, 2013 at 10:02 AM, David Bremner wrote: > What about setting this on the gpg level with the "encrypt-to" option? > Setting the emacs variable mml2015-encrypt-to-self seems like it ought > to work, but it seems to need some other settings as well. Perhaps have > a look at the

Solaris support - missing or incompatible functions

Hi, > > > I didn't pay too much attention to the test output as it's broken on > > > linux too :) > > > > It shouldn't be. All tests pass for me, and we're pretty strict about > > maintaining that. > > > > There may be some prerequisites to running tests that you're missing, > > and the test

Solaris support - missing or incompatible functions

On Fri, Aug 16 2013, Vladimir Marek wrote: > Hi, > >> > > I didn't pay too much attention to the test output as it's broken on >> > > linux too :) >> > >> > It shouldn't be. All tests pass for me, and we're pretty strict about >> > maintaining that. >> > >> > There may be some prerequisites to

[PATCH v2 2/3] reply: Remove extraneous space from generated References

On Thu, 15 Aug 2013, Austin Clements wrote: > Previously, the References header code seemed to assume > notmuch_message_get_header would return NULL if the header was not > present, but it actually returns "". As a result of this, it was > inserting an unnecessary space when concatenating an

Solaris support - missing or incompatible functions (v2)

Hi, I'm re-sending the patches which were rebased to current top of the tree. Apart from rebasing there has been no change made. I am using this notmuch for half a year and it seems to work fine. As I said in my previous email, not all the tests pass, but I know that the failures in the testing

[PATCH 2/4] asctime: check for standards compliance (Solaris support)

From: Vladimir Marek Add checks to "configure" to see whether _POSIX_PTHREAD_SEMANTICS needs to be defined to get the right number of arguments in the prototypes for asctime_r(). Solaris' default implementation conforms to POSIX.1c Draft 6, rather than the final POSIX.1c spec.

[PATCH 1/4] getpwuid: check for standards compliance (Solaris support)

From: Blake Jones Add checks to "configure" to see whether _POSIX_PTHREAD_SEMANTICS needs to be defined to get the right number of arguments in the prototypes for getpwuid_r(). Solaris' default implementation conforms to POSIX.1c Draft 6, rather than the final POSIX.1c spec.

[PATCH 4/4] timegm: add portable implementation (Solaris support)

From: Blake Jones The timegm(3) function is a non-standard extension to libc which is available in GNU libc and on some BSDs. Although SunOS had this function in its libc, Solaris (unfortunately) removed it. This patch implements a very simple version of timegm() which is good

[PATCH 3/4] strsep: check for availability (Solaris support)

From: Blake Jones Solaris does not ship a version of the strsep() function. This change adds a check to "configure" to see whether notmuch needs to provide its own implementation, and if so, it uses the new version in "compat/strsep.c" (which was copied from Mutt, and apparently

[PATCH v2 2/3] reply: Remove extraneous space from generated References

Quoth Jani Nikula on Aug 16 at 5:19 pm: > On Thu, 15 Aug 2013, Austin Clements wrote: > > Previously, the References header code seemed to assume > > notmuch_message_get_header would return NULL if the header was not > > present, but it actually returns "". As a result of this, it was > >

[PATCH v3 0/3] Clean up reply's encoding story

This is v3 of id:1376587658-19202-1-git-send-email-amdragon at mit.edu. This addresses Jani's comment in id:87k3jl3ehe.fsf at nikula.org by treating errors while retrieving the original message's References header as if the original message didn't have a References header. It also adds a comment

[PATCH v3 1/3] reply: Test replying to messages with RFC 2047-encoded headers

--- test/reply | 56 1 file changed, 56 insertions(+) diff --git a/test/reply b/test/reply index ee5d361..c877ffe 100755 --- a/test/reply +++ b/test/reply @@ -193,4 +193,60 @@ References: <${gen_msg_id}> On Tue, 05 Jan 2010 15:43:56

[PATCH v3 2/3] reply: Remove extraneous space from generated References

Previously, the References header code seemed to assume notmuch_message_get_header would return NULL if the header was not present, but it actually returns "". As a result of this, it was inserting an unnecessary space when concatenating an empty or missing original references header with the new

[PATCH v3 3/3] reply: Use RFC 2822/MIME wholly for text format template

Previously, reply's default text format used an odd mix of RFC 2045 MIME encoding for the reply template's body and some made-up RFC 2822-like UTF-8 format for the headers. The intent was to present the headers to the user in a nice, un-encoded format, but this assumed that whatever ultimately

[PATCH v3 0/3] Clean up reply's encoding story

On Fri, 16 Aug 2013, Austin Clements wrote: > This is v3 of id:1376587658-19202-1-git-send-email-amdragon at mit.edu. > This addresses Jani's comment in id:87k3jl3ehe.fsf at nikula.org by > treating errors while retrieving the original message's References > header as if the original message