Proposal: List-Id

[guyzmo]

On Mon, Mar 16, 2015 at 04:28:44PM +0100, Amadeusz ?o?nowski wrote:
> There's afew [0].  One of its core features is tagging mails by List-Id.
> [0] https://github.com/teythoon/afew

wha, didn't know about it, GG, I might switch away from procmail! 
And that's a huge deal, as I've been using it for >15years :-)

-- 
Guyzmo

Proposal: List-Id

[Amadeusz Żołnowski]

There's afew [0].  One of its core features is tagging mails by List-Id.

[0] https://github.com/teythoon/afew


Cheers,

-- 
Amadeusz ?o?nowski
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 472 bytes
Desc: not available
URL: 

Proposal: List-Id

[David Bremner]

Harlan Lieberman-Berg  writes:
>
> The standard for identifying mailing lists seems to be List-Id, as per
> RFC 2919.  I can understand the desire to keep the number of headers
> included in the header block low, but I wonder if this might be a common
> enough use-case to suggest its inclusion.
>

I think the real blocker at this point is that some copies of a message
may have list-id header and some not. Currently we only index the first
copy of a message that arrives. Indexing all copies would probably be a
good step in any case, but e.g. handling deletion of files requires some
care in that case.

d

Proposal: List-Id

[Guyzmo]

Hi Harlan,

On Sun, Mar 15, 2015 at 07:02:56PM -0400, Harlan Lieberman-Berg wrote:
> One of my (few) problems right now with notmuch is around mailing lists
> that are copied, either as CC or BCC, on various emails that go around.
> My filtering inside notmuch right now doesn't catch all the messages,
> since the only tag I can match on is "to:foo at bar.org" and not all
> messages have the to rewritten.

I'm not sure to correctly understand your issue. You're talking about
looking up all mails that are of a given mailing list?

Then I'm not sure it needs notmuch to be patched, as this can be added
pretty easily using an incoming mail filter. I'm personally using
procmail, so it'd be one such as:

:0:notmuch.lock
* ^List-[Ii][dD]:.*
{
TAGS="${TAGS} +ml -inbox"
}

To have the inbox tag removed and the ml tag added.

Then I tend to use the right hand side of the `+` on incoming mail, so
that I can choose a unique tag for my mail filtering upon subscription
to the mailing list:

:0:notmuch.lock
* ^TO\/guyzmo\+[a-z0-9]+ at m0g\.net
* MATCH ?? ^guyzmo\+\/[a-z0-9]+
{
TAGS="+${MATCH}"
}

As an example, just look my From header here ;-)

> The standard for identifying mailing lists seems to be List-Id, as per
> RFC 2919.  I can understand the desire to keep the number of headers
> included in the header block low, but I wonder if this might be a common
> enough use-case to suggest its inclusion.
> As a counter-argument, I can see the parallel to spam filtering which
> come with their own set of headers that are not special cased by
> notmuch, but there seems to be much more variety in headers there - as
> well as different user configurations.

One issue I can see for indexing `List-Id` is that even though there's
an RFC for that, the value given can be either a `name `, a
`mail` or a `name` field. There's no real rule and the content can
sometimes be quite unreliable when it comes to index search.

I believe that this discussion has happened in the past, and IIRC, the
output that it was not to be integrated.

HTH,

-- 
Guyzmo

Re: Proposal: List-Id

[Guyzmo]

Hi Harlan,

On Sun, Mar 15, 2015 at 07:02:56PM -0400, Harlan Lieberman-Berg wrote:
 One of my (few) problems right now with notmuch is around mailing lists
 that are copied, either as CC or BCC, on various emails that go around.
 My filtering inside notmuch right now doesn't catch all the messages,
 since the only tag I can match on is to:f...@bar.org and not all
 messages have the to rewritten.

I'm not sure to correctly understand your issue. You're talking about
looking up all mails that are of a given mailing list?

Then I'm not sure it needs notmuch to be patched, as this can be added
pretty easily using an incoming mail filter. I'm personally using
procmail, so it'd be one such as:

:0:notmuch.lock
* ^List-[Ii][dD]:.*
{
TAGS=${TAGS} +ml -inbox
}

To have the inbox tag removed and the ml tag added.

Then I tend to use the right hand side of the `+` on incoming mail, so
that I can choose a unique tag for my mail filtering upon subscription
to the mailing list:

:0:notmuch.lock
* ^TO\/guyzmo\+[a-z0-9]+@m0g\.net
* MATCH ?? ^guyzmo\+\/[a-z0-9]+
{
TAGS=+${MATCH}
}

As an example, just look my From header here ;-)

 The standard for identifying mailing lists seems to be List-Id, as per
 RFC 2919.  I can understand the desire to keep the number of headers
 included in the header block low, but I wonder if this might be a common
 enough use-case to suggest its inclusion.
 As a counter-argument, I can see the parallel to spam filtering which
 come with their own set of headers that are not special cased by
 notmuch, but there seems to be much more variety in headers there - as
 well as different user configurations.

One issue I can see for indexing `List-Id` is that even though there's
an RFC for that, the value given can be either a `name mail`, a
`mail` or a `name` field. There's no real rule and the content can
sometimes be quite unreliable when it comes to index search.

I believe that this discussion has happened in the past, and IIRC, the
output that it was not to be integrated.

HTH,

-- 
Guyzmo
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: Proposal: List-Id

[David Bremner]

Harlan Lieberman-Berg hlieber...@setec.io writes:

 The standard for identifying mailing lists seems to be List-Id, as per
 RFC 2919.  I can understand the desire to keep the number of headers
 included in the header block low, but I wonder if this might be a common
 enough use-case to suggest its inclusion.


I think the real blocker at this point is that some copies of a message
may have list-id header and some not. Currently we only index the first
copy of a message that arrives. Indexing all copies would probably be a
good step in any case, but e.g. handling deletion of files requires some
care in that case.

d
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Proposal: List-Id

[Harlan Lieberman-Berg]

Hello everyone!

One of my (few) problems right now with notmuch is around mailing lists
that are copied, either as CC or BCC, on various emails that go around.
My filtering inside notmuch right now doesn't catch all the messages,
since the only tag I can match on is to:f...@bar.org and not all
messages have the to rewritten.

The standard for identifying mailing lists seems to be List-Id, as per
RFC 2919.  I can understand the desire to keep the number of headers
included in the header block low, but I wonder if this might be a common
enough use-case to suggest its inclusion.

As a counter-argument, I can see the parallel to spam filtering which
come with their own set of headers that are not special cased by
notmuch, but there seems to be much more variety in headers there - as
well as different user configurations.

Thank you all for your help, and I'm looking forward to hearing your
thoughts.  (I'm not yet subscribed, so please keep me CCed to the
thread.)

Sincerely,

-- 
Harlan Lieberman-Berg
~hlieberman
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: Proposal: List-Id

[guyzmo]

On Mon, Mar 16, 2015 at 04:28:44PM +0100, Amadeusz Żołnowski wrote:
 There's afew [0].  One of its core features is tagging mails by List-Id.
 [0] https://github.com/teythoon/afew

wha, didn't know about it, GG, I might switch away from procmail! 
And that's a huge deal, as I've been using it for 15years :-)

-- 
Guyzmo
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Re: Proposal: List-Id

[Amadeusz Żołnowski]

There's afew [0].  One of its core features is tagging mails by List-Id.

[0] https://github.com/teythoon/afew


Cheers,

-- 
Amadeusz Żołnowski


signature.asc
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch

Proposal: List-Id

[Harlan Lieberman-Berg]

Hello everyone!

One of my (few) problems right now with notmuch is around mailing lists
that are copied, either as CC or BCC, on various emails that go around.
My filtering inside notmuch right now doesn't catch all the messages,
since the only tag I can match on is "to:foo at bar.org" and not all
messages have the to rewritten.

The standard for identifying mailing lists seems to be List-Id, as per
RFC 2919.  I can understand the desire to keep the number of headers
included in the header block low, but I wonder if this might be a common
enough use-case to suggest its inclusion.

As a counter-argument, I can see the parallel to spam filtering which
come with their own set of headers that are not special cased by
notmuch, but there seems to be much more variety in headers there - as
well as different user configurations.

Thank you all for your help, and I'm looking forward to hearing your
thoughts.  (I'm not yet subscribed, so please keep me CCed to the
thread.)

Sincerely,

-- 
Harlan Lieberman-Berg
~hlieberman