Fatal error: Class 'ezcMailPop3Transport' not found [SOLVED]

[bcobin]

I'm trying to set up CiviMail according to the instructions at http://en.flossmanuals.net/CiviCRM/SystemConfiguration and when I try to check the Email processor via browser, I get the following message:

connecting to xxx.xx.xxx.xxx and authenticating as [user]
Fatal error: Class 'ezcMailPop3Transport' not found in /home/[user]/public_html/sites/all/modules/civicrm/CRM/Mailing/MailStore/Pop3.php on line 57

Same basic message using IMAP.

Not using SSL on the site - any idea what's going on here? Thanks!

[Roman Zimmermann]

I've encountered the same problem. It seems that the ezc-autoloader function is somehow disfunctional. The code that defines it is executed though. I will report back here when I have found a solution …

[bcobin]

Thank you for looking into this! Been struggling with this for about a week now without success (but I'm not a coder...)

Awaiting anxiously!

[Roman Zimmermann]

So here we go …

For me the problem was that some other drupal modules used the spl_autoload stack to autoload their classes. This makes __autoload ineffective and breaks ezc. If you apply the following patch to packages/ezc/Base/src you should be fine:

Code: [Select]

--- ezc_bootstrap.php.orig      2010-11-02 18:32:47.000000000 +0100
+++ ezc_bootstrap.php   2010-11-02 18:33:16.000000000 +0100
@@ -28,7 +28,9 @@
 }
 
 // Joomla, libraries/loader.php, already defined __autoload
-if ( !function_exists("__autoload") ) {
+if ( spl_autoload_functions() !== false ) {
+       spl_autoload_register(array('ezcBase', 'autoload'));
+} elseif ( !function_exists("__autoload") ) {
     /**
      * Implements the __autoload mechanism for PHP - which can only be done once
      * per request.

When I have the time I'll probably send this patch upstream.

I hope this does solve your problem too.

[bcobin]

You are a beautiful person. HOORAY!

The patch didn't apply:

Code: [Select]

patching file ezc_bootstrap.php
patch unexpectedly ends in middle of line
Hunk #1 FAILED at 28.
1 out of 1 hunk FAILED -- saving rejects to file ezc_bootstrap.php.rej
But I made the change manually and it looks like the system is merrily processing bounces! Thank you SO much!

Now, to fix the "bounced emails 'on hold'" issue... but that's another story.

This is a bit off-topic, but you obviously know what you're talking about, so I'll ask: what's the difference between the EmailProcessor.bin and CiviMailProcessor.bin scripts? The manual now specifies the EmailProcessor, but earlier documentation recommended CiviMailProcessor.

Thanks again for taking care of this!

[xavier]

Yeap, the book is up to date and that's EmailProcessor you should use.

If I recall properly, two scripts (handling the bounces and incoming emails respectively) have been merged into EmailProcessor.

This is a bit off-topic, but you obviously know what you're talking about, so I'll ask: what's the difference between the EmailProcessor.bin and CiviMailProcessor.bin scripts? The manual now specifies the EmailProcessor, but earlier documentation recommended CiviMailProcessor.

[Roman Zimmermann]

Nice to know. It seems that not all of documentation is updated.

http://wiki.civicrm.org/confluence/display/CRMDOC32/CiviMail+Processor still refers to CiviMailProcess.php

[CiviTeacher.com]

I was using the Autoload   6.x-2.0-rc1 module on my Drupal as required by dev versions of Organic Groups.  This module caused the CiviMailProcessor to fail.  I made the hack that is show in this post and the CiviMailProcessor began working.

[Eileen]

This fixed the problem for me. I tried to log on the ezcmail site as an issue but the site stopped working for me

[Eileen]

http://issues.ez.no/IssueView.php?Id=17821&activeItem=1
http://issues.civicrm.org/jira/browse/CRM-7329

[Eileen]

Sigh - hit another site with this - doesn't look like anything is happening with the issues queue on the EZ site - it's 6 months since an issue has been fixed & we now have 3 sites using the autoloader module so we're stuck with patching them every upgrade

[planigan]

THANK YOU for posting this! This issue just popped up on my site today, presumably after I enabled a couple of new modules.