[tommythejoat]

Originally Posted by itconsultingnv

Continuing to have the problem where it works for awhile, posts to the forum are sent out and email responses are posted, then suddenly, for no apparent reason it keeps sending an email post over and over and over, when I check the webmail I see the offending email post as well as other posts sent after that one that are sitting there waiting to be processed. If I go into the cron it gives me a line 1093 error, then if I go to the webmail, clear out all of the emails, then run the ei cron again it no longer errors. Don't know if that is related in some way. Anyone know what to do? Is Cyrcicx still supporting this software? Not sure if I should continue spending time on this option until further notice. Please help. Anyone else running this successfully? Thanks!

I have been trying to get this going also. I am willing to spend quite a bit of time on it and have been looking through a listing of the cron job.

There seem to be a number of places where the incoming email format does not get handled properly and eventually you get around to processing a message that generates a fatal error. 1093 is one of the error lines. That particular one seems to be eliminated by commenting it out, but it looks like one needs to know the vBulletin function library pretty well to be able to effectively read the code.

Is there anyone participating here who is a programmer of this material? It is very new to me, although I have about 30 years experience as a programmer in other environments.

Debugging something running on a server with a live message board is kind of painful.

I am running 3.7.3 pl1 and the latest version of the mod posted here.

I set up my server mailbox as a pop3 source for my personal mail that I can turn on or off. That lets me pull the pathological emails out of the box and continue testing. If you leave them in, the scheduled task will continue to process everything with a datetime later than the broken email and the cron job will generate its fatal error on every pass.

I think it might be better to disable the scheduled running of the routine and just run it manually when you want to work on it. That way you can put output statements in the code and see them in the AdminCP as the routine runs.