This section provides an overview of the basic top-level questions about what MailMan is and what it does.

The HTTP error 400, bad request, means that the Web server received a request that it could not process, because it is not configured to do so, or because it expects certain headers or parameters in the request that are not present.

This is a common error found in a Web browser when you are attempting to run a Perl or CGI script that has problems. The three most common reasons for this error are the following: Your script permissions are set wrong. Try setting them to 777 or 755 temporarily while troubleshooting the error. Your script was uploaded in binary file format instead of ASCII. You must upload Perl and CGI scripts in ASCII format only. Your path to Perl (the "sha bang" )line is wrong.

Log in to your account with SSH and test your script. To do this, go into the directory in which your script is located, then execute the script.

I keep getting "THE REQUESTED URL COULD NOT BE RETRIEVED..." when I try to run any software script from CGI Connection

There's a time limit for sending and receiving information on the web. Usually, web servers kick out any transactions after a certain amount of time in order to prevent server rundown, which is usually caused by heavy, prolonged server load.

Internal Server Errors, where you have edited the program yourself, are most commonly caused by typos during editing. These typos result in the program not being valid Perl, and errors confusing the webserver. What you should initially do, is check every line you edited, to check that you have not left a set of quotes or brackets (of any variety) open.

If you are running a Windows server, make sure that you have perl installed. If not, download an install ActiveState Perl. Linux usually has a version of Perl already, although you may need to get a more complete version of CGI.pm. Make sure the first line in all the perl script files(.pl) have the correct path to the perl executable on the server.

There are many different possibilities. If you have a problem, misconfiguration, or syntax error in you script, you will probably be able to find it by checking your error logs which can be found in your your control panel under "Statistics -> Show Error Logs". Although this is generally caused by a problem within the script, many times it is caused by incorrect file permissions either on the script itself, or another file or directory used by the script.

A Web server (external website) encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. a Web browser or web server's CheckUpDown robot) for access to the requested URL. This is a 'catch-all' error generated by the Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. It is up to the operators of the Web server site to locate and analyse these logs.

The Path to Perl or CHMOD of your file or directory may be wrong. Try CHMOD all the files and directory again. Your server may not like the CHMOD setting ask you host what you should be using. Check you did not open the script with anything other than notepad. Check your log to find out more. Also try putting the code below directly after your Path to Perl this will stop and report the script error in more detail.

This is the most general CGI error message you will come across and has a number of causes. Please check the following points: Ensure that your script was ftp'ed to the webserver in ascii mode. If not, your script will be transfered with control characters added to it. You may have specified a mail program that does not exist or resides in a different directory to the one specified in your CGI script. Edit your CGI script and make sure that the mail program is specified correctly.

Make sure the path to perl is correct for your server and the permissions are set as instructed in the Readme file. Make sure the files are uploaded in ASCII mode. If they are uploaded in binary mode they will become corrupted. Full of usefull information to get your autoresponder campaign making you profits each and every month.

First check here (in Student Web Server Upgrade to Apache 1.3 ) to see if your problem is because of Apache 1.3 slightly silly directory permission requirements. If not, you can get hints about what's really going wrong by looking in /software/wwwapache-1.3_server/logs/error_log /software/wwwapache-1.3_server/logs/access_log /software/wwwapache-1.3_server/logs/cgi.

Only one in ten thousand "Internal Server Errors" are actually caused by a server fault. Most likely, your script has a bad permission (a.k.a. CHMOD) setting, error statements and/or a wrong path to the PERL intepreter. Fix the problem and you'll soon realize that the error is actually not caused by the server in any sense.

A 403 "Forbidden" error is a generic HTTP error that your server will send if it thinks for some reason that you should not be allowed to to have access to the file or script that you have requested. This error can be caused by a lot of things. The key thing to remember though, is that if you see a 403 error, then your server has probably already located the resource that you have requested and verified that it exists. This is a good thing, it means that you're almost there.

Internal server error” message (Error 500) basically means that something has gone wrong, but the server can not be more specific about the error condition. It is likely that a server configuration change, CGI script, or other server-side application has triggered the error. If you received this error from clicking on a link on this site, you may want to contact us so we can address the problem.

When executed, you must print an HTTP header followed by a blank line. The header must contain either a Content-type field or a Location field. eg. print "Content-type: text/htmlnn"; 2.You have incorrectly set the path to Perl in your script. 3.You have used invalid Perl arguments.

There is an error somewhere in your ASP pages, but Internet Explorer is hiding the real error message from you. To turn this off, select Options from the Tools menu, select the Advanced Tab, and scroll down until you see "Show Friendly HTTP Error Messages". Uncheck the options and press OK. On refreshing your erroneous page, you will be able to see IIS' explanation of your problem.

All scripts are limited in the amount of CPU they can use. If your script is too CPU intensive, or runs for longer than 20 seconds, it will be shut down, giving a 500 error.

If you have just recently set up your hosting account with us, your site DNS records may not have fully propagated yet. It generally takes 24-72 hours for all the root servers around the world to update any changes in your DNS records. If you have a name based hosting account, try pointing to http://yourIP/~username using the IP and username provided in your Activation Email. If you have an IP based hosting account, try pointing to http://yourIP.