CiviCRM Community Forums (archive)

I posted this on the main forums, but no response yet. posting it here as well since I'm using standalone.

CiviMail isn't sending out scheduled mailings - I looked into Cron Jobs to get that going, but I'm having a problem with the key when trying to nudge the cron job with a link.

Here is the whole thread and my most recent post below:

I'm having a problem with the key for this as well.

I carefully followed the instructions at http://wiki.civicrm.org/confluence/display/CRMDOC/Command-line+Script+Configuration

And I edited the site key line in my civicrm.settings.php file to read:

define( 'CIVICRM_SITE_KEY', 'r0zsfYtC0PcEF\x^' );

and went to the URL: http://recycleabike.org/crm/bin/civimail.cronjob.php?key=r0zsfYtC0PcEF\x^

It still gave me the error: ERROR: You need to send a valid user name and password to execute this file.

Also, once before when I was trying a different site key, it gave a different error:

Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING in /home/mikeeng/recycleabike.org/crm/standalone/civicrm.settings.php on line 148

At which point I checked around line 148, but didn't find anything immediately obvioiusly wrong there.

Thoughts?

Okay. I'm not sure if I need to change the URL to accept my OpenID or actually come up with a user name and password in its place and put that in the URL.

How does one create a user name and password with the rights to send from CiviMail?

I had problems with *any* special characters in the key value. Try creating one with just numbers and letters.

It's not a preferable solution, but you could disable the user/pwd authentication for the cronjob. In that file, there's an authenticateScript function called with "true" as the variable passed. Change it to false. Not sure if you still need the key.

Yes, for standalone 2.1, that's the actually the "official" way to do it. Definitely a hack, definitely not secure, but that's all we've got for now.

2.2 will be a slight improvement security-wise, but will still require setting an API key in the database manually. I'm planning to get a full OAuth implementation going for 2.3, or some other better system that is easier and secure.

If you'd like to help influence the direction it goes in 2.3, send me a message and we can talk about your requirements.

Did you disable the authorization requirement in civimail.cronjob.php?
Upgrading to v2.2 would have overwritten the change you previously made to that file. You have to reinstitute the modification.