API mail/list error 400

jerry

Sometime in the last couple of days, requests to list all email addresses (https://my.opalstack.com/api/v0/mail/list/) has started returning an error 400, with the response {"error": "error"}.

Requests to list all mail users (https://my.opalstack.com/api/v0/mailuser/list/) continues to work.

Error 400—malformed request—seems to indicate that the server is now expecting something different than what it used to?

The documentation (https://my.opalstack.com/api/v0/redoc/#operation/List%20Email%20Addresses) still lists https://my.opalstack.com/api/v0/mail/list/ with no parameters.

sean

jerry mail/list seems to work fine in my own testing, eg:

curl --header "Content-Type:application/json" --header "Authorization: Token my-api-token-here"  https://my.opalstack.com/api/v0/mail/list/

Can you try the call like that and let me know if it works for you?

jerry

Same thing:

> curl --header "Content-Type:application/json" --header "Authorization: Token my-token"  https://my.opalstack.com/api/v0/mail/list/
{"error": "error"}%

If I add --head, I get:

HTTP/1.1 405 Method Not Allowed
Server: nginx
Date: Tue, 17 Nov 2020 21:18:50 GMT
Content-Type: application/json
Content-Length: 41
Connection: keep-alive
Vary: Accept
Allow: OPTIONS, GET
X-Frame-Options: DENY
X-Content-Type-Options: nosniff

sean

jerry It looks like it has something to do with the number of email records that you have in the database. I'll open a bug report.

sean

jerry actually it looks like this was caused by some bad data on the backend. I've corrected that and you should be able to use mail/list now.

jerry

Thanks. Looks good now.