CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • EmailProcessor error message - 'No clue about the ezcMailDeliveryStatus'
Pages: [1]

Author Topic: EmailProcessor error message - 'No clue about the ezcMailDeliveryStatus'  (Read 1494 times)

gibsonoliver

  • I post occasionally
  • **
  • Posts: 65
  • Karma: 2
    • Northbridge Digital
EmailProcessor error message - 'No clue about the ezcMailDeliveryStatus'
March 15, 2013, 03:39:13 am
Hi

I'm working with an organisation who are using CiviCRM 3.4.8 on a Joomla install.
The EmailProcessor isn't running properly, I suspect this is a bug but I'm not sure.
Unfortunately they can't update their version right now as a previous employee has inserted lots of custom code which we haven't got to the bottom of yet.

When you run the email processor the backTrace is;
/home/sroiuk/public_html/administrator/components/com_civicrm/civicrm/CRM/Core/Error.php, backtrace, 296
/home/sroiuk/public_html/administrator/components/com_civicrm/civicrm/CRM/Utils/Mail/Incoming.php, fatal, 76
/home/sroiuk/public_html/administrator/components/com_civicrm/civicrm/CRM/Utils/Mail/Incoming.php, formatMailPart, 164
/home/sroiuk/public_html/administrator/components/com_civicrm/civicrm/CRM/Utils/Mail/Incoming.php, formatMailMultipartReport, 98
/home/sroiuk/public_html/administrator/components/com_civicrm/civicrm/CRM/Utils/Mail/Incoming.php, formatMailMultipart, 72
/home/sroiuk/public_html/administrator/components/com_civicrm/civicrm/CRM/Utils/Mail/Incoming.php, formatMailPart, 250
/home/sroiuk/public_html/administrator/components/com_civicrm/civicrm/bin/EmailProcessor.php, parseMailingObject, 211
/home/sroiuk/public_html/administrator/components/com_civicrm/civicrm/bin/EmailProcessor.php, _process, 122
/home/sroiuk/public_html/administrator/components/com_civicrm/civicrm/bin/EmailProcessor.php, process, 400

Error message is 'No clue about the ezcMailDeliveryStatus'

Does anyone know what the error issue is?
Any help really appreciated.

Oliver
Oliver Gibson, Northbridge Digital

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: EmailProcessor error message - 'No clue about the ezcMailDeliveryStatus'
March 15, 2013, 08:40:31 am

that file (CRM/Utils/Mail/Incoming.php) has not changed a lot since 3.4.x, i think your best bet might be to see the version of the file in 4.2 and potentially copy over any changes from the 4.2 copy

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

gibsonoliver

  • I post occasionally
  • **
  • Posts: 65
  • Karma: 2
    • Northbridge Digital
Re: EmailProcessor error message - 'No clue about the ezcMailDeliveryStatus'
March 18, 2013, 02:40:27 am
Thanks Lobo!

I'll give that a try

Olly
Oliver Gibson, Northbridge Digital

ChrisChinchilla

  • I post occasionally
  • **
  • Posts: 104
  • Karma: 3
  • CiviCRM version: 4.1.2
  • CMS version: Drupal 6 & 7
Re: EmailProcessor error message - 'No clue about the ezcMailDeliveryStatus'
May 14, 2013, 10:13:04 pm
I've been tracking down this problem for ages with a client, tried replacing the incoming.php file with a more recent version (which as far as I can tell, was no different) and still the same problem.

I have to figure this out, so will keep you posted!
Melbourne CiviCRM meetup group - http://www.meetup.com/MelbourneCiviCRM/

ChrisChinchilla

  • I post occasionally
  • **
  • Posts: 104
  • Karma: 3
  • CiviCRM version: 4.1.2
  • CMS version: Drupal 6 & 7
Re: EmailProcessor error message - 'No clue about the ezcMailDeliveryStatus'
May 14, 2013, 10:51:12 pm
So far I have come up with one solution… To remove the fatal error code. I'm sure that's not ideal, but it seems to work, if anyone with more knowledge of what that file is doing would like to comment I'm happy to try a few things.
Melbourne CiviCRM meetup group - http://www.meetup.com/MelbourneCiviCRM/

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: EmailProcessor error message - 'No clue about the ezcMailDeliveryStatus'
May 15, 2013, 06:51:59 am

A better idea might be to throw an exception which is caught at the top of the mail loop and that email is moved into the "dont know what to do with this folder"

that way other emails can be processed

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

ChrisChinchilla

  • I post occasionally
  • **
  • Posts: 104
  • Karma: 3
  • CiviCRM version: 4.1.2
  • CMS version: Drupal 6 & 7
Re: EmailProcessor error message - 'No clue about the ezcMailDeliveryStatus'
May 15, 2013, 03:31:12 pm
But this was the problem with the current code, with the error, if it doesn't know what to do it stops completely and nothing gets processed beyond the problematic message.

Removing the error still seems to make it process messages it couldn't understand correctly, which is equally strange. I feel this needs more investigation, but not really sure where to start with it all, the actual processing code is beyond me!
Melbourne CiviCRM meetup group - http://www.meetup.com/MelbourneCiviCRM/
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • EmailProcessor error message - 'No clue about the ezcMailDeliveryStatus'

This forum was archived on 2017-11-26.