301739 - IMAP Quota parsing fails on AIM mail

Status: RESOLVED INVALID

(MailNews Core :: Networking: IMAP, defect)

Description

[Brian Kennelly]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050721 SeaMonkey/1.0a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050721 SeaMonkey/1.0a

With an IMAP account on AIM (imap.aim.com), the Quota property page shows "There
are no storage quotas on this folder."

imap.aim.com returns a standards-compliant response, but one that is not
recognized by the parser.

Example:
. getquotaroot INBOX
* QUOTAROOT INBOX "AIM Standard"
* QUOTA "AIM Standard" (items 4 2147483647 storage-kbytes 53 2097152)
. OK GETQUOTAROOT completed

The quota parser only recognizes storage limits in the form "(STORAGE # #)"


Reproducible: Always

Steps to Reproduce:
1. Set up a (free) AIM mail account at aim.com
2. Add an IMAP account for imap.aim.com 
3. View the properties for any folder on the account, select the Quota page.

Actual Results:  
"There are no storage quotas on this folder."

Expected Results:  
The Quota root and usage should have been displayed.

Comment 1

[Stephen Donner [:stephend] Not actively reading bugmail]

476[2381158]: 2378348:imap2.indiana.edu:S-INBOX:SendData: 18 getquotaroot "INBOX"

2228[3e17fa8]: 21e5e50:imap2.indiana.edu:NA:SendData: Logging suppressed for
this command (it probably contained authentication information)
476[2381158]: ReadNextLine [stream=23813d0 nb=33 needmore=0]
476[2381158]: 2378348:imap2.indiana.edu:S-INBOX:CreateNewLineFromSocket: *
QUOTAROOT INBOX user.stdonner

476[2381158]: ReadNextLine [stream=23813d0 nb=46 needmore=0]
476[2381158]: 2378348:imap2.indiana.edu:S-INBOX:CreateNewLineFromSocket: * QUOTA
user.stdonner (STORAGE 50450 102400)

476[2381158]: ReadNextLine [stream=23813d0 nb=17 needmore=0]

Comment 2

[Stephen Donner [:stephend] Not actively reading bugmail]

Attachment: Full log

This was with trunk build 2005-07-22-05 on Windows XP.

Comment 3

[Stephen Donner [:stephend] Not actively reading bugmail]

Sorry, pasted the wrong thing.  Here's the relevant part from imap.aim.com logs:

760[22d7780]: 24476c8:imap.aim.com:S-INBOX:SendData: 7 getquotaroot "INBOX"

760[22d7780]: ReadNextLine [stream=3dc0588 nb=34 needmore=0]
760[22d7780]: 24476c8:imap.aim.com:S-INBOX:CreateNewLineFromSocket: * QUOTAROOT
INBOX "AIM Standard"

760[22d7780]: ReadNextLine [stream=3dc0588 nb=70 needmore=0]
760[22d7780]: 24476c8:imap.aim.com:S-INBOX:CreateNewLineFromSocket: * QUOTA "AIM
Standard" (items 2 2147483647 storage-kbytes 1 2097152)

760[22d7780]: ReadNextLine [stream=3dc0588 nb=29 needmore=0]
760[22d7780]: 24476c8:imap.aim.com:S-INBOX:CreateNewLineFromSocket: 7 OK
GETQUOTAROOT completed

Comment 4

[Mikael Parknert]

It seems like the major problem here is that RFC2087 
(http://www.apps.ietf.org/rfc/rfc2087.html) does not
define the QUOTA atoms to used by servers, but
it seems like STORAGE & MESSAGES are common.

some examples:
Cyrus, courier and uw-imap define STORAGE (aim: storage-kbytes)
courier also defines MESSAGES (aim: items)

Comment 5

[Chris Eastlund]

This does work if the response starts '(STORAGE <num> <num>', but RFC2087 doesn't specify an order.  Any chance that the parsing will take that into account?

Comment 6

[Wayne Mery (:wsmwk)]

we're still stuck on comment comment 4


brian, reporter, writes 
AOL no longer seems to have quotas:
    . getquotaroot INBOX
    * QUOTAROOT "INBOX"
    . OK GETQUOTAROOT completed
So, the problem does not exist in its original form.

Comment 7

[Wayne Mery (:wsmwk)]

And AIM is gone