Before nodding your head and saying, "So?", think about this...
You choose to send a mass emailing to All Users, pick your template, fill in anything you need to fill in, and tell the system to send.
It doesn't send; it isn't supposed to send. It is supposed to sit in a queue, waiting for you to send it. This is good; I use this to schedule mailings via cron.
Now, for the bad news. You don't send it right away; maybe it takes a few hours, or maybe a few days...
And when you send it, the emailing you have scheduled to go to 1,000 names dies after, say, 250. Fatal error.
Because you (or one of your minions) deleted user 251 from the database before the emailing actually went out. Worse, there is no way to edit the emailing to email to only those who didn't get emailed before the crash. The system knows; it tells you how many emails went out from the list. The only worthwhile solution is to create and mail the item all over again, and subject the first 250 to a duplicate emailing.
We expect to queue emailings up to 7 days in advance. We now have a policy that requires any account to be deleted to be removed from the Mail list at least 7 days before deletion, to protect against this error.
That works for us, but maybe not for you. I write this so you can be aware (especially those who develop), as I'd like to be the only one to utter choice words when a scheduled emailing dies.
Alan Frayer
Don't just read the news - make the news!
Your World News - http://yourworldnews.frayernet.com
You choose to send a mass emailing to All Users, pick your template, fill in anything you need to fill in, and tell the system to send.
It doesn't send; it isn't supposed to send. It is supposed to sit in a queue, waiting for you to send it. This is good; I use this to schedule mailings via cron.
Now, for the bad news. You don't send it right away; maybe it takes a few hours, or maybe a few days...
And when you send it, the emailing you have scheduled to go to 1,000 names dies after, say, 250. Fatal error.
Because you (or one of your minions) deleted user 251 from the database before the emailing actually went out. Worse, there is no way to edit the emailing to email to only those who didn't get emailed before the crash. The system knows; it tells you how many emails went out from the list. The only worthwhile solution is to create and mail the item all over again, and subject the first 250 to a duplicate emailing.
We expect to queue emailings up to 7 days in advance. We now have a policy that requires any account to be deleted to be removed from the Mail list at least 7 days before deletion, to protect against this error.
That works for us, but maybe not for you. I write this so you can be aware (especially those who develop), as I'd like to be the only one to utter choice words when a scheduled emailing dies.
Alan Frayer
Don't just read the news - make the news!
Your World News - http://yourworldnews.frayernet.com