===============================================================
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+							      +
+	UPGRADING CUSTOMIZED TEMPLATES DOCUMENT		      +
+							      +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
===============================================================


***************************************************************
	PURPOSE
***************************************************************

This document is designed to provide assistance for users who
would like to alter the web templates for Web Messaging 
v6.04/v6.05 so that these templates will function with Web
Messaging v7.10.


***************************************************************
	AUDIENCE
***************************************************************

This document assumes that the reader has sufficient knowledge
of HTML, JavaScript, and working experience with the IMail
Server.


***************************************************************
	OUTLINE
***************************************************************


- Installation Choices
  1. Overwrite existing templates with the new files 
  2. Keep existing files, but copy over new required files 
  3. Do not install any template related files 

- Changing the element named "action"
  1. Alter the existing templates
    - chghostrule.html
    - chgrule.html
    - msgsum.html
    - readmail.html
    - vh.html

- Upgrading templates for Spell Check
  1. Placing the *.tlx files in the proper domain
  2. Changing the web templates to allow for spell checking
    - draft.html
    - fwdmsg1.html
    - replymsg1.html
    - sendmail.html
  3. Adding the additional files to the web directory
    - help.html
    - pspell.html
    - spell.gif
    - spell_js.cgi
    - spell11.html<*>
    - spell11.jar
    - spell12.html<*>
    - spell12.jar
    - splckbtn.gif

- Upgrading User Admin templates
  1. Alter the existing templates
    - adduser.html
    - chguser.html
    - chpasuad.html
    - dispusr.html
    - sysusradmin.html
    - usradmin.html
  2. Customize the newly added files
    - disableaccount.html
    - disabledlist.html<*>
    - displayuserlist.html<*>
    - domainstat.html<*>
    - enablebtn.gif
    - stat.gif
    - suspendaccount.html
    - userstat.html<*>

- Upgrading List Admin Templates
  1. Alter the existing templates
    - dghedlst.html
    - dgseplst.html
    - dgtralst.html
    - diglst.html
    - headlst.html
    - helplst.html
    - listadm.html
    - mntlst.html
    - subjlst.html
    - subslst.html
    - traillst.html
  2. Customize the newly added files
    - editlistrule.html
    - listaddrule.html<*>
    - listbtn.gif
    - listchgrule.html<*>
    - listmodrule.html<*>
    - mntlst1.html<*>
    - mntlst2.html<*>
    - nolistfile.html<*>
    - plfile.html
    - poster.gif
    - rules.gif
    - syntax.html<*>

- Upgrading general templates
  1. Alter the existing templates
    - addalias.html
    - addhostrule.html
    - addrule.html
    - aliasadmin.html
    - aliasdisplay.html
    - aliasmodify.html
    - chgfwd.html
    - chghostrule.html
    - chgldap.html
    - chgpass.html
    - chgplan.html
    - chgsign.html
    - chgvac.html
    - cs_help.cgi
    - delconfirm.html
    - draft.html
    - editnews.html
    - editwelc.html
    - fwdmsg.html
    - fwdmsg1.html
    - login.html
    - menu.html
    - mnacclog.html
    - mnsyslog.html
    - modhostrule.html
    - modrule.html
    - msgdel.html
    - msgmove.html
    - msgsort.html
    - msgsum.html
    - pattach.html
    - pbutton.html
    - plogin.html
    - pref.html
    - print.html
    - psearch.html
    - psndmail.html
    - pspell.html
    - readfail.html
    - readmail.html
    - replymsg.html
    - replymsg1.html
    - search.html
    - sendmail.html
    - shspool.html
    - ssl.cgi
    - syslog.html
    - systmlog.html
    - summenu.cgi
    - unlock.html
    - vh.html
    - vh_add.html
    - vh_modify.html
  2. Customize the newly added files
    - avsvradm.html
    - badact.html
    - badreqst.html
    - cookie.cgi
    - dropdown.cgi<*>
    - edithostrule.html
    - editoutrule.html
    - editrule.html
    - errorresp.html
    - evalexp.html
    - forward.gif
    - frames.html
    - imapierr.html
    - mailtail.html
    - movedown.gif
    - moveup.gif
    - nofile.html
    - nowebacc.html
    - pavadmin.html
    - pdllload.html
    - replied.gif
    - sysstat.html<*>

