Thanks for the tip on chmod.
I did that, but seemed to have gone backwards.
This is the error message I get.
Optimizing tables... DONE
Error: Path to MySQL could not be detected. Manually set the path to the MySQL binaries in config.php
Writing backup file... DONE
Verifying backup file... NOT FOUND
What's interesting about this, is the Path to MYSQL error came up last week, and I fixed that. I changed config.php to have this
$sqlpath = "/usr/bin/mysql/";
based on what my hosting company said about the location of mysql.
That got me around that error, but then I got the
Verifying backup file... NOT FOUND
which I wrote up yesterday. I changed the permissions of the attach folder within listmail to be 777.
Now I get both of those error messages in the same execution.
To rephrase - I've had the config.php modified for about a week now, and was not getting the Path to MySQL error. Then today it came back.
Hmmm...
I don't think my hosting company is moving mysql around on me, but I don't have any other theories at this time.
I'll check with them, and if anybody has any other ideas, please speak up.
Thanks
mark