Novell GROUPWISE 7 - USERS User manual

Users
IV
novdocx (en) 11 December 2007
201
IV
Users
Chapter 13, “Creating GroupWise Accounts,” on page 203
Chapter 14, “Managing GroupWise Accounts and Users,” on page 217

202 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007

Creating GroupWise Accounts
13
novdocx (en) 11 December 2007
203
13
Creating GroupWise Accounts
For users to be able to use GroupWise®, you must give them GroupWise accounts. A GroupWise
account defines the user in the GroupWise system by providing the user with a GroupWise user ID
and GroupWise mailbox.
You can give GroupWise accounts to Novell®eDirectoryTM users during or after their creation in
eDirectory. You can also give GroupWise accounts to users who do not have eDirectory accounts.
Refer to the following sections for details:
Section 13.1, “Establishing a Default Password for All New GroupWise Accounts,” on
page 203
Section 13.2, “Creating GroupWise Accounts for eDirectory Users,” on page 204
Section 13.3, “Creating GroupWise Accounts for Non-eDirectory Users,” on page 214
Section 13.4, “Educating Your New Users,” on page 215
13.1 Establishing a Default Password for All New
GroupWise Accounts
To save time and energy when you are creating new GroupWise accounts, you can establish a
default password to use for all new accounts.
1In ConsoleOne®, click To ols > GroupWise System Operations > System Preferences > Default
Password.
2Type the password you want to use as the default, then click OK.
3Explain to users how to set their own passwords in the GroupWise client, as described in:
“Assigning Passwords to Your Mailbox” in the GroupWise 7 Windows Client User Guide
“Assigning Passwords to Your Mailbox” in the GroupWise 7 Cross-Platform Client User
Guide
“Changing Your GroupWise Password” in the GroupWise 7 WebAccess Client User Guide

204 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
13.2 Creating GroupWise Accounts for
eDirectory Users
Depending on your needs, you can choose from the following methods to create GroupWise
accounts for eDirectory users:
Creating a Single GroupWise Account: You can create a GroupWise account for a single
eDirectory user by editing the GroupWise information on his or her User object. This method
lets you create the GroupWise account on any post office, select the GroupWise user ID, and
configure optional GroupWise information. It provides the most flexibility in creating a user’s
GroupWise account.
Creating Multiple GroupWise Accounts: You can create GroupWise accounts for multiple
eDirectory users by editing the membership information on a Post Office object. This method
allows you to quickly add multiple users to the same post office at one time. However, you
cannot select the user’s GroupWise user ID; instead, the user’s eDirectory username is
automatically used as his or her GroupWise user ID. In addition, to configure other optional
GroupWise information for a user, you need to modify each User object.
Using a Template to Create GroupWise Accounts: You can create a template to apply to new
eDirectory User objects you create. The template can be configured to automatically assign the
user to a post office.
Creating GroupWise Accounts by Importing Users: You can import information from ASCII-
delimited text files.
13.2.1 Creating a Single GroupWise Account
To create a GroupWise account for an eDirectory user:
1In ConsoleOne, right-click the User object, then click Properties.
2Click GroupWise > Account to display the Account page.
3Fill in the following fields:

