On Wed, Nov 18, 2009 at 08:03:02 +0100, Joachim Breitner wrote: > > How about this? > > ^This patch bundle.* is now tracked on DarcsWatch at > > http://darcswatch.nomeata.de/repo_http:__darcs.net_.html > > yes, should work.
Hmm, looks like this is not the case. I think it's only filtering on headers that's at work. And as you guessed above, it is applying an 'or' on the regexps: | Each header filter rule has two parts, a list of regular expressions, one per | line, and an action to take. Mailman matches the message's headers against | every regular expression in the rule and if any match, the message is rejected, | held, or discarded based on the action you specify. Use Defer to temporarily | disable a rule. You can have more than one filter rule for your list. In that | case, each rule is matched in turn, with processing stopped after the first | match. Note that headers are collected from all the attachments (except for the | mailman administrivia message) and matched against the regular expressions. | With this feature, you can effectively sort out messages with dangerous file | types or file name extensions. Anyway, I've disabled the rule completely, but now we have a few too many notifications on the list :-) Perhaps DarcsWatch could avoid sending its 'now being tracked' notification messages? Alternatively, there's the complicated solution of hacking up one of our Roundup detectors to implement the notion of 'mailing-list users' and 'admin users' (the idea being that emails from admin users never go to mailing list users). This would build off the 'quiet' users notion you kindly implemented for us :-) Thanks! -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
pgphyotHiJnbR.pgp
Description: PGP signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
