Emailing the form submissions in NetMAX 3.x and earlier.

Here are the steps that you must take to configure the sending of mail for the FrontPage server extensions for old versions of NetMAX.

Login as root and edit the /var/local/frontpage/version4.0/frontpage.cnf file to contain the following entries:

SendmailCommand:/usr/sbin/sendmail %r
MailSender:frontpage@yourdomain.com

The other option would be to add these lines:

SMTPHost:127.0.0.1
MailSender:frontpage@yourdomain.com

The MailSender address will be used if the from address is not specified in the form. These settings will be used for all virtual hosts as well.

To use different settings for different hosts, instead of editing the frontpage.cnf file, you would edit the .cnf file for each virtual host in the /var/local/frontpage directory.

You will want to read the knowledge base article at:

http://www.netmax.com/fom/cache/266.html

Saving the form submissions to disk

If you are saving form submissions to a file with a webbot, ensure that the directory that you're saving to is writeable by the user "nobody", and that the file already exists and is writeable by the user "nobody". FrontPage expects the file to already be there, and will not create it.

Helpful Notes

(You only need to do the following if you are going to copy your FrontPage created documents over from a Microsoft website, instead of publishing them, like you're supposed to. If you use FrontPage to publish your site to the NetMAX, you do not need to do this!)

In order for the NetMAX to handle the Microsoft FrontPage HTML markups just like a Microsoft FrontPage enabled web server, it only takes a two-line modification to the FrontPage root web's ".htaccess" file. If you have problems publishing your FrontPage documents, or to avoid having to create the form submission save-to files, you can try the following.

The HTML files need to be parsed by "/_vti_bin/shtml.exe" in order for the webbot markups to function as they would on a "normal" FrontPage enabled server. If the HTML pages are not put through "shtml.exe", then the webbot markups are not processed, and the web page will not displayed as intended.

In the FrontPage root's directory (like /var/mnt/System/Web/external) there should be a ".htaccess" file. Add these two lines at the end:

    AddType application/frontpage htm html
    Action  application/frontpage /_vti_bin/shtml.exe

This will make all ".htm" and ".html" files be passed through "/_vti_bin/shtml.exe", which will parse the FP webbot markups, making the NetMAX web server act just like a standard Microsoft FrontPage enabled web server.

SERIOUS DRAWBACK: Since we told Apache to send *all* HTML files through the external CGI script, accessing any HTML file will cause the "shtml.exe" program to be executed. This could seriously slow down the system during a period of time when there are a lot of HTML files being accessed.

Recommended solution: Instead of parsing all "htm" and "html" files for FrontPage webbots, pick another file name extension, like "fphtml", to parse for webbots. In this case, the .htaccess additions mentioned above should be changed to be:

    AddType application/frontpage fphtml
    Action  application/frontpage /_vti_bin/shtml.exe

Note that we do not recommend running the FrontPage server extensions due to multiple security problems associated with them. We can not provide support beyond ensuring that you have enabled FrontPage in the NetMAX Interface. If enabled for a web site, Microsoft's FrontPage Server Extensions for UNIX should be installed as instructed by Microsoft.

http://support.microsoft.com/support/default.asp?SD=SO&PR=fp2000

address-suppressed