Gossi, Dean wrote:
> What information are you looking for......I just told you how to
> reproduce it. What me to fix it for you...........
The information you provided boils down to that on Win2k SP2, IIS,
mail() works for you when PHP runs as CGI, but not as a module.
Since only mail() doesn't work for the module, and does for cgi, I (and
probably you, too) assume that PHP is installed correctly. Module <=>
CGI is the only difference, so this might be the problem.
(side note: regarding how few information you provided, your report was
a little too long)
This is why you'd prefer this bug to be reproduced by someone of the
qa-team rather than being bogusified.
But a developer who knows PHP (and Derick sure does, far better than I
do, anyway, he is in the php-dev team, not me) will notice that the
change in the (server-API) should not affect the mail function, they
are not related (I assume).
This is either a pretty strange side-effect, or a configuration issue.
IIS might be a little strange sometimes.
And although IIS is not the most common webserver used with PHP, there
is quite a userbase for this combination, many of them using PHP as a
module. If mail() didn't work for all of them, it is quite strange
nobody noticed. This makes it more probable that this is a
configuration issue.
This is why Derick bogusified the bug.
I hope both sides see each others points now.
Anyway, configuration issues are not bugs within PHP.
Basically, what Derick and Jeroen ask you to do is to go ahead and ask
on php-general and php-windows, two public mailinglists about php, if
somebody knows this problem.
If you don't find a solution, somebody else can reproduce this problem
or you find out what the configuration problem was, feel free to ask
for re-opening the bug-report (using the web-interface, not answering
to the mail), request a change in the manual noting the config-problem
or just add it yourself to the annotated manual.
PHP is a community effort. You'd be part of this community then :-)
If neither php-general nor php-windows can help you or you can prove
that this bug can be reproduced on other systems, I'm sure the php-qa
and dev teams will try to resolve this.
You'd have to provide more information then. Like does PHP even try to
connect to the SMTP-server or does it fail after the connect?
Otherwise, it's hard to do remote diagnostics.
> I guess I should just use asp. With this type of developer support
> (2-5 word responses to your emails) I don't think php will cause any
> stir in the marketplace............
A response that basically says "not enough input" isn't required to be
wordy, is it? Mind you, these people are volunteers.
Also, for many of them english is not their native language, english is
just the common ground they meet on.
When you get something for free, please remember that you're not in a
corporate environment. This is a community. If all parts (core-team and
users in this case) are nice to each other, it makes the world a better
place.
Didn't Gartner just recommend not using IIS? Either having to install a
patch every week or reinstalling the whole machine every few months?
Is that a stir?
When Microsoft tells you that with their software, you can do
complicated things easily, you might not end up with what you wanted.
I would recommend to try using Apache, it tends to be more reliable
(this is just my opinion) and is more common (=> tested) in combination
with PHP.
I heard a few really bad stories from people having used ASP who ended
up with PHP and were happy. On the other hand, what else would you
expect from the PHP-community?
regards
Wagner
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