Creating GroupWise Accounts 205
novdocx (en) 11 December 2007
Post Office: Select the post office where you want the user’s mailbox created.
Mailbox ID: The mailbox ID (also referred to as the GroupWise user ID or username) defaults
to the eDirectory username. You can change it if necessary.
Do not use any of the following invalid characters in the mailbox ID:
4Click Apply to create the account.
You must create the account by clicking Apply (or OK) before you can modify any of the other
fields, including the GroupWise password.
5If desired, modify any of the following optional fields:
Visibility: Select the level at which you want the user to be visible in the Address Book.
System enables the user to be visible to all users in your GroupWise system. Domain enables
the user to be visible to all users in the same domain as the user. Post Office enables the user to
be visible to all users on the same post office as the user. Setting the visibility level to None
means that no users can see the user in the Address Book. However, even if the user is not
displayed in the Address Book, other users can send messages to the user by typing the user’s
ID (mailbox ID) in a message’s To field.
External Sync Override: This option applies only if your GroupWise system links to and
synchronizes with an external system, as described in “Connecting to GroupWise 5.x, 6.x, and
7.x Systems” in the GroupWise 7 Multi-System Administration Guide.
Select the Synchronize According to Visibility setting if you want the user information to be
provided to the other system only if the user’s visibility is set to System.
Select the Synchronize Regardless of Visibility setting if you always want the user information
provided to the other system regardless of the user’s visibility level.
Select the Don’t Synchronize Regardless of Visibility setting if you never want the user
information provided to the other system.
Account ID: This option applies only if you have a GroupWise gateway that supports
accounting. For more information about gateway accounting, see your GroupWise gateway
documentation (http://www.novell.com/documentation/gwgateways).
File ID: This three-letter ID is randomly generated and is non-editable. It is used for various
internal purposes within the GroupWise system, including ensuring that files associated with
the user have unique names.
Expiration Date: If you want the user’s GroupWise account to no longer work after a certain
date, specify the expiration date. This date applies to the user’s GroupWise account only; it is
independent of the eDirectory account expiration date (User object > Restrictions > Login
Restrictions). For more information, see Section 14.10.2, “Expiring a GroupWise Account,” on
page 243.
ASCII characters 0-13 Comma ,
Asterisk * Double quote “
At sign @ Extended ASCII characters that are graphical or typographical
symbols; accented characters in the extended range can be used
Braces { } Parentheses ( )
Colon : Period .

206 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Gateway Access: This option applies only if you have GroupWise gateways that support
access restrictions. For more information, see your GroupWise gateway documentation (http://
www.novell.com/documentation/gwgateways).
Disable Logins: Select this option to prevent the user from accessing his or her GroupWise
mailbox. For more information, see Section 14.9, “Disabling and Enabling GroupWise
Accounts,” on page 240.
LDAP Authentication: This option applies only if you are using LDAP to authenticate users
to GroupWise, as described in Section 36.3.4, “Providing LDAP Authentication for GroupWise
Users,” on page 501, and if the LDAP server is not a Novell LDAP server. If this is the case,
specify the user’s LDAP authentication ID.
Restore Area: This field applies only if you are using the GroupWise backup and restore
features. If so, this field indicates the location where the user’s mailbox is being backed up. For
details, see Chapter 32, “Restoring GroupWise Databases from Backup,” on page 411.
Change GroupWise Password: Click this option to assign a password to the user’s
GroupWise account or change the current password. The user is prompted for this password
each time he or she logs in to GroupWise.
To be able to skip this option by setting a default password, see Section 13.1, “Establishing a
Default Password for All New GroupWise Accounts,” on page 203.
Delete GroupWise Account: Click this option to delete the user’s GroupWise account. This
includes the user’s mailbox and all items in the mailbox. The user’s eDirectory account is not
affected. For more information, see Section 14.10, “Removing GroupWise Accounts,” on
page 241
6Click Apply to save the changes.
7Click GroupWise > General > Identification to display the user’s current eDirectory
information.
This information appears in the GroupWise Address Book, as described in Chapter 6,
“GroupWise Address Book,” on page 85. If you keep private information in the Description
field of the User object, you can prevent this information from appearing the GroupWise
Address Book. See Section 6.1.5, “Preventing the User Description Field from Displaying in
the Address Book,” on page 89.
8Make sure that the user’s eDirectory information is current, then click OK.
13.2.2 Creating Multiple GroupWise Accounts
If you have multiple eDirectory users who will have GroupWise accounts on the same post office,
you can use the Post Office object’s Membership page to quickly add the users and create their
accounts. Each user’s GroupWise user ID will be the same as his or her eDirectory username.
To create GroupWise accounts for multiple eDirectory users:
1In ConsoleOne, right-click the Post Office object, then click Properties.
2Click GroupWise > Membership to display the Membership page.

Creating GroupWise Accounts 207
novdocx (en) 11 December 2007
3Click Add, select the eDirectory user you want to add to the post office, then click OK to add
the user to the post office’s membership list.
By default, the user’s eDirectory username is used as the GroupWise ID.
A GroupWise user ID cannot contain any of the following invalid characters:
4Repeat Step 3 to create additional GroupWise accounts in the post office.
ASCII characters 0-13 Comma ,
Asterisk * Double quote “
At sign @ Extended ASCII characters that are graphical or typographical
symbols; accented characters in the extended range can be used
Braces { } Parentheses ( )
Colon : Period .

208 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
5When finished, click OK to save the changes.
13.2.3 Using a Template to Create GroupWise Accounts
If you frequently create new users, you might want to create Template objects with the necessary
GroupWise properties. This makes creating a new eDirectory user with GroupWise access a one-
step process. However, you cannot use a Template object to give GroupWise properties to existing
eDirectory users.
The steps to create a template with GroupWise properties include assigning the post office and
setting up directory rights. Because a user can have membership in only one post office, a different
template should be created for each existing post office. Further, for each post office, a template can
be created for different categories of users, such as secretarial, accounting, administrative, human
resources, development, sales, and manufacturing.
After one template has been created with eDirectory properties and post office directory rights, you
can use it to quickly create templates for subsequent post offices.
“Creating a Template” on page 208
“Creating a User Account from a Template” on page 209
Creating a Template
1In ConsoleOne, right-click the Organizational Unit object where you want to create the
Template object, then click New > Object to display the New Object dialog box.
Templates should be placed in the same organizational unit where they will be used because the
browser first lists any templates in the current context. The template also inherits rights from
the container the template is created in, further simplifying its setup.
2In the Class list, select Template, then click OK to display the New Template dialog box.
3Specify a name that describes the purpose for which the template will be used.
4If you want to base the template on another Template or User object, select Use Template or
User, then browse to and select the desired Template or User object.

Creating GroupWise Accounts 209
novdocx (en) 11 December 2007
5Select Define Additional Properties.
6Click Create to display the properties pages for the Template object.
7Click GroupWise > Information.
8Fill in the following fields:
Post Office: Select the post office the user will be assigned to.
Visibility: Select the level at which the user will be visible in the Address Book. System
enables the user to be visible to all users in your GroupWise system. Domain enables the user
to be visible to all users in the same domain as the user. Post Office enables the user to be
visible to all users on the same post office as the user. Setting the visibility level to None means
that no users can see the user in the Address Book. However, even if the user is not displayed in
the Address Book, other users can send messages to the user by typing the user’s ID (mailbox
ID) in a message’s To field.
Account ID: This field supports accounting for GroupWise gateways. For more information
about gateway accounting, see your gateway documentation.
Expiration Date: Use this to set a date when the user’s account will expire. The user cannot
access the account after that date. For more information, see Section 14.10.2, “Expiring a
GroupWise Account,” on page 243.
Gateway Access: This is used to grant or restrict access to some GroupWise gateways. See
your GroupWise gateway documentation (http://www.novell.com/documentation/gwgateways)
to determine if this field applies.
9Modify information on any of the other tabs to configure the template, then click OK to save
the template changes.
Creating a User Account from a Template
1In ConsoleOne, right-click the container where you want to create a new eDirectory user, then
click New > User.
2Specify a Name, Surname, and Unique ID (all three are required).
3Select Use Template, then browse to and select the template you want applied to this user.
4Modify any of the other options you want.
5Click OK to create the user’s eDirectory and GroupWise accounts.
13.2.4 Creating GroupWise Accounts by Importing Users
You can use the GroupWise Import utility to quickly create multiple GroupWise users. The Import
utility reads an ASCII-delimited text file created by the GroupWise Export utility or by a third-party
export, and creates Novell eDirectory and GroupWise objects with attributes from the file. The
Import utility supports most eDirectory classes (including extensions) and GroupWise classes. You
can specify the delimiters, eDirectory contexts, and file field positions to use during import.
IMPORTANT: The Import/Export utility is not included on the GroupWise CDs. You can
download the Import/Export utility from TID 2960897 in the Novell Support Knowledgebase (http:/
/www.novell.com/support/supportcentral). To install the Import/Export utility, follow the

210 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
instructions provided with the download. After you have installed the Import/Export utility, the
Import and Export menu items appear under Tools > GroupWise Utilities in ConsoleOne.
“Using the Import Utility” on page 210
“Using the Export Utility” on page 212
NOTE: The Import/Export utility is not available for use on Linux.
Using the Import Utility
In order to import objects into GroupWise, the following conditions must be met:
You must create an ASCII-delimited text file by using the GroupWise Export utility or another
export utility.
The destination context for each eDirectory object must already exist. The GroupWise Import
utility supports creating organizational units. If a large portion of a tree needs to be
reconstructed to support the objects, you can import organizational units before importing the
objects.
To import objects into GroupWise:
1In ConsoleOne, select the eDirectory tree to which the objects will be imported, then click
Tools > GroupWise Utilities > Import to display the GroupWise Import dialog box.
2If you have previously defined and saved a configuration file, click Load to fill in the fields
from the configuration files, then click Run to perform the import.
or
Fill in the fields in the Import Dialog box.
NDS/GroupWise Class: Select this option to import objects belonging to an eDirectory class
or to a GroupWise-related eDirectory class. Choose the class from the list.
GroupWise Class: Select this option to import objects belonging to a GroupWise class not
represented in eDirectory. Choose external user, external domain, external post office,
Document-Version, or Lookup Entry from the list

Creating GroupWise Accounts 211
novdocx (en) 11 December 2007
Parent: If you are importing objects that belong to a GroupWise-related eDirectory class or a
GroupWise-only class, the parent attribute is required unless:
The class is the eDirectory User class, in which case the object can be optionally
associated with GroupWise by specifying a value here.
The value is in the import file and is explicitly imported by your positioning the NGW:
Post Office attribute in the File Fields list box, explained below. In this case, if the value
obtained from the file is blank, the Post Office field value, if any, is used.
Import File: Specify the full path and file name of the ASCII text file.
Attributes / File Fields: This list displays the attributes of the selected class. Move the
attributes to correspond to the fields in the ASCII text file to the File Fields list.
Some attributes are marked with an exclamation point (!), indicating that a value for that
attribute must exist for a successful import. The import also requires a value for either the
object name or distinguished name.
Starting Destination Context: Specify the destination eDirectory context for the objects to be
imported. If DN or Context from Root is selected as an import field, the value in this field is
ignored because both DN and Context from Root specify the destination context.
An imported object’s position in the tree can be constructed in a flexible manner using the
Context from Root, Context from Starting, DN, and Object Name class attribute fields and the
Starting Destination Context field. The following combinations are valid:
Skip the First Line of the Import File: This directs the import to skip the first line if it
contains the attribute names.
Delimiters: Accept the defaults shown or change the delimiters to match those used by the
export file. For more information, see “Delimiters” on page 212.
3For convenience, save the configuration for later use. See “Loading or Saving a Configuration
File” on page 211.
4Click Run to perform the import.
An import.log file is created in the same directory as the import file and contains a list of the
imported objects.
Loading or Saving a Configuration File
An import or export configuration can be saved and loaded, saving you the trouble of manually
filling in the fields for multiple imports or exports. A configuration saved from an export can be
DN Each object’s name and context are found in this field value.
Object Name +
Starting Destination
Context
Each object name in the Object Name field is added to the context
specified in Starting Destination Context.
Object Name +
Context from Starting +
Starting Destination
Context
Each object name in the Object Name field is added to the context
obtained by concatenating the value in the Context from Starting field
and the value specified in Starting Destination Context.
Object Name +
Context from Root
Each object name in the Object Name field is added to the context read
from the Context from Root field.

212 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
loaded for an import, helping ensure that the file field positions, for example, correspond for both
the import and export.
Delimiters
Delimiters are used in ASCII text files to separate items that represent fields and records in imported
or exported data.
Default delimiters are associated with each delimiter type. A delimiter can be set to None, but if so,
and the export encounters a condition requiring a delimiter, the export reports an error.
Between Fields: This delimiter is placed between each field.
Around Each Field: Use this delimiter to indicate the beginning and end of each field.
After Each Record: This delimiter is placed at the end of each record.
Between Values (Multi-Value Fields): Use this delimiter to separate the values in a multi-
valued field. For example, an attribute such as Group Membership can have one or more
values. Each Group Membership value is delimited by the multi-value field delimiter.
Between Elements (Multi-Element Values): Use this delimiter to separate the elements of a
multi-element value. For example, an attribute having the syntax of SYN_OBJECT_ACL has
three elements: the protected attribute name, the subject name, and the privileges.
Before Literal Characters: When you import an ASCII file created by a third-party export
program, precede each literal character that is also a delimiter with the Before Literal
Characters delimiter. If you use the Around Each Field delimiter, you do not need to precede
literal characters within the field with the Before Literal Character delimiter.
Using the Export Utility
The GroupWise Export utility reads eDirectory and GroupWise object information from GroupWise
databases and creates an ASCII-delimited text file containing the object attributes. The Export utility
supports most eDirectory classes (including extensions) and GroupWise classes. You can specify the
delimiters, eDirectory contexts, and file field positions during export.
IMPORTANT: The Export utility is not included on the GroupWise CDs. You can download the
Import/Export utility from TID 2960897 in the Novell Support Knowledgebase (http://
www.novell.com/support/supportcentral). To install the Import/Export utility, follow the instructions
provided with the download. The Import/Export utility is not available for use on Linux.
To export objects from GroupWise:
1In ConsoleOne, select the eDirectory tree that contains the GroupWise objects you want to
export, click Tools > GroupWise Utilities > Export to display the GroupWise Export dialog box.

Creating GroupWise Accounts 213
novdocx (en) 11 December 2007
2If you have previously defined and saved a configuration, click Load to fill in the fields from
the configuration file, then click Run to perform the export.
or
Fill in the fields in the Export dialog box.
NDS/GroupWise Class: Select this option to export objects belonging to an eDirectory class
or to a GroupWise-related eDirectory class. Choose the class from the list.
GroupWise Class: Select this option to export objects belonging to a GroupWise class not
represented in eDirectory. Choose external user, external domain, external post office,
Document-Version, or Lookup Entry from the list.
Parent: If you are exporting objects that belong to a GroupWise-related eDirectory class or a
GroupWise-only class, and that class has a parent attribute, post office, or domain, this field
allows you to export objects having only the parent attribute value you specify. The object
selection process is still subject to the values in Starting Context, explained below, and the
Export from Subordinate Contexts check box.
Export File: Specify the full path and file name of the ASCII text file.
Attributes / File Fields: This list displays the attributes of the selected class. Move the
attributes to correspond to the fields in the ASCII text file to the File Fields list.
Some attributes are marked with an exclamation point (!), indicating that a value for that
attribute must exist.
Starting Context: Specify the eDirectory context from which to begin the export. If the Export
from Subordinate Contexts list box is selected, objects belonging to contexts subordinate to the
context specified here is also exported.
Export from Subordinate Contexts: Select this option to cause objects in subordinate
contexts to be exported. If this box is left deselected, only those objects in the immediate
Starting Context context are exported.
Put Attribute Names in First Line: Select this option to direct the export to put the attribute
names as a comment in the first line of the export file.
Create the File in WordPerfect Office Notebook Format: If you use this option, you might
also want to select Put Attribute Names in First Line to permit WordPerfect* to display the
attribute names for each merge field.

214 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Delimiters: Accept the defaults shown or change the delimiters. For more information, see
“Delimiters” on page 212.
3Click Run to perform the export.
13.3 Creating GroupWise Accounts for Non-
eDirectory Users
If you have users who do not have eDirectory accounts, you can still assign them GroupWise
accounts by defining them as GroupWise external entities in eDirectory. Defining a user as a
GroupWise external entity provides the user with access to GroupWise only; it does not enable the
user to log in to eDirectory. External entities have eDirectory objects, but they are not considered
eDirectory users for licensing purposes.
To create a GroupWise account for a non-eDirectory user:
1In ConsoleOne, right-click the eDirectory container where you want to create the user’s
GroupWise External Entity object, then click New > Object to display the New Object dialog
box.
2Select GroupWise External Entity, then click OK to display the Create GroupWise External
Entity dialog box.
3Fill in the following fields:
GroupWise Object ID: Specify the user’s GroupWise ID. The user’s ID along with the user’s
post office and domain, provide the user with a unique name within the GroupWise system
(userID.po.domain).
Do not use any of the following invalid characters in the GroupWise object ID:
Last Name: Specify the user’s last name.
GroupWise Post Office: Select the post office where you want the user’s mailbox.
External Network ID: Specify the user’s network ID for the network that he or she logs in to.
ASCII characters 0-13 Comma ,
Asterisk * Double quote “
At sign @ Extended ASCII characters that are graphical or typographical
symbols; accented characters in the extended range can be used
Braces { } Parentheses ( )
Colon : Period .

Creating GroupWise Accounts 215
novdocx (en) 11 December 2007
4Select Define Additional Properties, then click OK to display the GroupWise Identification
page.
5If desired, fill in any of the fields on the Identification page.
This information appears in the GroupWise Address Book, as described in Section 6.1,
“Customizing Address Book Fields,” on page 85. If you want to keep private information in the
Description field, you can prevent this information from appearing the GroupWise Address
Book. See Section 6.1.5, “Preventing the User Description Field from Displaying in the
Address Book,” on page 89.
6If you want the external entity user to be able to access his or her GroupWise mailbox using
LDAP authentication, as described in Section 36.3.4, “Providing LDAP Authentication for
GroupWise Users,” on page 501, click GroupWise > Account, then provide the fully
distinguished name of the user’s External Entity object in LDAP format (for example,
cn=user_id,ou=orgunit,o=organization).
7Click OK to save the information.
The user is given a GroupWise mailbox in the post office you selected and can access his or her
mailbox through the GroupWise client.
Because the external entity does not have an associated eDirectory User object, external entity users
must access their mailboxes using GroupWise passwords. They cannot use eDirectory
authentication or LDAP authentication to obtain mailbox access. For more information, see
Section 70.1, “Mailbox Passwords,” on page 1111.
13.4 Educating Your New Users
After users can log in to their GroupWise accounts, all of the GroupWise client’s features are at their
fingertips, but some new users do not know how to get started. You can give your users the
following suggestions to encourage them to explore their GroupWise client:
Click Help > Help Topics > Contents > How Do I to learn to perform common GroupWise
tasks
Click Help > What’s New to learn about the latest new GroupWise features

216 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Click Help > User Guide to view the GroupWise 7 Windows Client User Guide in HTML
format
Refer to the GroupWise 7 Client Frequently Asked Questions (FAQ) as needed
For convenience in printing, the GroupWise 7 Windows Client User Guide is available in PDF
format at the GroupWise 7 Documentation Web site (http://www.novell.com/documentation/gw7).

Managing GroupWise Accounts and Users
14
novdocx (en) 11 December 2007
217
14
Managing GroupWise Accounts
and Users
As your GroupWise®system grows, you will need to add users and manage their GroupWise
accounts.
Section 14.1, “Adding a User to a Distribution List,” on page 217
Section 14.2, “Allowing Users to Modify Distribution Lists,” on page 218
Section 14.3, “Adding a Global Signature to Users’ Messages,” on page 219
Section 14.4, “Moving GroupWise Accounts,” on page 222
Section 14.5, “Renaming Users and Their GroupWise Accounts,” on page 231
Section 14.6, “Managing Mailbox Passwords,” on page 231
Section 14.7, “Managing E-Mail Addresses,” on page 235
Section 14.8, “Checking GroupWise Account Usage,” on page 240
Section 14.9, “Disabling and Enabling GroupWise Accounts,” on page 240
Section 14.10, “Removing GroupWise Accounts,” on page 241
See also Section 26, “Maintaining Domain and Post Office Databases,” on page 377, Chapter 27,
“Maintaining User/Resource and Message Databases,” on page 385, and Section 31, “Backing Up
GroupWise Databases,” on page 407. Proper database maintenance and backups allow recovery
from accidental deletions, as described in Section 32.5, “Restoring Deleted Mailbox Items,” on
page 413 and Section 32.6, “Recovering Deleted GroupWise Accounts,” on page 416.
14.1 Adding a User to a Distribution List
GroupWise distribution lists are sets of users and resources that can be addressed as a single entity.
When a GroupWise user addresses an item (message, appointment, task, or note) to a distribution
list, each user or resource that is a member receives a copy of the item.
To add a user to a distribution list:
1In ConsoleOne®, right-click the User object, then click Properties.
2Click GroupWise > Distribution Lists to display the Distribution Lists page.

218 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
3Click Add, select the distribution list that you want to add the user to, then click OK.
By default, the user is added as a primary recipient (To: recipient).
4If you want to change the resource’s recipient type, select the distribution list, click
Participation, then click To, CC, or BC.
5Click OK to save your changes.
14.2 Allowing Users to Modify Distribution Lists
Because distribution lists are created in ConsoleOne, users by default cannot modify them.
However, in ConsoleOne, you can grant rights to selected users to modify specific distribution lists.
For setup instructions, see Section 18.6, “Enabling Users to Modify a Distribution List,” on
page 270.

Managing GroupWise Accounts and Users 219
novdocx (en) 11 December 2007
14.3 Adding a Global Signature to Users’
Messages
You can build a list of globally available signatures to be automatically appended to messages sent
by GroupWise client users. Global signatures are created in HTML format. For users who prefer the
Plain Text compose view in the GroupWise client, a plain text version of the signature is appended
instead of the HTML version. When this occurs, HTML formatting and embedded images are lost,
but you can customize the plain text version as needed to compensate for the loss of HTML
formatting.
For Windows client users, the global signature is appended by the client to messages after any
personal signatures that users create for themselves. It is appended after the user clicks Send. If S/
MIME encryption is enabled, the global signature is encrypted along with the rest of the message.
Windows client users can choose whether global signatures are appended only for recipients outside
the local GroupWise system or for all recipients, local as well as external. For Windows client users,
you can assign a global signature based on users, resources, post offices, and domains.
For all client users, the Internet Agent can append global signatures to the end of messages for
recipients outside the local GroupWise system. However, the Internet Agent does not append global
signatures to S/MIME-encoded messages, nor does it duplicate global signatures already appended
by the Windows client. You can assign a default global signature for all users in your system and
then override that default by editing the properties of each Internet Agent object
Section 14.3.1, “Creating Global Signatures,” on page 219
Section 14.3.2, “Selecting a Default Global Signature for All Outgoing Messages,” on
page 220
Section 14.3.3, “Assigning Global Signatures to Internet Agents,” on page 221
Section 14.3.4, “Assigning Global Signatures to Windows Client Users,” on page 221
Section 14.3.5, “Excluding Global Signatures,” on page 222
For information about users’ personal signatures, see:
“Adding a Signature or vCard to Items You Send” in “Working with Items in Your Mailbox” in
the GroupWise 7 Windows Client User Guide
“Adding a Signature or vCard to Items You Send” in “Working with Items in Your Mailbox” in
the GroupWise 7 Cross-Platform Client User Guide
“Adding A Signature to Items You Send” in “Working with Items in Your Mailbox” in the
GroupWise 7 WebAccess Client User Guide
14.3.1 Creating Global Signatures
1Click Too ls > GroupWise System Operations > Global Signatures.

220 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
2Click Create to create a new global signature.
3Specify a descriptive name for the signature.
4Compose the signature using the using the basic HTML editing tools provided, then click OK
to add the new signature to the list in the Global Signatures dialog box.
5If you want to check or edit the text version of the signature that was automatically generated:
5a Select the new signature, then click Edit.
5b Modify the text version of the signature as needed, then click OK.
6Click OK in the Global Signatures list dialog box to save the list.
7Continue with Assigning Global Signatures to Windows Client Users.
14.3.2 Selecting a Default Global Signature for All Outgoing
Messages
If you want the Internet Agent to append a global signature to all outgoing messages:
1Click Tools > GroupWise System Operations > Global Signatures.
2Click Settings.