Go Daddy help needed...

Studio381

Can anyone help?

I host a few applications with Go Daddy. These send out emails from PHP using the mail() function.
Everything worked fine until last Saturday when no emails were going out. Had worked for 2 months previously.
I talked to Go Daddy support and they told me the problem was my scripts - I hadn't changed anything. They made a test and everything was ok on their side.
Amazingly the mails started working again.
This morning it has stopped again - when I called them guess what, no problem on their side - must be the scripts.
Any suggestions how to resolve?
Thanks,
John.

NogDog

With no idea what the scripts look like and without access to the web server error logs, it's going to be pretty hard for us to resolve this (unless you're lucky enough to have this thread looked at by someone who had the exact same problem and doubly lucky enough that s/he was using the same script).

bradgrafelman

Does the content of the e-mails vary? Could it perhaps be that some messages are getting flagged by a spam filter yet others aren't? Are you hearing this from other users, or are you yourself experiencing this problem? If the latter is true, what domain do you receive e-mail on?

Studio381

The content of the emails is the same other than some dynamic data is added eg the name of the person - the issue impacts me and all others.

I know this is like looking for a needle in a haystack but...

bradgrafelman

Is PHP logging any errors?

Since this is a production environment, I assume you have some sort of error logging set up to catch all error messages (even notices IMO), right? 😉

Studio381

Hi,
no error logging set up (some direction on how to do this would be appreciated). However no php errors when the applications are accessed from the web and no complaints about this from any users.

bradgrafelman

Well you probably won't see the errors from the user-side, as I assume you also have display_errors turned Off...??

For information on error logging, see this manual page: [man]ref.errorfunc[/man]. Basically, you simply point the error_log variable to a file that the webserver can write to, enable the log_errors, directive (and disable display_errors if you haven't already!), and set error_logging to a generous level (I normally leave it at E_ALL).

Other than that... it's really hard to track an e-mail's progress once the SMTP gateway accepts it. It could be silently blocked as spam without you ever knowing, who knows.

Studio381

Ok, thanks. I'll have a go with this and see if anything appears.