Hello,
> > - for outgoing messages that match topics should mailman always include an
> > X-Topics header. and if multiple topics match is there a preferred format
> > or order?
> Always include as long as there are matching topics. The format in MM2.1 is
>
> for a single topic
>
> X-Topics: topic
>
> and for multiple topics
>
> X-Topics: topic1
> topic 2
> topic 3
>
> which is actually wrong. There should be commas as in
>
> X-Topics: topic1,
> topic 2,
> topic 3
>
> There's no preferred order.
Should topics in the X-Topics header be RFC2047 encoded?
It should be defined what characters can be / cannot be part of a topic. A
space? A comma? A tab? If both spaces and commata can be included in a
topic, writing Sieve script (RFC 5528) to filter these things out is hard:
• If header :contains "X-Topics" "Topic 2" …
will not work, if there are "Topic 21", "Topic 2", and "Topic 20".
• If header :contains "X-Topics" "Topic 2," …
will not work, if “Topic 2” is the last in the list and the list has no
terminating comma. One would have to write
• if anyof(header :is "X-Topics" "Topic 2", header :contains "X-Topics" [",
Topic 2", "Topic 2, "])
to check if either "Topic 2" is the whole content of the header, or there is a
comma before or after "Topic 2". But it will match incorrectly with X-Topics:
Topic1, Topic 22 .
Greetings
Дилян
-----Original Message-----
From: Mark Sapiro <[email protected]>
To: khushal <[email protected]>, [email protected]
Subject: [Mailman-Developers] Re: [GSoC] Topics feature - implementation
approach and a few questions
Date: 14/03/26 18:52:41
On 3/13/26 23:56, khushal via Mailman-Developers wrote:
>
> I wanted to confirm a few implementation details
>
> - from your earlier reply it sounded like untagged or non matching posts
> should still be delivered to all subscribers. if that is the case should MM3
> remove receive_nonmatching_topics entirely instead of keeping that state
You should keep the member's receive_nonmatching_topics setting to
control this.
> - for incoming messages if both an explicit topic header and regex/tagger
> matching apply what should take precedence?
Just my opinion, but a message could match multiple topics, so I think
the end result should be a union of the two.
> - for outgoing messages that match topics should mailman always include an
> X-Topics header. and if multiple topics match is there a preferred format or
> order?
Always include as long as there are matching topics. The format in MM2.1 is
for a single topic
X-Topics: topic
and for multiple topics
X-Topics: topic1
topic 2
topic 3
which is actually wrong. There should be commas as in
X-Topics: topic1,
topic 2,
topic 3
There's no preferred order.
> - in MM2 it seems digests do not have topic filtering, should MM3 keep the
> same behavior or should topics also filter what appears in digests?
Digests are not personalized. Every digest subscriber gets the same
digest so it is not possible to filter on topics. Digests contain all
messages.
> - if a topic is renamed or deleted what should happen to existing member
> subscriptions to that topic. should they be automatically migrated to the new
> topic removed or be left unchanged until the user updates their preference?
Good question. MM2.1 ignores this issue leaving the user's preferences
unchanged so the user is still subscribed to the old topic, but it never
matches.
> - as suggested by Дилян to take a look, LISTSERV has a 21 topic limit, for
> MM2 parity im assuming we should not add any hard limit on the number of
> topics unless there is a specific reason. please confirm
I don't think we need a limit.
--
Mark Sapiro <[email protected]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
_______________________________________________
Mailman-Developers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3
Security Policy: https://wiki.list.org/x/QIA9
_______________________________________________
Mailman-Developers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/mailman-developers.python.org/
Mailman FAQ: https://wiki.list.org/x/AgA3
Security Policy: https://wiki.list.org/x/QIA9
