by

Communigate Pro



  1. Communigate Pro Transact
  2. Communigate Pro Server

Product: CommuniGate Pro 7.0.2 Release Date: 3/18/2021 Download: In this release:New license key system introduced. CommuniGate Pro Version. The CommuniGate Pro version can be found on the 'Settings General Info' page of the web administration interface. Operating System. Configuration. Product(s). Products/Downloads that the ticket is dealing with. Message. Add Another Attachment.

Before you contact the CommuniGate Support Department, please:

  • consult with the How To and Help Me sections of the CommuniGate Pro manual.

Realtime Chat with Support
Ask your question online!

Basic Support

CommuniGate Systems provides the Basic and Pre-Sales support to all current and potential (trial) customers.

Communigate pro ccano

E-mail your questions to support@communigate.ru (24 hours, Monday-Sunday).

You can also call the support deparment at +49 30 2589 5018, Monday-Friday.

Please provide the following details: the CommuniGate Pro version, the platform it runs on, and the portions of the CommuniGate Pro Log displaying the problem. You may want to set some of the Log Level setting to ALL INFO in order to record detailed information into the Log.

Premium Support

The Premium packages add 24x7x365 telephone and IM support with various SLA options, as well as on-site support options.

Plants vs zombies free. Please contact sales@communigate.ru to purchase these packages.



  • Installation
You should download the CommuniGate Pro software either from the Stalker Web/FTP site, or from any authorized mirror site. Make sure you have the latest version of the software, and that the downloaded version is designed to work on the selected platform.
Install the Server following the instructions below, and then proceed with Initial Configuration.

Installation

On all systems, the CommuniGate Pro uses 2 directories (folders):
  • the application directory containing the Server application and supplementary files (as Web Interface page templates). Files in this folder are not modified when the system runs.
  • the base directory containing queued messages, account files, settings, and other server data.

Installing on a MS Windows 2000/NT/9x System

  • Use any 'unzip'-type tool to unpack the CGatePro-Win32-Intel-version.zip file. The tool should be able to use long file names.
  • Some 'unzip' applications have the Install option, use that option if available. If the Install option is not available, unpack the archive. The unpacked directory should contain the CommuniGate Pro application folder and the Installer.exe application. Launch the Installer.exe application.
  • If the CommuniGate Pro software is running, the Installer asks your permission to stop it.
  • The Installer asks you where to place the CommuniGate Pro application folder, and where to create the 'base' directory. If a previous version of CommuniGate Pro has been already installed, the Installer shows the locations used, and the Install button is renamed into the Update button.
  • Click the Install/Update button to copy the CommuniGate Pro software into the selected location. If the CommuniGate 'base' folder does not exist, the Installer creates an empty folder in the selected location.
  • The information about the selected locations is stored in the System Registry.
    Windows NT/2000
    The CommuniGate Pro Messaging Server (the CGStarter.exe application) is registered as a service that starts automatically when the system starts. This small application starts the CommuniGate Server itself, the CGServer.exe application. The Installer asks if you want to start the server now.

    Note:your should use the Services control panel to verify or change the Log On as name for the CommuniGate Pro service. That name should have the Act as part of the operating system Windows NT privilege. If the CommuniGate Pro Server does not have this privilege, not only it will fail to authenticate users using the Windows NT password system, but an attempt to use an incorrect password may cause the server to crash. This problem is fixed in the Windows NT Service Pack 4.

    Note:if your server should serve 100 accounts or more, check the description of the TIME_WAIT problem and follow the instructions to decrease the NT TIME_WAIT time interval.

    Windows 95/98
    The CommuniGate Pro (the CGServer.exe application) is added to the RunServices Registry key, so the server is started up when the system starts. Restart the Windows 9x system to start the server.

    Note:Unlike Windows 98, the Windows 95 system does not have the 'WinSock2' libarary installed. Download old version of find my friends on my macbook pro. Download this library (.dll) from the http://www.microsoft.com and install it before you try to launch the CommuniGate Pro Server.

  • Launch the Server and proceed with Initial Configuration.
