* W. Trevor King <issues@roundup-tracker.org> [20120515 18:54]:
> I also agree that `newissuecopy.py' is important.  After reading the
> config comments:
> 
>   # The 'dispatcher' is a role that can get notified
>   # of new items to the database.
> 
> It seems to me that DISPATCHER_EMAIL should be notified of all new
> items, not just bounced messages as is currently hardcoded into
> Mailer.bounce_message.
> 
> I've attached a tweaked version of `newissuecopy.py' that implements
> this for all items.  I thing that a number of email-generating methods
> from IssueClass should actually be Item methods, so they can also be
> used on non-Issue nodes.  This would remove a lot of the duplicated
> code from my `newitemcopy.py'

We nearly always use newissuecopy.py to inform some users or a
public mailing list about new issues (or in one case new merge
entries), but not about everything.

DISPATCHER_EMAIL is the supervisor who wants to be notified about
everything, so this is something different.

First step should be to revive the removed detectors. But yes,
providing more flexibility with less code duplication would be nice,
as would be the possibility to set the newissuecopy recipients in
config.ini (without preventing configuration in newissuecopy.py
itself of course).

Regards,
Thomas