- Editing butontxt.ini

- Editing message.ini

- New JavaScript functions
    - functions.cgi
    - quickclick.cgi
    - sm_js2.cgi<*>

<*> - Denotes that a change has been made to this
      template since its original 7.0 release.
      If you are upgrading from a 6.X install,
      ignore these changes and simply alter the
      template from the most recent install/patch.
      If you are upgrading from a 7.X install,
      you must apply the changes listed for this
      template.  Changes made to this original 7.X
      template will be listed below respectively
      as outlined above.

***************************************************************
	INSTALLATION CHOICES
***************************************************************

During the installation process for IMail v7.10, the web
templates are installed or not installed according to the
system administrator's preference.  The system administrator
can select from three options before any Web Messaging or Web
Calendaring templates are installed:
- Overwrite existing templates with the new files
- Keep existing files, but copy over new required files
- Do not install any template related files


1. Overwrite existing templates with the new files
--------------------------------------------------
This option is ideal for administrators who currently do
not have customized templates, and would like to upgrade
to the standard templates for IMail v7.10.  Select this option
if none of your domains have any customized templates, an
altered butontxt.ini file, or an altered message.ini file.
Selecting this option will update only the primary domain's 
directory.  Note that your existing files will be
overwritten if they share the same file name as the
new templates.  This option is also a good way to restore
your primary domain's web templates to the default setting.

Web Messaging:
If this option is selected, the install program will copy
the new Web Messaging templates into the ...\Web folder of the
IMail top directory (i.e. C:\IMail\Web).  Note that this will
overwrite any existing files that may be present from previous
IMail installs.  Two Web Messaging *.ini files will be copied
over into the IMail top directory.  This includes a more recent
copy of butontxt.ini and message.ini, which will be copied into
the IMail top directory (For example, C:\IMail).

Web Calendaring:
If this option is selected, the install program will copy
the new Web Calendaring templates into the ...Web\Calendar
folder of the IMail top directory (i.e. C:\IMail\Web\Calendar).
This option will also overwrite any existing files from previous
IMail installs.  Note that Web Calendaring does not have its own
butontxt.ini or message.ini file located in the IMail top
directory, so selecting this option for Web Calendaring will
not copy over any existing *.ini files.


2. Keep existing files, but copy over new required files
--------------------------------------------------------
This option will not overwrite your existing Web Messaging or
Web Calendaring templates.  All template related files will be
copied into the ..\Web\New folder from the primary domain's
directory.  This option allows the system administrator to
customize the new files accordingly.

Web Messaging:
If this option is selected during the installation process,
only the new Web Messaging templates for version 7.10 will be
installed in the ..\Web\New folder from the IMail top directory.
The contents of this directory should be copied to the ..\Web
folder for the primary or virtual domain(s), and the existing
templates should be updated according to the "UPGRADING CUSTOMIZED
TEMPLATES DOCUMENT" in order for the Web Messaging templates to be
properly read by the web server.  Also, a more recent
copy of butontxt.ini and message.ini will be copied to the
..\Web\New\TopDir folder.  These *.ini files should be copied
over to the root directory of each desired host.  Note
that if a *.ini is present within the primary host's root
directory, the file can be shared with other virtual domains,
unless a virtual domain has its own copy of the given file.

Web Calendaring:
If this option is selected during the installation process,
the Web Calendaring templates will be installed in the
..\Web\New\Calendar folder from the IMail top directory.
The contents of this directory should be copied to the
..\Web\Calendar folder in order for the Web Calendaring
templates to be read for a given host.  As long as the files
exist within the primary domain's ..\Web\Calendar folder, the
files can be shared by other virtual domains, unless a virtual
domain has its own copy of the given file.


3. Do not install any template related files
--------------------------------------------
If this option is selected during the installation process for
both, Web Messaging and Web Calendaring, no template related
files will be installed.  The administrator will have to ensure
that the primary domain's directory is updated with the necessary
files in order to properly use Web Messaging, and Web Calendaring.


***************************************************************
	CHANGING THE ELEMENT NAMED "ACTION"
***************************************************************

