[himerus]

Originally Posted by himerus

Now I've found that I'm actually having a problem with posting when the script is running under a cron...

If I run it manually, the posts that are made in my forum are being sent properly...

If the script runs on a cron and tries to post, it is recieving a 240 status after the post is sent, but the message id isn't being inserted into the post field property... it only appears as something like <himerus.0@> and doesn't have the settings domain or message id included in it... in those cases, the messages aren't being sent properly to the server....

If I manually edit phpmyadmin, and remove the msgid, ref, and reset the isusenetpost to 0, and then manually run the gateway.php file, the post is uploaded properly....

Any ideas???

I will have to create an email message for each time the cron is ran to really test this I think... since I'm not seeing any of the output, but it is saying the post was sent properly...

I'm still having the same problem, and I can't figure out what the #$@#$ is causing it... Again, I have it set up as a vB cron, and if I use the "RUN NOW" button from the Scheduled Task Manager, the new posts are successfully sent without a hitch... but if I let it run as a cron, the $settings variables aren't showing up... when the row in the post table is updated, the

PHP Code:

$msgid = $u . '.' . base_convert ($msgid_date, 10, 36) . '@'. $settings[email]; 


ends up looking like: himerus.0@

Even the simple $settings[email] variable isn't showing up when it's running as a cron...

ANY IDEAS Would be appreciated...

I have lots of users registering specifically for the USENET access, and not having the posts work right on the cron is turning into a large problem.