Bob,
On the form that you gave me to submit, what exactly is "Control Panel". Are you talking about the control panel for the entire site that my web host provides? I'm not clear why you would need anything more than my FTP and Listmail Pro directory and access information.
The control panel is where you manage your hosting account. From here you can set up email accounts, (possibly) MySQL databases, and other aspects of your hosting.
What does the database know/care about the directory from which signup scripts are run, and would where they signup have ANYTHING to do with this issue?
For example, many of these people are signed up via email automatically upon enrolling in our program through your script.
The signup.php script for those who actually filled out forms has always been run from a different directory than the actual listmail pro installation...that is I had a copy of signup.php and admin.php in the directory where the form HTML was. (I don't remember exactly why I did this, and as of this morning, I'm pointing those forms back to the code in the installation directory...)
The database and the directory are fairly independent - they're tied together in config.php, where you set up your database details. As long as the signup.php script exists in any directory it can subscribe users into the database configured.
Providing the user information appears correct in ListMail, it should not be a signup issue.
IF I were to create an entirely NEW installation with a NEW database, and put all the code into a "mail" directory (right now it's called something else), then EXPORT my existing database, then IMPORT it into the new database, would everything still work - or work properly, that is...
You could do this but you would lose some data as not all fields are currently supported by the Import/Export processes. I don't suspect it's a problem with your user data, the directory, or database ListMail is installed on.
When I first set up this software 3 years ago, I sent the cron job instructions to my host admin. Those instructions were pointing to an OLD installation of the program...a listmail directory I haven't "used" in forever, but the code was still there!
Perhaps THAT is what's causing the problem? Running old code on daily mail and scheduled mail? It had just been so long that it didn't occur to me until this morning to check the cron job instructions!
I am not sure if this is the problem. All of your email is being sent from the new host, correct? It should not matter which host you run the cron task on - you could run the task on an old server to point to a new server. Problems can arise if you are running 2 cron jobs on the same installation, however.
Since you mentioned running old signup scripts, I wonder if your files are all up-to-date. Can you please re-download v1.8 and upload all files in the main directory and make sure to overwrite all of them?
Another idea I have is that you may be Resuming too soon. When the page "times out" and you think there's an error, try going back into the ListMail program and browsing around. You will see a queue entry at the top of the program listing the number of remaining messages. Refresh the page or browse to another one to have it update the number of remaining messages. If this number is still decreasing you should not yet Resume mailing. I will be implementing a check for this. Perhaps when mailing it will update the database every 1 minute or so to tell ListMail that it's still running. ListMail could then prevent you from resuming queues that have responded within 1 minute. I am not certain that this can affect message codes in the manner you are experiencing, but it's an idea.
Regards