It is always a good idea to upgrade your version of CookMail to the latest
if you encounter any troubles. It is both easier for you and me to figure
out the problems. The following list of questions are not in any
particular order. If you have any additional questions, bug reports, or
feature requests, please email me.
- Can I use CookMail on Windows 9x?
- I tested CookMail with Apache Web Server 1.3.3 and Personal Web Server on Wnidows 95 and it seemed working fine on both.
- Why did I get "
HTTP/1.0 401 Object not found"?
- A few possible reasons.
- CookMail was not installed to the correct directory. As the result, you weren't able to run cookmail.
/tmp was not found. (Possible only if you use the regular version.)
- Why did I get "
HTTP/1.0 501 Not Supported"?
- There are quite a few reasons. If you are using CookMail version 2.1 or earlier, it would be a little bit hard to find out why. Please download version 2.11 or later of CookMail. Although 2.11 has no feature improvements over 2.1, it offers error messages which can be used to narrow down the problems.
- Possible reasons:
- CookMail was not installed in a CGI script directory.
- CookMail was unable to find/read/write files required. If you use
SHOW/FORM/CCFORM/ERROR files, make sure these files have correct pathnames. Make sure
C:\TEMP exists if you are using Windows NT.
- CookMail encountered an unrecoverable error.
- In Windows NT, the form tag should be
<FORM METHOD=POST ACTION=/cgi-bin/cookmail.exe>
.exe is necessary.
- Make sure that
cookmail.exe is readable & executable by the world.
- My NT web server does not support virtual directories. How to install CookMail then?
- Install CookMail Lite instead. If you are going to use CookMail regular version, there are quite a few ways around this problem, I will just describe one:
- In your web root, create a directory called
tmp. Make it readable and writable by the web server.
- Use a binary/hex editor and edit
cookmail.exe. Search for phrase
C:\TEMP and replace it with the full path name for the
tmp directory you just created. Terminate the directory name with a NULL character (hex number 00).
- How do I use the MIME feature of CookMail? When should I use it?
- MIME is used primarily to deliver emails which contain 8bit data (used mostly in international languages). It is easier to use than
UUENCODE/UUDECODE because of more standardized implementations and it is build in in most popular email readers. There is no need to use MIME if people who are going to visit your site speak English or your site email delivery agent supports 8 bits data. Here is how to use MIME feature in CookMail:
<INPUT TYPE=HIDDEN NAME=MIME VALUE=on>
*NOTE* This would cause both the email you received and the email send back to the viewer to be MIME encoded.
- I have installed cookmail successfully. Everything looks fine except that no emails were sent. What went wrong?
- This is a hard one. Make sure that
COOKBLAT.EXE is executable by the world. Also you will need to install this program in
PATH, such as
C:\WINNT\SYSTEM32\. The configuration of your web server may also affect this. Also, make sure that you did install COOKBLAT. It is very easy to forget doing it.
- I can receive the email, but no result page was displayed in the web browser. I did find the generated html file located in tmp. Why?
- Your web browser probably does not support (or is not configured to handle)
Location: filename. Use CookMail Lite instead.
- I installed CookMail on one server and it worked fine. But when I tried to install it on another server, CookMail refused to work. Why?
- There are four versions of CookMail for NT on intel, two versions (regular and lite) send
HTTP/1.0 200 OK header and two versions don't. If one regular version failed, please try the other one. Do the same to the lite versions. If you still have problems, email me.