RunBox 7 webmail bugs that really annoy me

Runbox 7 Runbox 7 Webmail
#4

Hello @Arfa and thanks for your comments.

Performance issues with Runbox 7 are likely related to the generic backend problems that we have been working on and that are now mostly under control.

When using a local/synchronized index, folder navigation and searching should be near-immediate when operations are running normally, and when using a relatively modern device on a decent network connection.

If you notice lag, we would appreciate it if you would be able to check the Web Console in your browser’s Developer Tools for errors, as well as the Network tab in said tools for any delays in the communication with the server. Details from these can help us pinpoint where the specific issue lies.

Your experience could also be related to this issue which is under investigation:

Since indexing and synchronization is happening on the local device to achieve this functionality, changes in CPU load may occur on each index update (every 15 seconds) and this seems more noticeable on Windows systems depending on index size. We will look into this discrepancy further.

When accessing message content the front-end is using the same back-end as Runbox 6, but may be more sensitive to slowness on the servers and we are investigating this issue as well.

We are increasingly focusing on streamlining the UX to remove remaining points with performance issues. We have for instance made improvements to functionality such as marking (multiple) messages in the list, and are working on further improvements to make all functionality respond immediately.

Regarding HTML messages they are always sanitized for security reasons, a text version of the message should be shown if HTML view is not enabled (whether or not one was included with the email, which should be the case).

A related issue which may overlap with what you describe can be found here:

Regarding overall layout and vertical spacing, we have this existing issue:

I should emphasize that the majority of our users are very happy with Runbox 7, and that we are adding further resources to resolve remaining obstacles such as those described here.

– Geir

#5

@Geir
On the plus side of your comments I can see now that issues with the backend are affecting front end performance - not a surprise to me - and I guess this will all take time as you optimize the backend to work with RB7. But how do you know that a majority of your users are happy with RB7? Sorry this is not a facetious question. Dave has confirmed to me that only a fraction of your users are active on RB community site. So how are your getting feed back from the remaining users? Regards @johntowler

#6

For transparency @JohnTowler had asked about this privately and I said that “most of our customers don’t use the forum website” and this is easily evident from the number of people who contribute here. This is normal for community websites.

We receive comments in support tickets and also via the project on GitHub. We also have some statistics on how much use Runbox 7 gets. The majority of the comments are positive but of course people do also point out bugs at the same time along with improvements and suggestions for features that they would like to see.

#7

Some more info for you. Just loading up RunBox 7 today, to browse emails, this is the constant churn in the console:
Done persisting to indexeddb main.00db2efefc3e941ebda1.js:1:149398
Getting latest messages from server after
Date Tue May 26 2020 14:32:02 GMT+0100 (British Summer Time)
main.00db2efefc3e941ebda1.js:1:149398
Adding to index 10 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 9 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 8 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 7 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 6 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 5 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 4 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 3 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 2 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 1 to go main.00db2efefc3e941ebda1.js:1:149398
All messages added main.00db2efefc3e941ebda1.js:1:149398
us false main.00db2efefc3e941ebda1.js:1:149398
(folder:“Inbox” OR folder:“INBOX” ) main.00db2efefc3e941ebda1.js:1:149398
Persisting to indexeddb main.00db2efefc3e941ebda1.js:1:149398
store remote entry /rmmsearchservice966128/indexLastUpdateTime main.00db2efefc3e941ebda1.js:1:149398
store remote entry /rmmsearchservice966128/xapianglasswr/docdata.glass main.00db2efefc3e941ebda1.js:1:149398
store remote entry /rmmsearchservice966128/xapianglasswr/iamglass main.00db2efefc3e941ebda1.js:1:149398
store remote entry /rmmsearchservice966128/xapianglasswr/postlist.glass main.00db2efefc3e941ebda1.js:1:149398
store remote entry /rmmsearchservice966128/xapianglasswr/termlist.glass main.00db2efefc3e941ebda1.js:1:149398
stored remote entry /rmmsearchservice966128/indexLastUpdateTime 1402 main.00db2efefc3e941ebda1.js:1:149398
stored remote entry /rmmsearchservice966128/xapianglasswr/docdata.glass 1453 main.00db2efefc3e941ebda1.js:1:149398
stored remote entry /rmmsearchservice966128/xapianglasswr/iamglass 1453 main.00db2efefc3e941ebda1.js:1:149398
stored remote entry /rmmsearchservice966128/xapianglasswr/postlist.glass 2002 main.00db2efefc3e941ebda1.js:1:149398
stored remote entry /rmmsearchservice966128/xapianglasswr/termlist.glass 1712 main.00db2efefc3e941ebda1.js:1:149398
Done persisting to indexeddb main.00db2efefc3e941ebda1.js:1:149398
Getting latest messages from server after
Date Tue May 26 2020 14:32:02 GMT+0100 (British Summer Time)
main.00db2efefc3e941ebda1.js:1:149398
Adding to index 10 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 9 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 8 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 7 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 6 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 5 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 4 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 3 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 2 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 1 to go main.00db2efefc3e941ebda1.js:1:149398
All messages added main.00db2efefc3e941ebda1.js:1:149398
us false main.00db2efefc3e941ebda1.js:1:149398
(folder:“Inbox” OR folder:“INBOX” ) main.00db2efefc3e941ebda1.js:1:149398
Persisting to indexeddb main.00db2efefc3e941ebda1.js:1:149398
store remote entry /rmmsearchservice966128/indexLastUpdateTime main.00db2efefc3e941ebda1.js:1:149398
store remote entry /rmmsearchservice966128/xapianglasswr/docdata.glass main.00db2efefc3e941ebda1.js:1:149398
store remote entry /rmmsearchservice966128/xapianglasswr/iamglass main.00db2efefc3e941ebda1.js:1:149398
store remote entry /rmmsearchservice966128/xapianglasswr/postlist.glass main.00db2efefc3e941ebda1.js:1:149398
store remote entry /rmmsearchservice966128/xapianglasswr/termlist.glass main.00db2efefc3e941ebda1.js:1:149398
stored remote entry /rmmsearchservice966128/indexLastUpdateTime 994 main.00db2efefc3e941ebda1.js:1:149398
stored remote entry /rmmsearchservice966128/xapianglasswr/docdata.glass 1069 main.00db2efefc3e941ebda1.js:1:149398
stored remote entry /rmmsearchservice966128/xapianglasswr/iamglass 1056 main.00db2efefc3e941ebda1.js:1:149398
stored remote entry /rmmsearchservice966128/xapianglasswr/postlist.glass 1520 main.00db2efefc3e941ebda1.js:1:149398
stored remote entry /rmmsearchservice966128/xapianglasswr/termlist.glass 1499 main.00db2efefc3e941ebda1.js:1:149398
Done persisting to indexeddb main.00db2efefc3e941ebda1.js:1:149398
Getting latest messages from server after
Date Tue May 26 2020 14:32:02 GMT+0100 (British Summer Time)
main.00db2efefc3e941ebda1.js:1:149398
Adding to index 10 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 9 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 8 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 7 to go main.00db2efefc3e941ebda1.js:1:149398
checking for updates main.00db2efefc3e941ebda1.js:1:149398
Adding to index 6 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 5 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 4 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 3 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 2 to go main.00db2efefc3e941ebda1.js:1:149398
Adding to index 1 to go main.00db2efefc3e941ebda1.js:1:149398
All messages added main.00db2efefc3e941ebda1.js:1:149398
us false main.00db2efefc3e941ebda1.js:1:149398
(folder:“Inbox” OR folder:“INBOX” ) main.00db2efefc3e941ebda1.js:1:149398

