1961148 - Bugzilla becomes non-functional if you do anything that wants to send an email before configuring email in the params

Status: RESOLVED FIXED

(Bugzilla :: Administration, enhancement)

Description

[Dave Miller [:justdave]]

On a clean install of Bugzilla 5.2, If you do something in Bugzilla that makes it send an email and you haven't yet configured the email in the params, Bugzilla will crash loading any page after that and you have no way to get to params to fix it.

If you don't have a mail transport agent installed, the error complains that it can't find sendmail. If you do have one installed, it complains that there is no sender set on the email. Both errors prevent further access to Bugzilla until you either truncate the mail_staging table or fix the config manually from the shell.

The quick fix is these errors should be informational and non-fatal, so you can still do things in Bugzilla like fix the config.

The error itself should look nicer, too. There's no reason we need to show the user a stack dump to tell them "you're configured to use sendmail but don't have sendmail installed"

Comment 1

[BMO Github Automation]

Attachment: [bugzilla/bugzilla] [5.2] Bug 1961148: Make mail configuration errors non-fatal (#216)

Comment 2

[Dave Miller [:justdave]]

While it would be nice to get the cool non-fatal error messages in harmony, the initial problem (blocking the admin from fixing the problem) does not appear to be present in Harmony. You do get a fatal error in harmony, but it doesn't persist across page loads like it does in 5.2, so the admin can still get to the params page. Not going to waste the time porting this to harmony then, since I'm on a budget. :-)

Comment 3

[Dave Miller [:justdave]]

Comment on attachment 9599493 [details] [review]
[bugzilla/bugzilla] [5.2] Bug 1961148: Make mail configuration errors non-fatal (#216)

landed on 5.2:
https://github.com/bugzilla/bugzilla/commit/50f709562f0b48e694ce3eaff0d1704fd4e316ce