-
Notifications
You must be signed in to change notification settings - Fork 138
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
[BUG] - ManageSieve unreachable #394
Comments
Hello! I have the same problem Thank you! |
I had the same issue and after some digging around, this seems to be caused by a conditional configuration for dovecot inside the front container: This variable is set through the configmap envvars
which is filled by _services.tpl helm-charts/mailu/templates/_services.tpl Lines 171 to 205 in 98da259
So, if you just enable ingress, and don't set front.externalService.enabled = true, PORT_4190 is not set and thus, 14190 is not available. I am not sure though if this is intended behaviour, because i am using hostPort.enabled = true (the default) and these two options seem mutually exclusive according to docs? https://github.com/Mailu/helm-charts/tree/master/mailu#exposing-mail-ports-to-the-public Long story short: I changed PORTS: 80,443 to PORTS: 80,443,4190 in the configmap and now everything works :) |
Ohh that sounds amazing! A working sieve would be so awesome! You mean that I edit the deployed ConfigMap after Helm has run. Let me try it. |
Thank you @NewBlade Your solution solved my problem |
Thank you @NewBlade, worked for me either. I added the Port 4190 to the ConfigMap "mailu-envvars" after the helm release was deployed and restartet front-pods. |
Describe the bug
In roundcube > Settings > Filter a connection problem occures.
To Reproduce
Steps to reproduce the behavior (include specific Helm or Kubernetes commands if applicable):
Expected behavior
I would like to edit sieves, but there seem to be a problem.
Environment (please complete the following information):
Values.yaml Configuration
Please provide your
values.yaml
configuration file or the relevant parts of it (ensure sensitive data is redacted).Additional information
I my kinda curious, is managed sieve supported or not. There are many issues and many pr's about that topic.
Shoud it work or is is daed?
Should it work out-of-the-box or can I do sth. to make is work?
The text was updated successfully, but these errors were encountered: