← Back to team overview

touch-packages team mailing list archive

[Bug 1367779] [NEW] [IMAPx] Fails to handle QUOTA response with no quotas

 

Public bug reported:

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.

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.

** Affects: evolution-data-server
     Importance: Unknown
         Status: Unknown

** Affects: evolution-data-server (Ubuntu)
     Importance: Undecided
         Status: New

** Patch added: "patch for e-d-s 3.10 to handle QUOTA responses with an empty resource lists"
   https://bugs.launchpad.net/bugs/1367779/+attachment/4200644/+files/imapx-empty-quota-3.10

** 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.
+ 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.
+ 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.
  
- 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.
+ 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.

** Bug watch added: GNOME Bug Tracker #735200
   https://bugzilla.gnome.org/show_bug.cgi?id=735200

** Also affects: evolution-data-server via
   https://bugzilla.gnome.org/show_bug.cgi?id=735200
   Importance: Unknown
       Status: Unknown

-- 
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:
  Unknown
Status in “evolution-data-server” package in Ubuntu:
  New

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.

  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.

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


Follow ups

References