E-mail not being sent for bugs

[David Miller]

Kamal Ahmed wrote:

> I have a bugzilla installation, and found out the a lot of bug
> notifications were not being sent to bug owners, and admins.
> 
> When I ran http://bugzilla.esecurityinc.com/sanitycheck.cgi , I found
> that there were 1000 unsent mail, now If I run "processmail rescanall"
> I will flood our MS Exchange , is there a way out of this situation ?

This is more of a support question than a development issue, so probably 
belongs on the mozilla-webtools list instead of here.

But since we're here... :)  There are some conditions which trigger the 
unsent mail notice which won't actually send mail.  In 2.16.x there were 
a couple situations where a change would happen that did not require any 
mail to be sent, and the flag saying it had been dealt with didn't get 
set.  The test in sanitycheck is just looking for mail that has changes 
more than a half hour old that don't have that timestamp updated to show 
the mail was sent for it.  When "processmail rescanall" gets run, it 
will then notice that there wasn't actually any mail necessary, and just 
update the timestamp without sending anything.

However, that's only one possibility.  It's also probably equally likely 
if process_bug is having problems that there really is changes requiring 
mail on those bugs and you will send off thousands of mails.

If you just want to wipe the slate clean, you can run this SQL:

UPDATE bugs SET lastdiffed = NOW();

If you are having this crop up frequently, you may want to set up a cron 
job that runs processmail rescanall once a night or something.

It does happen a lot less in the 2.18 candidates than it does in 2.16, 
but it still happens occasionally.  The mail code is all getting 
rewritten in either 2.20 or 2.22, and that will hopefully be permanently 
dealt with at that point.

-- 
Dave Miller      Project Leader, Bugzilla Bug Tracking System
http://www.justdave.net/             http://www.bugzilla.org/