• 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.

Mailnames left overs

T

timtrott

Guest
When a domain has been delted or migrated it appears that mail files and mail names remain behind, causing "not accepting mail" errors when trying to send messages to addresses that have been moved.

Can the old /mailnames directories be removed safely?

Can the mailnames config file be edited safely or is it generated somewhere else?

Is there some PSA utility that can be used to generate a fresh mailnames config file to eliminate the problem?
 
You must log in or register to reply here.

Similar threads

A
Issue Smartermail : must be textual to extract_string, JSON to extract_json.
Replies
1
Views
3K
scsa20
scsa20
N
Issue Plesk Monitoring Disk Threshold Alerts Wrong
Replies
5
Views
18K
nmdpa3
N
J
Issue Emails to postmaster@ not delivered without root@ (custom `adminAliases`)
Replies
4
Views
2K
jnthn
J
M
Resolved Plesk Email Security: Unable to disable greylisting server-wide, per-mailname, per-domain
Replies
1
Views
1K
maltris
M
K
Forwarded to devs Plesk tries to get server hostname from /etc/mailname for cronjob notifications on RHEL based systems
Replies
1
Views
3K
yspirin
Y
Back
Top