| 2009-02-09 00:17:18 |
Mark Sapiro |
mailman: statusexplanation |
|
This is fixed in Mailman 2.2. I'll fix it as well in for 2.1.12, but there are several caveats.
The main problem is the regexps entry for topics is not properly documented. In your case, the issue is not that you have the same word defined twice; it is that your regexp is invalid. For example, I think you really want something like
Wohnung.*|
.*wohnung.*
'*' is not a wildcard in regular expressions as it is for example in file name globing. You probably want '.*'. Also, the implication is if you list separate keywords on separate lines that they are connected with 'or', but the regexp is ultimately compiles in 'verbose' mode, so the lines are just strung together. This is where the documentation is wrong. This is all clarified and fixed in Mailman 2.2.
The problem in 2.1 is when you enter the regexp, we validate in by attempting to compile it normally, so we check 'Wohnung*\r\n*wohnung*' which doesn't mean what you want, but is valid, but when we use it we compile effectively 'Wohnung**wohnung*' which is not valid and throws the exception.
Note that the regexp is matched case insensitively in any case.
|
|
| 2009-02-09 01:27:17 |
Mark Sapiro |
mailman: statusexplanation |
This is fixed in Mailman 2.2. I'll fix it as well in for 2.1.12, but there are several caveats.
The main problem is the regexps entry for topics is not properly documented. In your case, the issue is not that you have the same word defined twice; it is that your regexp is invalid. For example, I think you really want something like
Wohnung.*|
.*wohnung.*
'*' is not a wildcard in regular expressions as it is for example in file name globing. You probably want '.*'. Also, the implication is if you list separate keywords on separate lines that they are connected with 'or', but the regexp is ultimately compiles in 'verbose' mode, so the lines are just strung together. This is where the documentation is wrong. This is all clarified and fixed in Mailman 2.2.
The problem in 2.1 is when you enter the regexp, we validate in by attempting to compile it normally, so we check 'Wohnung*\r\n*wohnung*' which doesn't mean what you want, but is valid, but when we use it we compile effectively 'Wohnung**wohnung*' which is not valid and throws the exception.
Note that the regexp is matched case insensitively in any case.
|
|
|
