[Mailman-Users] Re: Topic hack to streamline use of topics.
On 10/15/20 4:08 PM, Mark Sapiro wrote: Actually, as I note in another post, the header is Keywords:, not Topics:. That was my error. *nod*nod* I was following your lead. Simple mistakes happen. It's how we correct them that matters. ;-) -- Grant. . . . unix || die smime.p7s Description: S/MIME Cryptographic Signature -- 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/
[Mailman-Users] Re: Topic hack to streamline use of topics.
On 10/15/20 1:45 PM, Grant Taylor via Mailman-Users wrote: > While on the topic of topics ... ;-) > > I implemented a hack in my LDA to search the body of messages for > specific keywords. When one (or more) of the keywords is found, it adds > a specific value to the Topics: header. Actually, as I note in another post, the header is Keywords:, not Topics:. That was my error. > This way, posters don't have to worry about defining the topics before > they hit send. It also allows me to be more granular and flexible at > the same time. I can create an "email" topic that will match on > Mailman, Sendmail, Microsoft Exchange, GroupWise, etc. (Sure, there's a > little wiggle room in the pattern matching and logic.) > > This has largely worked out very well for the lists that I've applied it > to. > > > > > -- > 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/ > -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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/
[Mailman-Users] Re: Help with Topics
On 10/15/20 1:41 PM, Grant Taylor via Mailman-Users wrote: > On 10/13/20 3:51 PM, Mark Sapiro wrote: >> For example, if topic1 has regexp \WMailman\W and topic2 has regexp >> \Wlist\W, any message containing a Subject: or Topics: header or >> pseudo header containing the word Mailman ... > > What is a "pseudo header" in this context? > > Are you referring to the first line of the message body being abused and > treated like a header? Not exactly. In order to support MUAs that make it difficult to add a custom header such as Keywords: There is a topics_bodylines_limit setting, described as: topics_bodylines_limit (topics): How many body lines should the topic matcher scan? The topic matcher will scan this many lines of the message body looking for topic keyword matches. Body scanning stops when either this many lines have been looked at, or a non-header-like body line is encountered. By setting this value to zero, no body lines will be scanned (i.e. only the Keywords: and Subject: headers will be scanned). By setting this value to a negative number, then all body lines will be scanned until a non-header-like line is encountered. In another post in this thread, I referred to a Topics: header, I meant Keywords:, not Topics. As far as searching the message body for what I referred to as pseudo-headers it will only look at an outer text/plain part or a text/plain part within an outer multipart/alternative part, and it will look at any lines up to topics_bodylines_limit or the first non-header like line for Subject: or Keywords: matches. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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/
[Mailman-Users] Another Bug in Mailman version 2.1.29 Error
Hello, I've been working on migrating an old Mailman 2.1 server over to a new server. I'm currently using Mailman 2.1.29 for the new server. The new server is a CentOS 8 server. The Mailman package that is being used is mailman-3:2.1.29-4.module_el8.0.0+34+0459d3d0.x86_64. When I try to visit the following link in a web browser: server.com/mailman/listinfo, I get the following error: "Bug in Mailman version 2.1.29 / We're sorry, we hit a bug!" with a specific error of: IOError: [Errno 13] Permission denied: '/var/log/mailman/error'. I think this issue is very similar to this past email question: https://mail.python.org/pipermail/mailman-users/2005-December/048349.html But even after setting the group to "mailman" and setting the permissions as suggested in that other post for /var/log/mailman and the files within, I still get the same error. I've tried restarting the server to see if that would help (after reading this: https://bugzilla.redhat.com/show_bug.cgi?id=1733359#c16), and yesterday that seemed to work (because I then got another type of error with Mailman). But when I try to restart the server today, I still get the same Errno 13 error. I think I've even tried setting the /var/log/mailman files to 777 to see if that would temporarily fix the permissions issue, with the same result. I have then tried to disable selinux to see if that would change anything. Surprisingly, I'm able to successfully view Mailman on the server when selinux is disabled. So it works when selinux is disabled! Is there a way that I can keep selinux enabled and still have Mailman work as expected? In answer to that question, it looks like this informational page explains how to allow Mailman to work while selinux is enabled: https://wiki.list.org/DOC/SELinux%20errors%20after%20upgrade%20-%20RedHat I ran the following steps: sudo yum update selinux-policy sudo restorecon -R -v /var/lib/mailman sudo restorecon -R -v /usr/lib/mailman When I re-enabled selinux and tried visiting Mailman on the new server, it appeared to work! Hope this helps someone in the future. -- 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/
[Mailman-Users] Topic hack to streamline use of topics.
While on the topic of topics ... ;-) I implemented a hack in my LDA to search the body of messages for specific keywords. When one (or more) of the keywords is found, it adds a specific value to the Topics: header. This way, posters don't have to worry about defining the topics before they hit send. It also allows me to be more granular and flexible at the same time. I can create an "email" topic that will match on Mailman, Sendmail, Microsoft Exchange, GroupWise, etc. (Sure, there's a little wiggle room in the pattern matching and logic.) This has largely worked out very well for the lists that I've applied it to. -- Grant. . . . unix || die smime.p7s Description: S/MIME Cryptographic Signature -- 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/
[Mailman-Users] Re: Help with Topics
On 10/13/20 3:51 PM, Mark Sapiro wrote: For example, if topic1 has regexp \WMailman\W and topic2 has regexp \Wlist\W, any message containing a Subject: or Topics: header or pseudo header containing the word Mailman ... What is a "pseudo header" in this context? Are you referring to the first line of the message body being abused and treated like a header? -- Grant. . . . unix || die smime.p7s Description: S/MIME Cryptographic Signature -- 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/
[Mailman-Users] Re: Help with Topics
Thank you, Gentlemen! That was quite enlightening and _very_ helpful. I'm very grateful for your extensive explanations and examples and am going to give Topics a try and see if the subscribers take to them. -Chip- On 10/13/2020 5:51 PM, Mark Sapiro wrote: On 10/13/20 1:56 PM, Chip Davis wrote: 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. As noted in another reply, matching on subject_prefix won't work. Also, I don't understand 'subject bloat' Consider defining a topic named Get_only_nonmatchind with a regexp ov say ^This_is_a_bogus_topic_that_I_hope_will_never_match_a_real_message_ig35yth3hg3ot4ohj430$ And a description of say Subscribe to this topic and enable receiving messages that don't match any topic to receive only messages that don't match any other topic. 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? Short answer - Yes What you call multiple topic IDs are actually just things that match a topic regexp. For example, if topic1 has regexp \WMailman\W and topic2 has regexp \Wlist\W, any message containing a Subject: or Topics: header or pseudo header containing the word Mailman (matched case insensitively) will be delivered to every regular member subscribed to topic1 plus those subscribed to no topics. Any message containing a Subject: or Topics: header or pseudo header containing the word list (matched case insensitively) will be delivered to every regular member subscribed to topic2 plus those subscribed to no topics. Any message containing a Subject: or Topics: header or pseudo header containing both the words Mailman and list (matched case insensitively) will be delivered to every regular member subscribed to topic1 plus those subscribed to topic2 plus those subscribed to no topics. IOW, if a member is subscribed to those topics will he get multiple copies in that case? No. Question 3: What effect do Topics have on subscribers receiving the Digest? Are they effectively subscribed to all Topics? Digests contain all messages without any regard to 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. -- 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/
