• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Forwarded to devs Possible to create conflicting settings in mail address setup

mow

Silver Pleskian
Username:

TITLE

Possible to create conflicting settings in mail address setup

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Product version: Plesk Obsidian 18.0.49.2
OS version: Debian 11.6 x86_64

PROBLEM DESCRIPTION

On creating/editing a mail address, it is possible to set it to both [ ] Mailbox and ◉ Move spam to the Spam folder.

STEPS TO REPRODUCE

Create or edit address, disable the [ ] Mailbox, then go through the other tabs

ACTUAL RESULT

"◉ Move spam to the Spam folder" can be selected, although without mailbox there is no spam folder, so it makes no sense and could maybe even lead to lost messages; would be interesting where mails redirected to a non-existing spam folder end up ...

EXPECTED RESULT

That option should be grayed out, just like [ ] Do not deliver copies of forwarded emails to the Plesk mailbox

ANY ADDITIONAL INFORMATION

Password seems to not be saved when there's no mailbox and no plesk login, so the password related options should be greyed out too

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Thank you for reporting. The report has been submitted for further analysis. The ID is [PPS-13898].
 
The bug has been confirmed and a fix that will appear in future versions can be tracked by [PPPM-13890].
 
Back
Top