We ales need the `Received` headers for some FiltaQuilla search terms, see [FiltaQuilla Issue 243](https://github.com/RealRaven2000/FiltaQuilla/issues/243). (It also appears that some `x-` headers are missing in the filter properties array. Alternatively, we could also use the web mail extensions to get at all raw headers, but since web extensions are async this is currently not possible to call from the synchronous search terms of a filter. A bug future improvement would be turning both search terms and filter actions async so that we that can start incorporating asynchronous functions like the ones from the wx APIs.
Bug 1800759 Comment 18 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We also need the `Received` headers for some FiltaQuilla search terms, see [FiltaQuilla Issue 243](https://github.com/RealRaven2000/FiltaQuilla/issues/243). (It also appears that some `x-` headers are missing in the filter properties array. Alternatively, we could also use the web mail extensions to get at all raw headers, but since web extensions are async this is currently not possible to call from the synchronous search terms of a filter. A bug future improvement would be turning both search terms and filter actions async so that we that can start incorporating asynchronous functions like the ones from the wx APIs.
We also need the `Received` headers for some FiltaQuilla search terms, see [FiltaQuilla Issue 243](https://github.com/RealRaven2000/FiltaQuilla/issues/243). (It also appears that some `x-` headers are missing in the filter properties array). Alternatively, we could also use the web mail extensions to get at all raw headers, but since web extensions are async this is currently not possible to call from the synchronous search terms of a filter. A bug future improvement would be turning both search terms and filter actions async so that we that can start incorporating asynchronous functions like the ones from the wx APIs.