On Mon, Jan 15, 2024 at 08:35:37PM -0400, David Bremner wrote:
> HGV writes:
>
> > Does anyone have experience syncing the notmuch database or an entire
> > maildir directory via iCloud? I keep most of my email archive offline
> > but since iCloud added end-to-end encryption, I've considered sy
HGV writes:
> Does anyone have experience syncing the notmuch database or an entire
> maildir directory via iCloud? I keep most of my email archive offline
> but since iCloud added end-to-end encryption, I've considered syncing my
> archived mail and notmuch database via iCloud. But I'm worrie
Sławomir Grochowski writes:
> Dear All,
>
> I just have started using notmuch with Emacs.
>
> When I run `notmuch-poll-and-refresh-this-buffer` which run script
> '.notmuch/hooks/pre-new':
>
> #!/bin/sh
> mbsync -L gmail
>
> Most of the time it gives me an error & message:
> "notmuch-search: not
Does anyone have experience syncing the notmuch database or an entire
maildir directory via iCloud? I keep most of my email archive offline
but since iCloud added end-to-end encryption, I've considered syncing my
archived mail and notmuch database via iCloud. But I'm worried that
iCloud might i
Am Di., 9. Jan. 2024 um 13:38 Uhr schrieb David Bremner :
>
> Michael J Gruber writes:
>
> >>
> >> I agree the bindings documentation does not make much sense. I suspect
> >> that the bindings should follow the underlying library and return "" if
> >> the library does. I don't use the bindings t
Michael J Gruber writes:
>>
>> I agree the bindings documentation does not make much sense. I suspect
>> that the bindings should follow the underlying library and return "" if
>> the library does. I don't use the bindings that much, so I am curious
>> what others think.
>
> I might be misunder
Am Di., 9. Jan. 2024 um 00:09 Uhr schrieb David Bremner :
>
> Vojtěch Káně writes:
>
> > At first, this sounds reasonable: the subject is empty, so it is
> > effectively missing. That would indicate a bug in Lieer itself and would
> > be fixed by a try-catch block. Notmuch's source for Message.hea
Vojtěch Káně writes:
> At first, this sounds reasonable: the subject is empty, so it is
> effectively missing. That would indicate a bug in Lieer itself and would
> be fixed by a try-catch block. Notmuch's source for Message.header,
> however, states:
>
>>:returns: The header value, an empty s
Thanks for your suggestion! This doesn't work unfortunately because the author
string doesn't contain the email addresses, i.e. no @ symbols (unless somebody
includes that in their name).
Cheers,
Lars
On Fri, 22 Dec 2023 23:24:37 +0100, Sandra Snan
wrote:
> Curses, flowed again! I'm just go
Curses, flowed again! I'm just gonna attach the file
email_list = "Diaz, Marco , s...@mewni.com, Marco Diaz , s...@mewni.com"
addresses = []
current_address = ""
for char in email_list:
if char == ',' and '@' in current_address:
addresses.append(current_address.strip())
curre
Lars Kotthoff writes:
Python […] I have to split the returned string, which is
error-prone with comma separators (e.g. name in email address is
of form Lastname, Firstname).
email_list = "Diaz, Marco , s...@mewni.com, Marco
Diaz , s...@mewni.com" addresses = []
current_address = "" for ch
Lars Kotthoff writes:
Python […] I have to split the returned string, which is
error-prone with comma separators (e.g. name in email address is
of form Lastname, Firstname).
email_list = "Diaz, Marco , s...@mewni.com, Marco
Diaz , s...@mewni.com" addresses = []
current_address = "" for ch
David Bremner writes:
probably not out of the box, but I guess it might be easier to
hack notmuch-extract-* on the emacs side than to extend 'notmuch
show --format=mbox'
Those elpa-mailscripts also rely on calling notmuch show
--format=mbox.
The elisp files (similar to what I had been usin
Sandra Snan writes:
> David Bremner writes:
>> By the way, the mailscripts package (elpa-mailscripts on Debian)
>> contains some some add-on functions that might reduce the manual
>> labour in situations like this.
>
> That's what I had been using, do they really work when the patches
> are
David Bremner writes:
By the way, the mailscripts package (elpa-mailscripts on Debian)
contains some some add-on functions that might reduce the manual
labour in situations like this.
That's what I had been using, do they really work when the patches
are encrypted?
I've been trying to go
Sandra Snan writes:
> Finally saving the patches one by one with w in the Emacs interface to
> notmuch gave me patches I could apply. (Just in case someone else
> searches the mailing list for the same issue.)
By the way, the mailscripts package (elpa-mailscripts on Debian)
contains some some ad
Sandra Snan writes:
> David Bremner writes:
>> I guess we could add a second code path that parsed and
>> decrypted the messages before re-serializing them again.
>
> Or, as a stop gap measure, a warning when the flags are used
> together that mbox doesn't support
Sandra Snan writes:
> I did not run configure again, I just went straight to make. I'd think
> that after 20 years of using autotools I wouldn't make that mistake
> but that's what I found when I scrolled back up the buffer and looked
> more carefully.
Sounds like it's working for you now. I gu
David Bremner writes:
I guess we could add a second code path that parsed and
decrypted the messages before re-serializing them again.
Or, as a stop gap measure, a warning when the flags are used
together that mbox doesn't support decrypt.
I tried decrypting the pgp'd parts o
David Bremner writes:
Fair enough, but can you try without sudo to try to narrow down
where the issue is?
I found the problem. Sudo wasn't the issue. It was that after
./configure had failed to find some of the build deps and asked me
to
sudo apt-get install libxapian-dev libgmime-3.0-
t; patches.
Hmm. The code (format_part_mbox in notmuch-show.c) is pretty simple, it
basically reads the raw messages (up to gunzip and '^From ' escaping. I
guess we could add a second code path that parsed and decrypted the
messages before re-serializing them again. At the moment I don't have
Sandra Snan writes:
> I used sudo for the install because /tmp/ isn't gonna be my
> ultimate destdir and I don't want my own user to own these files,
> root should own them. I was planning to use fpm in --dir mode.
> Although I didn't get that far because it instead installed into
> /usr/loca
David Bremner writes:
I can't duplicate that on Debian testing with GNU Make.
I was using zsh in Emacs shell mode on Debian GNU/Linux 12
(bookworm) with GNU Make 4.3.
FWIW, it should not be required to use sudo to install into /tmp
(but as far as I know it should work).
I used sudo for
Sandra Snan writes:
> I just ran
>
> ./configure --prefix=/tmp/notmuch
> make
> sudo make install
>
> It clobbered /usr/local instead of installing to the prefix.
I can't duplicate that on Debian testing with GNU Make. FWIW, it should
not be required to use sudo to install into /tmp
Sandra Snan writes:
> This hook is run after `notmuch reply` has been successfully called
> with the headers from the original message.
It seems like the commit message should be updated to match the changes
in the patch. With my "editor" hat on, it's also a bit ambigous what
"with the headers
On 12/12/23 20:25, Michael J Gruber wrote:
The manual is not overly clear about the interaction between this config
and flag sync, but AFAIU, `notmuch new` sets `unread` and then possibly
unsets it during the flag sync (maybe in one atomic db write, i.e. you
don't see this). By removing `unread
https://lists.sr.ht/~pkal/public-inbox/patches/47695 <- This is what the
hook was for.
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
Am Di., 12. Dez. 2023 um 10:58 Uhr schrieb Andrew Todd :
> Hello,
>
> I'm trying to set up notmuch, and I think that the behavior I want
> should be possible (and is desirable), but I can't seem to make it work.
> I also can't find any reference online suggesting that it *shouldn't*
> work, and I
On Mon, Dec 11 2023, Sandra Snan wrote:
> This hook is run after `notmuch reply` has been successfully called
> with the headers from the original message.
> ---
> emacs/notmuch-mua.el | 17 -
> 1 file changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/emacs/notmuch-mua.el
I missed the other notes. I'll do a v3 renaming to
notmuch-mua-reply-functions.
The reason I need message-id is because I need to call notmuch
again to get other headers beyond what's included in the sexp,
including autocrypt.
But the suggestion to jam the entire sexp is good. I did that for
Tomi Ollila writes:
>
> another thing what should be the parameters passed, and why. this change
> adds (just) message-id but no reasoning (nor documentation) there...
>
I wonder if we should pass the whole (parsed) original message, for
maximum flexibility?
__
On Mon, Dec 11 2023, David Bremner wrote:
> Sandra Snan writes:
>
>
>> +(defvar in-notmuch-mua-reply-functions nil
>> + "Functions to run after `notmuch-reply' was called successfully
>> +without erroring. The functions get the message-id as a string
>> +argument.")
>> +
>
> Overall this looks r
Sandra Snan writes:
> +(defvar in-notmuch-mua-reply-functions nil
> + "Functions to run after `notmuch-reply' was called successfully
> +without erroring. The functions get the message-id as a string
> +argument.")
> +
Overall this looks reasonable to me, but I'm not sure about the
name. Since
Giovanni Biscuolo writes:
> A previous running generation is using emacs 29.1 with company 0.9.13.
>
> It seems an incompatibility with company 0.10.2, no?
>
Seems likely. I have 0.10.0 running OK here.
If you are feeling motivated, you could try bisecting between 10.0 and 10.2
Hi David,
thank you for your quick reply!
David Bremner writes:
> Giovanni Biscuolo writes:
>
>> Hello,
>>
>> I recently upgraded my emacs applications, I'm using Guix as package
>> manager on Debian.
>>
>
> What versions of emacs and company are you using?
Uh, sorry for not reporting it befo
Giovanni Biscuolo writes:
> Hello,
>
> I recently upgraded my emacs applications, I'm using Guix as package
> manager on Debian.
>
What versions of emacs and company are you using?
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send
This thread inspired me to look a little more deeply into the address
completion issues I've been having since switching to corfu as well. It
was a rather long and twisted journey but I ended up getting completion
using corfu working with the following in my init file:
;; Make corfu-based a
Thank you, Sandra! With your advice, I was able to figure out that corfu
was overriding the Tab key from notmuch. If I disable it,
notmuch-address-expand-name works (with orderless and vertico). I'll see
if I can find a way to pipe it into corfu somehow.
Sandra Snan writes:
> David, I have messa
David, I have message-completion-alist set to this value:
(("^\\(Resent-\\)?\\(To\\|B?Cc\\|Reply-To\\|From\\|Mail-Followup-To\\|Mail-Copies-To\\):"
. notmuch-address-expand-name)
("^\\(Newsgroups\\|Followup-To\\|Posted-To\\|Gcc\\):" .
message-expand-group) ("^\\([^ :]*-\\)?\\(To\\|B?Cc\\|Fro
On Wed, Dec 06, 2023 at 03:07:08PM +0800, io wrote:
> i like to know how do we use 'FLAG_FUZZY' if one need to use 'quest'
> to do the search query.
E.g. this will match a document indexed by term "fuzzy":
quest --flags=default,fuzzy --db=/path/to/db 'phuzzy~'
Default edit distance is 2, but you
Alyssa Ross writes:
> David Bremner writes:
>
>> Hi Alyssa
>>
>> I'm not sure if this is a fix for your bug, but it is a fix for a
>> very similar bug.
>
> This is a fix for my bug, thanks a lot!
>
> Tested-by: Alyssa Ross
Applied to release and master. Planning another point release, let me
i like to know how do we use 'FLAG_FUZZY' if one need to use 'quest' to do the
search query.
--
Best regards,
io
On Mon, Dec 04, 2023 at 05:10:57PM -0400, David Bremner wrote:
> Olly Betts writes:
>
> > The development version of Xapian supports both `*` and `?` glob-style
> > wildcards in an
Olly Betts writes:
> The development version of Xapian supports both `*` and `?` glob-style
> wildcards in any position.
>
> You can enable them for the QueryParser using FLAG_WILDCARD_MULTI,
> FLAG_WILDCARD_SINGLE or FLAG_WILDCARD_GLOB (the last one is just the
> first two combined).
I see FLAG
On Mon, Dec 04, 2023 at 06:39:43AM -0500, David Bremner wrote:
> I guess the restriction is based on what is easy to do efficiently with
> the Xapian database (find prefixes). If I remember correctly there was
> some work in progress to support leading wildcards in Xapian. I can't
> find relevant
io writes:
> what xapian 'indexing system' did was to index the entire sentence
> 'xxx_yyy' and you will not be able to find any sentence which contain
> the word 'yyy'?
I'm curious that you refer to xxx_yyy as a sentence. In the contexts I
am familiar with, the point of _ is to join things toge
what xapian 'indexing system' did was to index the entire sentence 'xxx_yyy'
and you will not be able to find any sentence which contain the word 'yyy'?
xapian should have this simple wildcard feature which 'grep'(search) offer.
($grep '*word*' file). It is strange that xapian restrict the search
David Bremner writes:
> Hi Alyssa
>
> I'm not sure if this is a fix for your bug, but it is a fix for a
> very similar bug.
This is a fix for my bug, thanks a lot!
Tested-by: Alyssa Ross
signature.asc
Description: PGP signature
___
notmuch mailing
On Saturday, December 2nd, 2023 at 4:49 PM, David Bremner
wrote:
> Unfortunately there are likely to be inconsistencies between those
> fields supporting regex queries (like from) and "true" probabilistic
> prefixes.
Thanks. Yes, I expected this to be at play.
> The sexp query parser should not
David Bremner writes:
> Alyssa Ross writes:
>
>> Since commit 1c10d91d ("Pass error message from GLib ini parser to CLI"),
>> when I run "notmuch config list", I get this error message at the start
>> of the output:
>>
>> Error: Cannot open database at /home/qyliss/state/notmuch/default: No
Alyssa Ross writes:
> Since commit 1c10d91d ("Pass error message from GLib ini parser to CLI"),
> when I run "notmuch config list", I get this error message at the start
> of the output:
>
> Error: Cannot open database at /home/qyliss/state/notmuch/default: No
> such file or directory.
>
>
"artur.brzozowski" writes:
> Hey,
>
> Trying to add List matching to my notmuch tagging and I found
> something that surprises me. Namely,
This is a duplicate message, my fault, I saw it in the moderation queue,
didn't realize it already went to the list.
d
_
"artur.brzozowski" writes:
> Hi!
>
> Trying to add List matching to my notmuch tagging and I found
> something that surprises me. Namely,
>
> 1) when I want to match a bunch of alternatives for
> prefix, I have to quote the parenthesis to get the results:
>
> $ notmuch search 'from:"(b...@some.i
Jani Nikula writes:
> Currently the --to/--cc/--bcc options add "u...@example.com, " to the
> message headers, with the the unnecessary ", " separator after the
> last address, regardless of how many addresses are being added.
>
> This used to be fine, but with recent emacs mm, trying to send the
On Thu, Nov 30 2023, Jani Nikula wrote:
> Currently the --to/--cc/--bcc options add "u...@example.com, " to the
> message headers, with the the unnecessary ", " separator after the
> last address, regardless of how many addresses are being added.
>
> This used to be fine, but with recent emacs mm,
Michael J Gruber writes:
> Using xapian commands, one could extract all stems and grep those for a
> term which one "remembers partially" (often happened to me), and then feed
> that into notmuch. Might be worthwhile scripting or even integrating into
> notmuch (sexp?).
The words are stored uns
Am Do., 30. Nov. 2023 um 12:37 Uhr schrieb io :
>
>
>
> i have an html email with this sentence 'xycfe11cg64d_2501034012' within
> the body of the message.
> no result found when i search for '2501034012'
> i have even tried using '*2501034012*' (wildcard)
>
> Notmuch doesn't support regular expre
On Mon, Nov 27 2023, Caleb Herbert wrote:
> Hi,
Hi Caleb,
> I have a stupid newbie question.
No problem at all.
> I just started using Notmuch, opened my email in Emacs, and was
> bombarded by a bunch of old mail. My email was perfectly sorted in
> Icedove (Thunderbird) before I made the switc
Tomi Ollila writes:
> On Sat, Nov 25 2023, David Bremner wrote:
>
>> qsort(3) does not promise stability, and recent versions of glibc have
>> been showing more unstable behaviour [2]. Michael Gruber observed [1] test
>> breakage due to changing output order for message properties.
>>
>> We provi
On Sat, Nov 25 2023, David Bremner wrote:
> qsort(3) does not promise stability, and recent versions of glibc have
> been showing more unstable behaviour [2]. Michael Gruber observed [1] test
> breakage due to changing output order for message properties.
>
> We provide a sorting order of (key,val
Reto writes:
[thanks for the explanation of how aerc uses notmuch]
>
> Go will execute a C compiler / linker as usual.
> In your case, you basically need to setup 2 things:
>
> 1) notmuch.h in some include dir, normally /usr/include/notmuch.h or
> some such,
> which is needed by the
Hi both,
I realize I am a bit late to the party, nevertheless here's some information.
> I'm trying to build an email client (aerc) with support for notmuch
> on macOS. aerc is written in go. I can't find an aerc package for brew
> which includes notmuch headers/library files. Where can I get the
On Fri, Nov 24 2023, Michael J. Gruber wrote:
> So, with the key-value pairs sorted by both, I resumed testing for Python
> 3.1.13 and encountered failing T380 which gave me some a deja-vue due to
> its confusing messages:
>
> ```
> T380-atomicity: Testing atomicity
> cat: outcount: No such file o
So, with the key-value pairs sorted by both, I resumed testing for Python
3.1.13 and encountered failing T380 which gave me some a deja-vue due to
its confusing messages:
```
T380-atomicity: Testing atomicity
cat: outcount: No such file or directory
/builddir/build/BUILD/notmuch-0.38.1/test/T380-a
Am Fr., 24. Nov. 2023 um 14:57 Uhr schrieb David Bremner :
> Michael J Gruber writes:
>
> > Hi there,
> >
> > during my first tests for Python 3.13 (hooray...) I noticed that some
> tests
> > in T610 started to fail independent of that. It seems that with notmuch
> > 0.38.1 on current Fedora rawh
* David Bremner:
> Michael J Gruber writes:
>
>> during my first tests for Python 3.13 (hooray...) I noticed that some tests
>> in T610 started to fail independent of that. It seems that with notmuch
>> 0.38.1 on current Fedora rawhide, `notmuch_message_get_properties()`
>> returns properties in
Michael J Gruber writes:
> Hi there,
>
> during my first tests for Python 3.13 (hooray...) I noticed that some tests
> in T610 started to fail independent of that. It seems that with notmuch
> 0.38.1 on current Fedora rawhide, `notmuch_message_get_properties()`
> returns properties in a differen
David Bremner writes:
> Michael J Gruber writes:
>
>> during my first tests for Python 3.13 (hooray...) I noticed that some tests
>> in T610 started to fail independent of that. It seems that with notmuch
>> 0.38.1 on current Fedora rawhide, `notmuch_message_get_properties()`
>> returns propert
Michael J Gruber writes:
> during my first tests for Python 3.13 (hooray...) I noticed that some tests
> in T610 started to fail independent of that. It seems that with notmuch
> 0.38.1 on current Fedora rawhide, `notmuch_message_get_properties()`
> returns properties in a different order, while
On Tue, Nov 21 2023, Peter Lawrence wrote:
> Thanks for the feedback, Carl!
No problem. I'm glad you were able to push even a little past what I was
able to do.
> I have a feeling now that this isn't just a macOS issue, but possibly a
> broader issue that would effect anyone using a newer version
On Tue Nov 21, 2023 at 2:19 PM EST, Carl Worth wrote:
> On Sun, Nov 19 2023, Peter Lawrence wrote:
> > Hi.
>
> Hi Peter!
>
> > I'm trying to build an email client (aerc) with support for notmuch
> > on macOS. aerc is written in go. I can't find an aerc package for brew
> > which includes notmuc
On Sun, Nov 19 2023, Peter Lawrence wrote:
> Hi.
Hi Peter!
> I'm trying to build an email client (aerc) with support for notmuch
> on macOS. aerc is written in go. I can't find an aerc package for brew
> which includes notmuch headers/library files. Where can I get these
> language bindings
Ryan Tate writes:
> Jonas Bernoulli writes:
>
>> - -(defun notmuch-tree-close-message-pane-and (func) - "Close
>> message pane and execute FUNC.
>
> I am confused why a function used in config files and documented
> on the notmuch website (to this moment) as an example of how to
> configure
> On Oct 28, 2023, at 5:32 AM, Michael J Gruber
>
> Maybe you can help us by rephrasing your complaints into suggestions for
> documentation updates, and thus help others getting less confused?
I’ve updated the documentation before when I discovered changes after the fact,
in coordination w
ing
> it and having that configuration continue to work. It's not like it was
> remotely easy getting that config setup in the first place.
> _______
>
With all due respect, I suggest you try to (re-)read your posts again
through the eyes
Jonas Bernoulli writes:
- -(defun notmuch-tree-close-message-pane-and (func) - "Close
message pane and execute FUNC.
I am confused why a function used in config files and documented
on the notmuch website (to this moment) as an example of how to
configure something would be removed, and
Ryan Tate writes:
David Bremner writes:
Firmin Martin writes:
For now, I can sort my email newest-first by customized the
variable. But I would prefer to use setq if possible.
It's a buffer-local variable, so you should use setq-default.
I don't understand anything about this reply
David Bremner writes:
Firmin Martin writes:
For now, I can sort my email newest-first by customized the
variable. But I would prefer to use setq if possible.
It's a buffer-local variable, so you should use setq-default.
I don't understand anything about this reply.
1. If I don't wa
Paul Wise writes:
> Fixes: commit 239fdbbbf0cbd6cd6ebafb87e88cdb3cded75364
> ---
> contrib/notmuch-mutt/notmuch-mutt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/contrib/notmuch-mutt/notmuch-mutt
> b/contrib/notmuch-mutt/notmuch-mutt
> index 1ac68065..b81252c8 100755
On Thu, Oct 12 2023, Paul Wise wrote:
> Fixes: commit 239fdbbbf0cbd6cd6ebafb87e88cdb3cded75364
> ---
> contrib/notmuch-mutt/notmuch-mutt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/contrib/notmuch-mutt/notmuch-mutt
> b/contrib/notmuch-mutt/notmuch-mutt
> index 1ac680
Tomi Ollila writes:
> On Fri, Oct 06 2023, David Bremner wrote:
>
>> This is almost all docstring formatting, except for the last
>> patch.
>>
>> This is really just some low hanging fruit, but presumable eliminating
>> some warnings is better than nothing. The warnings are more annoying
>> now t
On Fri, Oct 06 2023, David Bremner wrote:
> This is almost all docstring formatting, except for the last
> patch.
>
> This is really just some low hanging fruit, but presumable eliminating
> some warnings is better than nothing. The warnings are more annoying
> now that native compilation exposes
chnically feasible, but would involve some
> elisp programming, would be to write a command that re-applies the
> calculation of Fcc from From that already exists, and run that manually
> or perhaps opt-in to running it automatically on send.
Thank you for the hints. I followed your hint and r
Michael J Gruber writes:
> Am So., 1. Okt. 2023 um 13:13 Uhr schrieb David Bremner :
>>
>> I have applied this series to release and master (and uploaded a
>> pre-release for 0.38.1)
>
> Is "pre" the new "rc", or how is this supposed to sort?
>
> Michael
sorry about that. yeah, luckily rc1 sorts
Am So., 1. Okt. 2023 um 13:13 Uhr schrieb David Bremner :
>
> I have applied this series to release and master (and uploaded a
> pre-release for 0.38.1)
Is "pre" the new "rc", or how is this supposed to sort?
Michael
___
notmuch mailing list -- notmuch@
David Bremner writes:
> This obsoletes the series
>
> id:20230916235137.334886-2-da...@tethera.net
>
> The update consists of the following bugfix:
>
I have applied this series to release and master (and uploaded a
pre-release for 0.38.1)
d
___
n
Jesse Rosenthal writes:
>
> Depending on how long the scan takes, getmail might pull down both of
> these emails. The second duplicate is available through the emacs change
> index command, but the attachment is not available (since it tries to
> pull the first attachment from the first version,
* 2023-09-27 13:48:50-0300, David Bremner wrote:
> By the way, if using the emacs front-end did you try the unthreaded
> view (U)? That would at least mitigate damage from people replying to
> the poisoned messages.
I didn't. So thanks for reminding about the unthreaded view. It is a
nice fallbac
Teemu Likonen writes:
> Some person on debian-user mailing list seems to be sending messages
> with fixed Message-ID field: the same ID in different messages. In
> Notmuch it is creating trouble because it connects unrelated threads to
> one. The person has different messages in different threads
Teemu Likonen writes:
> Will Notmuch also break the thread so that this edited message will
> start a new thread? Maybe the message itself but its follow-ups need to
> be fixed too. Often "References" points several earlier messages in the
> chain. So, to detach a subthread from bigger thread wou
Andreas Kähäri writes:
> [...]
>> > stupid "external message" headers added by malicious^Wcorporate mail
>> > servers, etc...
>>
>> Headers would not "muddy the waters" since they are headers. In my mind,
>> the hash would be over the body only.
>
> Hi, I'm not really part of the discussion, but
at least *see* the different variant forms of a given
message by cycling through the list of duplicates (e.g. via
notmuch-show-choose-duplicate in notmuch-emacs), thanks to excellent
work by David Bremner:
https://nmbug.notmuchmail.org/nmweb/show/20220701214548.461943-1-david%40tethera.net
As for
* 2023-09-26 07:07:46-0300, David Bremner wrote:
> Teemu Likonen writes:
>> Perhaps my wish is that there was an easy way to break threads: mark a
>> message as origin of a new thread.
> How about if you delete the Message-ID, References, and In-Reply-To
> headers from th
On Tue, Sep 26, 2023 at 01:44:00PM +0200, Alexander Adolf wrote:
> David Bremner writes:
>
> > Alexander Adolf writes:
> >
> >> Bearing in mind that re-recognising a message which has arrived
> >> multiple times via different routes is a worthwhile feature,
David Bremner writes:
> Alexander Adolf writes:
>
>> Bearing in mind that re-recognising a message which has arrived
>> multiple times via different routes is a worthwhile feature, it would
>> seem to me that a hash over the invariant part of the message, that is
>
Alexander Adolf writes:
>
> Bearing in mind that re-recognising a message which has arrived
> multiple times via different routes is a worthwhile feature, it would
> seem to me that a hash over the invariant part of the message, that is
> the body, would allow for such detection
gt; message as origin of a new thread. Or perhaps I just use my custom
> ignore mechanism to mark messed threads automatically as read and move
> on.
How about if you delete the Message-ID, References, and In-Reply-To
headers from the bad messages and re-index? No
Hi,
On Mon, Sep 25, 2023 at 11:53:34PM +0200, Gregor Zattler wrote:
> Hi Teemu, notmuch users,
> * Teemu Likonen [2023-09-25; 11:54 +03]:
> > Some person on debian-user mailing list seems to be sending messages
> > with fixed Message-ID field: the same ID in different messages.
[…]
> would you
Hi Teemu, notmuch users,
* Teemu Likonen [2023-09-25; 11:54 +03]:
> Some person on debian-user mailing list seems to be sending messages
> with fixed Message-ID field: the same ID in different messages. In
> Notmuch it is creating trouble because it connects unrelated threads to
> one. The person
Hello,
This sounds like a nasty problem indeed. OTOH, “there’s nothing that couldn’t
be” as my granny would have put it.
Bearing in mind that re-recognising a message which has arrived multiple times
via different routes is a worthwhile feature, it would seem to me that a hash
over the
* 2023-09-25 07:33:23-0400, Daniel Corbe wrote:
> Silly question, I know, but have you actually tried reaching out to
> the user?
Not silly, but I don't even know who the person is. All I see is the
mess, and everything else is my interpretation of the cause. Notmuch
Emacs tree mode shows message
201 - 300 of 18667 matches
Mail list logo
