Re: [PHP-DB] I'm not getting any mailing list messages
Well, it's working over here. I think it just had to do with the list being quiet at the moment because I don't recall seeing any new posts in a while. --JMR Chip Wiegand wrote: I just subscribed to the list yesterday and have yet to receive any messages from the list. Any ideas? -- -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DB] Re: mail() function and AOL users
This is something I've been dealing with for a little too long. AOL has a big list of methods they use to block what they think are spam. Some of these things are: - Reverse DNS Lookups: If you don't have an entry, your mail is dumped - Mail Formatting: If the format of your message is not RFC Compliant, your mail is dumped. - Open Relay Lists: If your IP is on a blacklist, your mail is dumped. - MX Record Lookups: If the domain of your address does not have an MX record, your mail is dumped. - Dynamic IP Lists: If you are on a (known) dynamically assigned IP address, your mail is dumped. - Message Content: If your message contains obfuscated (hex-coded) URL's, your mail is dumped. - Rolling Blockouts: Aol has been known to block whole blocks of IP's just because they feel like it. The list goes on like this for awhile. For more info, pay a visit to http://postmaster.info.aol.com/ --JMR [EMAIL PROTECTED] wrote: Hello!! That's not always true. I just sent mail using php to my AOL account, and it worked. The smtp mail server doesn't have a reverse dns lookup. His problem might be that the SMTP server he is using my be on the black list. http://www.ordb.org/ This will cause a ton of problems. It took me 3 weeks to get off that list!!! Anyway... Instead of sending it like this... mail($email, application submitted, $message, From: [EMAIL PROTECTED]); Do something like this... $text = stripslashes($text); $subject = stripslashes($sub); $header = From: $From\nReply-To: $From\n; $header .= Cc: $cc\n; $header .= MIME-Version: 1.0\n; $header .= Content-Type: text/plain\n; $header .= Content-Transfer-Encoding: 8bnoit\n\n; $header .= $text\n; mail($To, $subject, , $header); I alwasy like working with strings Dan -Original Message- From: RJameson [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 19, 2004 9:12 AM To: php-db Subject: RE: [PHP-DB] Re: mail() function and AOL users I'm quite sure it's not a problem with the mail function. It's probably the reverse dns configuration on your SMTP/sendmail server. AOL Verizon have been two real sticklers for that. If you know the IP address that your server is sending the email from you can use this: http://www.dnsstuff.com/tools/ptr.ch?ip=YOURIPADDRESS To check the revers dns resolution. You may be surprised. Ryan -Original Message- From: Manuel Lemos [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 18, 2004 10:28 PM To: [EMAIL PROTECTED] Subject: [PHP-DB] Re: mail() function and AOL users Hello, On 12/12/2003 04:34 AM, Matt Perry wrote: I use the following php mail function in an online applicaiton program: mail($email, application submitted, $message, From: [EMAIL PROTECTED]); This function does not always work when I modify $message. I have checked for null values for $message already but this does not seem to be the problem. I am trying to develop some sort of pattern of when this function works and when it does not. The only essential difference between the values I pass in for message is the one that does not always work includes a link. Apparently anyone useing AOL email is particularly vulnerable to this problem. Is it likely that AOL and other mail servers sometimes block any email from a web site if it has a link in the main body? Or should I not be useing mail() in this manner to begin with? Maybe you are not generating the message headers and body properly. Without seeing the code that you use to define $message, it is hard to tell. I just suggest that you try this class to properly compose and send your messages: http://www.phpclasses.org/mimemessage -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DB] Mail Function
Your script actually connects to an SMTP server and sends the email? If this is the case, you can have your script look for success/error messages returned by the server when it sends - unless you're delivering to an AOL address. AOL accepts everything you throw at it and then sends back a notification of success/failure via email...sometimes. There are a few other servers that act the same way, but AOL is the biggest culprit in making an email list manager's life a living hell. I've actually been kicking around the idea of a PHP-based list manager that will also go through bounce notifications but haven't done anything more than that. The biggest hurdle is getting through the bounced messages. --JMR Graeme McLaren wrote: Evening all, I've written a script which sends emails, there is no problem with that. I was wondering how I can check for email bounces, anyone know how to do that? Cheers, G :) -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DB] Browser timing out.
Okay, I'm going mildly crazy now. I've got a huge query that runs and does all sorts of things...but the problem is that it's taking longer than the proxy server will allow to generate the HTML, thus the browser (IE) reports a timeout. I've successfully executed the entire script using Netscape, but Netscape appears to be a little more forgiving with it's buffer size than IE does. I've tried using a flush() call, but the output that is displayed to the user is fairly small in comparasion to all the stuff that's going on in the background. Is there a way to get IE to display the data it has received on the fly? If not, is there a way to force IE (and netscape) to use a smaller buffer size? I've thought about filling up the output buffer with some hidden garbage, but that would just be silly. Any thoughts would be greatly appreciated. --JMR
Re: [PHP-DB] Browser timing out.
unfortunately, it's not something that can be offline. What's actually happening is the database is being queried for information that allows the PHP script to find data files to be sent to the printer. The query really isn't the problem, it's the sending of data when there is ALOT of data being sent. Being that the actual data sent to the browser is minimal, both IE and Netscape wait until there is something worth printing before it renders the output. Basically, I need a way to force IE and Netscape to render the output so that the user doesn't get a timeout notification. --JMR [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Perhaps change it to an offline report? I've done that in the past, it get's scheduled or backgrounded and the results are either emailed to the person, or generated report stored in the database for quick load later on (user gets email that report is ready for viewing).. On Thu, 21 Aug 2003, J. Michael Roberts wrote: Okay, I'm going mildly crazy now. I've got a huge query that runs and does all sorts of things...but the problem is that it's taking longer than the proxy server will allow to generate the HTML, thus the browser (IE) reports a timeout. I've successfully executed the entire script using Netscape, but Netscape appears to be a little more forgiving with it's buffer size than IE does. I've tried using a flush() call, but the output that is displayed to the user is fairly small in comparasion to all the stuff that's going on in the background. Is there a way to get IE to display the data it has received on the fly? If not, is there a way to force IE (and netscape) to use a smaller buffer size? I've thought about filling up the output buffer with some hidden garbage, but that would just be silly. Any thoughts would be greatly appreciated. --JMR
Re: [PHP-DB] Browser timing out.
I've been going with the invisible data mathod right now and it doesn't seem
too bad. What happens on the page is not much to look at and it only
returns maybe 1K while the script is running. However, what's happening in
the background is a huge-ass transfer of data.
To the user, all that's happening is Running . . . until the process is
(almost) done, at which point it tells them approximately when their request
will be completed. To clarify, this is a print-request system I'm
developing so people stop bugging me about stupid printing stuff. They pick
everything they need, how many copies, and the system does the rest for
them, insuring that the prints will look the same each and every time and
waste will be reduced to near-zero. The big-ass query/process is the
transfer of data files to the printer. The actual database work is small and
fast.
What I've gone with (and works fairly well) is a print of 4096 spaces after
a file is transferred followed by a period. The user gets to watch a dot get
printed to the screen about once a second while their stuff is queued up. I
was hoping to avoid having to send a bunch of whitespace, but it seems to be
the only way I can prevent a timeout.
--JMR
Micah Stevens wrote:
Once the current page has loaded, the browser should display whatever it's
recieved, no matter how small.
I'm a little confused as to what you're trying to do, are you displaying a
litlle 'Please Wait for the big ass query' message for the user while the
SQL
plugs away? IF that's the case, you could do a HTML meta refresh to display
a
page that shows the message and then switches over to the second page that
actually does the query. This works pretty well.
I've had mixed results with the flush() command. It seems to work sometimes
with just 1 byte of data, and othertimes it will wait for get a big chunck.
('it' being the browser)
as far as doing it all on the same page goes, your best bet to deal with the
buffer is to output invisible data. IT seems silly, but as you can't
remotely
control the buffer size, it'd probably do the trick.
personally, I use the two page method though.
On Thursday 21 August 2003 1:18 pm, J. Michael Roberts wrote:
Okay, I'm going mildly crazy now.
I've got a huge query that runs and does all sorts of things...but the
problem is that it's taking longer than the proxy server will allow to
generate the HTML, thus the browser (IE) reports a timeout.
I've successfully executed the entire script using Netscape, but Netscape
appears to be a little more forgiving with it's buffer size than IE does.
I've tried using a flush() call, but the output that is displayed to the
user is fairly small in comparasion to all the stuff that's going on in the
background.
Is there a way to get IE to display the data it has received on the fly?
If not, is there a way to force IE (and netscape) to use a smaller buffer
size? I've thought about filling up the output buffer with some hidden
garbage, but that would just be silly.
Any thoughts would be greatly appreciated.
--JMR
[PHP-DB] Line of code should work...but doesn't
I've been going a little crazy here with a single line of code that
should work, but doesn't. It's probably has something to do with the
fact that I've been staring at pages of code for months on end.
In order to make user that nobody is screwing with the database while
the daily backups and maintainence are running, I decided to make a
little thing that would keep people from logging in, etc. Here's the line:
if (strftime(%H) == 03) { header( Location: maintainence.php ); }
In theory, if it's any time between 03:00:00 and 03:59:59 the user
should be redirected to the page maintainence.php, but when testing it
passes over this line without a blip. Any ideas?
Feeling fried,
--JMR
Re: [PHP-DB] Line of code should work...but doesn't
Very interesting...and extremely helpful.
It's amazing the major difference a little 'exit;' can make.
Many thanks for saving my sanity,
--JMR
Aaron Wolski wrote:
if (strftime(%H) == 03)
{
header( Location: maintainence.php );
exit;
}
Note the exit; line.
Aaron
-Original Message-
From: J. Michael Roberts [mailto:[EMAIL PROTECTED]
Sent: July 24, 2003 10:09 AM
To: [EMAIL PROTECTED]
Subject: [PHP-DB] Line of code should work...but doesn't
I've been going a little crazy here with a single line of code that
should work, but doesn't. It's probably has something to do with the
fact that I've been staring at pages of code for months on end.
In order to make user that nobody is screwing with the database while
the daily backups and maintainence are running, I decided to make a
little thing that would keep people from logging in, etc. Here's the
line:
if (strftime(%H) == 03) { header( Location: maintainence.php ); }
In theory, if it's any time between 03:00:00 and 03:59:59 the user
should be redirected to the page maintainence.php, but when testing it
passes over this line without a blip. Any ideas?
Feeling fried,
--JMR
--
J-Michael Roberts
Highland Associates
228 East 45th Street
New York, NY 10017
212-681-0200 - phone
212-681-0201 - fax
[EMAIL PROTECTED]
http://www.HighlandAssociates.com
[PHP-DB] Access 95 ODBC Annoyance
I'll be the first to admit this is a rather backwards system and prone to be illogical, but it's what was handed to me and I can't do much about that. I've got an ancient Access 95 database that I've linked to via another A95 database which is queried via ODBC. It was done this way because I'm not allowed to touch the first database due to the insane way they replace the data each week. (i.e.: any of my tables would be gone, so I need to keep 'my' data safe and link to 'their' data) While under development, I was working with a copy of the database and got everything to work fine. In order to go live with the current data, I had to go into 'my' database and update the linked tables. When this was done, my interface failed miserably and returned the following message: Warning: SQL error: [Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file 'T:\TS\Te_rdata.mdb'. It is already opened exclusively by another user, or you need permission to view its data., SQL state S1000 in SQLExecDirect in C:\Apache2\htdocs\projecthours\deptjobs.php on line 44 Now it gets worse: I need to be able to access the data even if someone has it open. Read-only access isn't a problem...because that's all this particular interface does...but I just keep getting denied. Any ideas? Suffering under a backwards system, --JMR PS - Access is a hunk of crap...especially Access 95.
Re: [PHP-DB] Access 95 ODBC Annoyance
I discovered the problem at had was in the network permissions set on the file (?) that was denying Apache to access it properly and the error code returned was the best thing the system could come up with. I changed my Apached service to 'run as' and authorized user (me) and it happily viewed the data. --JMR J. Michael Roberts wrote: I'll be the first to admit this is a rather backwards system and prone to be illogical, but it's what was handed to me and I can't do much about that. I've got an ancient Access 95 database that I've linked to via another A95 database which is queried via ODBC. It was done this way because I'm not allowed to touch the first database due to the insane way they replace the data each week. (i.e.: any of my tables would be gone, so I need to keep 'my' data safe and link to 'their' data) While under development, I was working with a copy of the database and got everything to work fine. In order to go live with the current data, I had to go into 'my' database and update the linked tables. When this was done, my interface failed miserably and returned the following message: Warning: SQL error: [Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file 'T:\TS\Te_rdata.mdb'. It is already opened exclusively by another user, or you need permission to view its data., SQL state S1000 in SQLExecDirect in C:\Apache2\htdocs\projecthours\deptjobs.php on line 44 Now it gets worse: I need to be able to access the data even if someone has it open. Read-only access isn't a problem...because that's all this particular interface does...but I just keep getting denied. Any ideas? Suffering under a backwards system, --JMR PS - Access is a hunk of crap...especially Access 95.
