exim pipe transport, notmuch insert and mbox-style messages

2014-11-22 Thread Andrei POPESCU
you can't explain it simply, you don't understand it well enough. (Albert Einstein) http://nuvreauspam.ro/gpg-transition.txt -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20141122/f9095b31/attachment-0001.pgp>

[PATCH v2 2/2] test: Add test for correct naming of author.

2014-11-22 Thread Jani Nikula
On Fri, 21 Nov 2014, Jesse Rosenthal wrote: > This is a new test file, since handling of unusual email addresses > doesn't seem to fit well in any of our existing tests. It would be nice to have this as patch 1/2 annotated with "known broken" and have the implementation patch fix it. It's nice

[PATCH v2 1/2] lib: Use email address instead of empty real name.

2014-11-22 Thread Jani Nikula
On Fri, 21 Nov 2014, Jesse Rosenthal wrote: > Currently, if a From-header is of the form: > > "" > > the empty string will be treated as a valid real-name, and the entry > in the search results will be empty. > > The new behavior here is that we treat an empty real-name field as if > it were

exim pipe transport, notmuch insert and mbox-style messages

2014-11-22 Thread David Bremner
Edward Betts writes: > I wonder if 'notmuch insert' could be modified to detect and drop the From_ > line before writing the message to disk and index it. It could do that > silently or with a warning. I don't know about the larger question(s), but I'd suggest just escaping it to something

exim pipe transport, notmuch insert and mbox-style messages

2014-11-22 Thread Edward Betts
My mail arrives on a Debian machine running exim. It was being filtered by procmail then piped into 'notmuch insert'. This was generating the single-message mbox warning: > Warning: ... is an mbox containing a single message, > likely caused by misconfigured mail delivery. Support for

[PATCH v3 2/2] lib: Use email address instead of empty real name.

2014-11-22 Thread Jesse Rosenthal
Currently, if a From-header is of the form: "" the empty string will be treated as a valid real-name, and the entry in the search results will be empty. The new behavior here is that we treat an empty real-name field as if it were null, so that the email address will be used in the search

[PATCH v3 1/2] test: Add known-broken test for empty author name

2014-11-22 Thread Jesse Rosenthal
We test for whether a quoted empty email address "" will show up as the address, instead of the empty string. This is marked as known-broken, since the current behavior is to use the empty string. This is a new test file, since handling of unusual email addresses doesn't seem to fit well

[PATCH v3 0/2] Use email address instead of empty real name.

2014-11-22 Thread Jesse Rosenthal
This version obsoletes [1]. The changes in this version are: * Commit test first with known-broken annotation, and then remove that annotation in the second commit (when the test passes) * Style fixes in the thread.cc to conform with notmuch style. [1]

exim pipe transport, notmuch insert and mbox-style messages

2014-11-22 Thread Edward Betts
My mail arrives on a Debian machine running exim. It was being filtered by procmail then piped into 'notmuch insert'. This was generating the single-message mbox warning: Warning: ... is an mbox containing a single message, likely caused by misconfigured mail delivery. Support for

Re: exim pipe transport, notmuch insert and mbox-style messages

2014-11-22 Thread David Bremner
Edward Betts edw...@4angle.com writes: I wonder if 'notmuch insert' could be modified to detect and drop the From_ line before writing the message to disk and index it. It could do that silently or with a warning. I don't know about the larger question(s), but I'd suggest just escaping it to

Re: [PATCH v2 1/2] lib: Use email address instead of empty real name.

2014-11-22 Thread Jani Nikula
On Fri, 21 Nov 2014, Jesse Rosenthal jrosent...@jhu.edu wrote: Currently, if a From-header is of the form: addr...@example.com the empty string will be treated as a valid real-name, and the entry in the search results will be empty. The new behavior here is that we treat an empty

Re: [PATCH v2 2/2] test: Add test for correct naming of author.

2014-11-22 Thread Jani Nikula
On Fri, 21 Nov 2014, Jesse Rosenthal jrosent...@jhu.edu wrote: This is a new test file, since handling of unusual email addresses doesn't seem to fit well in any of our existing tests. It would be nice to have this as patch 1/2 annotated with known broken and have the implementation patch fix

[PATCH v3 1/2] test: Add known-broken test for empty author name

2014-11-22 Thread Jesse Rosenthal
We test for whether a quoted empty email address addr...@example.com will show up as the address, instead of the empty string. This is marked as known-broken, since the current behavior is to use the empty string. This is a new test file, since handling of unusual email addresses doesn't

[PATCH v3 0/2] Use email address instead of empty real name.

2014-11-22 Thread Jesse Rosenthal
This version obsoletes [1]. The changes in this version are: * Commit test first with known-broken annotation, and then remove that annotation in the second commit (when the test passes) * Style fixes in the thread.cc to conform with notmuch style. [1]

[PATCH v3 2/2] lib: Use email address instead of empty real name.

2014-11-22 Thread Jesse Rosenthal
Currently, if a From-header is of the form: addr...@example.com the empty string will be treated as a valid real-name, and the entry in the search results will be empty. The new behavior here is that we treat an empty real-name field as if it were null, so that the email address will be

Re: exim pipe transport, notmuch insert and mbox-style messages

2014-11-22 Thread Andrei POPESCU
On Sb, 22 nov 14, 10:44:45, David Bremner wrote: Edward Betts edw...@4angle.com writes: I wonder if 'notmuch insert' could be modified to detect and drop the From_ line before writing the message to disk and index it. It could do that silently or with a warning. I don't know about