UCS+Kopano mail location?

Apps & App Center
#1

I’m curious to know where the mail is stored when using Kopano? it’s looking like emails are stored in the database, and attachments are stored in the file-system??

If so, how can I safely delete all email from the system… I have finished my testing and would like to clear everything out before I move it into the network and let them use imapsync to migrate everything over (which works perfectly)

Thanks!

#2

hrm… after doing some more research i found the kopano-cli command… would removing the store from the users be enough? will the system re-create a store for a user when a new mail is delivered or when they log in?

#3

The way to make sure that everything is deleted is to drop the Kopano database and remove /var/lib/kopano (while all Kopano services have been stopped).

To remove a store you’d have to unhook it first. After you have unhooked the store you need either create a new store or to hook an existing store to the user.

If you really want to start over the part of this answer before the quote is the more thorough one.

#4

Thank you… so will the db be created automatically again? or will I need to manually populate it with default info?

is there a way just to delete only the emails, but leave settings intact ??

#5

yes, if the server doesn’t find the configured database it will create a new one (as long as the configured mysql user has the permissions to do so, but that is the case on ucs).

Depends on what kind of settings you are talking about. general system configuration is stored below /etc/kopano and not stored in the database and will not be impacted by this.

User settings are stored in the mailbox of the user and would be removed by dropping the database (but would as well when just removing the store). ´kopano-backup´ is capable of backing up and restoring this kind of “meta data”.

#6

Again, thank you very much. I will try stopping the kopano service and drop the db… I would love to purchase a subscription but being a volunteer fire department I simply don’t have the budget… Kopano is a fantastic package. Thank you very much for all the work that has gone into it.

1 Like
#7

Hello @fbartels when you say the services, i’m assuming all of these must be stopped?

root@ucs2:/var/lib/kopano# ps aux | grep kopano
kopano     464  0.0  0.3 313424 10732 ?        Ssl  Mar22   0:15 /usr/sbin/kopano-spooler -F
kopano     470  0.0  0.3 140532  9588 ?        Ss   Mar22   0:01 /usr/sbin/kopano-ical -F
kopano     472  0.0  0.6 377332 21236 ?        Ssl  Mar22   2:28 /usr/bin/python2 /usr/sbin/kopano-search -F
kopano     475  0.0  0.2 178836  9120 ?        Ssl  Mar22   0:00 /usr/sbin/kopano-dagent -l
kopano     484  0.0  0.8 288364 25280 ?        Ss   Mar22   7:06 /usr/sbin/kopano-gateway -F
kopano     485  0.0  0.3 341072 11176 ?        Ssl  Mar22   0:06 /usr/sbin/kopano-monitor -F
kopano     545  0.0  0.0 141184  2704 ?        S    Mar22   0:00 /usr/sbin/kopano-spooler -F
kopano     547  0.0  0.0 141284  2592 ?        S    Mar22   0:00 /usr/sbin/kopano-dagent -l
kopano    1677  0.2 11.0 681072 341268 ?       Ssl  Mar22  22:08 /usr/sbin/kopano-server -F
kopano    1753  0.0  1.4 396480 44840 ?        Sl   Mar22   6:54 /usr/bin/python2 /usr/sbin/kopano-search -F
kopano    1757  0.0  0.1 299676  5072 ?        S    Mar22   0:00 /usr/bin/python2 /usr/sbin/kopano-search -F

so in a nutshell, stop all those services, then drop db… restart each… is there a particular order these should be done in? or is there a single service that spawns the remainder?

Thanks! PS… I am investigating the possibility of a subscription in our next budget.

#8

Ultimately it should not matter. If you want to be in the safe side you should start Kopano-server first.

+1

Mastodon