-
-
Notifications
You must be signed in to change notification settings - Fork 426
Problem with API and mailboxes-list and mailboxes-read #1582
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
Comments
Again me. How to found armessages ID? I was thinking that we can have it with /api/v1/accounts/mailboxes but I don't know as the API doesn't work. With /api/v1/accounts/ we don't get it (only mailbox pk ID) and in /armessages we can only search with the armessages ID. Maybe adding the accounts ID in armessages would be easier to access to the data. |
@stefaweb I think the bug you encounter with API is due to the radicale plugin. Are you browsing the API as default administrator? (which has no mailbox) If so, just switch to a user with a mailbox and it will work again. |
Sorry for this late answer. I was too busy. For the error 500, you're right. I was using admin. No 500 error using a login with mailbox. |
See in modoboa/modoboa-radicale#40 |
Seems the API is no longer working with last modoboa version.
If I go to https://mailserver/docs/api/#mailboxes-list/api/v1/mailboxes/, I got an error 500.
In /var/log/uwsgi/app/modoboa_instance.log:
GET /api/v1/mailboxes/ => generated 870 bytes in 217 msecs (HTTP/1.1 500) 5 headers in 181 bytes (1 switches on core 0)
Same if I use
/api/v1/mailboxes/{id}/
.EDIT : The new API module /api/v1/armessages/ seems to work but as /mailboxes don't work, I can access to the data.
The text was updated successfully, but these errors were encountered: