On Saturday 17 August 2002 09:45, Justin French wrote:
> I wouldn't call this a real solution, since it relies heavily on specific
> server requirements and config changes.
It's a bit harsh to say it's not a real solution just because it relies on
some specifics. There's no harm in taking advantage of your situation and use
whatever resources you can to complete your job.
I run a qmail server. When I send out newsletters, I run a query and extract
the mailing addresses I need. Then I build a .qmail file (similar to
sendmail's alias file), and finally I send mail to that .qmail (alias). The
mail is queued once and all recipients listed in the .qmail file gets a copy.
It is a solution that works for me so don't tell me that that is a virtual
The fact is that a solution that relies solely on PHP would probably be too
slow, unreliable and messy.
> Simple fact is that a LOT of PHP
> programmers are on shared servers, and their hosts would NOT want 50,000
> emails queued up on disk. No way!!
But you would have 50,000 mails going out anyway regardless of what solution
you come up with. You mentioned sparklist in previous posts. Assuming that
they allow customised mailings, how would you get 50,000 pieces of info to
them so that they can perform the mailing?
> I'd expect doing this frequently on a shared server would be the fastest
> way to get your account shut down.
I would recommend getting a dedicated server. They start from USD100/month and
can easily cope with 10-20 sites so cost per site is only $5-10. Of course
that opens another can of worms because you would have to deal with server
Jason Wong -> Gremlins Associates -> www.gremlins.com.hk
Open Source Software Systems Integrators
* Web Design & Hosting * Internet & Intranet Applications Development *
There's something different about us -- different from people of Europe,
Africa, Asia ... a deep and abiding belief in the Easter Bunny.
-- G. Gordon Liddy
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php