242396 - Mail: Quota alert popup window redisplays forever

Status: NEW

(MailNews Core :: Networking: IMAP, defect)

Description

[tom.blom]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040421
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040421

After doing 'Compact Folders' in Mail I get the following popup message:

Alert 
Mailbox is at 93% of quota

When I click 'OK' the same alert popup will display again. This will probably go
on forever. The only way to get out of this loop is to kill Mozilla with Windows
Task Manager and restart Mozilla. 

The same quota alert displayed at tne beginning of the session will not
redisplay after clicking 'OK'.

Details: 
IMAP Mail Server

Reproducible: Always
Steps to Reproduce:
1. Mail quota is over 90 % (?); IMAP Mail Server
2. Press DEL to mark messages to be deleted in Mozilla Mail
3. Select File - Compact Folders
4. Click 'OK' to dispose the alert popup window. Repeat this step.

Actual Results:  
The quota alert popup window will redisplay forever

Expected Results:  
The alert window should not redisplay after first time. At least one should not
get stuck by the redisplaying alert window.

Comment 1

[David :Bienvenu]

can you generate an imap protocol log? the server shouldn't give us an infinite
number of quota alerts, so I'd like to see what it's doing. Thx. Here are the
instructions for generating a protocol log.

http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap

Comment 2

[tom.blom]

(In reply to comment #1)
> can you generate an imap protocol log? the server shouldn't give us an infinite
> number of quota alerts, so I'd like to see what it's doing. Thx. Here are the
> instructions for generating a protocol log.
> 
> http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap

A small part of the log is included below. It seems that the alert popup is
produced separetely for each folder (not infinitely - tested). I have tens of
folders.


2384[2b9bd30]: ReadNextLine [stream=2e62d28 nb=20 needmore=0]
2384[2b9bd30]:
2c15c30:ml.mappi.helsinki.fi:S-INBOX.TB.TB_Ope_fi_II:CreateNewLineFromSocket: *
OK [UIDNEXT 34] 

2384[2b9bd30]: ReadNextLine [stream=2e62d28 nb=41 needmore=0]
2384[2b9bd30]:
2c15c30:ml.mappi.helsinki.fi:S-INBOX.TB.TB_Ope_fi_II:CreateNewLineFromSocket: *
NO [ALERT] Mailbox is at 91% of quota

2384[2b9bd30]: ReadNextLine [stream=2e62d28 nb=31 needmore=0]
2384[2b9bd30]:
2c15c30:ml.mappi.helsinki.fi:S-INBOX.TB.TB_Ope_fi_II:CreateNewLineFromSocket:
287 OK [READ-WRITE] Completed

...

884[2965bf0]: ReadNextLine [stream=2c46e00 nb=20 needmore=0]
884[2965bf0]:
2bb1020:ml.mappi.helsinki.fi:S-INBOX.TB.TB_SGOY:CreateNewLineFromSocket: * OK
[UIDNEXT 15] 

884[2965bf0]: ReadNextLine [stream=2c46e00 nb=41 needmore=0]
884[2965bf0]:
2bb1020:ml.mappi.helsinki.fi:S-INBOX.TB.TB_SGOY:CreateNewLineFromSocket: * NO
[ALERT] Mailbox is at 91% of quota

884[2965bf0]: ReadNextLine [stream=2c46e00 nb=31 needmore=0]
884[2965bf0]:
2bb1020:ml.mappi.helsinki.fi:S-INBOX.TB.TB_SGOY:CreateNewLineFromSocket: 280 OK
[READ-WRITE] Completed

Comment 3

[David :Bienvenu]

oh, you compacted all the folders - yes, that causes us to select and expunge
all the folders, one by one. I suppose we could detect an error attempting to
compact the first folder, and ask you if you want to continue...

Comment 4

[tom.blom]

(In reply to comment #3)
> oh, you compacted all the folders - yes, that causes us to select and expunge
> all the folders, one by one. I suppose we could detect an error attempting to
> compact the first folder, and ask you if you want to continue...

Is there a way to compact only one or some folders? Usually it is Inbox that
needs  compacting after messages are marked as deleted.

Comment 5

[Christian Eyrich]

What about right click on the inbox folder and choosing "Compact This Folder"?

Comment 6

[Jarmo Sorvari]

(In reply to comment #3)
> oh, you compacted all the folders - yes, that causes us to select and expunge
> all the folders, one by one.

But this is a new bug introduced in version 1.7! I have been doing "Compact
Folders" all the time (pre-1.7) and it has worked logically (quota notification
only once).

>I suppose we could detect an error attempting to
> compact the first folder, and ask you if you want to continue...

Mailbox quota notification is per-mailbox information, not per-folder
information. Just showing the alert once per "Compact Folders" operation is the
right thing to do. Which is how it has been working so far!

Comment 7

[David :Bienvenu]

file | compact folders, up until now, had a bug - it only compacted the current
folder, instead of all folders in the account. To compact just the current
folder, you use the context menu in the folder pane to "compact this folder".
File | compact folders should be File | Compact All Folders.

Comment 8

[Jarmo Sorvari]

(In reply to comment #7)
> file | compact folders, up until now, had a bug - it only compacted the current
> folder, instead of all folders in the account. To compact just the current
> folder, you use the context menu in the folder pane to "compact this folder".
> File | compact folders should be File | Compact All Folders.

OK, understood.

But I hope everyone agrees that the quota alert aspect does not work like it
should (doing "Compact All Folders" when you have, say, 100 folders, is a
nightmare). Hopefully someone has time to fix this one soon!

Comment 9

[Steffen Prohaska]

Bug 247193 is a duplicate of this one.

Comment 10

[rsx11m]

Not sure about comment #9. This is a Core bug whereas bug 247193 is specific
for Thunderbird. From the discussion there, both some backend logic would be
needed to identify quota messages and any duplicates, and some front end for
a log-viewer type user interface. Thus, keeping both bugs may be justified. 

Comment 12

[Wayne Mery (:wsmwk)]

Many bugs from that era - https://mzl.la/3v0l6Ha, but only this, bug 247193 and bug 261940 remain open.
Any reason to believe this issue still exists? (I don't recall ever seeing it or reports of it.)

Comment 13

[Magnus Melin [:mkmelin]]

I don't think this is an issue these days.

Comment 14

[gene smith]

We updated the imap quota code a few years ago and I haven't heard anything about it since. So I also doubt that this is still an issue.
(Sorry for the slow response to the NI.)