• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarded to devs Migrator fails to migrate users properly leading to mailbox inconsistencies

Hangover2

Regular Pleskian
Username: Hangover2

TITLE

Migrator fails to migrate users properly leading to mailbox inconsistencies

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.38 Update #2, Debian 10.10, x86-64

PROBLEM DESCRIPTION

Using email aliases as "External email address" for Plesk users in a subscription can lead to mailbox inconsistencies after migrating the subscription to a new Plesk server with the Plesk "Migration & Transfer Manager" tool.

STEPS TO REPRODUCE

- create a subscription with a domain: "test-domain.com"
- create an email address with an alias: [email protected] ([email protected])
- create a new Plesk user "Alias User" in the subscription and use "[email protected]" as "External email address" because we do not want to create a new email address (is used as alias already)
- migrate the subscription to a new Plesk server with the Plesk "Migration & Transfer Manager" tool

ACTUAL RESULT

- on the new server a new mailbox is created "[email protected]"
- the mailbox "[email protected]" will be created incorrectly without its alias, because a mailbox with this alias does already exist
- the "Alias User" created does not use "External email address" anymore, it is now using the newly created mailbox, that did not exist before

EXPECTED RESULT

- the "Alias User" should be migrated correctly not changing his settings about "External email address"
- no extra Mailbox should be created and the existing ones should be migrated correctly including email aliases, that are maybe used as "External email address" for users of the Plesk customer

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM


Confirm bug
 
This is already confirmed bug: PPPM-13179

Workaround:
  1. Log in to Plesk on the target server
  2. Delete all incorrectly created mail accounts from Domains > example.com > Mail addresses
  3. Go to Tools & Settings > Migration manager > select migration session > For affected subscription click Re-Sync > Choose Re-sync mail messages and click OK
 
Back
Top