You can also start the CommuniGate Pro server manually, as a 'console application', by launching the CGServer.exe file. If started without parameters, the Server creates the C:CommuniGatePro folder and uses it as its 'base' folder'. If you want to use any other location, use the --Base command line parameter:
CGServer.exe --Base D:OtherDirectory

Installing on a Sun Solaris System.

  • Log in as a super-user (root).
  • Unpack the CommuniGate Pro archive with the gtar command (or with the gunzip and tar commands):
    gunzip CGatePro-Solaris-version.tar.gz
    tar -xpf CGatePro-Solaris-version.tar
  • Install the CommuniGate Pro package:
    pkgadd -d .
    The CommuniGate Pro software will be installed in the /usr/local/sbin directory.
  • If your system was running sendmail or any other SMTP server, stop that server and remove that server start-up script from the /etc/rcn/ directory, so the system will not start that other SMTP server automatically.
  • If your system was running POP,IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.
  • The Installer creates a symbolic link /bin/cgmail for the command line mode mail program to use with the CommuniGate Pro system.
  • The Installer creates a startup script /etc/init.d/STLKCGPro, and the symbolic link /etc/rc2.d/S88CommuniGate for that script.
  • The Installer creates the 'base directory' /var/CommuniGate and the Server uses it by default. You can move the 'base directory' to any other location. In this case, open the /etc/init.d/STLKCGPro file and update it.
  • Restart the system or launch the start-up script manually:
    /etc/init.d/STLKCGPro start
  • Proceed with Initial Configuration.

