[Mailman-Users] Simple notification handler
yves.moisan at boreal-is.com
Thu Dec 22 20:42:29 CET 2011
It seems the handler stops the list from working. When I delete the new
pipeline the list works fine so it's the Python file (or the way I
included it in the pipeline ?) that has a problem.
I've tried including a she-bang line or not (see below for both the
handler and the text file used to shove it in the list pipeline),
importing Message in addition to UserNotification and a few other things
to no avail. One thing I find odd is that the handler doesn't get a
.pyc file upon restart. Should I expect that or does it get created the
first time it is invoked ?
I've copied the file over from a windows machine and I took care of
chowning it so it has the same permissions as the other Handlers. The
file looks ok in vi. What other options do I have before pdb ?
=== BackupErrors.py ===
#!/usr/bin/python # I also treid without, like in the other handlers on
"""Add a list specific alert generator in case there was a problem in
the backup, in which case the Subject of the email will contain the word
from Mailman import Utils
from Mailman.Message import UserNotification
# from Mailman.Message import Message,UserNotification
NTEXT = """Texte du corps du
NRECIP = 'xyz at example.com'
NFROM = 'abc at example.com'
NSUBJ = 'Error in backup'
def process(mlist, msg, msgdata):
subject = Utils.oneline(msg['subject'], 'us-ascii')
if re.search('.*error.*', subject, re.IGNORECASE)
nmsg = UserNotification(NRECIP, NFROM, NSUBJ, NTEXT)
=== backupHandlerPipeline.txt ===
mlist.pipeline = [
# These are the modules that do tasks common to all delivery paths.
# And now we send the message to the digest mbox file, and to the
# news queues. Runners will provide further processing of the message,
# specific to those delivery paths.
# Now we'll do a few extra things specific to the member delivery
# (outgoing) path, finally leaving the message in the outgoing queue.
More information about the Mailman-Users