On 13-02-13 05:26pm, Stefano Zacchiroli wrote: > OK, I understand the problem now. Although I don't understand how it's > possible. Can you please do the following test: > > - go on a mail, try on it to ensure it exhibit the bad behavior > you've reported It does. > - find out the Message-Id of that mail, e.g. > "20130213095752.GA20009@foobar" > - on a shell prompt, try: > notmuch search --output=threads id:20130213095752.GA20009@foobar > - it should give you something like > thread:0000000000018bce % notmuch search --output=threads id:8e85854f-8b30-4821-bf3e-4c19e576bf67@googlegroups.com thread:0000000000000566 % notmuch search thread:0000000000000566 thread:0000000000000566 Today 04:59 [39/39] […] So it’s not notmuch. Bear in mind that I use Arch, so this is the version on my system atm: https://www.archlinux.org/packages/community/x86_64/notmuch-mutt/ This is the bad guy: sub get_message_id() { my $mail = Mail::Internet->new(\*STDIN); $mail->head->get("message-id") =~ /^<(.*)>$/;# get message-id #l.124 return $1; } I’m not much of a perl coder (not at all to be exact), but Use of uninitialized value in pattern match (m//) at /usr/bin/notmuch-mutt line 124, line 66. sounds suspiciously like nothing gets read out of STDIN and $mail is definitely not a Mail::Internet object. ~Profpatsch -- Proudly written in Mutt with Vim on Archlinux. Q: Why is this email five sentences or less? A: http://five.sentenc.es