• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

inconsistent mail name issue after backup/restore

P

porkchop

Guest
Hi all!
Migrating sites from 8.01/FreeBSD 6.x box -> 8.10/FreeBSD 6.x box. Method used by client is: backup a site fully, move the backup file (manually) to the new box, restore the backup, correct some paths etc, end he's good to go.

Except, he isn't.

On the new box, some mail accounts are accessed as "username" whereas others require 'username@domain'. On the "old" box the format was consistent, access to email was "username"

He has dozens of users scattered around several countries, in a number of different timezones so instructing them to/how_to change their PC settings if their username format has changed would be a HUGE problem.

Can anyone point me to how to unify this so that the "old" format is restored (i.e. just plain old "username") please? Any and all suggestions would be most welcome and greatly appreciated.

Regards & TIA,
-Porky
[EDIT]
I think this issue is resolved.
----------------------
On the source box in server-wide mail settings "allow short & full mailnames" was the selected policy. On the target box I discovered that "allow only full names" was selected. So, something about the restored mailnames permitted short/long names, but newly created accounts adhered to the target machine policy, thus a hybrid of long or short names appeared to be possible on "legacy" accounts, but new accounts would permit only long format.
[/EDIT]
 
Back
Top