In the v6.X templates, several hidden input elements were 
created and given the name, "action."  These elements have been
changed in v7.10 to the name, "imail_action."  Therefore, all
references to the "action" element should be renamed to
"imail_action." The changes explained in this section should be
made in order to obtain proper functionality.

For example:
In the chgrule.html document, you will find the line of code
written below.

<input type="hidden" name="action" value="">

The value given to the name attribute of the input tag should
be renamed to "imail_action" for v7.10.  So, the new line should
read as follows:

<input type="hidden" name="imail_action" value="">

Since this element has been renamed, all JavaScript references
to the old name must be changed as well.  In JavaScript, it is
possible to set the value of the above hidden element by
accessing the properties of the document object.  In the
chgrule.html document, the above element is located in a form
named, "Rules." Some JavaScript code does refer to this element
as follows:

document.Rules.action.value = "<!--IMAIL.AddButton-->";

Above, we see that the old name of the hidden input element is
being used.  This reference must be changed as well to
"imail_action," thus becoming:

document.Rules.imail_action.value = "<!--IMAIL.AddButton-->";

Note:  It is not advisable to simply replace all occurrences of
       the word "action" in your files with "imail_action."
       This may cause additional problems.  You only want to
       rename the <INPUT> tag's value of its name attribute,
       and all references to that tag's name.  If you replaced
       all occurrences of the word, you would actually replace
       those occurrences where the word "action" is the
       attribute of the <FORM> tag, and this is not what you
       wish to do.

1. Alter the existing templates
-------------------------------
This is a list of the files that should be altered:
    - chghostrule.html
    - chgrule.html
    - msgsum.html
    - readmail.html
    - vh.html


***************************************************************
	UPGRADING TEMPLATES FOR SPELL CHECK
***************************************************************

The following information is intended for users who DO
NOT wish to use the new set of templates for v7.10, but
would like to make use of the new spell checking feature.
This section will provide instructions for making alterations
to your existing web templates.

1. Placing the *.clx files in the proper domain
-----------------------------------------------
IWebMsg v7.10 has an added spell check feature, which 
allows the user to check for spelling errors by using specific
dictionaries. There are a few dictionaries that can be
made available to the user depending on the type of spell 
checking required. The number of dictionaries available to the
user can be altered by providing a limited number of *.clx
files in the host's directory or the user's folder. Only the 
*.clx files stored in the host directory or the user's folder
will be seen by the user in a list box. This allows the
system administrator to limit or increase the number of
dictionaries available to the user. Placing the *.clx files in
the domain directory makes those dictionary files available to
all users within that domain.

Example:
If the following files are placed in the a virtual domain
directory (i.e. C:\VirtualDomain\): 

- ssceam2.clx 
- sscebr2.clx

All users of the virtual domain will be able to select "ssceam2"
and/or the "sscebr2" dictionary when trying to spell check
for this domain. However, if those files were to only be placed
in a specific user's folder, only that user would have access
to those files when using the spell check feature.  Note that
all users will have a UserDic.tlx file within his/her folder.
This allows the user to add words to this dictionary.

2. Changing the web templates to allow for spell checking
---------------------------------------------------------
Non v7.10 web templates will have to be altered in order to make
use of the spell check feature. Because customized web
templates may vary, these instructions simply explain what
lines of code should be added, and not specifically where they
should be added.  To create a list box for selecting the
dictionaries to be used, the following code should be added to
the HTML files.  Make the changes explained in this section to
each of the following files:

- draft.html
- fwdmsg1.html
- replymsg1.html
- sendmail.html

Below are six lines of HTML code (ignore the numbering of the
lines; the numbers were added for clarity):

1: <!--IMAIL.BeginIfUserSpellCheckEnable-->
2: <SELECT NAME="lexicons" MULTIPLE SIZE="4">
3: <!--IMAIL.GetDictionaries-->
4: </SELECT> 
5: <A HREF="javascript:getStatusForSplChkr()">Spell Check</A>
6: <!--IMAIL.EndBeginIfUserSpellCheckEnable-->

