Applicable to:
- Plesk for Windows
Symptoms
-
On a Plesk server with SmarterMail build 9770 or later, creating a new mailbox fails with
Login failure: Token revokedCONFIG_TEXT: Error: mailmng failed: Login failure: Token revoked
at setForwarding()(SmarterMail::Common::MailName::setForwarding line 240)
at postbox(true)(SmarterMail::Common::MailName::postbox line 128)
at Unable to execute console command: '--add-mailbox'(vconsoleapp::start line 95)
at Unable to execute command: '"C:\Program Files (x86)\Plesk\admin\bin\mailmng" --add-mailbox "--domain-name=example.com" "--mailname=test" "--password=*"'(vconsoleapp::run line 117)
(Error code 1) - Tools & Settings > Server Components shows SmarterMail as configured, at version 9770 or later
Cause
A recent SmarterMail update introduced changes in how its internal API handles user impersonation.
Normally, Plesk authenticates as sysadmin, impersonates the mailbox user, and calls the SmarterMails API user endpoints to make any changes. In version 9770, a sysadmin manage-domain request revokes the previous impersonation token for security reasons and so a new token is necessary for each manage-domain request.
The integration between SmarterMail and Plesk does not yet handle this behavior. We have tracked this as bug #PPPM-15564.
Resolution
A fix has been released on Plesk Obsidian 18.0.81.3. Please update Plesk to receive the fix.
Comments
Please sign in to leave a comment.