Hi all,
According to the manual, it seems that the lists and subscribe commands
only examine the "To:" field of incoming mail. Is that true?
Occasionally you get people who Bcc: a list, so then it slips past
the lists and subscribe commands. I've set up maildrop to examine
messages and change thei
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, June 20 at 06:58 AM, quoth Omari Norman:
> According to the manual, it seems that the lists and subscribe
> commands only examine the "To:" field of incoming mail. Is that
> true?
Not in my experience. Where does it say that?
Generall
On Wed, Jun 20, 2007 at 07:04:43AM -0600, Kyle Wheeler wrote:
> Generally, the lists and subscribe commands just add addresses to an
> internal list. This list is then consulted for several things. For
> example, it is used for the ~l pattern (which, according to the
> manual, matches "messages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, June 20 at 01:31 PM, quoth Omari Norman:
> On Wed, Jun 20, 2007 at 07:04:43AM -0600, Kyle Wheeler wrote:
>> Generally, the lists and subscribe commands just add addresses to
>> an internal list. This list is then consulted for several th
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
Moin fellow ML mutters,
by popular(?) request we have now List-Post headers identifying the
origin for each post sent via any list, even when in Bcc or
cross-posted.
If you wonder why: it helps sorting by procmail and responding via
list-reply (mutt uses List-Post).
While at it, replaced the old
-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 c
On Tue, Jun 19, 2007 at 11:17:48AM +0200, Hein Zelle wrote:
> I believe pine (used to) store it's addressbook on the imap server.
> I'd like to go a little further than that, and store most of my mutt
> configuration on a centralized place, except perhaps for the inital
> password.
IIRC, (al)pine
Kyle Wheeler wrote:
> 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
