PHP shouldn't leak memory even if output/input from/to external program differs. It seems it's a PHP problem for this matter.
Are you sure your input to mail() is RFC compliant? Even if input is not RFC compliant, PHP shouldn't leak memory, though. -- Yasuo Ohgaki Ari Pollak wrote:
Unless you come up with a way to migrate 500+ virtualhosts to some other MTA, no, that is not feasible.
You can think of qmail like minix in both author and license, in that the author is really arrogant about changing the way his software behaves even though it's not standards-compliant, and you can't distribute modified binaries. And qmail has been on the same version for many years, so nobody is expecting him to actually put out a new version anytime soon.
In any case, I'm not expecting any qmail patch to actually go into PHP, but I'd really like to get this memory leak fixed for those who need this patch (me).
On Fri, Dec 27, 2002 at 11:00:32AM -0500, George Schlossnagle wrote:
qmail devs == djb, right?
If his support doesn't suffice (and you cant find it in the enormous un-merged patch contributions that seem to litter the qmail community websites), might I suggest a new MTA? Exim works quite nicely.
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
