-
Notifications
You must be signed in to change notification settings - Fork 1
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
Update mail server configuration and random TCP port #7
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to rename action set-bcc-piler :)
7254b49
to
ae6cf75
Compare
14d63b5
to
c21d7dd
Compare
…-relay-rule mail action
… no default volumes
…lay and set BCC address
528cc8c
to
e52bb10
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but...
… and http2https environment variables
…lay and set BCC address using os.environ['MODULE_ID']
Should be good @DavidePrincipi |
Co-authored-by: Davide Principi <davide.principi@nethesis.it>
…arting the service
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This pull request includes updates to the mail server configuration and TCP ports. It also adds a script to restart the piler service when mail settings are changed.
the biggest change is we could have as many archive we want on the same server, we reclaim to the core two ports (one for traefik, one for smtp connection)
refs: NethServer/dev#6895
it needs NethServer/ns8-mail#109 to set the bcc in ns8-mail
When we first configure the archive, we import the emails, during the time the service runs to import we display a banner. the service could be started again by the CLI as many you need it.
When the restoration occurs for the example mail1 module, we start to restore a new module lets say piler2 and configure it, but when we remove piler1 if we have no errors, the destroy-module action remove the always bcc set in the mail server and let unconfigured always_bcc for piler2. So I display a banner in UI to let the admin knows that the always_bcc is not set in the mail server (just press save to configure again the piler module)