MikeJ

Certainly! Just submit a help desk ticket. In general, anytime you have a problem with your server, or need something changed on your server, you should always use the help desk first. It'll get to the right people to take care of it for you in a timely manner.

A vulnerability was discovered recently in phpBB versions prior to 2.0.11. 2.0.11 is now available in your cPanel and you should be able to upgrade to it via the cPanel upgrade option. If you use phpBB, you should upgrade to 2.0.11. If you have phpBB installed but are not using it, please consider uninstalling it. Note: If you find that 2.0.11 is not available in your cPanel, please send in a support ticket.

They can't really. That's one of the beauties of open-source. Thumbs Up

That looks like a configuration issue with your Geeklog. The Geeklog is bouncing it, not the system at that point. I haven't used Geeklog myself, so I'm not sure what you need to change to enable the email postings.

Your syntax is a little off. If you want to read in an email (following the direction of your use of define()), you would want something more like this: >// read from stdin define("STDIN", fopen("php://stdin", "r")); $message = ""; while (!feof(STDIN)) { $message .= fread(STDIN, 1024); } fclose(STDIN); Most importantly, your main problem is the quotes around the fopen() function. In your code, you are defining STDIN as the string "fopen('php://stdin','r')" instead of the result of the fopen() function. Also, without the while loop, you will only get the first 1,024 characters of your message.

Any output from the script will be interepreted as an error. To have the script process without getting a failure email bounced back, use #!/usr/bin/php -q as the first line of the script (defines the processor, and -q supresses header output) and make sure there are no blank lines outside of your PHP block (because they will output as blank lines if you do). For example: >#!/usr/bin/php -q <?php ... your php code here ... ... blank lines in this block are ok. blank lines outside of it are not. ... ?> Make sure outside of the <?php and ?> there are no blank lines.

The reason is because cPanel changed the configuration of how email is handled. When that post was done, :fail: would accept the message, process it, then bounce it. Now the mail software refuses to accept the message which means the mail never is transferred to the server. This saves you bandwidth, and saves our servers some processing time.

Just a minor note on this (not directed at you Jim but in general)... make sure you use :blackhole: or :fail: (note the colon before and after the word). I see our queues get filled with messages all the time being sent incorrectly to ":blackhole" which the mail server doesn't know.

If a server is down, the sending mail servers will queue the messages until delivery is possible as long as the mail server is not down for multiple days. This really has to do with the mail protocol in general, and not really with how TCH has anything setup. TCH can't do anything with the mail if the server is down because TCH doesn't have the mail yet. But you can be assured that when a server is down, the liklihood you would lose any mail at all would be very minimal.

Welcome to the Wordpress club, Thomas! Thumbs Up

Because it shows up (at least now). I assume you are looking at Scripts and Programs under PHP?

I would favor 1024 but my mother and a friend of mine still insist on keeping their systems at 800x600 (which bugs the ***** out of me when I use their machines), and I keep seeing how my sites don't look quite right on them. I have no idea what "industry recommendation" is though. I'm not exactly a web designer.

The error logs are not available outside of the cPanel function.

Default is short_open_tag on, asp_tags off. You can change those per account if needed, though (just set them using "php_value short_open_tag off" for example in your .htaccess file).

If you registered it through TCH, you should go here. In the forums we can't really help you with the status of the domain (especially since we don't even know what it is).

Is this what you are looking for? http://www.totalchoicehosting.com/forums/i...=awstats+update

He's been eating a lot of banana's lately.

Uh, yea.... you want to see pathetic... My domain back in 1998 (first time it got archived): http://web.archive.org/web/19981111190849/http://biggorilla.com/ My domain now: http://www.biggorilla.com What's pathetic is I've been meaning to put up a real site that entire time...

Try with permissions 755 (so that all can execute). And something unrelated to it working, but you can change that first line to !#/usr/bin/php -q to suppress the header output since this will only be used in your filters (assuming that's the case).

|/home/myusername/public_html/myfolder/parser.php Make sure not to put quotes in there. Also, this will run as a shell script, not a web page, so the script has to know how to execute, which means the script has to be set to executable (go into file manager and make sure the execution bits are set) and the first line of the script needs to be #!/usr/bin/php so the script knows what to run to parse it. The email will be passed to the script via STDIN (standard input).

I have a habit of encrypting all of my connections.

One last suggestion... If your email clients supports SMTP over SSL, you could enable that and try port 465 at mail.******.

You could also use port 465 if you enable SSL encrypted SMTP in your mail client.

Broken DNS servers, broken proxies... there are reasons email could still go to an old location, but that usually means that the person sending the email has something that isn't configured correctly on their end (hence most often spammers). When I moved my old domain, I had occasional spam coming to my old mailhost for over a month (in which I finally shut it down). Never had a legitimate mail come to the old host, though, so I wouldn't worry too much about it. The best thing is just to eventually get that old host shut off so that mail would bounce should it go there in the remote chance someone legitimate sends you something from a broken setup, so at least they know you didn't receive the message.

Count me in! There's even an Amtrak train from Chicago to Royal Oak.