lsflk / copper Goto Github PK

Check services are running properly
Check resource allocation for containers
Check error logs

Enable https access for webmail (rainloop) based letsencrypt certbot.

Mail archiving and backup are very important aspects of a mail server. And also the recovery part. We are planing to get them to the production level by getting support of k8s volumes.
https://kubernetes.io/docs/concepts/storage/volumes/

Even though internal mails can be sent , mails to gmail is not working.

Current inbox refresh time interval is 120 secs and it need to be reduced to 10 secs.

References
RainLoop/rainloop-webmail#1222

Mail encrypt dovecot configurations update for keep all the emails with asymmetric key based encrypted versions.

Check Dashboard (if required )
Check services are running properly
Check resource allocation for containers
Check error logs

Research existing Generic Agent models
Research Kubernetes APIs to integrate with agent

Can't access the backup folder when we tried to build dockers again.

sub task :

• Introduce software update handling method based on generic agent model
• testing update handling
• Copper-hub side implementation for show updated instances and related information as central admin dashboard

enable TLS connection between email server and LDAP

Expected to integrate a database to the copper email solution with Kubernetes .

https://kubernetes.io/docs/tasks/run-application/run-single-instance-stateful-application/

This is related to the admin side of the deployment

setup telegraf agent in email_service container and get summary data of postfix logs into grafana ui through the influxDB(as a time series db)

Rainloop doesn't provide calendar plugin. So this is a must for the system.

References

https://rainloop.uservoice.com/forums/223477-ideas-for-rainloop-webmail/suggestions/6365576-calendar-or-remote-caldav

RainLoop/rainloop-webmail#1275

ldap configurations added to mail server and use ldap user management for entire email solution with phpLDAPadmin interfaces.

sub tasks :

• integrate suitable model with the core, for alerting management purposes.
• testing alerting & monitoring process
• connect with slack/email or any related communication method.

With the current configuration PC slow down when the copper mail solution run on a kubernetes cluster. So The reason for this slowness should be investigated and recorrect.

Integrate horde groupware as a webmail client with support of k8s.

Email must be stored in a volume which at the host, not inside the container.

This is a core function for Cu-mail. After some research we came up with an idea to use prometheus (https://prometheus.io/) to solve this problem.

Idea is to have an agent per service to collect data from every single container.

Tasks is a main functionality of a mail system and it should be added as an enhancement.

Initial design for generic agent model.

get a warning in rainloop admin general view

"RainLoop data folder is accessible. Please configure your web server to hide the data folder from external access. Read more here: https://www.rainloop.net/docs/installation"

centralized configurations (.env) by introducing new config parameters for postfix/dovecot

When we select particular mail thread, a side panel will give some visual summary about the recent flow of that thread. This will be a good modification to give a clear idea about the flow and history of a mail thread.

mail.log in error in /var/lib/mail.log file:

warning: cannot get RSA certificate fro
m file "/etc/letsencrypt/live/mail.nextgenmed.dyndns.org/fullchain.pem": disabli
ng TLS support

Resolve mail sending bug

create a simple document about how this k8s based deployment can be setup in a local machine or a remote server.

Rainloop has developed something similar like address book. (refer below url)

But Cu-mail needs a separate address book. (Not like rainloop mentioned address book in below url)

RainLoop/rainloop-webmail#27

add TLS (startTLS) security support for openldap user management service.

Copper team has decided to go for new groupware due to horde obsolete UI. So Groupoffice groupware should be integrated with Kubernetes support.