CiviCRM Community Forums (archive)

do u have more details or links to forum posts of the potential issue?

lobo

Thanks for your responses.

1) yes I understand the new combined cron and it is working fine - but thanks, it's the sort of suggestion that could save my sanity.

2) Previous posts

 http://forum.civicrm.org/index.php/topic,25026.msg106316.html#msg106316

http://forum.civicrm.org/index.php/topic,26171.msg110716.html#msg110716

Note that the last one didn't throw as much light as I had hoped but it did clear for a little while - but all old emails that I copied in by mistake. So there is a good chance that there is something in the inbox that is blocking everything up.

I've not been able to get a remote debugger working to step through the code against that mailbox.

Xdebug is on the server and the port has been opened (not the standard one)

3) Failed since upgrade to 4.1.1

Now on 4.2.2 and Drupal 7 (latest)

By manually do you mean from admin> system setting > scheduled jobs > execute now (or whatever the right menu items are?)

Nothing useful - it just tells me that it ran with an error...

0
Summary
Finished execution of Process Inbound Emails with result: Failure, Error message: Process Activities failed
Details

Parameters parsed (and passed to API method):
a:1:{s:7:"version";i:3;}

Full message:
Finished execution of Process Inbound Emails with result: Failure, Error message: Process Activities failed

From an address bar in the browser...

http://domain/sites/all/modules/civicrm/bin/EmailProcessor.php?name=username&pass=password&key=site_key&emailtoactivity=1

I was going to day that with an admin username, password and the site key filled in, again nothing much useful... even with debugging turned on in both Drupal and CiviCRM, but just ot check I tried again and got a page not found from Drupal - agh..

Any other way of triggering it, and come to that, what am I doing wrong with the browser version? I've tried putting in ' single quotes just in case with the same result.

I've found some rogue mails - or rather mail delivery notices that the email processor can't process and a couple of other suspects.

Would the headers be useful to the team in improving the processor?

If so where would you like this posted - on JIRA?

Our problem is now officially sorted in that we have a working installation and can probably spot problem emails if it happens again.

Thanks for helping me to rally for another go.

THis may be beyond my capability.

After several months I have only got as far as finding the obvious method of isolating the problem emails.

Working out what the code isn't doing with them, and what it should be doing with it is another order -

My first step would I guess be to step through the code whilst it plays with the emails.

That means either debugging on a remote server - which I have been unable to get working to date

or

setting up a mail server on my laptop.

I'll explore the later.