I've been using phpList for several years on Sonic's server. Since Sonic upgraded php two weeks ago, distressing things have happened to this otherwise well-behaved application.
The latest problem I've encountered is that the rate at which email messages are sent dropped like a rock. Previously, it took about an hour and a half to send all of the messages. Monday, I launched the message. By morning only 300 messages had been sent.
The phpList documentation discusses two methods for controlling that rate: throttling and batching. Both are implemented through the config file. They recommend throttling (which sets a pause between each send) of php-cgi implementations--which is what I understand Sonic to be.
Instead of annoying my list with a bunch of trial and error fiddling with the config file, can anyone tell me what the Sonic mail server might be happy with?
The latest problem I've encountered is that the rate at which email messages are sent dropped like a rock. Previously, it took about an hour and a half to send all of the messages. Monday, I launched the message. By morning only 300 messages had been sent.
The phpList documentation discusses two methods for controlling that rate: throttling and batching. Both are implemented through the config file. They recommend throttling (which sets a pause between each send) of php-cgi implementations--which is what I understand Sonic to be.
Instead of annoying my list with a bunch of trial and error fiddling with the config file, can anyone tell me what the Sonic mail server might be happy with?