Even when seeing the bad behaviour, when looking at all "msg" objects
(using roundup-admin      table msg ) they all have a correct tx_Source
value.

In trying to see better what is going one, I've made a difference between
being called as "set" or "create":


diff -r 26a138760969 detectors/txSource_detector.py
--- a/detectors/txSource_detector.py    Wed Jan 02 22:26:31 2013 +0100
+++ b/detectors/txSource_detector.py    Fri Jan 04 23:32:37 2013 +0100
@@ -38,6 +38,10 @@
     # if db.tx_Source == "email":
     #    raise Reject, 'Change not allowed via email'
 
+def txSourceCheckAuditSet(db, cl, nodeid, newvalues):
+    print "called on 'set'"
+    return txSourceCheckAudit(db, cl, nodeid, newvalues)
+
 def txSourceCheckReact(db, cl, nodeid, oldvalues):
     ''' An reactor to print the value of the source of the
         transaction that trigger this change. The sleep call
@@ -54,8 +58,12 @@
     time.sleep(10)
     print "txSourceCheckReact(%s) post db.tx_Source: %s"%(nodeid, 
db.tx_Source)
 
+def txSourceCheckReactSet(db, cl, nodeid, oldvalues):
+    print "called on 'set'"
+    return txSourceCheckReact(db, cl, nodeid, oldvalues)
+
 def init(db):
-    db.issue.audit('set', txSourceCheckAudit)
+    db.issue.audit('set', txSourceCheckAuditSet)
     db.issue.audit('create', txSourceCheckAudit)
-    db.issue.react('set', txSourceCheckReact)
+    db.issue.react('set', txSourceCheckReactSet)
     db.issue.react('create', txSourceCheckReact)