Thanks for the suggestion, Richard.
The only downside to that is that your 'Subject:' line now has least
three identifiers: the list-id, the admin-id, and the topic-id.
Subject: [FlyGuys] [Admin] [B-26] Re: cockpit vent repair
I was hoping to avoid the Subject bloat, and it crossed my mind that
the list-id itself could be considered the common "topic". I wasn't
sure if the string "[FlyGuys]" in the Subject would be recognized as a
"topic", or if it would be ignored because it was the list-id. Or if
it mattered, since its primary purpose is to enable the "no-match
filter" option in the first place.
Any insights would be appreciated.
Question 2: If a 'Subject:' line has multiple topic-ids, will a copy
of the posting will be sent to the union set of members of the
topics? IOW, if a member is subscribed to those topics will he get
multiple copies in that case?
Question 3: What effect do Topics have on subscribers receiving the
Digest? Are they effectively subscribed to all Topics?
I see great potential for the use of Topics in our group, but I don't
know where to find the answers besides here.
Thanks!
-Chip-
On 10/13/2020 3:57 PM, Richard Damon wrote:
I create one topic that I request everyone using topic to select for
important administrative messages from the moderator of the list. That
gives them something to select if they don't want any of the normal topics.
On 10/13/20 3:21 PM, Chip Davis wrote:
I'm trying to set up Topics for a Mailman 2.1.33 list I administer,
and I'm a tad confused.
There appears to be no combination of options to allow a member of a
list to see _only_ non-topic-specific postings.
If you select one or more topics of interest, you will receive the
postings under those topics. You will not receive any
_topic-specific_ postings that do not match your selections.
Furthermore, if you have also set "Do you want to receive messages
that do not match any topic filter?" to 'Yes', you will also receive
all messages that are _not_ associated with a topic. Otherwise, you
will receive _only_ the postings associated with your selected
topics. (This appears to function as expected.)
However, if you have not selected any topics, you will receive all
postings, whether topic-specific or not, regardless the setting of "Do
you want to receive messages that do not match any topic filter?".
I would like to offer the members of my lists the option of receiving:
1. All of the postings to the list [All topic categories selected +
no-match filter=Yes]
2. Specific topics and all non-topic postings [At least one topic
category selected + no-match filter=Yes]
3. Specific topics only [At least one topic category selected +
no-match filter=No]
4. Only _non-topic_ postings [No topic categories selected +
no-match filter=No]
Apparently that is not the heuristic being applied. If no topic
categories are selected, the no-match filter setting is ignored (i.e.
defaults to 'Yes') effectively delivering all listserver traffic to
that user, and eliminating option 4. This is "as documented" and
embarrassingly empirically demonstrated. :-/
There seems to be no obvious way to say "I want to see only those
postings that are not topic-specific".
If I put the list's subject_prefix in as the Topic1 regexp (escaped as
necessary), would the member be able to select it and specify
'no-match filter=No' to receive _only_ the non-topic-specific
postings? (I would test this question myself, but see "embarrassingly
empirically demonstrated", above.)
If this question has already been addressed in a document somewhere,
please point me to it.
Thanks!
-Chip-
------------------------------------------------------
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/
