Versatile form server and processor.

Buy Now




System Requirements:

macOS 10.14


Stuck? We suggest reading through this checklist first. This list contains problems we have received by email and the solutions which solved them.


Mail Server Setup Trouble (top)

The most common problem that users have is configuring iForm so that it can communicate with the mail server. The best approach here is to either consult the administrator of the mail server or copy the settings from your regular email client.

Some tips:


  • • Don't use SSL (secure connections) if your mail server does not support it. SSL is on by default.
  • • You may be required to set the sender ("From Name"), in the form, to the name and email address associated with the mail server's account.
  • • Check that the mail server name, the user name or password are not mispelled.
  • • Check that the port you entered is correct.
  • • Check that you are not exceeding your email send limit imposed by the mail server.

Pathnames (top)

All pathnames are specified relative to the Document Root, and must be in the classic Macintosh format:




where "folder_1" is a folder inside the Document Root folder.

In other words names are delimited using the colon ':' and not '/'


Template Pathnames (top)

Occasionally when you cut and paste pathnames (ex. when doing the JumpStart projects) into the administration form a spurious "space" character is included at the end of the pathname. Since the space character is invisible you will not notice it - but iForm will. This could prevent iForm from finding templates and log files you specify on the administration form. Just remove the space.


Using Administration Values (top)

If you "hardcode" values into a form by specifying values of special parameters (such as iForm_mailTo, iForm_subject, etc.) on the administration form then do not forget to include the "iForm_formPathname" parameter on the form. This parameter must be set equal to the pathname of the form you entered on the administration form. It is the means by which iForm associates the submitted form with the saved administration values.


Remember: iForm is case sensitive.


Thus the "iForm_formPathname" essentially names the form so that iForm can find its administration data.

(See the JumpStart tutorial for an example of how to do this.)


Using AppleScript (top)

If you use Script Editor to create your scripts then remember to save the script as a plain text file. The file should have the extension scpt. Otherwise iForm will not be able to process the script. (iForm also allows file extensions applescript and as, but the file type must always be text.)


If your script is returning an error when executed by iForm then you should try running the script in a program such as Script Editor. If the script is using template tags try setting the values of the template tags at the top of the script, i.e. assign them values. Then run the script to catch the error. After you find the solution to the problem simply uncomment the assigments at the top of the script.


Required Items Not Working (top)

Make sure that you do not include extra space characters after each comma. iForm allows form parameter names to include the space character and will assume that the space is part of the name. For example, this may be wrong:


name, city , state


because of the space characters. Use this instead:




Character Case Sensitivity (top)

Remember: when in doubt assume that case counts. iForm treats all Macintosh pathnames and template tags with case sensitivity. This means that if you specify a form on the Main administration page as




but you specify the same form in the "iForm_formPathname" as




iForm will not be able to look up the administration values for the submitted form because case sensitivity counts when iForm compares words.


Template Tags Not Expanded (top)

First, make sure that you spell the template tags properly and remember that iForm is case sensitive whenever it compares words:

The tags {name} and {Name} are not the same.

Second, make sure that your HTML editing program is not inadvertantly encoding the curly brackets { and }. For example, in JumpStart Project 0 the error template builds a link to enable the user to return to the form and enter missing items on the form. The link is generated using the "referer" template tag:

<P>Please <A HREF="{referer}">go back</A> and enter these values.</P>


It is possible that an HTML editor will save this HTML snippet as:


<P>Please <A HREF="%7Breferer%7D">go back</A> and enter these values.</P>


i.e. it encoded the { as "%7B" and the } as "%7D"


Can't Connect To Server (top)

Make sure you include the port number in the host portion of the URL. For example, if you are running iForm on port 8080 then this URL will not work:




Instead use this:




Receiving message: No such resource (top)

Make sure that the document you are trying to read is in the Document Root folder that is specified on the "Server" tab of the Preferences window.


Error code: -3180 (top)

Make sure that you have correctly specified an outgoing SMTP mail server using the Preferences window.