you could use error_log() with __LINE__ __FILE__ right before each call to mail() to track the usage. Yes this does mean searching and editing a lot of files, but it will get you an answer (or more accurately it will show you what is not causing it. As it may not be php's mail func contracy to what the email headers show, as they could be faked). Ps if you want to write a wrapper func then use debug_backtrace() to identify the caller instead of __LINE__ __FILE__ Louis Solomon www.SteelBytes.com -----Original Message----- From: onemancrew [mailto:ilan@xxxxxxxxxxx] Sent: Saturday, 16 May 2009 8:20 PM To: php-windows@xxxxxxxxxxxxx Subject: Re: Debug PHP , Write Every Action (and not just errors debug related) into a file Hi Again I am the server administrator. some details about the server: OS: Windows Server 2003 PHP Version: PHP 4.4.6 (cgi-fcgi) (built: Feb 28 2007 21:35:46) MailServer Application: MailEnable (works under Windows OS) How do I know that the source of the problem is PHP ? Because I have investigated the email header and I have found that the emails have been created through PHP. It's 200% that the spam emails have been created through PHP code. The Mail() function is enable. Also I provide mail relay only to requests which comes from localhost (127.0.0.1) What does it means ? it means that if a php script try to create new email envelop and in the script the mail server which is defined is 127.0.0.1 or localhost then the php script will be able to create the email envelop. Also in such case no authentication is required. The relay option for 127.0.0.1 or localhost is defined in the Email Server Application (MailEnable). And I must use such setting because I have php applications which don't make any authentication through the email server. Under this server I have alots of web sites. So I can't start checking each IIS log file on daily basis. I have enabled the error php debug file. but it is only log unsuccessful php actions. So this log file doesn't provide me information regarding success mail() function operation. And because of that I can't track after the source of the PHP code which create those emails envelop. What I need is the following (because I don't find any better solution): I must have the capability to track any php action into a file. I need to have the capability to track down each action that php.exe is doing in relevant of mail() function. I did some investigation and couldn't find internal feature inside php.exe to log any action that it's doing (not only errors). Regarding the additional_parameters and the vhost-unique key. I think that I can't implement such feature while PHP is working under Windows OS and While the Email Server Application is MailEnable. I think that such feature is eligible and working only when the Email Server Application is SendMail. Because MailEnable doesn't support special Key processing. Any Suggestion ? -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
