It looks like you're new here. If you want to get involved, click one of these buttons!
As a suggestion is it possible to handle imports in 'chunks' of 100-150 users , to get round any potential timeout issues especially on shared hosting , when importing large lists.
I have read some of the other suggestions and I am sorry to say it is not always possible to just increase server timeouts, asides from going out and getting some dedicated tin to do just that.
As an example, PHP Newsletter Mailer is an application that suffered this very problem and got round it by splitting the import process link http://codecanyon.net/item/newsletter-mailer-v13/149365 this is what I am using for another of my larger lists till I am happy with Sendy.
Update: even importing a list of 140 additional users causes a timeout, although when I get back to sendy these 140 are in the NewList I created. The same cant be said when importing 'larger' lists ..it takes a few tries to get the list complete
Thanks for your suggestion. I am certainly going to optimize and improve CSV import.
For now, if your server times out while importing, split your CSV into multiple chunks and import them.
You mentioned that even importing 140 emails results in a timeout, I think your hosting server is very limiting. If you have a large list and email marketing is important to you or your business, you may want to look at non shared servers. Email marketing applications taxes the server a lot especially if you have a large subscriber base. I'd recommend setting up an Apache/Linux server on Amazon EC2 (just the micro instance will do, with 613MB of memory). I've tested Sendy heavily on it.
I'm using MediaTemple dedicated virtual server and so far does not have any problems importing or sending.
That said, I will still improve on the CSV import (improving the speed and working around timeouts).
Thanks once again.
@KevinB, put it on AWS on a micro instance and if you have issues you can auto-scale to increase resources to handle it without timing out, then scale down to eliminate the additional expense. I can upload 50,000+ people at one time without issue with AWS (though, I'm not on the free micro instance).
I'm jumping in the discussion but the import process it painfully slow, the speed is around 2-3 lines per second. Is this normal?
That's been my experience using an AWS micro instance.
I know sendy does some useful work filtering out invalid emails and checking for duplicates, but it is slow. Alternative, and costlier, solutions are much faster.
CSV import can now be imported via a cron job in the just released version 1.1.5. Any timeouts will be handled.
Note that the larger your CSV, the longer it'll take to import as Sendy not only "imports" your CSV, it "processess" it as well with a number of checks so that invalid emails, duplicates and previously bounced emails won't be imported. But if a timeout occurs because the import takes more than the timeout set by the server/host, Sendy will automatically resume.
There is also a real time percentage feedback to let you know the progress of the import as well.