[Mailman-Users] Re: What regular expressions are allowed for Mailman topics?
Mark Sapiro wrote: > On 5/12/22 10:45, Frank Thommen wrote: > > Dear all, > > I'm trying to implement Mailman topics through regular expressions. > > However I'm not sure, what expression types are supported. I was trying > > * ^(OK|WARN|CRIT|UP|DOWN) -> > > * ^(OK|WARN|CRIT|UP|DOWN) - > > to catch subject lines like "OK -> CRIT some text" and "UP -> DOWN some > > text" ecc. The regexpes above don't catch these mail, even though they > > should be perfectly ok according to several regular expression testers. > > Interestingly > > * ^(OK|WARN|CRIT|UP|DOWN) > > /does/ match, but I require the trailing " ->" to discern from other, > > very similar subjects. > > I'm not sure what the asterisks are, maybe bullets? Yep. The asterisks are the bullets of a bulleted list and /not/ part of the regexp. Sorry, if my formatting was unclear in that respect. > The regexp '^(OK|WARN|CRIT|UP|DOWN) ->' should match, e.g. > Subject: OK -> anything That's exactly what I want to achieve. But this doesn't seem to work, as these mails are /not/ added to the respective topic. > > I also didn't find any reference documentation regarding the supported > > regular expression syntax. Is there any? > > https://docs.python.org/2.7/library/re.html That's what I thought, but then why does '^(OK|WARN|CRIT|UP|DOWN) ->' not lead to an email with the respective topic but '^(OK|WARN|CRIT|UP|DOWN)' does? > > Out Mailman version is 2.1.9 > > Really? 2.1.9 is over 15 years old and 30 releases behind. Don't tell me :-). But we can't influence that. We are just consumers of this service Cheers, Frank -- 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] What regular expressions are allowed for Mailman topics?
Dear all, I'm trying to implement Mailman topics through regular expressions. However I'm not sure, what expression types are supported. I was trying * ^(OK|WARN|CRIT|UP|DOWN) -> * ^(OK|WARN|CRIT|UP|DOWN) \- to catch subject lines like "OK -> CRIT some text" and "UP -> DOWN some text" ecc. The regexpes above don't catch these mail, even though they should be perfectly ok according to several regular expression testers. Interestingly * ^(OK|WARN|CRIT|UP|DOWN) /does/ match, but I require the trailing " ->" to discern from other, very similar subjects. I also didn't find any reference documentation regarding the supported regular expression syntax. Is there any? Out Mailman version is 2.1.9 Cheers, Frank -- 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/
Re: [Mailman-Users] Updating MM 2.1.2 - 2.1.5 stucks
update exits at this point, but the next time it is run, the error does not appear any more (- I have to run 'update' three times to get rid of all these errors). These errors always appear, when 'update' is run after MM 2.1.2 has been used. OK. You have done with update to 2.1.5. Don't go back to 2.1.2. I cannot use 2.1.5: It does not deliver any mails after giving me the following errors (around 20 times) at start time: --- # mailmanctl start Starting Mailman's master qrunner. # Traceback (most recent call last): File /usr/pack/mailman-2.1.5-inf/bin/qrunner, line 270, in ? main() File /usr/pack/mailman-2.1.5-inf/bin/qrunner, line 230, in main qrunner.run() File /usr/pack/mailman-2.1.5-inf/Mailman/Queue/Runner.py, line 70, in run filecnt = self._oneloop() File /usr/pack/mailman-2.1.5-inf/Mailman/Queue/Runner.py, line 99, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/pack/mailman-2.1.5-inf/Mailman/Queue/Switchboard.py, line 147, in dequeue data = cPickle.load(fp) EOFError [...] # --- 2.1.2 at least still delivers mails. I'm helpless frank -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Help: MM 2.1.5 not working after failed update from 2.1.2
Hello list members, as written in a previous posting, the upgrade from 2.1.2 to 2.1.5 failed. When I nevertheless start MM 2.1.5, I get around 20 of the following errors: --- # mailmanctl start Starting Mailman's master qrunner. # Traceback (most recent call last): File /usr/pack/mailman-2.1.5-inf/bin/qrunner, line 270, in ? main() File /usr/pack/mailman-2.1.5-inf/bin/qrunner, line 230, in main qrunner.run() File /usr/pack/mailman-2.1.5-inf/Mailman/Queue/Runner.py, line 70, in run filecnt = self._oneloop() File /usr/pack/mailman-2.1.5-inf/Mailman/Queue/Runner.py, line 99, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File /usr/pack/mailman-2.1.5-inf/Mailman/Queue/Switchboard.py, line 147, in dequeue data = cPickle.load(fp) EOFError [...] # --- Mailman does not seem to deliver any mails after that. When I then stop 2.1.5 and start 2.1.2, I get around a dozen of these errors: --- Jun 26 21:43:27 2004 (1204) lost data files for filebase: 1088195523.0786779+4c5e6189f5cc4ba967f1556ffb911c03c84d6174 --- and I have the impression, that some maillists do not deliver, whereas other deliver well. Can anybody give hints how to debug or even correct this problem or the one described in 'Updating MM 2.1.2 - 2.1.5 stucks' (http://www.mail-archive.com/[EMAIL PROTECTED]/msg25414.html)? Thanks a lot in advance frank -- Frank Thommen, Informatik Support Gruppe, D-INFK, ETH Zuerich E-Mail: [EMAIL PROTECTED]; Tel: +41-1-63 27208 (Mo-Do) Web: http://www.isg.inf.ethz.ch -- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Updating MM 2.1.2 - 2.1.5 stucks
Hi ...and here the process waits/loops forever (at least more then three hours...). I ^C-stopped the update several times, but it gets always stucked at the same list. Examin the locks directory if there are lock files remained before executing bin/update. Make sure you stop qrunner and SMTP and clear the locks directory before issuing 'bin/update -f'. Thanks. I did, but it didn't help. While updating I also get the following errors at some lists (not the same ones, where 'update' hangs): --- Updating mailing list: Updating the held requests database. - updating old private mbox file looks like you have a really recent CVS installation... you're either one brave soul, or you already ran me - updating old public mbox file - This list looks like it might have = b4 list templates around Traceback (most recent call last): File /usr/pack/mailman-2.1.5-inf/bin/update, line 782, in ? errors = main() File /usr/pack/mailman-2.1.5-inf/bin/update, line 672, in main errors = errors + dolist(listname) File /usr/pack/mailman-2.1.5-inf/bin/update, line 357, in dolist os.rename(o_tmpl, n_tmpl) OSError: [Errno 2] No such file or directory --- update exits at this point, but the next time it is run, the error does not appear any more (- I have to run 'update' three times to get rid of all these errors). These errors always appear, when 'update' is run after MM 2.1.2 has been used. Any other ideas or hints? frank -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Updating MM 2.1.2 - 2.1.5 stucks
Hello list members, while updating MM from 2.1.2 to 2.1.5, the process of updating gets stucked at one specific maillist. I added a 'print mlist' in 'def update_pending()' after 'for listname in Utils.list_names(): mlist = MailList.MailList(listname)' to know where it happens: # bin/update Upgrading from version 0x20102f0 to 0x20105f0 getting rid of old source files Updating mailing list: XXX [...updates all lists with one could not acquire lock message...] Updating Usenet watermarks - nothing to update here Updating Mailman 2.1.4 pending.pck database WARNING: Ignoring duplicate pending ID: 7544. [..warns for many more pending IDs..] mailing list list1 (locked) at 4b8300 mailing list list2 (locked) at 4bbdf0 ...and here the process waits/loops forever (at least more then three hours...). I ^C-stopped the update several times, but it gets always stucked at the same list. Two questions: * Any hints, what the problem could be and how it could be solved? (please be very specific if it comes to coding, I'm a Python dummy) * I've stopped our maillist system with 80 lists: Can I restart MM 2.1.2 for the time being after this partial update or will that finally corrupt my system? Thank you very much in advance for any hints. frank -- Frank Thommen, Informatik Support Gruppe, D-INFK, ETH Zuerich E-Mail: [EMAIL PROTECTED]; Tel: +41-1-63 27208 (Mo-Do) Web: http://www.isg.inf.ethz.ch -- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Default action for anti-spam filter catched mails?
Hi, several possibilities to get rid of held messages (javascripts, cronjobs, procmail solutions etc.) have been proposed on this list and of the FAQs. However I cannot find any solution, that allows me to define a default action (accept/hold/reject/discard) for mails held by the anti-spam filters (bounce_matching_headers) as this is e.g. possible for the sender filters (generic_nonmember_action). Has anybody a patch for mailman 2.1.2, that allows to define such an action on a list by list basis via the web interface (if possible)? That would allow us to immediately delete e.g. all mails tagged by SpamAssassin (most of our list admins want to do that) w/o any additional activity. Thanks a lot for any help frank ** Problems, questions, feedback? Mail to [EMAIL PROTECTED] ** -- Frank Thommen, Informatik Support Gruppe, D-INFK, ETH Zuerich E-Mail: [EMAIL PROTECTED]; Tel: +41-1-63 27208 (Mo-Do) Web: http://www.isg.inf.ethz.ch -- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Cannot install Mailman 2.1: bin/update fails (Solaris 9, Python 2.2.2)
Hi,
I don't succeed in installing Mailman 2.1. 'make install' fails with the following
messages:
# make install
[...]
Compiling /home/mailman/Mailman//Mailman/versions.py ...
bin/update: downgrade is detected), nothing will be done.^J^J-h/--help^J
Print this text and exit.^J^JUse this script to help you update to the latest release
of Mailman from^Jsome previous version. It knows about versions back to 1.0b4
(?).^J: not found
bin/update: Perform all necessary upgrades.^J^JUsage: %(PROGRAM)s
[options]^J^JOptions:^J-f/--force^JForce running the upgrade procedures.
Normally, if the version number^Jof the installed Mailman matches the current
version number (or a^J: not found
bin/update: import: not found
bin/update: import: not found
bin/update: import: not found
bin/update: import: not found
bin/update: import: not found
bin/update: import: not found
bin/update: import: not found
bin/update: import: not found
bin/update: import: not found
bin/update: from: not found
bin/update: from: not found
bin/update: from: not found
bin/update: from: not found
bin/update: from: not found
bin/update: from: not found
bin/update: from: not found
bin/update: from: not found
bin/update: FRESH: not found
bin/update: NOTFRESH: not found
bin/update: syntax error at line 58: `(' unexpected
make: *** [update] Error 2
#
I tried with Mailman 2.1 tarballs from list.org and from sourceforge. For 'make' I
used solaris make and gnu make (3.80). Python is a freshly installed Python 2.2.2.
Compiler is gcc 2.95.3. There is no Mailman installed on the system yet.
It seems to me, that there might be a Python syntax error in bin/update, but since I
don't know Python, I'm not sure about it.
Any hints, where the problem could come from or where I could start to look for a
solution?
Thanks in advance
Frank Thommen
** Problems, questions, feedback? Mail to [EMAIL PROTECTED] **
--
Frank Thommen, IT Support Group, D-INFK, ETH Zuerich
Mail: [EMAIL PROTECTED]; Phone: +41-1-63 27208 (Mon-Thu)
Web: http://www.isg.inf.ethz.ch/
--
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] An other whish for umbrella lists
Hi, My problem with umbrella lists - besides those mentioned in previous postings - is, that all prefixes of the chained lists are prepended to the mail subject. Normally our umbrella lists are lists composed of lists which are used by themselves, too. Every list (also the umbrella list) has it's own prefix. Sending to the umbrella lists gives me subjects like: Subject: [umbrella][sublistN] some topic. Instead, I want Subject: [umbrella] some topic for all postings to the umbrella list and Subject: [sublistN] some other topic for posting to the specific sublists. I.e.: Mailman should suppress printing of the list prefix if the mail comes from some other (local!) list or from a defined list senders (similar to the acceptable_aliases setting). frank ** Problems, questions, feedback? Mail to [EMAIL PROTECTED] ** -- Frank Thommen, IT Support Group D-INFK, ETH Zuerich Email: [EMAIL PROTECTED]; Phone: +41-1-63 27208 (Mon-Thu) Web: http://www.isg.inf.ethz.ch -- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Re: [Mailman-Users] Help
Hi, Diagnostic-Code: X-Postfix; Command died with status 2: /var/mailman/mail/wrapper mailcmd test. Command output: Failure to exec script. WANTED gid 12, GOT gid 99. (Reconfigure to take 99?) You probaly run into the following error described in the 'README.INSTALL' of Mailman: Problem: I send mail to the list, and get back mail saying, unknown mailer error. Solution: The likely problem is that you are using the wrong GID or UID for mail. Check your syslog. If you see, for example, a line like: Attempt to exec script with invalid gid 51, expected 99 You need to reinstall Mailman, and specify $MAIL_GID to be 51, as described in the installation instructions. see notes on Postfix below, as by default it will create these problems on installation. frank -- Frank Thommen, Informatik Support Gruppe, D-INFK, ETH Zuerich E-Mail: [EMAIL PROTECTED]; Tel: +41-1-63 27208 (Mo-Do) Web: http://www.isg.inf.ethz.ch -- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Re: [Mailman-Users] wrong gid
Hi Lito, 1. when confirming I received this error message. What should i do? - The following addresses had permanent fatal errors - |/export/home/mailman/mail/wrapper mailcmd test (reason: 2) (expanded from: [EMAIL PROTECTED]) - Transcript of session follows - Failure to exec script. WANTED gid 1, GOT gid 2001. (Reconfigure to take 2001?) 554 5.3.0 |/export/home/mailman/mail/wrapper mailcmd test... unknown mailer error 2 From Mailmans README.INSTALL: Problem: I send mail to the list, and get back mail saying, unknown mailer error. Solution: The likely problem is that you are using the wrong GID or UID for mail. Check your syslog. If you see, for example, a line like: Attempt to exec script with invalid gid 51, expected 99 You need to reinstall Mailman, and specify $MAIL_GID to be 51, as described in the installation instructions. see notes on Postfix below, as by default it will create these problems on installation. 2. my mailman is running on another machine named lists.xyz.com running its own copy of http, aside from my real http server. How will I configure all mailman transactions to point to lists.xyz.com and not to xyz.com, as you can see the above email address is xyz.com and not lists.xyz.com., even the senders address is xyz.com. This should be mainly a question of configuring your MTA. There's currently a discussion about virtual domains in this mailing list, which might help you. frank -- Frank Thommen, IT Support Group, D-INFK, ETH Zuerich E-Mail: [EMAIL PROTECTED]; Tel: +41-1-63 27208 (Mo-Do) Web: http://www.isg.inf.ethz.ch -- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
[Mailman-Users] Webserver access problems (Permission denied on config.db)
Hi, I have problems with access permissions from the webserver to the mailman list database: admin(24095): IOError: [Errno 13] Permission denied: '/home/mailman/MLM/lists/mytestlist_1/config.db' The mailman directory is NFS shared (rw) to the webserver (apache 1.3.11, Solaris 2.6.1). The newlist script creates all files with ownership mailman:mailman. Most of them are world-readable, but not the config.db file, which has permissions 660. Therefore it is not readable by the httpd (which runs as httpd:httpd) and the *whole* mailman-webinterface breakes. Is there a solution to this problem which does *not* require to change access permissions of all lists files manually after each newlist? I am grateful for every hint. frank -- Frank Thommen, IT Support Group, D-INFK, ETH Zuerich E-Mail: [EMAIL PROTECTED]; Tel: +41-1-63 27208 (Mo-Do) Web: http://www.isg.inf.ethz.ch -- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
