smaller reset larger        English         

Main Menu

All times are in GMT -8 (DST) :: The time is now 5:04 am.

Sub Menu

Category Details
Category Name
Webmail
Category Created
Fri, 9th Mar 2007
Last Article Update
Fri, 9th Dec 2011
Category Actions
 
(Lost?)

   Webmail

Cannot Access the Webmail Interface 

This means that while DNS for 'something.domain.com' points to an IP assigned to the CGP server, 'something.domain.com' doesn't actually exist as a domain or domain alias on the system.

In most cases the actual name of the domain on CGP is just 'domainname.com' and not 'something.domain.com'. Simply adding 'something.domain.com' as a domain alias (http://www.communigate.com/cgatepro/Domains.html#Aliases) should address the problem.
View Full Article Add Comment

Customizing the WebMail Login Page 

This depends on your choice of "default layout" for all users.

Location of selecting the default layout is dependent on the version of CommuniGate Pro

For version 5.1 it is Users->Account Defaults->Preferences->Layout
For version 5.0 and 4.3 Domains->All Domains->Account Defaults->WebUser Prefs->Layout

Once created, your customized version of the Login page will always be
retained, even through upgrades. So, the following process only needs to
be done once.

For this example, we will change the login page when using the "Simplex"
skin as the default. Simplex is the "base skin" for all of these:
Aquinox, Overview, XChange, and Viewpoint - in many cases, you will only
modify the Simplex skin settings.

You can change the default login page by doing the following:

1. Login to WebAdmin

2a. 5.1 Go to Users->Account Defaults->Preferences
2b. 5.0 & 4.3 Go to Domains->(All Domains)->Account Defaults->WebUser Prefs

3. Select a default skin for users, such as Simplex

4a. 5.1 Go to Users->Skins
4b. 5.0 & 4.3 Go to Domains->(All Domains)->Skins

5. At bottom of page, do [Create Skin:] "Simplex". This will provide a
"local" (/var) directory for Simplex, with nothing in it at first
(/var/CommuniGate/WebSkins/Simplex on linux/unix)

6. At bottom of page, select the "Simplex" skin you just created

7. Download the login.wssp page to your system, modify it as desired,
then "Browse:" and "Upload:" it. "UnCache" it for good measure.

NOTE: In the event that you are unable to create the named skin Simplex, you will need to go
into the base directory of CommuniGate Pro and create a directory called Simplex in the
following location (CGPBase)->Settings->WebSkins

That should be it. The default Simplex skin will be applied to your
personalized version of the login page.

You can then do the same thing with the "bye.wssp" page for logout.
View Full Article Add Comment

Display Limit for Directory Browsing 

There is a hard maximum limit of 500 records set within the CommuniGate Pro software. This limit can be set to something less than 500 by modifying the 'Directory | <Storage Unit> | Settings | Search Results Limit' setting via the web administrative interface.
View Full Article Add Comment

How do I integrate CommuniGate Pro WebMail into a portal? 

There is a straightforward way to integrate any portal with CommuniGate.

Basically, follow these steps:

When the user authenticates into the portal, have the portal code initiate a special Perl/Java/whatever CommuniGate CLI script which does the following:

1) The script should authenticate as an administrator-type account, perhaps just a special account created just for this portal integration.

2) The script should issue the CLI command "GETWEBUSERSESSION" (http://www.communigate.com/CommuniGatePro/CLI.html), to check if the user already has an active session on the cluster.

3) If no session is currently active, the script should issue the "CREATEWEBUSERSESSION", and return the Session URL to the portal.

4) Optionally, you can also have the script issue the "GETMAILBOXINFO" CLI command, to retrieve the number of Unseen messages in the INBOX.

All of this data should get returned to the portal, which can be displayed by the portal as a link to the WebUserSession and displaying the number of unread messages. Clicking on the link will open up the WebUserSession without the user having to re-authenticate.
View Full Article Add Comment

Modify Date format in Pronto! 4 

