Back when I used to deal with this kind of problem, I simply had a wrapper script for the sendmail command that did some logging and various checks. It looked just like sendmail to PHP, but it could check a blacklist, verify outgoing mail didn't contain certain types of crap, add an X- header to help identify which site generated the email etc.
On 3 March 2010 16:35, Simon <[email protected]> wrote: > OK.. so what im wondering is what people are doing to protect themselves > from the PHP mail command from an ISP's point of view. We run a small > hosting company that deals mainly with corporate customers and also > wholesales to web developers. We run debian stable for our web servers > (apache/php) and a dedicated outgoing mail server (postfix) so we can review > log files etc. SOME customers are, how do we say it, less than perfect when > using form to mail solutions.. leaving the way open for header injection > attacks. Now we know how to put measures in place to stop it on the sites > that we build and manage, which is all good, but what im trying to think of > is a way to track usage of the outgoing mail command usage.. > > PHP 5.3 gives me some really good ways of doing this, but debian does not > have php 5.3 and there are some things that people need to do to their > websites before we upgrade. (in fact we will prob setup a new server and > migrate people over rather than just upgrade). > > Any input is much appreciated! > > Simon > > -- > NZ PHP Users Group: http://groups.google.com/group/nzphpug > To post, send email to [email protected] > To unsubscribe, send email to > [email protected] -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
