-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while loading messages #50
Comments
Please try again after enabling IMAP logging. Hopefully the imap log will shed more light on what's failing there. |
Added imap log |
Hm. That looks suspicious |
Well, the server seems to support SORT |
Hmm, any idea on how to proceed? I could get in touch with my provider, but they will most likely go "Well, other Mail-Clients work. Use ours, this one is supported". I have Roundcube running on the same server as well, works fine. Also, I could try to install horde and see if it works, but I'm not sure if I have all the necessary permissions for that... |
I'm pretty sure Lines 93 to 147 in 3249331
"UID SORT" seems to be the right command, see https://tools.ietf.org/html/rfc5256#section-4 Maybe we need to query the capability differently or more precisely… |
Well, sadly I don't have too much clue here, but maybe I can find some time in the evening to look into it. If you want me to try something, just let me know. |
Sure, go ahead. Would be great if we could debug and fix this together :-) |
Christoph, did you find out anything in the meantime? I could be looking into it now - any (new) suggestions where to start? |
Random suggestion but maybe can you test directly with your account / ISP using telnet? Over CLI - then copy/paste here. Simple tutorial is here. (There are lots of them on the web) - maybe try to duplicate the issue by hand going along with what is in your imap logs. |
Sorry, my Like, reading my own logfile, that my provider is using Courier-IMAP, apparently a 2008 version. In Roundcube's Forum I learned that Courier used to disable
I would not be surprised if this was the case for the version on my provider's server. For the moment, I commented out lines 143 and 145-147 in I know it will probably be impossible to get along with fake-advertised capabilities, but do you think you could somehow handle such a "lie" in a future version your app? If I can help, please just let me know. I wonder, how Roundcube does it. Maybe I can get their imap-logs and see what they do. BTW: now, that I can see and use the app: pretty cool, so far. Keep up the good work :-) |
What? Seriously? 😠 I knew not all servers support SORT, so I've added the check at Line 143 in 3249331
The problem is that we really want to use SORT as it gives a nice performance improvement when loading the list of messages (we need it sorted and paginated). Therefore I won't simply remove that one method. Hm… let me think about a solution |
well, we could wrap the SORT call in a try-catch block and use the slow fetching as fallback. Sounds hacky, but could work… |
Yep, I know - couldn't belileve what I was reading, especially that "advertising these capabilities, but rejecting the commands, will stop this silliness". Well, maybe there were some good reasons back in '08, but honestly: why would the client have to know that much detail about the server? Regarding the fix I was also thinking of a try/catch. At least it would make the app working with medieval mailservers and that is a benefit for users of such while not causing troubles for others. In any case: Thanks for your support! I'll try to find out more about the mailserver and its version tomorrow. Would you kindly ping me if a new version is shipped? |
Could you please try that and if that works, submit a pull request? If I'd fix it, I couldn't test it :-)
Sure. You can also star/watch the repo, then you'll be notified about releases AFAIK. You are also welcome to join us on IRC in #nextcloud-mail on freenode, help.nextcloud.com 💃 |
And there's an important event next week – the Nextcloud conf https://conf.nextcloud.com come and join us in Berlin ;-) |
I'm running Courier-imap as well and can confirm. Tested via telnet, and with
...so it looks like the ISP has set
...as far as app:mail, I guess upon error for the command it could fallback to same behavior as if SORT is not advertised. Looks like more of an imap server config issue though, since they disabled serverside THREAD and SORT but did not remove it from their |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and questions. |
Steps to reproduce
Expected behaviour
Load messages of inbox folder
Actual behaviour
Shows spinner and error "Error while loading messages". Since the app can load all the inbox folders, I would say that auth is okay. Mailserver is on the same host - I tried localhost as well as full domain names-
Mail app
Mail app version: 0.5.3
Mailserver or service: imap
Transport security - IMAP: SSL
Transport security - SMTP: STARTTLS
Number of accounts: 1
Server configuration
Operating system: Ubuntu
Web server: Apache 2.2.14
Database: MySQL 5.1.73
PHP version: 5.5.19
Version: 10.0.0
Updated from an older version or fresh install: fresh install
Client configuration
Browser: Chrome
Operating system: Windows 10
Logs
Web server error log
Server log (data/nextcloud.log)
The text was updated successfully, but these errors were encountered: