SendAs sendOnBehalfOf: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{BC|Community Sandbox}} | |||
__FORCETOC__ | |||
<div class="col-md-12 ibox-content"> | |||
=SendAs sendOnBehalfOf= | |||
{{KB|{{Unsupported}}|{{ZCS 8.0}}|{{ZCS 7.0}}|}} | |||
{{WIP}}'''ISSUE:''' When trying to configure ''zimbraAllowFromAddress'' or ''zimbraAllowAnyAddress'' using an internal address, you received the following error: | {{WIP}}'''ISSUE:''' When trying to configure ''zimbraAllowFromAddress'' or ''zimbraAllowAnyAddress'' using an internal address, you received the following error: | ||
| Line 18: | Line 23: | ||
''zmprov grr account account1@domain.com use account2@domain.com sendAs'' | ''zmprov grr account account1@domain.com use account2@domain.com sendAs'' | ||
{{Article Footer|Zimbra Collaboration 8.0, 7.0|04/16/2014}} | |||
Revision as of 21:58, 12 July 2015
SendAs sendOnBehalfOf
ISSUE: When trying to configure zimbraAllowFromAddress or zimbraAllowAnyAddress using an internal address, you received the following error:
Message: invalid request: zimbraAllowFromAddress may not contain an internal account: hrd@revenuemed.com Error code: service.INVALID_REQUEST Method: [unknown] Details:soap:Sender
CAUSE: Within 8.0 we have provided the ability to grant Send As and Send On the Behalf of rights within the ACL rules. Going forward, the zimbraAllowFromAddress or zimbraAllowAnyAddress will only support external addresses.
RESOLUTION: To provide the right to send as or Send on the behalf of, the user can log into their account and select Preferences => Accounts. Under Primary Account settings, the user then will select Add Delegate and enter the email address and right that they want to provide to the Delegate.
The admin can also provide this right from the command line by running:
Send on behalf of rights:
zmprov grr account account1@domain.com use account2@domain.com sendOnBehalfOf
Send as rights:
zmprov grr account account1@domain.com use account2@domain.com sendAs
