• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

mail api bug with update/set and group memberships

J

jgc94131

Guest
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk 9.5.2 on FC4 linux x86

PROBLEM DESCRIPTION AND STEPS TO REPRODUCE
The mail/update/set request (version 1.5.2.0 shown below) treats just the <group> parameters as if the
request was for mail/update/add.

ACTUAL RESULT

Doing a mail/update/set with no <group> setting does not remove the account from all groups.

Doing a mail/update/set with one <group> setting adds that account to that group, but does not
remove the account from all other groups.

EXPECTED RESULT

As with <alias>, mail/update/set with no <group> should remove the account from all mail groups.

As with <alias>, mail/update/set with one or more <group> elements should set the current group memberships
to just the groups selected, not the intersection of the existing group memberships and the new <group> elements sent.

ANY ADDITIONAL INFORMATION

Work around: For just groups, you MUST use mail/update/add and mail/update/remove.

===
Example:

mail/get_info response:

<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.5.2.0">
<mail>
<get_info>
<result>
<status>ok</status>
<mailname>
<id>51</id>
<name>test.user</name>
<mailbox>
<enabled>true</enabled>
<quota>-1</quota>
</mailbox>
<redirect>
<enabled>true</enabled>
<address>[email protected]</address>
</redirect>
<group>[email protected]</group>
<group>[email protected]</group>
<alias>robin</alias>
<password>xxxyyyzzz</password>
<password_type>plain</password_type>
<antivir>off</antivir>
</mailname>
</result>
</get_info>
</mail>
</packet>

mail/update/set request:

<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.5.2.0">
<mail>
<update>
<set>
<filter>
<domain_id>5</domain_id>
<mailname>
<name>test.user</name>
<redirect>
<enabled>true</enabled>
<address>[email protected]</address>
</redirect>
<group>[email protected]</group>
<alias>robin</alias>
<password>XXWWZZ123</password>
<password_type>plain</password_type>
</mailname>
</filter>
</set>
</update>
</mail>
</packet>

mail/update/set response:

<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.5.2.0">
<mail>
<update>
<set>
<result>
<status>ok</status>
<mailname>
<name>test.user</name>
</mailname>
</result>
</set>
</update>
</mail>
</packet>

mail/get_info response:

<?xml version="1.0" encoding="UTF-8"?>
<packet version="1.5.2.0">
<mail>
<get_info>
<result>
<status>ok</status>
<mailname>
<id>51</id>
<name>test.user</name>
<mailbox>
<enabled>true</enabled>
<quota>-1</quota>
</mailbox>
<redirect>
<enabled>true</enabled>
<address>[email protected]</address>
</redirect>
<group>[email protected]</group>
<group>[email protected]</group>
<group>[email protected]</group>
<alias>robin</alias>
<password>XXWWZZ123</password>
<password_type>plain</password_type>
<antivir>off</antivir>
</mailname>
</result>
</get_info>
</mail>
</packet>
 
Back
Top