Plesk migrator will re-create deleted email account

[nethubonline]

Username:

TITLE

Plesk migrator will re-create deleted email account

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian v18.0.69
AlmaLinux release 9.5

PROBLEM DESCRIPTION

When a user creates an email account in Plesk, the option "Can be used to log in to Plesk" is selected by default, resulting in the creation of a Plesk user. If the user deletes this email account, the associated Plesk user remains.

During migration to a new Plesk server, the migrator will unexpectedly recreate this deleted email account, raising security concerns.

Additionally, if the subscription has reached its email account quota, recreating deleted accounts will prevent the creation of new ones, as the quota will be full.

STEPS TO REPRODUCE

1. In old server: create an email account with "Can be used to log in to Plesk", delete this email account afterwards
2. In new server: Use migrator to migrate this subscription

ACTUAL RESULT

Deleted email account will be re-created in new server

EXPECTED RESULT

Deleted email account will not be re-created in new server

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Hangover2]

@nethubonline

The migrator still has many silly bugs and missing features that make migrating mailboxes a real headache. Besides the one already mentioned, be aware that webmail contacts and settings (e.g., from Roundcube) are not transferred. So, if your users are enthusiastic webmail users, you can expect a lot of support requests after migration.

Another bug — which has existed for us for years (though we haven’t submitted an official bug report yet) — concerns the critical DNS entry for the DKIM key. After migrating a domain, the public/private key pair becomes invalid, and signed outgoing emails can no longer be verified by the recipient. The best solution is to regenerate the keys after each migration by toggling DKIM support off and on in the email settings.

There are also additional bugs, particularly affecting users who utilize the "External email address" feature, as well as missing configuration data after migration and other issues. It’s actually quite unfortunate that the migrator is so buggy — not just in email handling, but in other areas as well — because it could be a great help for admins migrating customers between servers. However, at this point, we no longer use the tool. We prefer a manual approach, as the cleanup and verification effort would be required anyway. By handling the entire process ourselves, we can ensure that everything is correctly in place, just like before.