Line #1 is the opening of a conditional IMail tag (For more
information on conditional tags, see "Tags.doc").  The 
condition of the tag is to determine if the spell check feature
is enabled for this  user.  If spell check is enabled, then the
client will be sent lines #2 through #5.  Lines #2 - #4 of the
code will create the list box for which the user will use to
select the desired dictionaries.  Lines #2 - #4 should be added
somewhere between the <FORM> and </FORM> tag.  Note that the NAME
and ACTION attributes are a part of the <FORM> tag.  Add the code
between the <FORM> and </FORM> tag, which has a name and action
attribute equal to the following:

NAME="SendMail" 
ACTION="sendmail.<!--IMAIL.Number-->.cgi".

In line #5, a link is simply created. This link invokes a
javascript function called, getStatusForSplChkr(). The code for
this function, and other spell check related functions can be
found in spell_js.cgi.  Use the IMail Include tag to place the
content of spell_js.cgi inside the HTML files:

<!--IMAIL.Include.spell_js.cgi-->

Please note that the Include tag should be placed between the
<SCRIPT> and </SCRIPT> tag for all of the HTML files
(sendmail.html, draft.html, fwdmsg1.html, & replymsg1.html).

Note:  A new option should be added to the Edit Preferences
       page, allowing the users to choose between Java 1.1 or
       Java 1.2 Runtime for the spell checker applet.  The spell
       checker will be launched with the version of Java
       selected in the user's preferences.  By default,
       Java 1.1 is selected.  See "UPGRADING GENERAL TEMPLATES"
       for more information.

Note:  Other changes have been made to the compose pages
       (sendmail.html, draft.html, fwdmsg1.html,
       replymsg1.html).  Although these changes do not affect
       the new spell check feature, please see "UPGRADING
       GENERAL TEMPLATES" for more information.


3. Adding the additional files to the web directory
---------------------------------------------------
There are a few files that must be added to the web directory
for the primary domain or for each host domain. These files
will be provided specifically for users who do not wish to use
the standard v7.10 web templates.  Most of these files do not
require customizing, and should not be altered (i.e.
spell11.jar, spell12.jar, spell11.html, spell12.html).
These files are:
- pspell.html

- spell.gif

- spell_js.cgi

- spell11.html
  1. Change the <!--IMAIL.CurrentMessageNum--> tag
     to <!--IMAIL.CurrentUnsortedMessageNum-->

- spell11.jar

- spell12.html
  1. Change the <!--IMAIL.CurrentMessageNum--> tag
     to <!--IMAIL.CurrentUnsortedMessageNum-->

- spell12.jar

- splckbtn.gif


***************************************************************
	UPGRADING USER ADMIN TEMPLATES
***************************************************************

This section of the document describes the changes made to the
user administration templates.  These files were updated to
enhance the administrator's capabilities through web messaging.
Now, the host administrator has a few new user attributes that
can be enabled or disabled, and the ability to view user
statistics via web messaging.  Also, the system administrator
can view system statistics and more user account information.
The changes explained below are recommended enhancements; it
is also recommended that the new web template files are used
as a reference.


1. Alter the existing templates
-------------------------------
- adduser.html
  1. Add the new "Enable Spell Checking" & "Enable IMail Web
     Calendaring" user attributes to the user attributes table
  2. Change the JavaScript condition to allow for passwords
     that are 3 characters or more
  3. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users

- chguser.html
  1. Add the new "Enable Spell Checking" & "Enable IMail Web
     Calendaring" user attributes to the user attributes table
  2. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users
  3. For the checkbox named, "UA07," the
     <!--IMAIL.BeginIfHostAdmin--> and
     <!--IMAIL.EndBeginIfHostAdmin--> tags should be renamed to
     <!--IMAIL.BeginIfUserHostAdmin--> and
     <!--IMAIL.EndBeginIfUserHostAdmin--> respectively

- chpasuad.html
  1. Change the JavaScript condition to allow for passwords
     that are 3 characters or more
  2. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users

- dispusr.html
  1. Add the new "Enable Spell Checking" & "Enable IMail Web
     Calendaring" user attributes to the user attributes table
  2. Change the <!--IMAIL.EachUsreAdminMailboxSummary--> tag
     to <!--IMAIL.EachUserAdminMailboxSummary-->
  3. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users
  4. For the checkbox named, "UA07," the
     <!--IMAIL.BeginIfHostAdmin--> and
     <!--IMAIL.EndBeginIfHostAdmin--> tags should be renamed to
     <!--IMAIL.BeginIfUserHostAdmin--> and
     <!--IMAIL.EndBeginIfUserHostAdmin--> respectively

