At 5:39 PM -0600 5/5/07, Dada Mail (Justin Simoni) wrote:

On May 4, 2007, at 4:36 PM, John Collins wrote:

I don't really understand why a one time mailer is a cron function when the sending parameters are set in Beatude

Because Beatitude doesn't run all the time - it runs, looks and see if there are mailings that needs to be done and quits That's why you have to keep running it, again and again;

What's the line in the cronjob look like?

I entered two to be sure One as you recommended in the prior email and the second one that included /dada/ in the path: 0,30, * * * * /home/meetingsandmixers/www/cgi-bin/plugins/scheduled_mailings pl --run >/dev/null 2>&1 0,30, * * * * /home/meetingsandmixers/www/cgi-bin/dada/plugins/scheduled_mailings pl --run >/dev/null 2>&1

So then as I am trying to understand, with this cronjob set to poll Beatude every 30 minutes, it will at some point poll it right before, or after, or right on the time, that a mailing is set to send in Beatude and it will send it A single email

Again, I am not grabbing the contents of a web page that periodically changes I am sending one static email broadcast to my list at a time when I cannot be here to send it manually

Right now it is set to send a test at 730am Sunday, server time We;ll see what happens

Seems like it oughta ask for my dada password somewhere

>

Also, if you run the cronjob just on the command line, does it work? How about with the, --verbose flag, does it print anything interesting out?

Sorry, but you're over my head I have no idea what that means or how to go about it

>

-- Justin Simoni

Dada Mail - Write Once: Distribute Everywhere Software url: http://mojo skazat com

On May 4, 2007, at 4:36 PM, John Collins wrote:

>

Update 330pm Fri

Found a second page in the Magic Book that referred to Beatude
The second one did bring up cronjobs (why two separate pages?
Easy to miss #2)

So I used the Terminal in Mac OSX to add one like your example that polls (as I understand it) Beatude every half hour Went back in with Terminal and ran a cronjob -e and it was there Moreover, went into Apache and found the file, downloaded it and verified its existence exactly as entered

Still no cigar Reset Beatude within the Dada Admin panel for about an hour into the future, made sure it was active and saved it

Time passed and I kept checking email, but nothing happened No mailer

I don't really understand why a one time mailer is a cron function when the sending parameters are set in Beatude

---

Sent this morning::::::

Cronjob? Shoot, no I just reviewed the Beatude page in the Magic Book again and didn't see a thing about setting a cronjob

I don't care about repeating mailings

I only want to send a single mailer to my list next week at a time when I cannot be here to send it manually Just like the first example in the Magic Book where you pretend to go to Vegas
There's no mention of setting a cronjob on that example in the book You just set it to mail at a specified time and let Beatude do its thing

As far as SSH, I'm on a Mac and am not sure what that is or what I would use to do that BUT, I think I have command line access the hard way I can download any of the files in Dada, or most Apache files, modify them in a text editor and upload them again, so maybe better said is I have file level access

J

At 6:41 PM -0600 5/3/07, Dada Mail (Justin Simoni) wrote:

Here's two things to check:

Did you set the cronjob?

And if you did, do you have access to the command line (via ssh?) If so, try running the command that you've set in the cronjob right on the command line and see if it works - odds are, if it works for you on the command line, it'll work in the cronjob

For example, if you've set the cronjob to something like this:

*/5 * * * * /usr/bin/perl /home/youraccount/cgi-bin/plugins/scheduled_mailings pl --run

Running it right from the command line:

prompt:]/usr/bin/perl /home/youraccount/cgi-bin/plugins/scheduled_mailings pl --run

Should at least not give you an error You can also put the verbose flag on:

prompt:]/usr/bin/perl /home/youraccount/cgi-bin/plugins/scheduled_mailings pl --run --verbose

to make it give you some interesting things back

Another note about Beatitude - set the cron to about one half of the period of time you want messages to be sent

For example, say I want to grab the contents of a website every hour - but only if there's something new, I'd set the cronjob to check every half hour:

30 * * * * /usr/bin/perl

/home/youraccount/cgi-bin/plugins/scheduled_mailings pl --run

Justin Simoni

Dada Mail - Write Once: Distribute Everywhere Software url: http://mojo skazat com

On May 3, 2007, at 5:59 PM, John Collins wrote:

>

First time I've tried Beatude (Testing for now, but need it next week) The comments are removed in config pm so it should be fully active In fact, it is active in the Admin panel Noted that the server time is an hour ahead of local Clicked the active button Set up a message, both text and html

Sent "Test to mailing list owner" and got it fine

Then set one up, compensating for server time, set it to fire in 15 minutes (again, server time) Clicked to "only send this schedule to list owner" Clicked to "Save Schedule" Screen redrew with a 'Saved Successfully "

Waited the prescribed 15 minutes and checked email, but no message Tried again, changing the schedule to another 15 mins in the future (server time) Nope Read and reread the Magic Book and can"t see what I'm doing wrong

I expected a copy of the message to be sent to only me at the server time I chose