[PHP] Is mail() broken in 4.3.0 when it comes to BCC?
This line works as expected: mail("[EMAIL PROTECTED]", "My Subject", "Line 1\nLine 2", "From: [EMAIL PROTECTED]"); whereas if I change it to this: mail("[EMAIL PROTECTED]", "My Subject", "Line 1\nLine 2", "Bcc: [EMAIL PROTECTED]"); the mail never gets sent! I'm running 4.3.0 on Windows XP. Any thoughts? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Is mail() broken in 4.3.0 when it comes to BCC?
Your suggestion didn't work (but thanks anyway), but I tried removing the space from after the "Bcc:" (before the address) and it started working! So this line works: mail("[EMAIL PROTECTED]", "My Subject", "Line 1\nLine 2", "Bcc:[EMAIL PROTECTED]"); but this one doesn't mail("[EMAIL PROTECTED]", "My Subject", "Line 1\nLine 2", "Bcc: [EMAIL PROTECTED]"); It used to be fine before 4.3.0. "Francesco Leonetti" <[EMAIL PROTECTED]> wrote in message 008101c2d108$f75ff600$0100a8c0@fleo">news:008101c2d108$f75ff600$0100a8c0@fleo... > Try this: > > mail("[EMAIL PROTECTED]", "My Subject", "Line 1\nLine 2", "From: [EMAIL PROTECTED]\nBCC: > [EMAIL PROTECTED]"); > > > > - Original Message - > From: "Mark Virtue" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, February 10, 2003 2:18 PM > Subject: [PHP] Is mail() broken in 4.3.0 when it comes to BCC? > > > > This line works as expected: > > > > mail("[EMAIL PROTECTED]", "My Subject", "Line 1\nLine 2", "From: [EMAIL PROTECTED]"); > > > > whereas if I change it to this: > > > > mail("[EMAIL PROTECTED]", "My Subject", "Line 1\nLine 2", "Bcc: [EMAIL PROTECTED]"); > > > > the mail never gets sent! > > > > I'm running 4.3.0 on Windows XP. > > > > Any thoughts? > > > > > > > > -- > > PHP General Mailing List (http://www.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] MS SQL Server problem
This code works perfectly and returns all the data that I expect: mssql_pconnect($hostname, $username, $password) or die("blah blah"); mssql_select_db($dbName) or die("blah blah"); $result = mssql_query("select MyFieldName from MyTable"); But if I change the last line to this: $result = mssql_query("select * from MyTable"); I get the following warnings and no result is returned: Warning: mssql_query() [function.mssql-query]: message: Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. (severity 16) in c:\test.php on line 24 Warning: mssql_query() [function.mssql-query]: Query failed in c:\test.php on line 24 I am using 4.3.0 on WinXP. Any thoughts? Mark.
Re: [PHP] table border colors in html/xml
"Sunfire" <[EMAIL PROTECTED]> wrote > sorry.. does anybody know of any mailing list i can join for that then? alt.html -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Unsetting PHP_AUTH_USER
I'm having a devil of a time trying to "unset" the built-in global $PHP_AUTH_USER. My aim is to have a "logout" button. Obviously the first thing to try is unset($PHP_AUTH_USER). No good - when I refresh the page it's back. Then I tried unset($_SERVER['PHP_AUTH_USER']) - same deal. I also tried session_destroy() and unset($_COOKIE[session_name()]). All failed - as soon as I refresh the page, the $PHP_AUTH_USER value is restored. I heard that if you send the header lines: Header('WWW-Authenticate: Basic realm="My Realm"'); Header("HTTP/1.0 401 Unauthorized"); ...then the browser clear its authentication cache (and the value is forgotten), but those lines also cause that username/password dialog to pop up. That's not what I want. I want logout functionality, not log in again functionality. Anyone know how to make the value of $PHP_AUTH_USER get completely forgotten via a couple of simple lines of code? It should be easy - how many sites out there do you see with a "log out" button? Mark. P.S. The logout facility in phpMyAdmin has problems - it's actually a "relogin" facility, and if you supply the same username and password you don't get logged in.