On 04-12 14:20, Michael Elkins wrote:
Attached is a patch which implement an auto-subscribe feature. When
you load a mailbox, Mutt will parse the List-Post header field and add
it to the 'subscribe' list automatically, unless it matches something
on the 'unlists' or 'unsubscribe' list.
On Mon, Apr 12, 2010 at 10:47:21AM +0200, ilf wrote:
On 04-11 20:22, Michael Elkins wrote:
The reason for the distinction between lists/subscribe is that just
because you received an email that was addressed to a list doesn't
mean that you are subscribed to said list.
But if there's a
On 04-11 20:32, Michael Elkins wrote:
On Sat, Apr 10, 2010 at 01:38:19AM +0200, ilf wrote:
I would like a workaround to use Regex in 'lists' and 'subscribe', but
that feels dirty. Why doesn't Mutt allow 'lists'/'subscribe' to lists
based on the List-Id: header?
The List-ID header is not
On Mon, Apr 12, 2010 at 10:47:21AM +0200, ilf wrote:
On 04-11 20:32, Michael Elkins wrote:
On Sat, Apr 10, 2010 at 01:38:19AM +0200, ilf wrote:
I would like a workaround to use Regex in 'lists' and 'subscribe', but
that feels dirty. Why doesn't Mutt allow 'lists'/'subscribe' to lists
Attached is a patch which implement an auto-subscribe feature. When you load
a mailbox, Mutt will parse the List-Post header field and add it to the
'subscribe' list automatically, unless it matches something on the 'unlists'
or 'unsubscribe' list.
me
diff -r 2cd62f40d840 hcache.c
---
On Fri, Apr 09, 2010 at 11:51:49PM -0500, Brian Ryans wrote:
Quoting ilf on 2010-04-09 18:38:19:
Why was it decided to set the flag only for subscribed lists and not
listed lists?
In my limited mutt experience (as a user) I believe it was decided that
way as people would probably be more
On Sat, Apr 10, 2010 at 01:38:19AM +0200, ilf wrote:
I would like a workaround to use Regex in 'lists' and 'subscribe', but
that feels dirty. Why doesn't Mutt allow 'lists'/'subscribe' to lists
based on the List-Id: header?
The List-ID header is not necessarily a valid email address. All that
Quoting ilf on 2010-04-09 18:38:19:
I don't know where you got 3.1.1, my manual doesn't have that section
:)
That was my mistake. 2.3.1.1 (3.1.1 within Chapter 2).
Why was it decided to set the flag only for subscribed lists and not
listed lists?
I'm unsure of the actual reason for that.
Quoting ilf on 2010-04-08 16:09:46:
I'm confused by Mutts handling of mailing lists.
First, I do not understand the difference of known lists (lists) and
subscribed lists (subscribe). If Mutt handles mail from a known list,
I'm probably subscribed, no?
Mutt's meaning of known and subscribed
On 04-09 01:21, Brian Ryans wrote:
See above: concerns you raise, indirectly, in the remainder of this post
seem to be addressed above to the best of my ability. Please let me know
if that's not the case.
Thanks for your hints. But I am still confused :)
Manual section 4.8 Handling Mailing
Quoting ilf on 2010-04-09 12:18:08:
Thanks for your hints. But I am still confused :)
Now I'm confused too, see below.
Manual section 4.8 Handling Mailing Lists sais, Mutt can do things
with mailing lists once Mutt knows what [my] mailing lists are.
It can:
1. show mailing list in index
I'm confused by Mutts handling of mailing lists.
First, I do not understand the difference of known lists (lists) and
subscribed lists (subscribe). If Mutt handles mail from a known list,
I'm probably subscribed, no?
Secondly, I find having to manually maintain a list of subscriptions in
my
12 matches
Mail list logo
