[ mailman-Bugs-1484722 ] Topic regexes are never applied

[SourceForge.net]

Bugs item #1484722, was opened at 2006-05-09 07:28
Message generated for change (Settings changed) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1484722&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: 2.1 (stable)
>Status: Pending
Resolution: None
Priority: 5
Submitted By: Jesse Keating (jkeating-redhat)
Assigned to: Nobody/Anonymous (nobody)
Summary: Topic regexes are never applied

Initial Comment:
Topic filters are checked via a provided regex.  The
code that applies regexes to a message, and tags a
message with a topic and adds a header is called
Tagger.process.  This function is only called by a
test/ script, to test the code path.  In the production
code Tagger.process is never called, so a mail is never
checked/tagged with a topic, and thus when later
checked for who it should be delivered to based on
topic, it has no topic so it doesn't get delivered
correctly.

This is 2.1.8.

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2006-05-10 20:02

Message:
Logged In: YES 
user_id=1123998

Yes, Tagger is in GLOBAL_PIPELINE, so unless you have
redefined GLOBAL_PIPELINE in mm_cfg.py to not include Tagger
or the list has a pipeline attribute defined (default lists
don't) that doesn't include Tagger,
Mailman.Handlers.Tagger.process() is called by
IncomingRunner in processing the message through the pipeline.

----------------------------------------------------------------------

Comment By: Jesse Keating (jkeating-redhat)
Date: 2006-05-09 07:52

Message:
Logged In: YES 
user_id=1519854

Upon closer looking, it would seem that this could be called
through a pipeline.  I'm looking in our config to see if we
haven't defined this as a pipeline.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1484722&group_id=103