Opened 5 years ago
Closed 5 years ago
#1484784 closed Bugs (fixed)
unable to stop large folder loading
| Reported by: | EarlGrey | Owned by: | |
|---|---|---|---|
| Priority: | 5 | Milestone: | 0.2-stable |
| Component: | IMAP connection | Version: | 0.1-rc2 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
When loading a large folder (containing over 6000 spam emails), the tranfer takes time, which is ovious. However, I found no other way how to stop this transfer other than closing the tab.
Change History (4)
comment:1 Changed 5 years ago by seansan
- Milestone set to 0.1.1
comment:2 Changed 5 years ago by robo45h
I would like to point out that large folders should not to be considered unusual. It is very common for me (and many of my associates) to have an Inbox (or other folder) with thousands of messages. Mine has over 10,000 (with 200 unread at the moment, though I've looked at the Subject lines). I know people with many, many more messages than that. This is not behavior RoundCube should expect to change; it's a situation it needs to handle. SquirrelMail? works just fine with mailboxes this size -- as long as you enable server-side sorting (which, I'm lead to believe, is on by default in RoundCube).
The need to "cancel" out of a large mailbox transaction would be nice, but that is not the proper solution for the situation that was noted as the cause (large folder). The proper solution is that loading a large folder should not take this long. It doesn't in Thunderbird. It doesn't in SquirrelMail?.
comment:3 Changed 5 years ago by uwolfer
I support the comment of robo45h:
Roundcube really needs to handle big folders in a good way. At the moment if have to wait for folders with several 10'000 messages (for example mailing lists) for minutes until they are displayed in roundcube.
comment:4 Changed 5 years ago by alec
- Component changed from Client Scripts to IMAP connection
- Resolution set to fixed
- Status changed from new to closed
It was fixed in trunk.

Dupe of #1484690 - leaving open for review in 0.1.1 as this is the second account. Maybe has something to do with PHP max execution time