Re: reply to list (was Re: disable beep sound)
Hi,
* Kyle Wheeler wrote:
Second, since mutt already knows about List-Post to reply to a list
list even without a "subscribe" or "list" command, it should be
taught how to detect mailing lists completely. That way only mailing
lists without a given set of headers would require "list" commands.
That only applies when we are replying to a message. When I compose a
new message to mutt-user@xxxxxxxx, I want it to match the ~l
send-hooks that I've set up. The only way for mutt to know that that's
a mailing list address is for me to tell it.
...which should only apply to fcc-stored messages but not for the ones
you get back from the list.
Agreed, though I think we can make a stronger statement: there's
absolutely no way for mutt to ascertain the current state of a
person's list subscription status based on the message alone. For
example, I could unsubscribe to a mailing list, and then decide to
reply to a few of the last messages that I received. Those messages
were sent (and received) while I was subscribed, but nothing in them
will inform mutt that I *just* unsubscribed.
Sure. What I meant is not to replace "list" with list detection, but to
make mutt a little smarter. For example, you may clean up your mutt
config and use it later to read some really old archived mail containing
mailing lists you don't have subscribe/list commands for any longer. In
that case for example ~l can be made to work (which would be better than
nothing). Or you get mails forwarded to lists you haven't configured.
And, of course, when composing a new message, there is no prior
message for mutt to consult to even attempt to detect my subscription
status.
It's also not about detecting subscription status at any point, just
another attempt to detect non-list mail as actually list-mail by looking
at certain mailing list headers.
Rocco