fix for bug found in original 17464 patch, where removal from the CC list was not generating a mail.  r=donm@bluemartini.com

patch from bug 17464 to give user some control over what sorts of bug mail get sent to an account.  Original patch by al_raetz@yahoo.com and lots of additional hacking by me; r=donm@bluemartini.com

patch by JRobertson@medevolve.com (Jon Robertson)

patch submitted by zach@math.berkeley.edu, additional commentary by
cyeh@bluemartini.com.

patch submitted by john.beranek@pace.co.uk (John Beranek)

sendmail deferred vs immediate delivery Param is now honored even in Perl
5.6.

extra "<" in FormatTriple so that old/new are the same size

patches by mtakacs@pacbell.net.

details)

the difference between new comments and people copying stuff in from
old comments.

bottom.  Made "My bugs" show bugs you own AND bugs you submitted.
Added ability to display your named queries in the footer.  Many
random bugfixes.

Added "My votes" link to footer.  Other minor voting-related fixes.

dependent bugs.

different fields we keep an activity log on.  The bugs_activity table
now has a pointer into that table instead of recording the name directly.

Set up a new, highly experimental email-notification scheme.  To turn
it on, the maintainer has to turn on the "New email tech" param, and
then individual users have to turn on the "New email tech" preference.

me.  Added a footer to every page.  Add some options to do things like
display checkboxes instead of scrolling lists, and a new formatting
for email diffs, and show list items capitalized instead of all upper
case.

away from them or they get removed from the CC list.

it to report the resolution of the bug instead of the word "closed".
Many thanks to dbaron@fas.harvard.edu for suggesting this change, and
reporting the bug.

state on dependent bugs if they move from an 'open' to a 'closed'
state, or visa-versa.  Also, if there are more than 5 bugs on the
list, then we won't even try to generate the details (doing so only
generates lots of extra mail that is too hard to parse anyway.)

any mail that ought to be sent to someone.

be fixed.

than once (in case our mail transport is too stupid to remove the dups
for us).

usernames for email addresses.

case of the login, which might differ from the case in the database.

other ones.

the change (after all, they are right there viewing things interactively).
To make this clear to everyone, print out the exact email list as each
bug is processed.