Hi,
I recently received some spam mails, which have a utf-16 byte order mark
(BOM) U+FEFF as the first character in one of their Received:
lines. When I run notmuch new I get the following:
Note: Ignoring non-mail file: /home/user/Mail/new/path_to_email_with_BOM
Could this be a bug in notmuch?
Hello,
When the user display a thread by pressing enter in the notmuch show view,
the elisp function notmuch-search-show-thread is called.
Is it possible to display the thread with messages that have not the unread
tag collapsed ?
Best regards
___
Andreas Amann a.am...@ucc.ie writes:
Could this be a bug in notmuch? Possible emails with BOM are not legal
anyhow, but in my opinion it would be better to simply ignore the BOM.
I am using notmuch 0.18.
As of 0.18 notmuch is using the gmime mail parser exclusively. It could be a
Hi,
I recently received some spam mails, which have a utf-16 byte order mark
(BOM) U+FEFF as the first character in one of their "Received:"
lines. When I run "notmuch new" I get the following:
Note: Ignoring non-mail file: /home/user/Mail/new/path_to_email_with_BOM
Could this be a bug in
attachment was scrubbed...
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20140527/c6029446/attachment.html>
Hi,
I'm trying to take advantage of the tag:replied to give higher priority
to emails sent to very busy lists but it seems that it's not returning
the results that I am expecting.
$ notmuch search tag:unread AND from:lydia
thread:0001a791 Today 17:20 [1/10] Lydia | Wael Nasreddine;