Installing on a Linux System.

  • Make sure you are running Linux kernel 2.0.34 or better.
  • Log in as a super-user (root).
    • Using the Red Hat Package Manager (the .rpm file):
      rpm -i CGatePro-Linux-version.rpm
    • Using other systems (the .tgz file):
      tar -xzf CGatePro-Linux-version.tgz
      cd CGateProSoftware
      sh install.sh
    The CommuniGate Pro software will be installed in the /usr/local/sbin directory.
  • The installer will create the /etc/rc.d/init.d/CommuniGate startup script. To let the CommuniGate Pro server start and stop automatically when the system starts up and shuts down, add startup file links to the /etc/rcn directories. You can:
    • use the Run Level Manager
    • use chkconfig:
      /sbin/chkconfig CommuniGate on
    • use shell commands:
      cd /etc/rc.d/rc3.d
      ln -s ./init.d/CommuniGate S80CommuniGate
      cd /etc/rc.d/rc1.d
      ln -s ./init.d/CommuniGate K30CommuniGate
    Use the same methods to disable other mail servers (such as sendmail).
  • If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file (or put the hash sign (#) into the first position of those lines).
  • The Installer renames the /bin/mail program into the /bin/LegacyMail. If you decide to uninstall the CommuniGate Pro system, the legacy mail program will be renamed back to /bin/mail.
  • The Installer creates the new /bin/mail application - a drop-in substitution for the legacy mail program.
  • The Installer creates the 'base directory' /var/CommuniGate and the Server uses it by default. You can move the 'base directory' to any other location. In this case, open the /etc/rc.d/init.d/CommuniGate file and update it.
  • Restart the system or launch the start-up script manually:
    /etc/rc.d/init.d/CommuniGate start
  • Proceed with Initial Configuration.
Note: Under Linux, each thread in a multi-threaded application is seen asa 'process' when you use the ps and top system utilities. As a result, youmay see 30+ CGServer 'processes' when the server is just started, and moreafter it has been actively used. All those 'processes' are actually CommuniGate Pro Serverthreads, and they share all their resources - VRAM, File Descriptors, etc.

Installing on a MacOS X Server (Rhapsody) System.

  • Log in as a super-user (root).
  • Unpack the CommuniGate Pro archive using any uncompressing utility, or use the shell (Terminal.app) gnutar command:
    gnutar xzpf CGatePro-MacOSX-version.tgz
    the CommuniGate.pkg package directory will be created in the current directory.
  • Install the software by double-clicking the CommuniGate.pkg icon.
    The CommuniGate Pro software will be installed in the /Local/Servers directory.
  • Note: The installer will create a file /etc/startup/1950_CommuniGate, so the CommuniGate Pro Server will auto-start when the System starts.
  • Note: The installer will disable the file /etc/startup/1900_Mail used to auto-start sendmail on your system.
  • If your system was running POP,IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.
  • The Installer renames the /usr/bin/mail program into the /usr/bin/LegacyMail. If you decide to uninstall the CommuniGate Pro system, the legacy mail program will be renamed back to /usr/bin/mail.
  • The Installer creates the new /usr/bin/mail application - a drop-in substitution for the legacy mail program.
  • The Installer creates the 'base directory' /Local/CommuniGate and the Server uses it by default. You can move the 'base directory' to any other location. In this case, open the /etc/startup/1950_CommuniGate file and update it.
  • Restart the system or launch the startup script manually:
    /etc/startup/1950_CommuniGate
  • Proceed with Initial Configuration.

Installing on a FreeBSD System.

  • Make sure you are running FreeBSD version 3.0 or better.
  • Log in as a super-user (root).
  • Install the CommuniGate Pro package:
    pkg_add CGatePro-FreeBSD-version.tgz
    The CommuniGate Pro software will be installed in the /usr/local/sbin directory.
  • If your system was running sendmail or any other SMTP server, stop that server and modify the OS start-up scripts so the system will not start that other SMTP server automatically.
  • If your system was running POP,IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.
  • The Installer creates a script /usr/local/etc/rc.d/CommuniGate.sh, so the CommuniGate Pro Server is started automatically when the FreeBSD system starts.
  • The Installer creates a symbolic link /bin/cgmail for the command line mode mail program to use with the CommuniGate Pro system.
  • The Installer creates the 'base directory' /var/CommuniGate and the Server uses it by default. You can move the 'base directory' to any other location. In this case, open the start-up script file and update it.
  • Restart the system or launch the start-up script manually:
    /usr/local/etc/rc.d/CommuniGate.sh start
  • Proceed with Initial Configuration.

Installing on a BSDI BSD/OS System.

  • Make sure you are running BSD/OS version 4.0.1 or better.
  • Log in as a super-user (root).
  • Unpack the CommuniGate Pro archive with the gunzip and tar commands:
    gunzip CGatePro-BSDI-version.tar.gz
    tar -xpf CGatePro-BSDI-version.tar
  • Install the CommuniGate Pro package:
    installsw -c /../CGatePro (use the full path to the CGatePro directory)
    The CommuniGate Pro software will be installed in the /usr/local/sbin directory.
  • If your system was running POP,IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.
  • If your system was running sendmail or other mail transfer agent, remove the lines describing those servers from the /etc/rc file.
  • The Installer adds a reference to the CommuniGate Pro startup script to the /etc/rc.local file, so the CommuniGate Pro Server is started automatically when the BSDI BSD/OS system starts.
  • The Installer creates a symbolic link /usr/bin/cgmail for the command line mode mail program to use with the CommuniGate Pro system.
  • The Installer creates the 'base directory' /var/CommuniGate and the Server uses it by default. You can move the 'base directory' to any other location. In this case, open the start-up script file (/usr/local/sbin/CommuniGate/Startup) and update it.
  • Restart the system or launch the start-up script manually:
    /usr/local/sbin/CommuniGate/Startup start
  • Proceed with Initial Configuration.

Installing on an AIX System.

  • Make sure you are using the AIX System version 4.3 or better.
  • Make sure the
  • Log in as a super-user (root).
  • Unpack the CommuniGate Pro archive with the gunzip and tar commands:
    compress -d CGatePro-AIX-version.bff.Z
  • Use either the installp command, or the smit utility, or the smitty utility to install the software.
  • The installation script creates a startup script /etc/rc.cgpro and updates the /etc/inittab file to start the CommuniGate Pro server on run level 2.
  • The startup script creates the 'base directory' /var/CommuniGate and the Server uses this directory by default. You can move the 'base directory' to any other location. In this case, open the /etc/rc.cgpro script file and update it.
  • If your system was running sendmail or any other SMTP server, stop that server and modify the OS start-up scripts so the system will not start that other SMTP server automatically.
  • If your system was running POP,IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.
  • Restart the system or launch the start-up script manually:
    /etc/rc.cgpro start
  • Proceed with Initial Configuration.

Installing on an HP/UX System.

  • Make sure the HP/UX version 11 is installed.
  • Apply all patches availble for HP-UX 11.00, or, at least the threads-related ones.
  • Set the kernel parameters as follows:
    • set the maxdsize kernel parameter to 50MB or more.
    • set the max_thread_proc (max number of threads per process) to 128 or more.
    • set the ncallout parameter (max number of pending timeouts) to 128 or more.
    • set the maxfiles parameter to 512 or more.
  • Log in as a super-user (root).
  • Unpack the CommuniGate Pro archive with the gunzip and tar commands:
    gunzip -xzpf CGatePro-HPUX-HPPA-version.tar.gz
    tar -xf CGatePro-HPUX-HPPA-version.tar
    The CGatePro directory should appear in the current directory.
  • Install the CommuniGate Pro package:
    swinstall -s /.../CGatePro (you should use the absolute path for the unpacked CGatePro directory)
    The CommuniGate Pro software will be installed in the /opt/CommuniGate directory.
  • If your system was running sendmail or any other SMTP server, stop that server and modify the OS start-up scripts so the system will not start that other SMTP server automatically.
  • If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.
  • The server startup script is created as /sbin/init.d/CommuniGate and its symbolic links /sbin/rc2.d/S80CommuniGate and /sbin/rc1.d/K80CommuniGate are automatically created.
  • The Server uses /var/CommuniGate as its 'base directory' by default. You can move the 'base directory' to any other location. In this case, open the /sbin/init.d/CommuniGate script file and update its BASEDIRECTORY parameter.
  • The symbolic link /bin/cgmail is created for the CommuniGate 'mail' program.
  • Restart the system or launch the start-up script manually:
    /sbin/init.d/CommuniGate start
  • Proceed with Initial Configuration.

Installing on a Tru64 (Digital Unix) System.

  • Make sure the Tru64 version 4.0e with the update package #2 (Sept/98) or better is installed.
  • Log in as a super-user (root).
  • Unpack the CommuniGate Pro archive with the gtar command (or with the gunzip and tar commands):
    gtar -xzf CGatePro-Tru64-platform-version.tar.gz.
  • Install the CommuniGate Pro package:
    setld -l .
    The CommuniGate Pro software will be installed in the /usr/opt/ directory.
  • If your system was running sendmail or any other SMTP server, stop that server and modify the OS start-up scripts so the system will not start that other SMTP server automatically.
  • If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.
  • The Installer creates the symbolic link /sbin/init.d/CommuniGate for the server startup script. Use the system utilities to include this script into the list of automatically started services.
  • The Installer creates the 'base directory' /var/CommuniGate and the Server uses this directory by default. You can move the 'base directory' to any other location. In this case, open the /usr/opt/CGPxxx/startup script file and update it.
  • Restart the system or launch the start-up script manually:
    /sbin/init.d/CommuniGate start
  • Proceed with Initial Configuration.

Installing on an SGI IRIX System.

  • Make sure you are using the IRIX System version 6.5 or better.
  • Log in as a super-user (root).
  • Install the CommuniGate Pro package:
    inst -f CGatePro-IRIX-MIPS-version.tardist
    or
    swmgr -f CGatePro-IRIX-MIPS-version.tardist
    The CommuniGate Pro software will be installed in the /opt/CommuniGate directory.
  • If your system was running POP, IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.
  • If your system was running sendmail, use the chkconfig to disable it:
    /sbin/chkconfig sendmail off
    The CommuniGate Pro installation script writes the word off into the /etc/config/sendmail file.
  • The installation script creates a startup script /etc/init.d/CommuniGate, and the symbolic links /etc/rc2.d/S75CommuniGate and /etc/rc0.d/K05CommuniGate for that script.
  • The installation script creates the 'base directory' /var/CommuniGate and the Server uses this directory by default. You can move the 'base directory' to any other location. In this case, open the /etc/init.d/CommuniGate script file and update it.
  • Restart the system or launch the start-up script manually:
    /etc/init.d/CommuniGate start
  • Proceed with Initial Configuration.

Installing on an SCO UnixWare System.

  • Make sure that UnixWare 7.1 or better is installed.
  • Log in as a super-user (root).
  • Unpack the CommuniGate Pro archive with the gunzip and tar commands):
    gunzip CGatePro-UnixWare-version.tar.gz
    tar -xpf CGatePro-UnixWare-version.tar
  • Install the CommuniGate Pro package:
    pkgadd -d `pwd`
    The CommuniGate Pro software will be installed in the /usr/local/sbin directory.
  • If your system was running sendmail or any other SMTP server, stop that server and modify the OS start-up scripts so the system will not start that other SMTP server automatically.
  • If your system was running POP,IMAP, or poppwd servers, remove the lines describing those servers from the /etc/inetd.conf file.
  • The Installer creates a symbolic link /bin/cgmail for the command line mode mail program to use with the CommuniGate Pro system.
  • The Installer creates a startup script /etc/init.d/STLKCGPro, and the symbolic link /etc/rc2.d/S88CommuniGate for that script.
  • The Installer creates the 'base directory' /var/CommuniGate and the Server uses it by default. You can move the 'base directory' to any other location. In this case, open the /etc/init.d/STLKCGPro file and update it.
  • Restart the system or launch the start-up script manually:
    /etc/init.d/STLKCGPro start
  • Proceed with Initial Configuration.
    Note: UnixWare 7.1.0 has a very small per process limit for open listeners. To avoid the problem, the CommuniGate Pro ACAP server is disabled by default, and the LDAP server does not create a listener to accept secure connections. Do not try to create additional listeners before this limit is increased.

Installing on an IBM OS/400 System.

  • Make sure you have OS/400 version V4R4M0 or later.
  • Decide where to place the CommuniGate Pro base directory:
    • The files used by the CommuniGate Pro Software must reside in a thread-safe file system. Only the following file systems are thread-safe:
      / (root), QOpenSys, QNTC, QSYS.LIB, QOPT, QLANSrv, user-defined.
      For details see the Integrated File System concepts book in the AS/400 Information Center.
    • If you need to have case-sensitive mailbox names you should place the CommuniGate Pro base directory into a case-sensitive file system. The QOpenSys file system is case-sensitive. User-defined file systems can be created as case-sensitive, too. The Installer program allows you to create a case-sensitive file system for the CommuniGate Pro base directory.
  • If your OS/400 system was running SMTP, POP, IMAP, ACAP, or poppwd servers, stop those servers, and modify the start-up defaults, so the system will not start those legacy servers automatically. You can change the start-up defaults using the AS400 Operations Navigator.
  • Make sure your OS/400 system has its TCP/IP stack active and the FTP server running.
  • Download the current CommuniGatePro OS400 version (the CGatePro-OS400-AS400.exe file) to a computer running MS Windows OS and connected (via a TCP/IP network) to your OS/400 system.
  • Run the CGatePro-OS400-AS400.exe installer on that MS Windows system. Follow the instructions the installer program provides.
  • On the OS/400 system, start the CommuniGate Pro Server job: QGPL/STRCGSRV. The CGSERVER job will start in the QSYSWRK subsystem. You may want to create an autostart job entry for the CommuniGate Pro Server, or run it in a specially created subsystem. For details see OS/400 Work Management book in AS/400 Online Libary.
  • Note: the source code of the STRCGSRV and ENDCGSRV commands is included into the CGatePro distribution set, so you can modify these commands to meet your needs.
  • Proceed with Initial Configuration.

Initial Configuration

  • Restart the system or start the CommuniGate Pro Server manually.
  • On a Unix system: use either the super-user account or any account included into the 'mail' group to access the CommuniGate Pro files in the 'base directory' (by default that directory is /Local/CommuniGate for MacOS X, /var/CommuniGate/ for other Unix systems).
  • On a Unix system, open the file:
    {CGateBase}/Accounts/postmaster.macnt/account.settings
    On a MS Windows system, open the file:
    {CGateBase}Accountspostmaster.macntaccount.settings
    On an OS/400 system, use any ASCII-capable text editor to open the file:
    {CGateBase}/Accounts/postmaster.macnt/account.settings
    This text file contains a random password assigned to the postmaster account. Remember this password.
  • Connect to the server with any Web browser, using the port number 8010. In your browser, type the following URL:
    http://your.server.domain:8010
    where your.server.domain is the domain name or the IP address of the computer running the CommuniGate Pro server.
  • To open Setup, Accounts, Monitor, and Master configuration pages (realms), use the postmaster username and the password you have seen in the postmaster account.settings file.
  • Check the General settings. Make sure the Server domain name is correct and the date/time settings of the Server operating system are set properly.
  • Enter the Accounts page and register your users.
You may want to check the Migration section to planyour CommuniGate Pro deployment process.

Upgrading to a Newer Version

When you upgrade to a new version, the files in the application directory are substituted with the new files.

The base directory and all its files are not modified when you update the CommuniGate Pro Server software, so all accounts, mailboxes, messages, settings, Personal Web Sites, customized WebUser and WebAdmin files stay and continue to work with the new version of the Server.

Note: if you chose to manually modify WebUser and/or WebAdmin files right in the application directory, then you should save them before updating. If you properly placed your customized versions of WebUser and/or WebAdmin files into the Domain Webuser/WebAdmin directories, these customized files are not removed when you upgrade the Server software.

To upgrade:

  • download the new version of the CommuniGate Pro Software
  • stop the CommuniGate Pro Server
  • [optional] remove the previous version of the software using the same installation utility you used to install the software (the base directory will not be removed)
  • install the new version of the CommuniGate Pro Software
  • start the CommuniGate Pro Server.

Moving to a New Hardware Server

You may want to move your CommuniGate Pro server to a different computer - running the same or a different OS. All your module settings, account and domain settings, mailboxes, and other data can be preserved.

CommuniGate Pro keeps all its data in the base directory. This is the only directory you need to copy to your new server computer.

CommuniGate Pro uses the same file formats on all hardware and software (OS) platforms, so usually you can just pack the entire CommuniGate Pro base directory into an archive file (using tar and gzip on Unix systems, zip on MS Windows systems), and unpack the archive on the new server computer.

Communigate Pro Transact

Additional processing is needed when you move the CommuniGate Pro Server from a computer running any MS Windows operating system to a computer running any flavor of Unix, or vice versa. CommuniGate Pro files are text files, and text files on MS Windows and Unix have different EOL (end of line) symbols: CR-LF (return - linefeed) on MS Windows and bare LF (linefeed) symbol on Unix systems. To copy files properly, you may want to use any FTP software to copy files between those systems: when an FTP client is instructed to transfer files in the ASCII mode, it properly converts EOL symbols.
Note: CommuniGate Pro base directory can contain non-text (binary) files in the WebUser and WebAdmin directories inside the Account and Domains subdirectories - graphic files used in the customized WebUser and WebAdmin Interfaces. Binary files can also be stored in Personal Web Sites - account.web directories inside the account directories. When you move a CommuniGate Pro base directory between systems using different EOL conventions, check that those binary files are copied in the BINARY mode (i.e. without EOL recoding).

Communigate Pro Server

If the new server computer is running a Unix system, check that the copied directory and all its files and subdirectories have the same access rights as they had on the old system.

After the CommuniGate Pro base directory is copied, download and install the proper version of the CommuniGate Pro Server on the new server computer. There is no need to copy the content of application directory from the old server computer, even if both new and old computers are running the same operating system.

Download gimp mac free. Check that the newly installed copy of the CommuniGate Pro Server (its startup script, if any) is configured to use the copied base directory, and then start the CommuniGate Pro Server on the new computer. Use the WebAdmin Interface to modify the computer-related settings on the new server. For example, you may need to update the Client IP Addresses table or re-assign IP addresses to CommuniGate Pro Domains.

CommuniGate® Pro Guide. Copyright © 1998-2000, Stalker Software, Inc.