The process is to create a custom skin file (strings.data) and modify the 'numericDate" string from the "DatePictures" dictionary. The custom strings.data should be uploaded then to the corresponding skin. So, this would mean you need to create a custom skin called Pronto4 on the 'Users | Skins' page of the web administrative interface and upload the file there.

This process is outlined in the following video: https://mail.communigate.com/~jolson/screencasts/ChangeDateFormatPronto4.mp4

Here is what the DatePictures dictionary from strings.data looks like before and after the modifications:

Before (with date format as DD/MM/YY):

  DatePictures    = {
    Mon    = "Mon";    Tue    = "Tue";    Wed="Wed";    Thu    = "Thu";    Fri    = "Fri";    Sat    = "Sat";    Sun    = "Sun";
    Jan    = "Jan";    Feb    = "Feb";    Mar= "Mar";    Apr    = "Apr";    May    = "May";    Jun    = "Jun";
    Jul    = "Jul";    Aug    = "Aug";    Sep="Sep";    Oct    ="Oct";    Nov    = "Nov";    Dec    = "Dec";

    timeOnly    = "^h:^m:^s^t";
    hourMinute    = "^h:^m^t";
    dateOnly    = "^D ^M, ^Y";
    numericDate    = "^D/^N/^y";
    dayAndDateAndTime    = "^W, ^D ^M, ^Y ^h:^m:^s^t";
    dayAndDate    = "^W, ^D ^M, ^Y";
    dateAndTime    = "^D ^M, ^Y ^h:^m:^s^t";
    dayAndMonthAndTime    = "^D ^M ^h:^m:^s^t";
    dayAndMonthDate    = "^W, ^D ^M";
    yearMonth    = "^M ^y";
    never    = "Never";
    weekend    = "Weekend";
    weekday    = "Week Days";
    everyday    = "Every Day";
  };

After (with date format as MM/DD/YY):

DatePictures    = {
    Mon    = "Mon";    Tue    = "Tue";    Wed="Wed";    Thu    = "Thu";    Fri    = "Fri";    Sat    = "Sat";    Sun    = "Sun";
    Jan    = "Jan";    Feb    = "Feb";    Mar= "Mar";    Apr    = "Apr";    May    = "May";    Jun    = "Jun";
    Jul    = "Jul";    Aug    = "Aug";    Sep="Sep";    Oct    ="Oct";    Nov    = "Nov";    Dec    = "Dec";

    timeOnly    = "^h:^m:^s^t";
    hourMinute    = "^h:^m^t";
    dateOnly    = "^M ^D, ^Y";
    numericDate    = "^N/^D/^y";
    dayAndDateAndTime    = "^W, ^M ^D, ^Y ^h:^m:^s^t";
    dayAndDate    = "^W, ^M ^D, ^Y";
    dateAndTime    = "^M ^D, ^Y ^h:^m:^s^t";
    dayAndMonthAndTime    = "^M ^D ^h:^m:^s^t";
    dayAndMonthDate    = "^W, ^M ^D";
    yearMonth    = "^M ^y";
    never    = "Never";
    weekend    = "Weekend";
    weekday    = "Week Days";
    everyday    = "Every Day";
  };
View Full Article Add Comment

Modifying the Login page to limit the available skins 

This requires modifying the login.wssp page like the following example
(in "patch" syntax):

--- login.wssp-orig     2007-04-03 08:47:22.000000000 -0700
+++ login.wssp  2007-04-03 09:20:53.000000000 -0700
@@ -55,6 +55,9 @@
             <!--%%IF NOT(EXISTS(restoreSessionPage))-->
             <tr>
-               <td nowrap
class="externalField">%%HTML:STRING("LayoutTag")%%</TD>
-               <td><SELECT name=SessionSkin><OPTION value="*"
SELECTED><!--%%STRINGMENU NULL() IN skinNames DISPLAY
DICTIONARY("SkinNames")--></SELECT></td>
+               <td nowrap
class="externalField">%%HTML:STRING("LayoutTag")%%</TD>
+               <td><SELECT name=SessionSkin><OPTION value="*" SELECTED>
+                          <OPTION VALUE="Aquinox">Aquinox
(default)</OPTION>
+                          <OPTION VALUE="Simplex">Simplex</OPTION>
+                          </SELECT></td>
             </tr>
             <!--%%ENDIF-->