- sysusradmin.html
  1. Add the new "Enable Spell Checking" & "Enable IMail Web
     Calendaring" user attributes to the default user
     attributes table
  2. Add links to the "Status of Accounts," "Suspended User
     Accounts," and "User Statistics" pages
  3. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users

- usradmin.html
  1. Add links to the "Status of Accounts" and "User
     Statistics" pages
  2. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users


2. Customize the newly added files
--------------------------------------
If you are upgrading from a 6.X install, ignore these
changes and simply alter the templates from the most recent
install/patch.

If you are upgrading from a 7.X install, you must apply the
change(s) listed for these templates below.

- disableaccount.html

- disabledlist.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users

- displayuserlist.html
  1. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users

- domainstat.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users

- enablebtn.gif

- stat.gif

- suspendaccount.html

- userstat.html
  1. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users


***************************************************************
	UPGRADING LIST ADMIN TEMPLATES
***************************************************************

This section of the document is intended to outline the
alterations to the list administration templates.  The files
listed in this section will require editing for one of the
following reasons:
- in order to link with the new files
- in order to remove HTML code that has been placed in a new
  template
It is recommended that the new web template files are used as
a reference.

1. Alter the existing templates
-------------------------------
- dghedlst.html
  1. Rename the textbox named "text" to "imailtext"
  2. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- dgseplst.html
  1. Rename the textbox named "text" to "imailtext"
  2. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- dgtralst.html
  1. Rename the textbox named "text" to "imailtext"
  2. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- diglst.html
  1. Rename the textbox named "text" to "imailtext"
  2. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- headlst.html
  1. Rename the textbox named "text" to "imailtext"
  2. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- helplst.html
  1. Rename the textbox named "text" to "imailtext"
  2. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- listadm.html
  1. Add a link to syntax.html and nolistfile.html
     files with its surrounding conditional tags
  2. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- mntlst.html
  1. Rename the text INPUT named "New" to "newaddr"
  2. Remove the Digest and Kill information
  3. Add "Modify Poster Address List" section
  4. Add a new List option, "Enable Posters List"
  5. Add a new List option, "Enable Password"
  5. Add search button
  6. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- subjlst.html
  1. Rename the textbox named "text" to "imailtext"
  2. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- subslst.html
  1. Rename the textbox named "text" to "imailtext"
  2. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- traillst.html
  1. Rename the textbox named "text" to "imailtext"
  2. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users


2. Customize the newly added files
--------------------------------------
If you are upgrading from a 6.X install, ignore these
changes and simply alter the templates from the most recent
install/patch.

If you are upgrading from a 7.X install, you must apply the
change(s) listed for these templates below.

- editlistrule.html

- listaddrule.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- listbtn.gif

- listchgrule.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users
  2. Change <FORM> action from "listchgrules" to "editrules"
  3. Add hidden <INPUT> tag named "boundType" with VALUE="I"
  4. Add "boundType=I" to all of the Rule related links
  5. Add new "Name" column to the rules table with 
     new <!--IMAIL.##RuleName##--> tag
  6. Change link containing "listrulemodify" to "editrules"

- listmodrule.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- mntlst1.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- mntlst2.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- nolistfile.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users

- plfile.html

- poster.gif

- rules.gif

- syntax.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfListAdminOrOwner--> and
     <!--IMAIL.EndBeginIfListAdminOrOwner--> tag to prevent
     the display of this template to invalid users


***************************************************************
	UPGRADING GENERAL TEMPLATES
***************************************************************

In most cases, the changes listed below are required.  These
alterations are not specific to one feature.  It is recommended
that the new web template files are used as a reference.

1. Alter the existing templates
-------------------------------
- addalias.html
  1. Change the alias type, "List" to "Group"
  2. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users

- addhostrule.html
  1. Rename the text field named "new" to "newMbxName"
  2. Edit the "field" and "subarea" <SELECT> list boxes to
     get their <OPTION> values from new IMail tags
  3. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users

- addrule.html
  1. Rename the text field named "new" to "newMbxName"
  2. Edit the "field" and "subarea" <SELECT> list boxes to
     get their <OPTION> values from new IMail tags

- aliasadmin.html
  1. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users

- aliasdisplay.html
  1. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users

- aliasmodify.html
  1. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users

- chgfwd.html
  1. Rename the textbox named "text" to "textFwd"

- chghostrule.html
  1. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users
  2. Change <FORM> action from "chgrules" to "editrules"
  3. Add <SELECT> tag named "boundType"
  4. Add "boundType=I" to all of the Rule related links
  5. Add new "Name" column to the rules table with 
     new <!--IMAIL.##RuleName##--> tag
  6. Change link containing "rulemodify" to "editrules"
  7. See "CHANGING THE ELEMENT NAMED 'ACTION'" for additional
     changes to this template

- chgldap.html
  1. Add a new text field for the user's Common Name

- chgpass.html
  1. Add a new text field that takes in the old password,
     this text field is named, "oldpasswd"
  2. Change the JavaScript condition to allow for passwords
     that are 3 characters or more

- chgplan.html
  1. Rename the textbox named "text" to "textPlan"

- chgrule.html
  1. Change <FORM> action from "chgrules" to "editrules"
  2. Add hidden <INPUT> tag named "boundType" with VALUE="I"
  3. Add "boundType=I" to all of the Rule related links
  4. Add new "Name" column to the rules table with 
     new <!--IMAIL.##RuleName##--> tag
  5. Change link containing "rulemodify" to "editrules"
  6. See "CHANGING THE ELEMENT NAMED 'ACTION'" for additional
     changes to this template

- chgsign.html
  1. Rename the textbox named "text" to "textSign"

- chgvac.html
  1. Rename the textbox named "text" to "textVac"

- cs_help.cgi
  1. Add the <!--IMAIL.UserKey--> into the "url" javascript
     variable

- delconfirm.html
  1. Added hidden <INPUT> tag named "msgsort"
  2. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link
  3. Change the <!--IMAIL.CurrentMessageNum--> tag
     to <!--IMAIL.CurrentUnsortedMessageNum-->

- draft.html
  1. Rename the textbox named "text" to "textBody"
  2. Added hidden <INPUT> tag named "SpellCheckOn"
  3. Added hidden <INPUT> tag named "msgsort"
  4. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link
  5. Change the <!--IMAIL.CurrentMessageNum--> tag
     to <!--IMAIL.CurrentUnsortedMessageNum-->
  6. See "UPGRADING TEMPLATES FOR SPELL CHECK" for additional
     changes to this template

- editnews.html
  1. Rename the textbox named "text" to "textNews"
  2. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users

- editwelc.html
  1. Rename the textbox named "text" to "textWelCome"
  2. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users

- fwdmsg.html
  1. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link

- fwdmsg1.html
  1. Rename the textbox named "text" to "textBody"
  2. Added hidden <INPUT> tag named "MsgType"
  3. Change the <!--IMAIL.ForwardNoEditStatus--> tag to
     <!--IMAIL.ForwardNoEdit-->
  4. Added hidden <INPUT> tag named "SpellCheckOn"
  5. Added hidden <INPUT> tag named "msgsort"
  6. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link
  7. Change the <!--IMAIL.CurrentMessageNum--> tag
     to <!--IMAIL.CurrentUnsortedMessageNum-->
  8. See "UPGRADING TEMPLATES FOR SPELL CHECK" for additional
     changes to this template

- login.html
  1. Rephrased "Cookies for security" to "Remember userid &
     password"
  2. Added Cookie.cgi for enhanced cookie capability
  3. Renamed the FORM named "Login" to "logon"

- menu.html
  1. Add a link to "IMail Web Calendaring" and its surrounding
     conditional tags
  2. Add a link to "System Statistics" and its surrounding
     conditional tags
  3. Add a link to "Anti Virus Administration" and its
     surrounding conditional tags
  4. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link

- mnacclog.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users

- mnsyslog.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users

