Well how about that

Post #316,243 by drook 10/27/09 1:22:48 AM Reply	Well how about that I narrow it down to the simplest test case. They actually left the file in my home directory that they used to test PHP email after the migration. Still had their technician's email addy in it. I called them, got a tech to look at that file. He started looking at my MX records. I explained why that wasn't it. Said he'd forward the ticket to programming. I explained why that wasn't it. Told him that most likely it was a sysadmin issue. Either someone had changed the sendmail configuration on the webserver, or they had changed a routing rule between the webserver and the internet. And it had happened between 8:30 (last confirmed email sent) and 10:30 (when I noticed the issue) last night. He writes it all down and says they'll email me in the morning. Twenty minutes later, I get an email from that little test file. And now my other apps seem to be sending again. I wonder what the email tomorrow morning will say? I wonder if I'll even get one? -- Drew
Post #316,247 by static 10/27/09 8:23:06 AM Reply	I hate PHP's mail() function. It is way too idiosyncratic and highly dependant on php.ini settings that often rely on a mail injector running locally and correctly configured. It needs to Go Away and I wish the PHP people would realize that. PHPMailer is generally regarded as the best replacement, as it either completely avoids the local SMTP handling, or knows how to make it work correctly behind an API that makes sense. But of course, you don't have the luxury of changing your code, do you? :-/ They probably turned off the local MTA. Unfortunately, that doesn't make mail() spit back an error because the local injector still runs! The way to debug that is to rummage in the local SMTP logs. Wade. Q:Is it proper to eat cheeseburgers with your fingers? A:No, the fingers should be eaten separately.
Post #316,252 by drook 10/27/09 9:26:19 AM Reply	And I don't get SMTP logs But I do have the luxury of changing the code. The app I'm using is ... unfinished. I've already updated the piece of code that handles sending multiple messages on a schedule -- assuming I get them to fix crontab [sigh] -- to use PEAR Mail_Mime. I discovered last night the code for sending one-off messages doesn't use the same functions. -- Drew
Post #316,322 by static 10/28/09 7:36:53 AM Reply	Oh, well, then PHP Mailer is recommended. I haven't used anything in PEAR in years; the average quality of code last time I looked was dreadfully low. Wade. Q:Is it proper to eat cheeseburgers with your fingers? A:No, the fingers should be eaten separately.
Post #316,329 by drook 10/28/09 9:45:28 AM Reply	Really? I haven't had any problems with PEAR Of course I'm only using Mail (and Mail_Mime), DB and Log. They're fairly straightforward, and are things that I had written myself before PEAR was available. The syntax for calling each of them was so similar to what I had already done that it was easy to switch out, and use something maintained by more than just me. -- Drew
Post #316,362 by static 10/28/09 6:10:36 PM Reply	I looked at DB and ilk a few years ago. None of them could do what my own custom handler could already do and when I looked at what it would take to modify one of them so they could, I was turned off by the code. It was simplistic where it shouldn't have been, complex where it was unnecessary and condescending when you didn't subscribe to the author's vision. :-/ Wade. Q:Is it proper to eat cheeseburgers with your fingers? A:No, the fingers should be eaten separately.

Welcome to IWETHEY!