Google Message Security Batch Reference Guide - Manual (Page 135)

138
If is an existing alias for another user, the alias will be transferred to
the new .
If is an existing user’s primary address:
• The existing user’s primary address is deleted. This primary address
name becomes an alias for the new user’s primary address.
• Any associated aliases for the existing user will be deleted and will
become aliases for the new user’s primary address.
• The existing user’s messages will be transferred before creating the alias.
For example:
addalias [email protected], [email protected], confirm
In this organization, [email protected] already exists as a user’s
primary address with an existing alias,
[email protected]
.
After the addalias command is run, [email protected] has 2 new
aliases,
[email protected]
and
[email protected]
. And the
primary address [email protected] is removed.
• confirm -- A required positional parameter if an existing user address is being
overwritten to become an alias address. The text
confirm must be at the end
of the command. There is no numeric equivalent.
EZCommand Description for addalias
See the Batch Interface Description for addalias for general usage details.
When used as an EZCommand, the command must be URL-escaped in order to
properly submitted.
Example:
addalias [email protected], [email protected], confirm
changes to
addalias%20msmith%40jumboinc.com%20mary%40jumboinc.com%20confirm
Errors
Possible batch command error messages include:
‘No such user ‘username’ (unknown administrator address supplied).’
‘String authorization failed.’
‘No commands to process.’
‘Command not recognized: command.’
‘You don’t have permission to insert users into org name.’
‘No such organization ‘org name’.’
‘No default user available for organization org name.’
‘No secret key in database’.’
If the alias is not added successfully, the possible batch command error
messages are: