CommuniGate Pro Server: Accounts

To create a new Account, type a new Account name into the field on the right side of the Create Account button and click that button.

Use the pop-up menu to specify the Account type:

MultiMailbox: A folder-type Account that can contain several mailboxes of various types. The INBOX mailbox is automatically created within the new Account. All incoming mail is stored in the INBOX mailbox by default. The user can create additional mailboxes using any IMAP client software, or using the CommuniGate Pro Web E-mail Interface.
Text Mailbox, MailDir Mailbox, ...

By default, the Account name becomes the person's E-mail name, so Account names should contain only letters, digits, dash and point (dot) symbol - some mail systems cannot send mail to E-mail addresses containing other symbols.

external INBOX: Select this option if you want the new Account INBOX to be created as an external mailbox, so new Account can be used with legacy local mailers. This option is enabled only if the external mailbox location is specified in the Domain Settings.

Click the Create Account button. When a new Account is created, its name appears in the Accounts list. The Server automatically displays the Settings page for the new Account.

The Settings of a newly created Account are automatically set to the Account Template values.

You can create several Accounts at once, by preparing an Account List file and using the Import option.

To specify Account Settings, click the Account name link in the Accounts list. The Account Settings page appears.

Real Name: This field is used to specify the real-life user name. The Server uses this information to compose the default 'From' address in Web Mailer.
additional System fields

The modified values of the Real Name and additional fields are updated in the Directory if the Domain has the Directory Integration setting set to Keep In Sync.

After the Account Settings are modified, click the Update button.

Authentication Methods

Use the Authentication panel to specify the Account authentication methods.

Authentication

Secure Only:

CommuniGate Password:
Password Modification:
Password Encryption:
Password Recovery:

OS UserName:

	*

OS Password:

Kerberos:
Certificate:
External Password:

Alt RADIUS Password:
Alt SIP Password:

Last Failed Login:

12:09:28AM [64.173.55.167]

CommuniGate Password

If the CommuniGate Password, OS Password, Kerberos, Certificate, and External Authentication options are disabled, the user will not be able to access the Account.

Any Authentication setting can be set to the default value, in this case the setting value is taken from the Domain Default Account Settings or the Server-wide or Cluster-wide Default Account Settings.

Enabled Services

There is a set of settings that specify which CommuniGate Pro services can be used with the Account:

Enabled Services
Default	Mail	Relay	Signal	Mobile	TLS	POP	IMAP	MAPI
	AirSync	SIP	XMPP	WebMail	XIMSS	FTP	ACAP	PWD
	LDAP	RADIUS	S/MIME	WebCAL	WebSite	PBX	HTTP

The Server checks the Account and the Account Domain settings. Only if the service is enabled for both the Account and the Account Domain, that service can be used with this Account.

See the Domains Settings section for more details.

If you select the default option, the Enabled Services for this Account are defined using Domain Default Account Settings or the global Default Account Settings.

Please note a difference between the Default Account settings and the Enabled Services specified for the domain: while you can override the Default Account Settings for some Account by explicitly specifying the enabled services for that Account, you cannot override the Enabled Services specified for the Domain. If the Default Account Settings disable POP and IMAP access, you can explicitly enable POP and IMAP access for a particular account. But if POP and IMAP access is disabled in the Domain Settings, no Account in that Domain can be accessed via these protocols.

Mail Settings

Mail
Mail Storage Limit:	Used:
Mailbox Limit:	Used:	31
Message Size Limit:	Outgoing Size Limit:
New Mailbox Format:	Non-Mail Folders visible via IMAP:

Mail Storage Limit: This option is used to specify the maximum total size of the all Account mailboxes. If a new incoming message cannot be stored in an Account, because the Account size would exceed the specified limit, the message is rejected and the message sender receives an error report.
The current Mail Storage usage value is shown as a button, if the page is viewed by a System Administrator. By clicking this button you can re-calculate the usage storage counter if that counter was de-synchronized.
Mailbox Limit: This option is used to specify the maximum number of Mailboxes that can be created in this Account.
Message Size Limit: This option is used to specify the maximum size of an E-mail Message that can be stored in any Account Mailbox.
Outgoing Size Limit: This option is used to specify the maximum size of an E-mail Message that can be composed and submitted by this Account.

Mail
Delay New Mail if:	% full
Send Alerts if:	% full
Send Notice if:	% full

Delay New Mail

To disable these options, set their values to 101%.

Mail

Used

Allowed Mail Rules:

7

RPOP modifications:

3

Accepts Mail to "all":

Add Trailer to Sent Mail:

Allowed Mail Rules

Any of these Settings can be set to the default value, in this case the setting value is taken from the domain Default Account Settings or the global Default Account Settings.

Signaling Settings

Calls
Registered Devices:	Used:	2
Roster Limit:	Used:	7
Allowed Call Rules:	Used:	10
Concurrent Calls:	Used:	0
Call Logs:	Call Info:

Registered Devices: This setting specifies the maximum number of "Contacts" (devices) the Server can register for this Account.
Roster Limit: This setting specifies the maximum number of Roster elements ("Buddies") for this Account.
Allowed Call Rules

File Storage Settings

Files

Used

Default file for HTTP:

	default.html

File Storage Limit

WebUser Interface Settings

Hidden Skins

Each Account can have zero, one, or more Telephone (PSTN) numbers assigned to it.

The Server maintains a global list of all Telephone Numbers assigned to all Accounts in all Domains.

Telephone numbers should be specified in the E.164 format: +country_code area_code local_number. The number should contain only digits and it can start with the plus (+) symbol.

Note:

Only when a Signal (a call) comes to your CommuniGate Pro Server or Cluster, these Telephone Number mappings take effect.
An assigned Telephone Number should be registered with one of the PSTN Gateways. When a PSTN call is made to that number, the Gateway should receive the call and it should direct the call to your CommuniGate Pro Server via a VoIP protocol (such as SIP).
When a call made to a PSTN number arrives to the Server, it is usually still directed to the dialed PSTN number, and not to the user Account name. The Server uses its global list of assigned Telephone Numbers to route the call to the proper Account.
Users may want to register their assigned Telephone Numbers with one of the global ENUM services.
If a Telephone number is linked to a CommuniGate Pro Aomain using such a service, VoIP calls made by users of all VoIP systems employing that ENUM service will be routed to the CommuniGate Pro Account directly, via the Internel, bypassing PSTN.

See the PSTN section for more details.

The Account owner can grant certain rights to other users: a right to access certain Mailboxes, a right to control telephony features, etc.

Each element of the Access Control List contains a name and a set of access rights granted to that name.

An ACL element name can be:

anyone: This ACL element specifies the access rights granted to everybody (all authenticated accounts).
anyone@: This ACL element specifies the access rights granted to all Accounts in the same CommuniGate Pro Domain.
anyone@domainName: This ACL element specifies the access rights granted to all Accounts in the CommuniGate Pro domainName Domain. The domainName should be the real Domain name, and not a Domain Alias name.
accountName: This ACL element specifies the access rights granted to the accountName Account user in the same CommuniGate Pro Domain. The accountName should be a real Account name, and not an Account Alias or a Forwarder.
accountName@domainName: This ACL element specifies the access rights granted to an Account user in a different CommuniGate Pro Domain. The domainName should be the real Domain name, and not a Domain Alias name.
#groupName: This ACL element specifies the access rights granted to all members of the groupName Group (in the same Domain).
#groupName@domainName: This ACL element specifies the access rights granted to all members of the groupName Group in a different CommuniGate Pro Domain. The domainName should be the real Domain name, and not a Domain Alias name.

An ACL element name can have a + or a - prefix.

Account owners always have all access rights to all objects (Mailboxes, functions) in their own Accounts.

For any other someaccount Account, the effective access rights are checked.

The effective access rights are calculated in several steps:

If there is an ACL element for the someaccount name (without a + or a - prefix), then the Access right specified in that ACL element are used as the effective access rights.
Otherwise
All ACL elements without a + or a - prefix and matching the someaccount name are merged to form the "direct" access rights.
All ACL elements with the - prefix and matching the someaccount name are merged to form the "removed" access rights.
All ACL elements with the + prefix and matching the someaccount name are merged to form the "added" access rights.
The "removed" access rights are removed from the "direct" access rights.
The "added" access rights are merged with the "direct" access rights.
The resulting "direct" access rights are used as the effective access rights.

When granting access rights, the real Account names, not Account Aliases should be used. If an Account j.smith has two aliases john.smith and jonny, the access rights should be granted to the name j.smith.

Examples:

Grant the Lookup, Select, and Seen access rights to all users in the same Domain, excluding the user John, who should have only the Lookup right, and the user Susan who should have the Lookup, Select, Seen, and Delete rights:

`anyone@`		Lookup, Select, Seen
`-john`		Select, Seen
`+susan`		Delete

Grant the Lookup, Select, and Seen access rights to all users in a different company2.com Domain, excluding the user john@company2.com who should have no access rights, and grant the Lookup, Select, and Delete rights to the user susan in a yet another company3.com Domain.

`anyone@company2.com`		Lookup, Select, Seen
`-john@company2.com`		Lookup, Select, Seen
`susan@company3.com`		Lookup, Select, Delete

The Access Control Lists can be set and modified using the WebUser Interface, a XIMSS, a MAPI, or a decent IMAP client.

The CommuniGate Pro Server maintains an Access Control List (ACL) for every Account.

The Access Control Lists are used to control what other users can do with this Account.

A Server Administrator with the All Users access right has all access rights to all Server or Cluster Accounts.

The Account owner can grant certain limited access rights to other users, controlled with a Access Control List.

The following Account access rights are supported:

c (CreateMailbox): If you grant a user the CreateMailbox access right, that user will be able to create Mailboxes on the "top" of your Account (i.e. Mailboxes that are not sub-Mailboxes of existing Mailboxes in your Account).
j (CallControl): If you grant a user the CallControl access right, that user will be able to access the information about your real-time communications.
This information includes the data about Signal objects handling your incoming calls, and it can be used to intercept your incoming calls ("call pick-up").

The Account Access Control Lists can be set and modified using the WebUser Interface, a XIMSS, or a MAPI client.

Every CommuniGate Pro Mailing List has an owner - an Account in the main or one of the secondary Domains. To create a Mailing List, you should create the Owner Account first. For each list, the Mailing List manager creates several mailboxes inside the owner Account, so the owner Account should be of the MultiMailbox type.

Mailing Lists
Name	Subscribers
RD-List	1025

To create a mailing list, type the list name and click the Create List button. To modify the list settings, to rename and remove the mailing lists use the links to the Mailing List Settings pages.

If you are a Domain Administrator, you should have the Can Create Mailing Lists Access Right to create Mailing Lists in your Domain.

If you want to remove an Account, open its Settings page, and click the Remove Account button. The confirmation page should appear.

If you confirm the action, the selected Account, all its Mailboxes, Settings, and other Account-related data files will be permanently removed from the Server disks.

The Account Aliases and all Mailing List owned by this Account will be removed, too.

You cannot remove an Account when it is in use.

If you are a Domain Administrator, you should have the Can Create Accounts Access Right to remove Accounts from your Domain.

An Account setting can have the default value. In this case the actual setting value is taken from the Default Account Settings for the Account Domain.
You can modify the Default Account Setting values by clicking the Account Defaults link on any Domain administration page of the WebAdmin Interface.

The Default Account Settings page resembles a regular Account Settings page.

The Domain Default Account Settings themselves can be assigned the default value.
In this case the setting value is retrieved from the Server-wide or Cluster-wide Default Account Settings.
You can modify the server-wide Default Account Settings by clicking the Account Defaults link on the Domains (Domain List) page.

A Dynamic Cluster installation maintains separate server-wide Default Account Settings for all Accounts in non-Shared (Local) Domains, and cluster-wide Default Account Settings for all Accounts in the Shared Domains. In the Cluster environment, the Default Account Settings page displays links that allow you to switch between the Server-wide and Cluster-wide Default Settings.

Settings

Example:

The global (Server)	Default Account Settings:	`Storage Limit = 10Mbytes`
The `company.dom`	Default Account Settings:	`Storage Limit = 30Mbytes`
The `client1.dom`	Default Account Settings:	`Storage Limit = default`

Now:

If you create an Account in any Domain, and set its Storage Limit to some value, that value will be used.
If you create an Account in the company.dom Domain, and set its Storage Limit value to default, the Account will be able to keep up to 30Mbytes of mail (the Default Account Setting for that Domain).
If you create an Account in the client1.dom Domain, and set its Storage Limit value to default, the Account will be able to keep up to 10Mbytes of mail (the global Default Account Setting for the Server).

When you serve many Accounts, you should try to specify most of the setting values as default, so you can easily change those settings for all Accounts. If some Account should be treated differently, you should explicitly specify the required setting value for that Account.

A Class of Service is an additional named Default Account Settings set. You can have several sets within each Domain, and you can specify a set to use for each Account, so Accounts in the same Domain can have different Default Settings.

To create a new Class of Service, use the WebAdmin Interface to open the Account Defaults page (a Domain one, a Server-wide, or a Cluster-wide one).

If you are a Server Administrator, or a Domain Administrators with the ServiceClasses Access Right, you can create additional Classes of Service:

Enter the new Class of Service name and click the Create Class of Service button. A new Class of Service will be created.

The Account Defaults page lists all created Classes of Service:

Classes of Service
FreeUser	Basic
Premium	Business

To open the Class of Service settings, click its name. The Class of Service settings page is the same as the Account Defaults page.

Account Defaults can be viewed as an unnamed Class of Service.

If you are a Server Administrator, or a Domain Administrators with the ServiceClasses Access Right, you can rename or remove Classes of Service. Use the WebAdmin Interface to open the Class of Service page, and scroll to the bottom of the page:

When there is at least one Class of Service created on the Domain or Server/Cluster level, the Account Settings page includes the Class of Service setting. If you are a Server Administrator, or a Domain Administrators with the ServiceClass Access Right, you can modify this setting:

When an Account Class of Service setting is not empty, the following algorithm is used to retrieve an Account settings:

If the Account has a setting value explicitly assigned, that value is used.
If the Domain has a Class of Service with the specified name, and that Class of Service settings contain a setting value, that value is used.
If the Server-wide (a Cluster-wide for Accounts in shared Domains) has a Class of Service with the specified name, and that Class of Service settings contain a setting value, that value is used.
Finally, the Server-wide (a Cluster-wide for Accounts in shared Domains) Account Default settings are used to retrieve the setting value.

You can create a Domain Class of Service with the same name as a Server-wide (or Cluster-wide) Class of Service to override some of its settings.

When you need to create many Accounts, you may want to specify some non-default setting for all new Accounts. Each Domain has its own Account Template, and you can modify it by clicking the Template link on the Account List page.

The Accounts Template page resembles a regular Account Settings page.

All the settings set there will be copied to all newly created Accounts in this domain.

Note: The Default Account Settings and Account Template are quite different. The Account Template is used only when an Account is being created. All template settings with non-default values are copied to the new Account settings. If you modify the template settings after an Account has been created, those Account settings will not change.

Besides the initial, non-Default setting values, the Account Template can be used to instruct the Server to create additional Mailboxes in each new Account (by default only the INBOX Mailbox is created), to subscribe the Account to certain Mailboxes, and to create Mailbox Aliases in all newly created Accounts.

Enter a name into the empty field to add a Mailbox name to the list.

For non-mail mailboxes, specify the Mailbox Class from the pop-up menu.
If you select the Lock checkbox, it will be impossible to delete or rename the created Mailbox.

In this sample, when a new multi-mailbox Account is created in this Domain, the mail Mailboxes Sent and Drafts, and the calendar Mailbox Calendar will be created in that Account, along with the INBOX Mailbox.
The Account users will not be able to delete or rename the Calendar Mailbox.

See the Mailboxes section to learn about Mailbox Subsciptions.

Creating initial non-empty subscription:

simplifies the initial set-up of some client mailers that can access only those Account Mailboxes that are included into the Mailbox Subscription list;
helps new users to subscribe to public mailboxes containing administrative information, news, etc.

See the Mailboxes section to learn about Mailbox Aliases.

Specifying a non-empty list of Mailbox Aliases simplifies the initial set-up for Microsoft Outlook users that need access to public Mailbox and other Foreign mailboxes, but cannot use their mailers to access foreign Mailboxes directly.

Greeting E-mail
From: Server Postmaster <postmaster@communigate.com> To: New Subscriber <^A@^D> Subject: Welcome to our wonderful server! MIME-Version:1.0 Content-Type: text/plain Dear ^E <^A@^D>, We are happy to see you with us! If you ever have any problem with our service, please send e-mail to: support@^D. The support team.

This field can contain a mail message in the RFC822 format. If this field is not empty, then the specified message is stored in the INBOX mailbox of every newly created Account.

The text can contain the following macro combinations, replaced with the newly created Account data:

^A - the newly created Account name.
^D - the Domain name.
^E - the newly created Account Real Name.

The Date: header field is automatically added to the stored messages.

The message text can start with a [charsetName] prefix, then the text will be converted from UTF-8 to the specified character set. Specify the Content-Type header field with the proper the charset= parameter:

Greeting E-mail
[ISO-8859-1] From: Server Postmaster <postmaster@communigate.com> To: New Subscriber <^A@^D> Subject: Bienvenue à notre serveur merveilleux! MIME-Version:1.0 Content-Type: text/plain; charset=ISO-8859-1 Cher Client, Nous sommes heureux de vous voir avec nous!

Templates can be used to generate an initial default Web (HTML) page in the File Storage for all newly created Accounts:

This field can contain an HTML text. If this field is not empty, then the specified text is stored as the Default Web Page file in the File Storage of each newly created Account.

The built-in Account Loader allows the administrator to register sets of users. The user names and Account attributes should be placed into a tab-delimited text file on the administrator (client) computer, and that file should be uploaded to the server using the Import field.

Click the browse button to select a file on your local system, and then click the Import Accounts button to create Accounts listed in the selected file.

Below is a sample IMPORT file:

Name Type Ignore Storage Aliases

johnd MultiMailbox sales dept 50M

susan MultiMailbox mgmnt 10M susan.s,susan_smith

sales MultiMailbox dummy 30M

info MultiMailbox dummy 50M help

Note: The import file must be prepared on the client computer (on the computer you use to run your browser). The browser allows you to upload files from disks connected to that computer, not to the CommuniGate Pro Server computer.

Note: When using Netscape and some other Unix browsers, make sure that the file name ends with the .txt suffix - otherwise the browser won't upload the file as a text one, and the file will be ignored.

Note: The MacOS 9.x versions of the Microsoft Internet Explorer upload Macintosh files in the encoded x-macbinary format if the file contains a resource fork. Most text files created with Macintosh text editor applications contain resource forks that keep the information about the file fonts, file window position, and other Macintosh data. Such files cannot be used as import files with the Microsoft Internet Explorer browser. Either use a text editor application that saves text files without resource forks or use a browser that uploads Macintosh files without encoding.

The first file line describes the file contents. It should contain tab-delimited names of Account attributes. The following names are supported:

Name: This column contains the Account names. This attribute is not required to be in the first column, but it must exist. All other attributes are optional.
RealName: This column contains the Account user "real name".
Type: This column contains the Account type (MultiMailbox, Text Mailbox, etc.). If the file does not contain this column, or this field is empty, the Account type selected on the Account List WebAdmin page is used.
Password: This column contains the Account password. If the file does not contain this column, or this field is empty, the CommuniGate Password and the Use CommuniGate Password settings are taken from the domain Account Template.
UnixPassword

If the first line is parsed, all other lines are processed. Each line should contain tab-delimited fields, with the field contents specified in the first line. A line can contain less fields than the first line, in this case missing fields are processed as empty fields.

Attribute values for empty and missing fields are taken from the Account Template.

If an error occurs while processing some file line (missing name field, duplicate name, etc.), all Accounts created while processing previous lines are removed, and the number of the line that caused the problem is displayed. You can fix the file and try again.

Created:	12-May-2007	Access Rights
Real Name:
Title:
City:
Services:
Organization:
Space Test:
CommuniGate Password:
FirstName:
FamilyName:
department:

Accounts

Creating a New Account

Specifying Account Settings

Authentication Methods

Enabled Services

Mail Settings

Signaling Settings

File Storage Settings

WebUser Interface Settings

Account Aliases

Account Telephone Numbers

Access Control Lists (ACL)

Access Rights

Creating Mailing Lists

Renaming Accounts

Removing Accounts

Default Account Settings

Class of Service

Account Template

Importing User Account Information

`Name`	`Type`	`Ignore`	`Storage`	`Aliases`
`johnd`	`MultiMailbox`	`sales dept`	`50M`
`susan`	`MultiMailbox`	`mgmnt`	`10M`	`susan.s,susan_smith`
`sales`	`MultiMailbox`	`dummy`	`30M`
`info`	`MultiMailbox`	`dummy`	`50M`	`help`