Good afternoon,
Some of my customers are using an IMAP access and send their emails through the SMTP server.
The problem is, port 25 is generally blocked by the ISP here in Belgium to prevent spam.
I noticed that Grommunio doesn't provide smtps or submissions out of the box.
So I thought it was time to test this "dbconf" feature accessible via the admin part or the cli... Examples in the docs show screenshots with postfix... Great.
But everytime I create a config, there is an error appearing on the screen:
The server encountered an error while processing the request.
Looking a bit further I find some details in the API log:
Autorefresh
2021-10-06 17:09:47.976395: File "/usr/lib/python3.6/site-packages/werkzeug/routing.py", line 911, in match
2021-10-06 17:09:47.976395: raise RequestPath(path)
2021-10-06 17:09:47.976395: werkzeug.routing.RequestPath: /api/v1/system/dbconf/postfix/main.cf/
2021-10-06 17:09:47.976395: During handling of the above exception, another exception occurred:
2021-10-06 17:09:47.976395: Traceback (most recent call last):
2021-10-06 17:09:47.976395: File "/usr/lib/python3.6/site-packages/flask/app.py", line 1813, in full_dispatch_request
2021-10-06 17:09:47.976395: rv = self.dispatch_request()
2021-10-06 17:09:47.976395: File "/usr/lib/python3.6/site-packages/flask/app.py", line 1791, in dispatch_request
2021-10-06 17:09:47.976395: File "/usr/lib/python3.6/site-packages/flask/app.py", line 1774, in raise_routing_exception
2021-10-06 17:09:47.976395: raise request.routing_exception
2021-10-06 17:09:47.976395: File "/usr/lib/python3.6/site-packages/flask/ctx.py", line 336, in match_request
2021-10-06 17:09:47.976395: File "/usr/lib/python3.6/site-packages/werkzeug/routing.py", line 1878, in match
2021-10-06 17:09:47.976395: werkzeug.routing.RequestRedirect: 308 Permanent Redirect: None
2021-10-06 17:09:47.976395: [WARNING] (flask.app) PUT /api/v1/system/dbconf/postfix/main.cf? from IP -> 500 '{"message":"The server encountered an error while processing the request."}\n'
Does someone have more chance than I do?
I'm using the community edition at the moment and the update is not solving the problem.
(I have a licence ready to use but I wait for the debian packages before proceeding with a definitive installation)