With each round of “Persisting to indexeddb” to adding to all 10 indices, taking just over 18 seconds.
It just seems to be constantly busy, churning over, using up a fair chunk of CPU for little perceiveable gain. Whilst all the time having a sluggish UX as you try to load and render emails or long waits for UI updates to show message as marked red or deleted from a folder.

#8

@Arfa Thanks for the log. It appears the app is downloading the same indexed messages repeatedly, which is not normal.

There appears to be discrepancies in your account’s index on the server and we have initiated a re-index which should help. This could be caused by server issues that have since been resolved, or that certain messages caused errors in the indexing process.

Please stop and restart index synchronization in a few minutes. Note that this will trigger a re-download of the entire account index, but thereafter it should be kept in sync.

– Geir

#9

Dave, sorry but I still can’t believe that 23 MONTHS has past since I request you to add me to the beta test and two years later, you don’t have a functional new webmail version ready.

I was extremely hopeful in the beginning, thinking that we would have a completely new version soon, but things stays 90% the same since two years ago.

How is it possible?

The older version is slow, the HTML editor for new messages is heavy as NSA database.
The new one is faster, but all the interface of the webmail is green. VASTLY green, as it was two years ago.

Sorry but I can’t believe that most users are even “ok” with the “new” version, imagine SATISFIED.

Look at the contacts, the calendar, it’s all green. Bad looking. It’s like I developed this “new” version.

I paid 80 USD and got two years with the Max plan. After two years, I feel dumb to have paid again and at this time, with hope that something decent would be developed. Specially from a Norwegian company.
I am an user, with other logins, almost since the beggining of the service and I saw Fastmail being from something full of things and messy to a well done, well designed and extremely fast interface, whatever you are in your desktop using the browser, the native app for iOS and Android or anything. It just works. It just loads.

Mailfence is simple and fast also. Has less function than Fastmail, but its ripe. It’s a service and an interface that you can enjoy.

Tutanota also improved, even not being my really my thing.

And Mailbox.org, even with that HEAVY interface, full of details and functionalities, can be faster than the “new” old Runbox 7.

That’s all. Sorry to say wide open about the Runbox 7 version, but two years it’s time enough to build something 100% stable and bringing improvement just as it means, improvements, not bug fix that doesn’t finish the product at all, even after two years.

I was very hopeful to have a service faster, with more functionalities with the time, a pleasant and well done interface and in a sever that I can trust if not 100%, 99%, instead of my regular Fastmail account with the content storage in US. But life is not perfect.

And sorry for my 80 USD for nothing.

#10

Hello @mrh.izzo and welcome to the forum.

