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 »
  • Installing CiviCRM »
  • CiviMail installation and configuration (Moderator: Donald Lobo) »
  • EmailProcessor crash
Pages: [1]

Author Topic: EmailProcessor crash  (Read 1114 times)

Erich Schulz

  • I post frequently
  • ***
  • Posts: 142
  • Karma: 5
    • When no-one understands what you are going on about its time to start a blog
  • CiviCRM version: 4.4
  • CMS version: Drupal 7
  • MySQL version: 5.somthing
  • PHP version: 5.3.3
EmailProcessor crash
March 28, 2011, 06:56:25 am
ok after having got my key, user and password and user table prefix all sorted now this:

connecting to mail.crm.antarqld.org.au and authenticating as file Fatal error: Ignoring exception from ezcMailPop3Transport::__destruct() while an exception is already active (Uncaught ezcMailTransportException in /hsphere/local/home/antarqld/antarqld.org.au/sites/all/modules/civicrm/packages/ezc/Mail/src/transports/pop3/pop3_transport.php on line 368) in /hsphere/local/home/antarqld/antarqld.org.au/sites/all/modules/civicrm/CRM/Mailing/MailStore.php on line 86

 ???

clues welcome!!


I'm on drup 6.20, php 5.2.14, mysql 5.0.77, apache 1.3.41, civi 3.3.5


i'm very happy to fiddle with php if someone civiwise directs!

http://www.antarqld.org.au/sites/all/modules/civicrm/bin/EmailProcessor.php?name=nottelling&pass=nottelling&key=nottelling

Erich

Erich Schulz

  • I post frequently
  • ***
  • Posts: 142
  • Karma: 5
    • When no-one understands what you are going on about its time to start a blog
  • CiviCRM version: 4.4
  • CMS version: Drupal 7
  • MySQL version: 5.somthing
  • PHP version: 5.3.3
Re: EmailProcessor crash
April 09, 2011, 05:55:44 pm
it turns out this was a bad username/password (actually pw was correct but the user should have been xyx@example.com not xyx as I had it)

there remains a broader issue in that useful exceptions that are being thrown inside the code are somehow being discarded because of some up-stack mishandling

seems like a bug that will make anybody's trouble shooting of misconfigurations harder...

is it worth reporting... bug admins have discarded my previous reports of similar issues of cryptic reporting for misconfiguration as being "not going to fix it because its your fault" so I'm not sure if there is any point reporting bugs any more

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 crash
April 10, 2011, 07:43:16 am

Would be great if you can investigate and submit a patch for the below.

The main problem is that different servers throw out different messages AND we are using a third party library (ezc / Mail) to handle all these interactions. We basically pass on the error message they throw out to the end user.

We do agree that we should try to be as specific as possible and give the user as much relevant information. We currently do fall short of this. We do need the help of the community and from people like you to investigate and submit patches to the code as needed

thanx

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

Erich Schulz

  • I post frequently
  • ***
  • Posts: 142
  • Karma: 5
    • When no-one understands what you are going on about its time to start a blog
  • CiviCRM version: 4.4
  • CMS version: Drupal 7
  • MySQL version: 5.somthing
  • PHP version: 5.3.3
Re: EmailProcessor crash
April 10, 2011, 05:28:01 pm
thanks Lobo,

so are you saying its a waste of time to submit bug reports unless I'm also going to submit a patch?

I'm afraid I have time for the former but not the latter I'm afraid. but my last one just gone binned so i'm not sure if its worth the effort... especially these misconfiguration issues when you kinda loose interest once you've figure out what the problem is (ie incorrect user name)

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 crash
April 10, 2011, 06:36:50 pm

For issues like this, would be nice for folks to take the extra step of figuring out what changes can be done to the code to help improve the error message fo future users. This helps the whole community and avoids the frustrating aspect for users who stumble across the same bug

"loosing interest in it" and then expecting someone else to reproduce (which is potentially the biggest hurdle due to various 3rd party dependencies) / fix it, really goes against the very spirit and ethos of open source, IMHO

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
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • CiviMail installation and configuration (Moderator: Donald Lobo) »
  • EmailProcessor crash

This forum was archived on 2017-11-26.