Andreas Amann writes:
> 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:
Jani Nikula writes:
> My quick guess is that gmime stops header processing at that point, and
> all the headers we require are after that invalid header.
I can confirm that. I adapted one of the example programs which comes
with gmime to read out the "From" header, and it indeed was not found,
On Wed, 28 May 2014, David Bremner wrote:
> I've tagged this as a wishlist bug / feature request for now, until
> somebody has a chance to track down where exactly the issue is, and how
> hard it would be to fix.
My quick guess is that gmime stops header processing at that point, and
all the
On Wed, 28 May 2014, David Bremner da...@tethera.net wrote:
I've tagged this as a wishlist bug / feature request for now, until
somebody has a chance to track down where exactly the issue is, and how
hard it would be to fix.
My quick guess is that gmime stops header processing at that point,
Jani Nikula j...@nikula.org writes:
My quick guess is that gmime stops header processing at that point, and
all the headers we require are after that invalid header.
I can confirm that. I adapted one of the example programs which comes
with gmime to read out the From header, and it indeed was
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
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?
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