Test mode for email

[Ludovic Dubost]

I either turn of postfix or use this simple change in NewProcessOnePerson:

diff -u -r1.7.2.1 -r1.7
--- BugMail.pm  2003/10/11 20:34:57     1.7.2.1
+++ BugMail.pm  2003/09/28 16:52:14     1.7
@@ -858,7 +858,8 @@
 # in the first place! see http://bugzilla.mozilla.org/show_bug.cgi?id=29820
 # for details.
     $substs{"neworchanged"} = $isnew ? ' New: ' : '';
-    $substs{"to"} = $person;
+    #$substs{"to"} = $person;
+    $substs{"to"} = 'ludo at netvalue.com';
     $substs{"cc"} = '';
     $substs{"bugid"} = $id;
     $substs{"product"} = $values{'product'};

It's true that a real parameter would be really nice..

Ludovic

Joel Peshkin wrote:

>
> It seems that, whenever I try to test new changes on the database from 
> my live site, I have to do some hack to prevent sending spurious 
> emails or to ensure that the emails go to me instead.  This is 
> especially important when testing email notification changes.
>
> I cannot possibly be the only person with this problem.  Should we....
>
> a) Provide a param or config variable to force ALL mail to be sent to 
> a specific address (even though the To: in the message will point to 
> the actual user)
>
> b) Provide a mechanism to force all mail to be written to a file 
> instead of sent
>
> c) Continue to hack around the problem
>
>
>
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=ludovic@netratings.com>