diff options
author | Kyle Meyer <kyle@kyleam.com> | 2020-04-19 20:13:32 -0400 |
---|---|---|
committer | Eric Wong <e@yhbt.net> | 2020-04-20 00:59:08 +0000 |
commit | b3a04ae18a42ed960c89cc81c209633da6976380 (patch) | |
tree | 2589568b9b7a4003d6a3a19c8c27dddb658fc554 /t/feed.t | |
parent | b3f81ce0c71d5d4eca347f259b5ae69660a2cb13 (diff) | |
download | public-inbox-b3a04ae18a42ed960c89cc81c209633da6976380.tar.gz |
The watchheader key supports only a single value. Supporting multiple watchheader values was mentioned in discussion [1] of 8d3e3bd8 (doc: explain publicinbox.<name>.watchheader, 2019-10-09), and it wasn't clear if there was a need. One scenario in which matching multiple headers would be convenient is when someone wants to set up public-inbox archives for some small projects but does _not_ want to run mailing lists for them, instead allowing others to follow the project by any of the pull mechanisms. Using a common underlying address, an address alias for each project is configured via a third-party email provider, with messages for each alias being exposed as a separate public-inbox archive. In this setup, messages for an inbox cannot be selected by a List-ID header but can be identified by the inbox's address in either the To or Cc header. To support such a use case, update the watchheader handling to consider multiple values, accepting a message if it matches any value. While selecting a message based on matching _any_ rather than _all_ values is motivated by the above scenario, it's worth noting that the "any" behavior is consistent with how multiple listid config values are handled. [1] https://public-inbox.org/meta/20191010085118.r3amey4cayazfycb@dcvr/
Diffstat (limited to 't/feed.t')
0 files changed, 0 insertions, 0 deletions