Re: lists and subscribe commands and the To: header
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday, June 20 at 03:03 PM, quoth Todd Zullinger:
>Kyle Wheeler wrote:
>> Now, it's probably fair criticism if you want to say that mutt
>> should also check List-Post and/or List-ID headers (if they exist),
>> but for good or ill, it does not currently (file a bug report).
>> Other than that, though, how do you think mutt *should* identify
>> messages as being from a list?
>
>Pardon me if I'm missing the important bits of this thread (quite
>likely)... but there is some support for RFC2369 List-Post headers in
>parse.c. If you use list-reply on a message with a List-Post header
>it will do the right thing.
Yes, BUT mutt does *not* use those headers to match against the
lists/subscribed lists for the purposes of ~l and ~u pattern matching.
Check out pattern.c, line 1172; all it uses is h->env->to and
h->env->cc. h->env->to is built (in parse.c) from To and Apparently-To
headers, and h->env->cc is build from the CC headers.
~Kyle
- --
No man needs a vacation so much as the man who has just had one.
-- Elbert Hubbard
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFGeYkhBkIOoMqOI14RAiqaAKCpriLvm0Cw1g0eTowyZ1i7xR3bJwCcDCG6
FA+9LQYPVpmBcgO4oSMPiwE=
=6hqx
-----END PGP SIGNATURE-----