• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Plesk Creates [email protected] Coming from Ensim 4.x

KrazyBob

Regular Pleskian
When using the Plesk Migratiion Manager on Virtuozzo 3 Plesk is migrating in all email addresses correctly *except* that Plesk creates [email protected] as an alias for what was the default Ensim user address (like [email protected])

root@ is getting spammed to death on several servers.

Where is this root@ *alias* written to? It is not in the standard alias file.

I don't write BASH, so let me ask about a script that could travel to each domain, look for the root@ alias, delete it, and save the file back.

Thanks in advance.
 
Hello!

Really, Ensim creates defautl aliases

MAILER-DAEMON ---> postmaster
postmaster ---> root
site_blackhole ---> /dev/null
root ---> default-address
catch-all ---> default-address

Youd could use

/usr/local/psa/bin/mail --update [email protected] -aliases del:root

to remove this alias by command line.

Thanks.
 
Thank you for the reply.

Your answer is great but assumes that the email address is [email protected]. I still need to figure out which of many email addresses per domain contains the alias.
 
The easiest way is to analyze dump you made from ensim. There aliases stored as

<alias>ALIAS_NAME</alias>.

Thanks.
 
Thanks again, but we have long since deleted the migration files. I was hoping for an automatced soltion as opposed to a manual process of thousands of domains.
 
You could use Plesk API.

You could analyze results from script like this (for example)

awk -F: '{print $1, ":", $5; }' /var/qmail/users/assign | grep '\-<ALIAS>\ :'

where <ALIAS> - alias you found.
 
Back
Top