Then you have grown your userbase too fast with a terrible setup, and now
you're caught in the middle of fixing the problem or avoiding downtime.
Sure, if you go through and find every line of code where mail() is called,
you can add logging at that point. But so far you've refused to make any
changes to the applications.
His idea is the right one. Most PHP applications I've dealt with support, at
least through plugins or extensions, SMTP + AUTH for sending mail instead of
PHP's mail().
I don't think PHP ever changes the working directly except explicitly;
probably every call to mail() (which leads to mini_sendmail) occurs in the
chroot /.
There are, but they require you to set the parameters of how web apps can work
in your environment so as to enforce a minimum of auditability. You have
already said that you can't enforce that minimum, and it turns out that you're
left with nothing to audit.
sendmail_path = "/bin/mini_sendmail
Well, mini_sendmail is an external package... talk to the authors about that,
but I think they'll tell you they can't really track what you need tracked.
--
Matthew Weigel
hacker
unique & idempot . ent