Forwarded to devs "plesk bin certificate -u" change SMTP port setting unexpectedly

[nethubonline]

Username:

TITLE

"plesk bin certificate -u" change SMTP port setting unexpectedly

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.65 Update #1
Windows Server 2022 Standard

PROBLEM DESCRIPTION

In Plesk Windows, we changed the MailEnable SMTP settings of "Additional Port". One day we updated the SSL certificate by the command "plesk bin certificate -u". The certificate was installed successfully, but the SMTP additional port settings I updated were lost and it suddenly required my additional port to use SSL for my additional port (e.g. 1234), and it also changed my custom setting of port 465, which caused an error for all users sending emails through these additional ports.

STEPS TO REPRODUCE

1. Fresh install Plesk for Windows with MailEnable
2. Open MailEnable MMC > Servers > localhost > Services and Connectors > Right click "SMTP" > Properties > Inbound > Port Settings > Additional Ports > checked "Auth" and selected "Only secure (SSL/TLS)" for 465
3. Open MailEnable MMC > Servers > localhost > Services and Connectors > Right click "SMTP" > Properties > Inbound > Port Settings > Additional Ports > add a port 1234, unchecked "SSL", checked "Auth", select "Always allow"
4. run command

   plesk bin certificate -u www.abc.com -admin -key-file www.abc.com.key -cert-file www.abc.com.crt -cacert-file intermediateCA.crt

5. settings in step 2 and 3 are changed unexpectedly

ACTUAL RESULT

it suddenly required my additional port to use SSL for my additional port (e.g. 1234), and it also changed my custom setting of port 465

EXPECTED RESULT

do not change additional port setting

ANY ADDITIONAL INFORMATION

The updated SSL certificates are used by "Certificate for securing Plesk" and "Certificate for securing mail"

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Sebahat.hadzhi]

Thank you for the report, @nethubonline. I forwarded it to our team and the behavior was identified as a bug with ID PPP-66690. At this point, I cannot provide a workaround or any estimate for the resolution. I will update you with more information as soon as possible. Thank you for your patience and understanding in the meantime.