You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2017/06/06 02:07:18 UTC

[jira] [Commented] (JAMES-1900) Decode headers before indexing

    [ https://issues.apache.org/jira/browse/JAMES-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037989#comment-16037989 ] 

Tellier Benoit commented on JAMES-1900:
---------------------------------------

https://github.com/linagora/james-project/pull/778 Solved this issues in other places: JSieve, HasHeader, JMAP, ES indexing, etc...

> Decode headers before indexing
> ------------------------------
>
>                 Key: JAMES-1900
>                 URL: https://issues.apache.org/jira/browse/JAMES-1900
>             Project: James Server
>          Issue Type: Bug
>            Reporter: Quynh Nguyen
>             Fix For: 3.0.0
>
>
> Headers in emails are usually encoded using https://tools.ietf.org/html/rfc2047
> It's the so-called encoded-word encoding.
> When we put emails into ES, we should decode headers to UTF-8 to make sure search will match even non-ascii characters.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org