-
Notifications
You must be signed in to change notification settings - Fork 38
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
Second sync fails #12
Comments
So I'm no python developer, but I did some debugging. It seems to check for a json field "type: error" (I'm guessing mailcow would return this in some cases?). Mailcow had some API related updates on August 7, I'm guessing maybe that's related? |
For reference, this is what an API request returns with /api/v1/get/mailbox/[email protected]
|
I fixed it! I was slightly off. you just need to replace de field "active_int" with "active" in api.py. I'm using a custom api.py for now |
@zeroone82 |
I've been trying to get this working and I have been able to get an initial sync at least. It will add my one test user, but then it fails on the second sync:
This a very basic user, has a username, first and last name and nothing else. Should I add another field too?
My docker-composer setup is:
The text was updated successfully, but these errors were encountered: