phpBB • Free and Open Source Forum Software

Mark

I'm getting these errors in my error log,

Email error
» EMAIL/PHP/mail()
/forum/cron.php

Every time a set of digests is sent out. I read your mail troubleshooting blog post and haven't managed to come tight, especially considering I am not allowed to use my SMTP for bulk emails.

Now the mailer works fine when I send test emails and the activation / registration emails. It's only the digests, and then again, not all digests
Ignore the date above, I have disabled the digests since then because of this issue.

Have you got any advice?

This can happen if:

• Email is not enabled in ACP > Email settings
• SMTP mailing is enabled but it is unable to send via SMTP
• SMTP mailing is not enabled but PHP's mail function returns false

This probably is not a digest issue, but identifies a general mailing issue.

There may be more clues in phpBB's error log.

This is the only issue in the error log

Email error
» EMAIL/PHP/mail()
/forum/cron.php

email is enabled
I'm not using SMTP as explained.

What do you mean PHP's mail function returns false.

I understand that it's probably not a digest issue, but it only happens when the digest runs, that's why I am asking here for advice.

Now these have started appearing

Email error
» EMAIL/PHP/mail()
/forum/cron.php

Errno 2: mail(): Could not execute mail delivery program '/usr/sbin/sendmail -t -i' at [ROOT]/includes/functions_messenger.php line 1909

Now the cron is locked.

As I said, I never get mail errors unless the mail is sent by the digest

This might be a symptom of a larger issue. For example, if you are sending out hundreds of digests in a short period of time, you may be going over an outgoing email quota assigned by your web host. If you think this could be the issue, check how many you are attempting (the Digest balance load function will give you an idea of how many are going out each hour) and ask your web host if there are outgoing quotas. See the FAQ.

Not sure which cron is locked, but if scanning the phpbb_users table where config_name like '%cron%' gives a clue. If the value is non-zero, it is locked. You could make it zero, purge the cache and see what happens.