touch-packages team mailing list archive

[Jeffrey Hutzelman <1367779@xxxxxxxxxxxxxxxxxx>]

** Description changed:

  The IMAP QUOTA extension permits the list of resource-usage-limit tuples
  in an untagged QUOTA response to be empty (see RFC2087 section 5.1,
  which states "The list contains zero or more triplets".  This happens
  when the server supports quotas, but no quota is set on a particular
  mailbox.
  
  However, e-d-s does not handle this case, and instead reports an error
  parsing the server response.  This prevents opening the Properties
  dialog for folders in this state.
  
  In effect, this is a regression since raring.  Support for the IMAP
  QUOTA extension was introduced in 3.7.3; prior to that, there was no
  quota support, but users were able to open the folder properties.
  
  This is reported upstream as GNOME #735200
  (https://bugzilla.gnome.org/show_bug.cgi?id=735200) and has been fixed
  in 3.12 and later.  However, trusty has 3.10.4, which upstream declined
  to fix.  The attached patch applies the same fix to 3.10 which was
  accepted upstream for later versions.
  
  [Test Case]
  This requires an IMAP server which supports the QUOTA extension, allows
  some mailboxes to have no quota assigned even when the extension is
  enabled, and which (correctly) responds to QUOTA or QUOTAROOT requests
  relating to that mailbox by including an empty resource list.  Current
  Cyrus IMAP is one example of such a server that meets this requirement.
  
  Naturally, it also requires a folder with no quota, and which is
  accessible to the user performing the test.
  
  The test, then, is simple:  Right-click on the folder in question in
  Evolution, and select "Properties".  When the test is successful, this
  opens a dialog showing settings and status information for the folder.
- With the bug, instead an error is shown.
+ With the bug, instead an error is shown:
+ 
+ >> Failed to open folder.
+ >> The reported error was "Error retrieving quota information:
+ >> expecting atom".
  
  [Regression Potential]
  Low.  This is a relatively small patch to code which parses untagged
  QUOTA responses, plus a change in return code when a mailbox has no quota assigned.  It affects only IMAP folders, and only on servers
  which support the QUOTA extension.  It is possible that a bug could
  result in mis-parsing of QUOTA responses which are currently handled
  correctly, which would result in the same symptoms as this bug (but
  under different circumstances).  Since the patch affects code which is
  used only to parse QUOTA responses, it cannot result in incorrect
  handling of other responses from the server.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1367779

Title:
   [IMAPx] Fails to handle QUOTA response with no quotas

Status in Evolution Data Server:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released

Bug description:
  The IMAP QUOTA extension permits the list of resource-usage-limit
  tuples in an untagged QUOTA response to be empty (see RFC2087 section
  5.1, which states "The list contains zero or more triplets".  This
  happens when the server supports quotas, but no quota is set on a
  particular mailbox.

  However, e-d-s does not handle this case, and instead reports an error
  parsing the server response.  This prevents opening the Properties
  dialog for folders in this state.

  In effect, this is a regression since raring.  Support for the IMAP
  QUOTA extension was introduced in 3.7.3; prior to that, there was no
  quota support, but users were able to open the folder properties.

  This is reported upstream as GNOME #735200
  (https://bugzilla.gnome.org/show_bug.cgi?id=735200) and has been fixed
  in 3.12 and later.  However, trusty has 3.10.4, which upstream
  declined to fix.  The attached patch applies the same fix to 3.10
  which was accepted upstream for later versions.

  [Test Case]
  This requires an IMAP server which supports the QUOTA extension, allows
  some mailboxes to have no quota assigned even when the extension is
  enabled, and which (correctly) responds to QUOTA or QUOTAROOT requests
  relating to that mailbox by including an empty resource list.  Current
  Cyrus IMAP is one example of such a server that meets this requirement.

  Naturally, it also requires a folder with no quota, and which is
  accessible to the user performing the test.

  The test, then, is simple:  Right-click on the folder in question in
  Evolution, and select "Properties".  When the test is successful, this
  opens a dialog showing settings and status information for the folder.
  With the bug, instead an error is shown:

  >> Failed to open folder.
  >> The reported error was "Error retrieving quota information:
  >> expecting atom".

  [Regression Potential]
  Low.  This is a relatively small patch to code which parses untagged
  QUOTA responses, plus a change in return code when a mailbox has no quota assigned.  It affects only IMAP folders, and only on servers
  which support the QUOTA extension.  It is possible that a bug could
  result in mis-parsing of QUOTA responses which are currently handled
  correctly, which would result in the same symptoms as this bug (but
  under different circumstances).  Since the patch affects code which is
  used only to parse QUOTA responses, it cannot result in incorrect
  handling of other responses from the server.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1367779/+subscriptions