Scheduled mail didn't send...

[boundless]

2 days ago, I scheduled a mail for May 1, 2005 (today). Well, it's May 1, 2005 at 8:00am and it's still sitting there in the Scheduled email section...

Bob

[DW]

Have you set up your scheduled task, as per http://listmailpro.com/help/dailymail_cron.html?  If you have and it's not working properly you may want to talk to your host.  You can also search the forum here for some alternative command-lines and other ideas.

Regards

[boundless]

Have you set up your scheduled task, as per http://listmailpro.com/help/dailymail_cron.html?  If you have and it's not working properly you may want to talk to your host.  You can also search the forum here for some alternative command-lines and other ideas.

Regards

Yes, but the dailymail is definitely being sent.

(And it's still sitting there scheduled for yesterday...)

Bob

[DW]

Do you have "send report to admin when dailymail is run" enabled in your ListMail Config?  If so, you should receive a notification each time dailymail is executed.  If you do receive the notification then your scheduled message should have been sent.  If not, you probably need to check to make sure the cron task is running correctly.

Regards

[boundless]

Do you have "send report to admin when dailymail is run" enabled in your ListMail Config?  If so, you should receive a notification each time dailymail is executed.  If you do receive the notification then your scheduled message should have been sent.  If not, you probably need to check to make sure the cron task is running correctly.

Regards

As I said in my last message, I know Dailymail is running, because I'm hearing back from students who are receiving the mail.

Also, I checked my cronjob and it's fine as far as I can tell:

0 0 * * * /usr/bin/GET -d http://www.boundlessliving.com/flightwaves/moolon/dailymail.php?pw=XXXXX

...though I see that your help file has a different set of parameters now...

Is there something that needs to be different? This is the command I've been using for 3 years, and I've always been successful in sending dailymail and scheduled mail...at least before the upgrade. Though I DO know that dailymail HAS been sent.

[DW]

The cron task should not need to be changed, unless something has changed at your server. I've seen hosts use GET but not /usr/bin/GET, so I'm not sure if this is correct.  If it worked before it should be...  I wonder if your host removed or renamed the /usr/bin/GET program.  Are you receiving dailymail reports?

Regards

[boundless]

The cron task should not need to be changed, unless something has changed at your server. I've seen hosts use GET but not /usr/bin/GET, so I'm not sure if this is correct.  If it worked before it should be...  I wonder if your host removed or renamed the /usr/bin/GET program.  Are you receiving dailymail reports?

Regards

I always have been, but to be honest I don't know about the past couple of days...I generally just gloss over them, you know? I'll have to see in the morning I guess to be sure, but I don't know why I'd suddenly NOT get them. And I'm nearly 100% certain I've gotten email responses to mail that would have been sent out as part of my dailymail followup over the past couple of days - but I can't swear to that.

And yes, GET is what our server uses instead of wget, something I just reconfirmed.

[DW]

Another thing you can check is that your dailymail password in ListMail matches the one set in the cron task.  Copy/paste from the task to be sure.

[boundless]

Another thing you can check is that your dailymail password in ListMail matches the one set in the cron task.  Copy/paste from the task to be sure.

It definitely matches.

At this point, I'm tempted just to wait until the morning, and see if I get email confirmation of dailymail sending. If I don't, then I'll run dailymail manually from the listmail and see what happens. If everything runs ok, I'll know for sure the problem is with the cron job.

Bob

[boundless]

It's one of those crazy Windows/Linux things.

I had to update the cron job a few days ago, and I created the instructions in a Windows text editor.

Although there was no way to "see" it, there was a ^M carriage return character that LINUX saw after my password. I actually checked for this in my text editor, of course I couldn't see it.

Luckly my host admin took a look in the right place, saw it, fixed it, and all my mail went out.



Bob