• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

catchall feature missing on Almalinux 9 Plesk web admin LXC

JulianDot

Regular Pleskian
Username:

TITLE


catchall feature missing on Almalinux 9 Plesk web admin LXC

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

OS: AlmaLinux 9.1 (Lime Lynx)
Plesk Obsidian 18.0.51
LXC on Proxmox
Web Admin license

PROBLEM DESCRIPTION

Cannot set Catchall email for a domain
I do not have in Tools & Settings the Interface Management item.

Also, on the test domain, Mail Settings, is missing the BCatchall email feature

STEPS TO REPRODUCE

You can take a look at my test//migration server.

I have on it a license from Plesk, for migration

[redacted]

admin




Note: this is not a production server, i can destroy and reinstall it in minutes. You can play with it at will.

ACTUAL RESULT

Not
able to set Catchall .

EXPECTED RESULT

To be able
to set Catchall .

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Last edited by a moderator:
As mentioned before in the thread where we discussed this, a colleague had already tested it thoroughly and could not confirm your situation. Please open a ticket with Plesk support so that the issue can be investigated directly on your server.
 
Back
Top