Runbox has always chosen to innovate and create new solutions to existing problems instead of simply copying other services. This is part of the reason Runbox 7 has taken longer to reach a stable and complete state than would have been preferred. You can find much more about our approach in this post.

We are generally quite satisfied and proud of Runbox 7, while we recognize that opinions will differ based on previous experience as well as platforms/devices and networks being used.

Therefore we are adding more resources to increase the rate of development of both bug fixes, improvements, and new functionality.

Perhaps you would like to expand on how you would like to see Runbox 7 improve, especially items that have not been discussed already.

– Geir

#11

Hello Geir,
maybe your satisfied and proud of your achievements at Runbox, but I’m not!

When I started my Runbox account some 4 years back, the Contacts and Calendar sync on Apple devices worked flawlessly. After launching the new Contacts and Calendar versions nothing is synced anymore and my 3 or 4 help tickets were forgotten eventually postponed.
As I understand, you received some grant to improve Runbox, I wonder that such situation is acceptable for donor?!

P.S. It is pure irony that after the Yahoo mail scandal I went to Runbox for more privacy and now as EU citizen to end again at an US entity where everything works!

#12

@Valdo If you are seeing errors when using Runbox Contacts (CardDAV) or Calendar (CalDAV) on your device then please create a new topic in Runbox Chat with details.

We have tried to find any unanswered support tickets as well but they might be under a different username, so if you open a new ticket we’ll be able to relate these issues.

It’s correct that Runbox is receiving funding from the Norwegian Research Council for our development of Runbox 7 and its browser-based email search engine, as described in the Runbox 7 Roadmap.

– Geir

1 Like
#13

@Geir

" please create a new topic in Runbox Chat" No, my final limit exhausted at #4!

#14

Back on the topic of the lack of speed on RB7 webmail

Once a month I switch from RB6 to RB7 to look at progress and performance but I keep switching back because, for instance, switching between folders in the mail can be reel slow, more than 10 seconds has been notices.
it doesn’t matter if my index is on or off. I use a chromium browser (Brave these days).
In RB6 all actions are instant (maximum of a second for a action) but RB7 doesn’t perform.

Did also a switch from RB6 to RB7 with the perfromance monitor on and clicking on the link to RB7 started around 2400 ms and at 12000 ms the inbox was visible. And in my feeling it is faster today as in other days.

I like the look of RB7 very much but performance keeps me switching back each time.

1 Like
#15

Adjustment to the previous post.

Today I switched from a mail that I opened last in a specific folder (where only mail from one source enters) and went back to the INBOX but it showed only the content of the previous folder (with the specific sender). Clicked the SENT folder and it showed the same mails but with the columns of that folder (To instead of From field). Back to INBOX gave me the previous view with the content of the specific folder.
Only after more than 30 seconds the content of the INBOX came in view.

Had just installed the last build: https://runbox.com/app/changelog?since=1594888673

#16

And the last follow up: the counter on folders is realy slow in updating. The specific folder mentioned above is still showing one unread where there’s no unread mails in the folder.

#17

@bassie.com Thanks for the feedback and the details.

We would be interested in screenshots from your browser’s Performance and Network tab as it could help pinpoint whether this is caused by network latency or slowness in the app itself, especially since you mention it’s independent of the use of a local index.

If the account is large (several hundred thousand messages) and using a local index it could be affected by this issue which we are working to resolve:

– Geir

#18

I’ve got screenshots of the performance screen but maybe you want the full json performance file and the network har file from the log? Give a reply if you want that.

I can enter only one image so here’s the performance screenshot

RB7-Profile-20200731T160650
RB7-Profile-20200731T1606503772×1040 453 KB

Did a login, ignored the update screen, when the inbox was visible, changed to the spam folder and when that was visible, changed back to the inbox, and this took a while till the content became visisble again. Then ended the performance recording.

#19

And here’s the network screenshot

RB7-Network-20200731T160650
RB7-Network-20200731T1606503840×1080 356 KB

#20

today 2 folders with new mails but no indication on the folder pane.
2 new in the inbox (anomized it for my privacy wbut you can see be two top mails are bold)
same for another folder.

image
image755×439 53.1 KB

NB: Got a brand new image on the laptop, new browsers, etc. so all up-to-date.

#21

Same here. And sometimes the reverse situation, i.e., the unread counter still stays on after the messages were read (and sometimes read and moved to another folder). That’s why I gave up on using the R7 web interface, along withthe issue of previously deleted messages still popping up as unread for a couple of seconds when logging into R7.I guess it’s the app updating the data or whatever, but it’s still raher unpleasant and misguiding.

#22

Please consider using IMAP retrieval if the app takes too long. Also, I found that limiting the number of concurrent connections to 4 at a time helped ease the congestion.

#23

As a new user, i can say that I have spent a good deal of time questioning my purchase of email service from runbox due to all the issues with accessing my account. the runbox7 app never keeps me logged in, and when it does load up, i cannot access the menu options. with the webmail, 7 is slow there, too. Using outlook, it takes a bit of time for mail to show up there, not so with other accounts on outlook.
i have no spent $7 on fairmail app and hopefully things improve