On 11/24/2015 06:53 PM, Stephen J. Turnbull wrote: > Adrian Pepper writes: > > Am I correct in my conclusion that .* won't match newline characters, > > but <space-chars><not-space-chars><linefeed><carriage-return> will ? > > (And also, that that is the character class I created). > > Yes. Here are the docs for Python regular expressions as used in > Mailman: https://docs.python.org/2.7/library/re.html. > > In general this problem would be addressed with the DOTALL flag: > > The special characters are: > > '.' > (Dot.) In the default mode, this matches any character except a > newline. If the DOTALL flag has been specified, this matches any > character including a newline. > > Note that the definition of "newline" here is exactly "\n".
Note you can turn on DOTALL in the regexp itself. so while Farmers[_ ]Weekly.*Ac doesn't match, (?s)Farmers[_ ]Weekly.*Ac will (see docs referenced above). > > Empirically I see ?=\n =?utf-8?q?_ after "Weekly" and before "Ac". > > (And it seems the matching is done on the incoming subject, not the > > one formatted for resending, which, with my tag, and the utf-8 > > of an incoming tag pushes the expression entirely onto the second > > line where I think the ".*" variant (or even [_ ]) would match. This is all a bug in not decoding RFC2047 encoded headers before matching. See <https://bugs.launchpad.net/mailman/+bug/891676> fixed in Mailman 2.1.15. -- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
