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

Issue Postfix delivers mail as if a domain was an alias, but it is not

romofoos

New Pleskian
Server operating system version
Almalinux 9.4
Plesk version and microupdate number
Version 18.0.66 #2
I have a subscription aaa.com
Within the subscription a few 100 domains, bbb.com, ccc.com etc. All domains have been added as domain. Mail-service on bbb.com, ccc.com etc is 'not configured'
There are NO aliases for aaa.com

When i send a mail from my server to an address like [email protected], [email protected], the mail does not leave the server, but it is delivered to an address on my server [email protected].
As if bbb.com, ccc.com were aliases for aaa.com, which they are not

If i enable mail for bbb.com, and next disable mail for bbb.com (not configured), the problem disappears for this domain bbb.com

What is going on here?
 
Hello, @romofoos . Could you please navigate to Domains > bbb.com > Mail > Mail Settings, and confirm what is the option selected for "What to do with mail for non-existent users"?
 
Thanks for the confirmation. Please also check what's the setting for the service plan assigned to that subscription - Service Plans > service plan name > Mail > Policy on mail for non-existent users. If that's set to anything different than "forward to [email protected]" I would suggest getting in touch with our support team for further investigation.
 
Back
Top