On Wed, 2008-01-02 at 18:06 +0000, Peter Bowyer wrote: > So this sounds like the Apache / mod_php bug referred to in the Debian > bug that Marc H posted earlier in the thread....
Ah, it's all come back to me now. Don't run PHP via mod_php. If you want security, isolation and some semblance of control, use suEXEC and run PHP as a CGI script, or better (for PHP at the very least, and because of its' enhanced configurability when compared to suEXEC) use suPHP instead. This is, of course, if you have the system resources to do so - mod_php trades off the good things above against all but immediate code compilation & execution through not having to fork()/exec() the interpreter for every call. Still, none of this is Exim related. And neither, to be honest, is the OP's problem - it's an Apache/mod_php problem. I do wonder, however, why we don't see similar reports with PHP and sendmail/postfix/qmail et al... Graeme -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