We simply remove the STRINGMENU WSSP command, and replace it by a static
list of the available skins, in HTML.

In the above example - it is worth noting that while the real default
Skin Layout in CGatePro was defined as "Simplex", the menu states the
default is "Aquinox". This was done intentionally to demonstrate the
difference between the actual preferences and the displayed ones. This
example is continued below.
View Full Article Add Comment

Modifying the users Settings page to limit the available skins 

Following is the patch syntax for modifying the settings.wssp page. This
page uses an "ENUMMENU" rather than a pure STRINGMENU WSSP function, so
the syntax is a little different, and dependent on static numeric values
assigned to each skin in the product:

--- settings.wssp-orig  2007-04-03 08:47:30.000000000 -0700
+++ settings.wssp       2007-04-03 09:25:28.000000000 -0700
@@ -38,5 +38,14 @@
        <tr>
           <td width="35%" nowrap
align="%%STRING("AlignEndCode")%%">%%HTML:STRING("LayoutTag")%%</td>
-           <td ><select class="FieldText"NAME=SkinName><!--%%ENUMMENU
settings.skinName DEFAULT defaultSettings.skinName IN skinNames DISPLAY
DICTIONARY("SkinNames")--></SELECT></td>
+           <td >
+                               <select class="FieldText" name="SkinName">
+                                 <!--%%IF SETTINGS("SkinName")-->
+                                 <option value="-1"  <!--%%IF
EQUALS(SETTINGS("SkinName") AND "default")-->   selected <!--%%ENDIF-->
Aquinox (default)</option>
+                                 <option value="6"  <!--%%IF
EQUALS(SETTINGS("SkinName") AND "Simplex")-->   selected <!--%%ENDIF-->
Simplex</option>
+                                 <!--%%ELSE-->
+                                 <option value="-1">Aquinox
(default)</option>
+                                 <option value="6">Simplex</option>
+                                 <!--%%ENDIF-->
+                  </SELECT></td>
        </tr>
         <tr>
View Full Article Add Comment

Modifying the WebGuide for Domain Administration 

Modifying the WebGuide for Domain Administration is actually quite
simple - each skin has a set of "admin*" pages in it. These are the
Domain Administration pages. So, for the default skin chosen (in our
example here, Simplex) modify the [Help] links to point at new custom
pages. Then, create those pages as desired.

In particular, there is a single file for the domain which must be
modified to modify the [Help] link:

admintophtml.wssi

This is an "include file" (hence the "i" in wssi), and gets included
into many other admin pages. Therefore, by just changing this one page,
it affects most or all of them.

A patch example of this change might be something as simple as this:

--- admintophtml.wssi-orig      2007-04-03 09:39:57.000000000 -0700
+++ admintophtml.wssi   2007-04-03 09:41:01.000000000 -0700
@@ -29,5 +29,5 @@
                <td align="%%STRING("AlignEndCode")%%" nowrap="nowrap"
class="helpLink">
                        <!--%%IF EXISTS(ExpertLevel) &
hasPreferences-->&nbsp;|&nbsp;<a
href="Preferences.html">%%HTML:TRANSLATE(ExpertLevel USING
DICTIONARY("ExpertLevels"))%%</a><!--%%ENDIF-->
-                       <!--%%IF EXISTS(INCLUDEARG(0))-->&nbsp;|&nbsp;<a
href="/Guide/%%INCLUDEARG(0)%%"
target="_blank">%%HTML:STRING("HelpTag")%%</a><!--%%ENDIF-->
+                       <!--%%IF EXISTS(INCLUDEARG(0))-->&nbsp;|&nbsp;<a
href="MyHelpPage.html"
target="_blank">%%HTML:STRING("HelpTag")%%</a><!--%%ENDIF-->
                </td>
                </tr></table></td></tr>

Where "MyHelpPage.html" can be any new/customized help page you create
there.
View Full Article Add Comment