MikeJ

I have a mac, and I can tell you the editor works in Firefox on Mac OS X. It does not work in Safari.

Yes, it is possible to register domains with 2 letters, however you won't find any 2 letter combinations that aren't already registered, especially under .com. Pretty much the same story with 3 letter combinations.

Just my personal opinion, but I don't consider "phone company" type support to be a good thing. My only experience directly with Qwest is when I had a T1 with them several years ago, but I can only categorize that support experience as "horrific". However, being several years ago, that could have changed by now.

For starters, make sure your software is up to date. I believe you are running vBulletin, so make sure you upgrade to the latest release which just came out (Jan 7, 2005) and is considered a critical update due to security vulnerabilities in previous releases. Any software you actively use for your website you should keep pretty up to date. Anything that you have installed that you do not use, you should remove. The main thing you will want to look for in the weblogs is how they compromised your site. The ip address they did it with will rarely be beneficial to you as 99.9% of the time that address will just be another compromised site the hacker used. If you have a pretty active site, unusual activity will be harder to find in the log. If you know roughly when the site was defaced, you can look at the activity leading up to that time.

Congrats Mike and Rob! Both excellent choices.

Email that goes through a forward on your account is not subjected to any spam filtering (that only happens when it's being delivered to a local mailbox and if you have spamassassin enabled on your account). So that means 100% of the spam that gets sent to your forwarded email address is forwarded.

Indeed, when mail is already being blocked by AOL and can't be fixed until we make the change to stop forwarding, this is the least distruptive solution based on the options TCH had. The result is some people will have to change where they accept email (and we've recommended against forwarding to AOL in the past), but they still have the option to do that. But anyone from the blacklisted servers that wants to send email to aol customers does not have any options until the blacklists are lifted.

There is no limit on the size of the files you upload via FTP, or that you serve via HTTP (web). The only limits are the amount of diskspace you have, and the amount of bandwidth you have (this could be an issue if too many people are viewing these large files).

If you ever hope to see the outside of your house again... don't do it! Between keeping people alive (my primary char is a priest), plucking herbs, and mixing my concoctions (I'm also an artisan alchemist), what seems like minutes can easily become hours. But then again...I play WoW with friends... so is that considered socialising???

Submit it as a help desk ticket so we can get your account details to troubleshoot the problem.

The best part about that jeep that isn't noticable from the picture, is that it houses two... I repeat... two hemi-powered V8's.

That means the remote host has been failing for so long our mail server temporarily is bouncing messages destined for that address instead of attempting again. After a retry period has passed (which currently for that domain is listed as 21:29:19 Eastern time tonight), new email will attempt to be delivered again. If you need more direct support on this particular issue, you'll need to submit a support ticket.

It most likely means the remote server (the provider of your client) wasn't functioning properly when you sent the email. The error definitely is coming from the remote server. EHLO is the first step in initiating a connection to the remote mail server. That failed when the remote mail server didn't respond to the command, and that's why the mail never left TCH's server. I just tested connectivity to their mailserver now from your server and it looks fine, so I'd recommend trying to send email to your client again.

This one's for you Glenn (both images from today's news)... A new jeep... And something to tackle with it... Source stories: http://www.detnews.com/2005/autosinsider/0501/09/-54845.htm http://story.news.yahoo.com/news?tmpl=story2&u=/050110/480/cadd10101102308&e=6&ncid=1778

You have a pretty active community. There's value in that. You should research sponsorships, advertising, or even donation routes (although those often don't prove to be the most reliable) to raise the money needed to support your forums. You'll probably find that advertisors in particular place a lot of value on a highly active forums with a focused audience. I'm not sure how much of that you've done already, but it could help if you haven't.

While we only list limits on bandwidth and diskspace consumption, we also reserve the right to not allow sites that require too much processing time (therefore affecting the ability of other sites on the same server to be served). A forum of your size and level of activity is really not going to function well on any shared hosting environment because it requires a pretty substantial amount of cpu and disk access. Just as an example, these forums here are somewhat comparable in size and activity to yours, and these run on two dedicated servers to provide the performance you see. For your own good, you really should be looking at dedicated servers, or virtual private servers (VPS) for that type of setup. Anything less, and you will not get the performance you desire, if you don't get outright suspended/terminated due to too much processing. VPS is the cheaper of the two solutions, giving you your own "virtual machine" on a semi-shared server, but is not something TCH offers or has plans to offer, and still will have some restrictions on processor and disk usage. A dedicated server will give you the maximum benefits, but also with the maximum price as I'm sure you already know. To answer your shell question, TCH does not offer shell access to any of our shared or semi-dedicated accounts. I know these aren't the answers you were hoping for, but to be honest, you have outgrown shared accounts.