- modhostrule.html
  1. Rename the text field named "new" to "newMbxName"
  2. Edit the "field" and "subarea" <SELECT> list boxes to
     get their <OPTION> values from new IMail tags
  3. Surround HTML code with the <!--IMAIL.BeginIfHostAdmin-->
     and <!--IMAIL.EndBeginIfHostAdmin--> tag to prevent the
     display of this template to invalid users

- modrule.html
  1. Rename the text field named "new" to "newMbxName"
  2. Edit the "field" and "subarea" <SELECT> list boxes to
     get their <OPTION> values from new IMail tags

- msgdel.html
  1. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link
  2. Alter javascript code to replace "msg" argument with
     "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument

- msgmove.html
  1. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link
  2. Alter javascript code to replace "msg" argument with
     "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument

- msgsort.html
  1. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link

- msgsum.html
  1. In the table header, change the "Line" column to "Size"
  2. Change <!--IMAIL.##Lines##--> to <!--IMAIL.##Size##-->
  3. Update sorting for ascending/descending order located at
     the top of the message summary table
  4. Add message status indicators for forward/reply-to 
     messages
  5. Change all of the hidden <INPUT> tags named "msg" to 
     "msgsort"
  6. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link
  7. See "CHANGING THE ELEMENT NAMED 'ACTION'" for additional
     changes to this template

- pattach.html
  1. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link

- pbutton.html
  1. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link

- plogin.html
  1. Rephrased "Cookies for security" to "Remember userid &
     password"
  2. Added Cookie.cgi for enhanced cookie capability
  3. Renamed the FORM named "Login" to "logon"

- pref.html
  1. Add the option to select between Java 1.1 or Java 1.2 for
     the spell check applet
  2. Add the option to open IMail Web Calendaring in a new
     window or the current window
  3. In one of the options, change "Number of Lines" to "Size"

- print.html
  1. Add additional support for HTML messages

- psearch.html
  1. Change the search option "Lines" to "Size"

- psndmail.html
  1. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link

- pspell.html
  1. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link

- readfail.html
  1. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link

- readmail.html
  1. Add additional support for HTML messages
  2. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link
  3. Change the <!--IMAIL.CurrentMessageNum--> tag
     to <!--IMAIL.CurrentUnsortedMessageNum-->
  4. Add "&msg=<!--IMAIL.CurrentUnsortedMessageNum-->" into
     the javascript function used to construct the URL for
     the "Print Preview" page
  5. See "CHANGING THE ELEMENT NAMED 'ACTION'" for additional
     changes to this template

- replymsg.html
  1. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link

- replymsg1.html
  1. Rename the textbox named "text" to "textBody"
  2. Added hidden <INPUT> tag named "MsgType"
  3. Added hidden <INPUT> tag named "SpellCheckOn"
  4. Added hidden <INPUT> tag named "msgsort"
  5. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link
  6. Change the <!--IMAIL.CurrentMessageNum--> tag
     to <!--IMAIL.CurrentUnsortedMessageNum-->
  7. See "UPGRADING TEMPLATES FOR SPELL CHECK" for additional
     changes to this template

- search.html
  1. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link

- sendmail.html
  1. Rename the textbox named "text" to "textBody"
  2. Added hidden <INPUT> tag named "MsgType"
  3. Added hidden <INPUT> tag named "SpellCheckOn"
  4. Added hidden <INPUT> tag named "msgsort"
  5. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link
  6. Change the <!--IMAIL.CurrentMessageNum--> tag
     to <!--IMAIL.CurrentUnsortedMessageNum-->
  7. See "UPGRADING TEMPLATES FOR SPELL CHECK" for additional
     changes to this template

- shspool.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users

- ssl.cgi
  1. Add the new 
     <!--IMAIL.BeginIfCurrentDomainIsAVirtualDomain-->
     tag for determining if the current domain is a virtual
     domain

- syslog.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users

- systmlog.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users

- summenu.cgi
  1. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link

- unlock.html
  1. Alter compose, summary, and read mail links to contain
     the "msgsort=<!--IMAIL.CurrentSortedMessageNum-->"
     argument inside of the link

- vh.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users
  2. See "CHANGING THE ELEMENT NAMED 'ACTION'" for additional
     changes to this template

