After installing enewsletter and all of its component modules, my cron job (which runs every hour) stopped working. In the watchdog, I get over and over 'Last cron run did not complete'.
The administrative and subscription APIs of the module seem to be working all right, but the newsletters I created are not being sent.
When I disable module and components in administer > modules, the cron job comes back to life.

It is evident some of the tasks invoked by the cron hook is broken - the point is which, and how to fix it.

I'm running Drupal 4.6 on Unix platform.

Thank you!

Comments

robert castelo’s picture

robert castelo commented

It's probably the bounced email handling which is causing the problem.

See here:

http://drupal.org/node/33082

I've got some time on Thursday I've scheduled to go through all the bug reports, hopefully be providing a fix then.

solaas’s picture

solaas commented
Title: enewsletter breaks my cron job » Yep

That was it.
I just commented all the contents of the bounced_email_cron() function, and now it is working. I got my first newsletter as a subscriber to my own site.
The point is, I was not getting any error messages either. I think it's natural that things don't work now and then, but in such cases I love to get some information. It makes life a lot easier.
Plus, the undelivered mail handling is not very important for me. I still don't understand very well why is pop or imap access necessary at all.

Whatever, I think this set of modules is a wonderful development and has a great potential. I'll be giving a hand as beta-tester, because I'm already implementing it for a customer that was needing just that.
Thanks for the effort.

dman’s picture

dman commented

Cron error messages are notoriously hard to find, in all environments. :)
cron executes (and sometimes dies) without you ever having to know about it. In theory.

If you patch with the conditional I documented, instead of commenting everything, it'll log to watchdog and be more apparent.
I agree the return handling could be set to be 'optional' in the settings, but it's good practice (in a mailout situation like this) to encourage bounce handling by default.

.dan.

pfaocle’s picture

pfaocle
He/Him
Primary language English
commented
Title: Yep » bounced_mail cron causes run to fail with IMAP errors

Setting back to sensible title.

robert castelo’s picture

robert castelo commented

OK, who's in the mood for some testing?....

I've updated bounced_email.module, should now fail gracefully if it can't connect.

Publications.module and enewsletter.module have also been updated, make sure to read the UPGRADE notes in the enewsletter README.txt

robert castelo’s picture

robert castelo commented
Status: Active » Fixed
robert castelo’s picture

robert castelo commented
Status: Fixed » Closed (fixed)