The following NEW bug has been ADDED.

If I add
$g_use_bcc = OFF;

(Which wasn't needed before 0.18.0a3)
I do not get errors, bu I do not get any e-mails either ;-)

Because we are using the BCC send mail feature of php mail - does that mean, that bcc:-sending doesn't work actually?
If so, please fix it til 0.18.0 release, please

In 0.17.5, 0.18.0a1 and 0.18.0a2 I used the BCC feature on W2K and did not experience any problems (PHP 4.3.0), but with 0.18.0a3 I have not received a single mail yet.

(Before 0.18.0a3 I didn't use $g_use_bcc = OFF; and mailing just worked as it should.. But now it doesn't at all.)

(The Bcc field of the error message is empty, while I would assume it should contain the real receipents)

I had to add:

$g_default_notify_flags['threshold_min'] = DEVELOPER;
$g_default_notify_flags['threshold_max'] = ADMINISTRATOR;
$g_email_receive_own = ON;

after upgrading to 0.18.0a3, to keep the same behevior as before for developer-admin.

The BCC error page is the real bug. There were no receipents for the bug report without these added settings, as was noted by the mail server.

ok, someone should look at this then.

We intended to add a note to the release notes about that config change - sorry about that. But there shouldn't be an error with no recipients. I take it this only happens when use_bcc is off?

As an aside, make sure you run the admin/check.php page after an upgrade. It will tell you any config options you may have overriden that are now obsolete. In this case it wouldn't help because we actually changed the default behaviour. Perhaps we should put the behaviour back so that developers get emails by defaults. The issue was that a lot of people didn't like admins getting emails by default - and I couldn't think of a default that would really make everybody happy.

A fix for the bcc error with no recipients:

In email_api.php
line 285

Currently:

win-bcc-bug

    if ( $t_use_bcc ) {
        $t_bcc .= "\n";
    }

Change this to:

win-bcc-bug

    if ( $t_use_bcc and strlen($t_bcc) > 5  )
       {
        $t_bcc .= "\n";
       }
    else
       {
        $t_bcc = "";
       }

The problem actually was created up in line 279, but it's probably easier to fix it here. The length of 5 is to account for "Bcc: " (as inserted in 279).

And I don't think you'll get a valid email address that's less than 5 characters anyway, so there shouldn't be a problem even if the "Bcc: " isn't inserted (see 279).

edited on: 03-12-03 21:49

I used a different fix (which should work regardless of the size of the email adress), which has been committed to CVS and should be in the next release.