Error: Could not instantiate mail function

[vegasgeek]

WP Version: 3.2-bleeding (rev 17693)

Error Message:
Could not instantiate mail function. Could not instantiate mail function. Could not instantiate mail function.
Warning: Cannot modify header information - headers already sent by (output started at /var/www/wpcore/wp-includes/class-phpmailer.php:586) in /var/www/wpcore/wp-includes/pluggable.php on line 885

Process to reproduce:
In network admin, Add site. After submiting new site details, the above error message shows up.

Notes:
This is running on my local dev server that does NOT have mail functionality turned on. Although it's no surprise that it can't send email, this error message is new as of the past 3 days (sorry I don't know the previous revision number I was on). Prior to an SVN UP a couple days ago, adding new sites would work fine and the mail portion would fail gracefully.

[vegasgeek]

Forgot to mention, the new site gets created successfully.

[dd32]

This will be related to the new PHPMailer version: #15912

[dd32]

basically, PHPMail now uses exceptions.

Here's an example of a API function:

    if (!self::ValidateAddress($address)) {
      $this->SetError($this->Lang('invalid_address').': '. $address);
      if ($this->exceptions) {
        throw new phpmailerException($this->Lang('invalid_address').': '.$address);
      }
      echo $this->Lang('invalid_address').': '.$address;
      return false;
    }

So other than modifying phpmailer to remove all the echo's for any failure of any kind, we can wrap every API call in a try {}..

[ryan]

We could probably ignore and continue instead of return in some of those places.

[ryan]

Yep, the destinations can all be continues. If all destinations end up empty then Send() will throw an exception and we'll catch that and return false. This is more in line with previous behavior.

[ryan]

(In [17753]) Use exceptions with phpmailer to avoid headers already sent errors. fixes #17228