Roundup Tracker - Issues

Issue 931884

classification
Enable bcc for nosy message
Type: Severity: normal
Components: None Versions:
process
Status: closed fixed
:
: : myers_carpenter, richard
Priority: normal : patch

Created on 2004-04-08 17:53 by myers_carpenter, last changed 2004-04-18 05:40 by myers_carpenter.

Files
File name Uploaded Description Edit Remove
bcc.patch myers_carpenter, 2004-04-08 17:53 enable the bcc field
Messages
msg2684 Author: [hidden] (myers_carpenter) Date: 2004-04-08 17:53
At work we use roundup, and we have two users that need
to see "EVERYTHING" that happens on the issue tracker.
 Two solutions: 1) add a auditor that added their
usernames to the nosy list, 2) bcc a message to mailing
list

I liked #2 better because then the users could filter
the mailing list to a folder and still get nosy list
messages that where sent to the explictly in their Inbox.

This patch enables the bcc feature, so I just had to
add a roundup user for the mailing list, then figure
out what the user key was, then change
"nosyreaction.py" to: 


    for msgid in determineNewMessages(cl, nodeid,
oldvalues):
        try:
            cl.nosymessage(nodeid, msgid, oldvalues,
bcc=['20'])
        except roundupdb.MessageSendError, message:
            raise roundupdb.DetectorError, message

Where 20 was the key of mailing list user.
msg2685 Author: [hidden] (richard) Date: 2004-04-10 22:28
Logged In: YES 
user_id=6405

I'm not sure I follow why Bcc is needed when Cc is available... 
msg2686 Author: [hidden] (myers_carpenter) Date: 2004-04-18 05:40
Logged In: YES 
user_id=335935

Because I didn't want the messages going to the list to
include others it it's "CC" field.  
msg2687 Author: [hidden] (richard) Date: 2004-04-18 05:53
Logged In: YES 
user_id=6405

OK, I've applied the patch to 0.7 (I'd really rather not apply it 
to 0.6 as I don't want to introduce any new features there) 
 
History
Date User Action Args
2004-04-08 17:53:42myers_carpentercreate