From: Kenzaburo I. <ke...@30...> - 2002-06-11 18:42:31
|
Unless there's a bug, you should just be able to turn off all your email notifiation events in your account preferences. Thanks, -Ken > Hi- > > One thing that would be nice (definitely not a priority!) would be an > ability to not send out an e-mail to the person who made the change to a > defect. Since I do most of the bug entry/maintenance on our system, I'm > bombarded with e-mails which I already know the contents of :-) > > I've been doing some looking into it, but I'm not sure how to do it without > storing in the db the id of the person who made the last change (yuck!). > Just a thought, it may be possible to grok the cookie to get the ID? > > Should this be a forum and/or BugTracker entry? > > -ed > > -----Original Message----- > From: Kenzaburo Ito [mailto:ke...@30...] > Sent: Wednesday, June 05, 2002 6:32 PM > To: man...@li... > Subject: [Mantisbt-dev] Email Rewrite > > > Hello all, > > Jeroen and I are going to embark on rewriting core_email_API.php. Right > now > the code is a mess and needs to be consolidated and rewritten for our > needs. > > Here are our core requiremnets: > > * Send mails in each users localized language > * Send mails based on access to the view_state of the bug > * Filter private/public bugnotes according to access > * Honor user preferences > * Send mail to those monitoring bugs > * Work on any platform/SMTP server > > Here are wanted items: > > * Email templates > * Custom Mantis headers > > As a result of localized versus private/public bugnotes I don't think we > can > get away with BCC/CC'ing users anymore. > > Email templates would be so that multiple forms of the message(s) could be > sent to different users. For example, many users use blackberries > (portable > email devices) which have a screen width of about 24 characters. We can > use > templates to try to fit messages into that form factor. > > Pros: Cleans and simplifies code. Needs to be done to comply with listed > requirements. > > Cons: The performance impact could be significant unless messages are > queued. > Not all servers may have an easily accessed queueing capability. However, > our > chosen email class, phpMailer, may have queueing functionality at some > point. > > We plan to proceed by creating a second core_email2_API.php file and making > that functional then switching over. > > We plan on using phpMailer to completely replace our homebrew mail() > solution. > It's LGPL and we should have no problems using it. Some may want to use > PEAR > but I'm leery of using it yet. > > Thanks, > -Ken > > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > Mantisbt-dev mailing list > Man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |