ListMail keeps stopping during send - corrupt DB?

[kyle]

Prior to this issue, I tried importing 2.7 million addresses as a suppression list for comparison to my real list.  That was taking many hours and eventually crashed the server (a /tmp drive filled up, apache went down, and the ListMail DB got corrupted [ListMail couldn't list the users in the user database])...  Now I'm trying to delete that suppression list and so far it's taking a very long time (25 minutes so far).  

Anyway, my hosts had to repair the database, and it seemed to be okay.  But now that I'm actually doing a send (once with the Scheduler and then tried to resume after it failed after 2,000 of the 124,000 messages were sent), it keeps failing.  When I tried to Resume it through ListMail, it sent to 12,900 more on the list, then failed with this message:
"Sending error. Check your mail settings.
Server said:"
...and there was nothing there for "Server said:"...    Is the database still corrupt?  What can I do??  Thanks,
--Kyle

[DW]

Please search the forum for "smtp_timeout".  Setting it in config.php should fix this:

Code: [Select]

$smtp_timeout=45;
Regards

[kyle]

I'm sending with Exim though, so that setting shouldn't matter, correct?  If not, please let me know.  

Do you plan to fix the importation of really large lists?  I even broke up the list into 600,000 or so chunks, and it still was taking forever (and I was afraid may cause another crash).  Not a big deal as I shouldn't need to do this again though...  Thanks,
--Kyle

[DW]

No, the setting should not be needed on Exim.  Please let me know if the SMTP problems continue.

The database, with all its indexing for searches, etc. is very demanding.  At minimum, MySQL should be properly optimized to make maximum use of available RAM.  I can't recommend storing more than about 500,000 records at this time.  I hope to make some improvements for larger lists in the future.

Regards