On Fri, Sep 02, 2022 at 06:24:24PM +0000, Tim Chase wrote:
> On 2022-09-02 20:07, Francesco Ariis wrote:
>> Il 02 settembre 2022 alle 18:01 Tim Chase ha scritto:
>>> However, often these messages don't have a To: or CC: header, so I
>>> can't identify them with a ~C and I don't see an option for
>>> identifying messages by the Delivered-To or Envelope-To headers.
>>>
>>> Is there a good way to identify these messages?
>>
>> Check ~h and =h, it those don???t do, consider filtering with your
>> mail retriever (e.g getmail, that is what I use).
>
> Hmm, that looks like it might work. Is there further documentation
> on the ~h beyond this:
>
> http://mutt.org/doc/manual/#tab-patterns
>
> It seems to mostly do what I want, but I don't see a way to limit
> it to just the Delivered-To/Envelope-To headers,
As Obi-Wan Kenobi didn't say, "Use regular expressions, Luke!"
Could you not prepend your EXPR with something like this?
`^(Delivered|Envelope)-To:\ `
(Remove the backticks, of course. But don't forget the space after the
backslash.)
WFM.
Sam
--
A: When it messes up the order in which people normally read text.
Q: When is top-posting a bad thing?
() ASCII ribbon campaign. Please avoid HTML emails & proprietary
/\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.