Generally, that's done by using computers they managed to infect or compromise to later use for this type of spamming. So those numerous dynamic IP addresses you are seeing are likely people's home computers who aren't even aware their computer is being used for this purpose. Most are relatively automated and rather persistant. I had one spammer this weekend attempt to spam my blog over 3,000 times from all kinds of IP's even though none of them ever made it to my blog. The trackback's are starting to be used more for precisely the reason that it's harder to moderate them.

Most likely it sounds like your machine has been infected with adware, and probably has nothing to do with your website. Grab Ad-aware (google for it, it's made by lavasoft) or similar "ad cleaning" tools to clean out your system with.

This is what I used to use. I'm not even sure where I originally picked up the example, but I'm not the original author of it, but I do know it's free to use. ><?php # Put the SERVER PATH to image directory. # INCLUDE trailing slash $dir = "/home/youraccount/public_html/images/random/"; # Put the HTML PATH to image directory. # DO NOT include trailing slash $html_dir = "http://www.******/images/random"; $dir_handle = opendir($dir); $image_array = array(); # This opens up the image directory, grabs all files with a ".jpg" extension # and puts them into an array. You can set whatever extension you'd like here. # Just switch out the .jpg for .gif, etc. If you have more than one extension, # replace this line with something like this: # if (($file !=".") && ($file !="..") && (substr($file, -4) == ".jpg") || (substr($file, -4) == ".gif"))) { # This will pull up all .jpg OR .gifs. If you name all the images you want to pull # a certain way (example, image-thumb.jpg or image.thumb.jpg) you can do this: # if (($file !=".") && ($file !="..") && (substr($file, -10) == ".thumb.jpg")) { # basically you want to put the extension in quotes and then count how many characters # it is and place that after $file, - while ($file = readdir($dir_handle)) { if (($file !=".") && ($file !="..")) { $file_name = "$html_dir/$file"; $image_array[$file_name] = $file_name; } } # sorts the array. For some reason this won't work at all # unless this is done. Can anyone tell me why? sort($image_array); $count = sizeof($image_array); # trims all the URLs of whitespace and assigns each # item in the array a number to identify it. for($i = 0;$i<$count; $i++) { $image[$i] = rtrim($image_array[$i]); } # assign a random value $r = rand(0,$count-1); # get the size of a random image $size = getimagesize($image[$r]); $width = $size[0]; $height = $size[1]; # This is the HTML output. You can change any of this, but you should # leave src=\"$image[$r]\" width=\"$width\" height=\"$height\" where it is. # Remember to escape any quotation marks, etc. $img_src = "<center><img src=\"$image[$r]\" width=\"$width\" height=\"$height\" vspace=\"5\" border=\"1\" alt=\"This is a Random Image\" /></center>"; echo $img_src; # closes the directory (why keep it open?) closedir ($dir_handle); ?>

I can understand the confusion. The vulnerable script is actually called "Jack's FormMail".

No. Ultimate Form Mail script is a completely different script and does not have this vulnerability.

An advisory has been released regarding Jack's FormMail script v5.0. Jack's FormMail script is not a TCH supported or supplied script, but I know many users use it. The above vulnerability can allow a remote user to gain access to read files normally not viewable through your website (such as your .htaccess file, or other private files). The following fix is recommended for users of Jack's FormMail script until a new version is released that fixes this problem:

Slashcode is a bit of a nightmare. Your only real options are to get a dedicated server or VPS of your own where you have root access, or find a host that provides slashcode preinstalled for you (TCH does not, and we don't plan to). It is not real friendly in shared environments. And just to confirm, slashcode will not run on TCH shared servers. Specifically, we do not provide mod_perl, and we don't allow shared hosting clients to run their own daemons (services).

See this thread for information on upgrading your phpBB software.

'course...if so many people didn't get plastic surgery to conform to some fantasy "ideal", then maybe self-esteem would be less of a problem. I think self-improvement is a good thing... I just think some people take it too far.