[rodneytamblyn]

Hi Cyricx,

A few email integration woes today.

I have about 15 forums enabled with EI addresses. A user complained that mails being sent to one of the addresses were not being delivered. I ran the cron job manually and discovered it complaining:

Fatal error:
* The text that you have entered is too long (10328 characters). Please shorten it to 10000 characters long.
Unable to proceed with save while $errors array is not empty in class vb_datamanager_thread_firstpost in [path]/includes/class_dm.php on line 810

Fair enough, I increased the maximum post length. Bad mistake. Turns out there were a lot of messages queued up in other forum email accounts. The system went crazy and generated thousands of email messages before I realised what was going on.

Next issue I found:

Fatal error: Call to a member function on a non-object in /Users/oceanbrowser/Sites/forum/includes/cron/emailintegration.php on line 1615

This has been referred to elsewhere, I applied the fix changing that line to $plaintext_parser->set_parsing_language( 1 )

However I also got this error which I haven't seen reported:
Fatal error: Call to a member function on a non-object in /Users/oceanbrowser/Sites/forum/includes/cron/emailintegration.php on line 1093

Applied your fix to that line too.

Next I got this error:

Fatal error:
* This forum requires that you wait 30 seconds between posts. Please try again in 30 seconds.
Unable to proceed with save while $errors array is not empty in class vb_datamanager_post in [path]/includes/class_dm.php on line 810

It's very difficult to work out which forum is affected. Would be great if the error messages in the cron also outputted the details of the email message being processed (which would also show the forum being sent to)

I still haven't solved the last above issue, have disabled EI in the forum tonight and will have to spend more time tomorrow investigating that.

The installation documentation should warn users to check the maximum post length and be aware that if an email comes in that exceeds this length it will stop ALL processing of emails in all lists - i.e. when an error occurs the cron job doesn't log it and continues, it aborts. And if you change that setting later, it can initiate an email flood if you have an accumulated backlog of messages.

For some reason (also TBD) EI posted the same messages over and over into the forum - I think it was erroring out before it had a chance to delete the messages (?) then next time the script ran, it posted them again. Would be good if the posting mechanism checked for duplicate post, and also if there could be some in-build flood protection measures.

~ Rodney