- vh_add.html
  1. Add the new "Enable Spell Checking" & "Enable IMail Web
     Calendaring" domain attributes to the page
  2. Add the new "Enable SSL" & "Force SSL" domain attributes
     to the page
  3. Add the new "Maximum User Count" domain attribute
  4. Add the new "Maximum number of login attempts" domain attribute
  5. Add the new "Maximum number of times suspended" domain
     attribute
  6. Add the new "Maximum suspended duration" domain attribute
  7. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users
  8. Add the new "Maximum Outbound Message Size" domain attribute
  9. Add the new "Full Mailbox Notify" domain attribute
 10. Add the new "Full Mailbox Notify Address" domain attribute
 11. Add the new "Sub-mailbox Creation" radio options
 12. Add the new "Enable Virus Scanning" domain attributes

- vh_modify.html
  1. Add the new "Enable Spell Checking" & "Enable IMail Web
     Calendaring" domain attributes to the page
  2. Add the new "Enable SSL" & "Force SSL" domain attributes
     to the page
  3. Add the new "Maximum User Count" domain attribute
  4. Add the new "Maximum number of login attempts" domain attribute
  5. Add the new "Maximum number of times suspended" domain
     attribute
  6. Add the new "Maximum suspended duration" domain attribute
  7. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users
  8. Add the new "Maximum Outbound Message Size" domain attribute
  9. Add the new "Full Mailbox Notify" domain attribute
 10. Add the new "Full Mailbox Notify Address" domain attribute
 11. Add the new "Sub-mailbox Creation" radio options
 12. Add the new "Enable Virus Scanning" domain attributes


2. Customize the newly added files
--------------------------------------
If you are upgrading from a 6.X install, ignore these
changes and simply alter the templates from the most recent
install/patch.

If you are upgrading from a 7.X install, you must apply the
change(s) listed for these templates below.

- avsvradm.html

- badact.html

- badreqst.html

- cookie.cgi

- dropdown.cgi
  1. Surround Anti Virus link with the
     <!--IMAIL.BeginIfAVInstalled--> and
     <!--IMAIL.EndBeginIfAVInstalled--> tag to limit
     access to the Anti Virus Administration page

- edithostrule.html

- editoutrule.html

- editrule.html

- errorresp.html

- evalexp.html

- forward.gif

- frames.html

- imapierr.html

- mailtail.html

- movedown.gif

- moveup.gif

- nofile.html

- nowebacc.html

- pavadmin.html

- pdllload.html

- replied.gif

- sysstat.html
  1. Surround HTML code with the
     <!--IMAIL.BeginIfSystemAdmin--> and
     <!--IMAIL.EndBeginIfSystemAdmin--> tag to prevent the
     display of this template to invalid users


***************************************************************
	EDITING BUTONTXT.INI
***************************************************************

The butontxt.ini file can be used to rename a button/link
without having to edit every location where that button/link is
displayed.  Simply make the changes in this file, and the
change will automatically occur where the IMail tag is being
called.

For example, the following line can be found in the
butontxt.ini file:

RemoveButton = Remove

Now, on the compose pages, the <!--IMAIL.RemoveButton--> tag is
used.  When this tag is parsed by the server, it will replace
the tag with the data found in the butontxt.ini file.  In this
case, the tag would be replaced with the word, "Remove."

There are several new buttons/links/variables added to this
file.


***************************************************************
	EDITING MESSAGE.INI
***************************************************************

The message.ini file can be used to rename the error messages
and other content. Like the butontxt.ini file, phrases can be
modified within message.ini, and the change will effect every
occurence of the respective IMail tag.  See "EDITING
BUTONTXT.INI" for an example.  There are several new
messages/phrases/variables added to this file.


***************************************************************
	NEW JAVASCRIPT FUNCTIONS
***************************************************************

Several JavaScript functions have been added for increased
usability.  Most of the new functions have been added to the
following include files for the standard v7.10 web templates:
- functions.cgi
- quickclick.cgi
- sm_js2.cgi
  1. JavaScript code was altered to automatically replace
     the spell check dictionary file names with the actually
     title name for each dictionary

If you would like to make use of these additional functions
within your set of customized templates, you may have to make
some additional alterations to the templates that will be
using the new functions.