PATCH /admin/api/v1/boxes/{email}/sieve fails
Issue #308
resolved
Attempt to update sieve filter via API still fails in v2.0.3 pro
Also, script parameter is missing in API doc (i guess it's because of the bug)
Comments (4)
-
-
reporter It does not work either way: No matter if port 4190 is exposed or not. It must be broken as it stopped working with the v2.x pro versions. Furthermore, getting sieve data via API is working, but not posting sieve data via API. Also, if it was be a port issue, neither would work.
-
repo owner - changed status to resolved
fixed in 2.0.4
-
reporter Cool, great! The API doc still misses the parameter if the SIEVE script though.
- Log in to comment
The API would be functioning within the docker container and therefore have access to port 4190, but just out of curiosity have you exposed port 4190 when running/starting your container??
-p 4190:4190