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

Forwarded to devs API: Setting Mail Service Prefs is not working properly

ChrisH

Basic Pleskian
TITLE:
API: Setting Mail Service Prefs is not working properly
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onyx Linux 17.5.3 #21
PROBLEM DESCRIPTION:
Trying to Change the mail service settings via API is not working. "Webmail" can only be changed it is used alone and changing "Greylisting" is not working at all.​
STEPS TO REPRODUCE:
<packet> <mail> <set_prefs> <filter> <site-id>1</site-id> </filter> <prefs> <greylisting>false</greylisting> <webmail>none</webmail> <mailservice>true</mailservice> </prefs> </set_prefs> </mail> </packet>​
ACTUAL RESULT:
Parser error: Request is invalid. Error in line 13: Element 'webmail': This element is not expected. Expected is one of ( mailservice, ip_address, mail-provider, webmail-certificate ).​
EXPECTED RESULT:
The answer should be "Status: OK"​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
BTW... Please check also the transmission of an forward e-mail address for non-existent users:
<packet> <mail> <set_prefs> <filter> <site-id>1</site-id> </filter> <prefs> <nonexistent-user> <forward>info@xxx.de</forward> </nonexistent-user> </prefs> </set_prefs> </mail> </packet>
Actual result is "The 'forward' parameter does not contain a valid e-mail address." Entering the address in the normal Panel is working.
 
You should put fields in following order:
  • nonexistent-user
  • webmail
  • spam-protect-sign
  • greylisting
  • mailservice
  • ip_address
  • mail-provider
  • webmail-certificate
E.g. this packet works fine:

Code:
<packet>
<mail>
<set_prefs>
<filter>
<site-id>1</site-id>
</filter>
<prefs>
<nonexistent-user>
<forward>info@xxx.de</forward>
</nonexistent-user>
<webmail>none</webmail>
<greylisting>false</greylisting>
<mailservice>true</mailservice>
</prefs>
</set_prefs>
</mail>
</packet>
 
Back
Top