- BM-Core is BlueMind's core component. It serves a a single management center for data and business rules. It is the only component that accesses the database.
All functionalities are exposed as Web Services and can therefore be driven by other applications.
All components, whether internal or external, use Web Services. This is useful for limiting incoming and outgoing BlueMind Mail flows (which are restricted to Web Services flows and mail flows) and ensuring the use of consistent management rules whatever the point of entry of a modification.
Packages supplied with BlueMind
Packages are available in /var/spool/bluemind-pkgs/
Aptitude (Debian/Ubuntu) and yum (RedHat) shell commands allow you to search and list available and/or installed packages.
Data used by BlueMind
Backup
/etc
The directories listed below contain the configuration of the components used by BlueMind.
- /etc/bm: contains bm.ini, bm-node ssh certificates and keys.
- /etc/bm-core
- /etc/bm-dav
- /etc/bm-eas
- /etc/bm-elasticsearch
- /etc/bm-hps
- /etc/bm-ips: contains ips.ini
- /etc/bm-lmtpd
- /etc/bm-locator: contains certificates
- /etc/bm-milter
- /etc/bm-mq
- /etc/bm-node: contains rsync.excludes
- /etc/bm-tika
- /etc/bm-webmail: contains the configuration of php5-fpm for BlueMind and nginx-webmail.conf
- /etc/bm-xmpp
- /etc/cyrus.conf: configuration of cyrus
- /etc/imapd.conf: configuration of imap (generated by bm-core)
- /etc/nginx: configuration of nginx
- /etc/php5: configuration of php5
- /etc/postfix: configuration of postfix, including transport maps
- /etc/postgresql: configuration of postgresql
Astuce |
---|
Additional postfix maps can be added but existing maps used by BlueMind must NOT be removed. |
The mynetworks parameter is overwritten by the values in the BlueMind admin console.
/usr/share
The directories below contain the web modules and applications. The data they contain is installed by the BlueMind packages and must not be modified.
/usr/share/bm-admin-console
/usr/share/bm-calendar
/usr/share/bm-client-access
/usr/share/bm-contact
/usr/share/bm-core
/usr/share/bm-cyrus
/usr/share/bm-dav
/usr/share/bm-dav-data
/usr/share/bm-default-app
/usr/share/bm-eas
/usr/share/bm-elasticsearch
/usr/share/bm-hps
/usr/share/bm-im
/usr/share/bm-installation-wizard
/usr/share/bm-ips
/usr/share/bm-lmtpd
/usr/share/bm-locator
/usr/share/bm-mq
/usr/share/bm-node
/usr/share/bm-pimp
/usr/share/bm-push
/usr/share/bm-settings
/usr/share/bm-tika: contains the bm-tika ini file
/usr/share/bm-tomcat
/usr/share/bm-webmail
/usr/share/bm-webmail-conf: contains configurations
/usr/share/bm-xmpp: contains the bm-xmpp ini file
/var/spool
The directories below contain the data used by BlueMind (excluding the data contained in the postgresql database).
/var/spool/ Directory | Data | Storage Type |
---|
bm-docs |
/var/spool//var/spool/BlueMind documents (user/resource photos) | all |
bm-elasticsearch |
| ElasticSearch index | block device |
/var/spool/cyrus/var/spool/postfix/var/spool/sieve/var/spool/bluemind-pkgs/var/lib
The data below must not be modified manually.
/var/lib/bm-ca: contains BlueMind's self-signed certificate/var/lib/bm-core/var/lib/bm-dav/var/lib/bm-eas/var/lib/bm-hps/var/lib/bm-ips/var/lib/bm-lmtpd/var/lib/bm-locator/var/lib/bm-mq/var/lib/bm-mq-data/var/lib/bm-node/var/lib/bm-pimp/var/lib/bm-tika/var/lib/bm-tomcat/var/lib/bm-xmpparchived emails | all |
bm-filehosting | linked email attachments | all |
cyrus/data | emails | all |
cyrus/meta | email metadata | block device |
postfix | | all |
sieve | script sieve | all |
bluemind-pkgs | BlueMind installation data - used during installation and as long as you don't have a subscription | all |
/var/lib
The data found in /var/lib/
must not be edited manually.
Directory | Contents |
---|
bm-ca | certification authority generated during installation |
postgresql | postgresql database |
cyrus | Cyrus administrative information - list of BAL, ACLs, quota, quota used |
Estimating folder sizes
The usual size of some folders can be estimated:
Folder | Estimated Size |
---|
/var/spool/bm-elasticsearch | ~10% /var/spool/cyrus/data + /var/spool/bm-hsm The size of the partition must be AT LEAST twice the volume of the data it contains. Ideally, this folder should be deported and split into 2 dedicated partitions, which must meet the same size constraints: - /var/spool/bm-elasticsearch/data
- /var/spool/bm-elasticsearch/repo
|
/var/spool/cyrus/meta | ~10% /var/spool/cyrus/data + /var/spool/bm-hsm |
/var/spool/sieve | ~1Mb/(users+mailshare) |
Folder | Mount Type | Estimated Size |
---|
/var/lib/cyrus | block device | ~10Gb |
/var/lib/cyrus: contains the cyrus database/var/lib/ysnpLogs
/var/log/bm/ Remarque |
---|
These are mere estimates, which may vary depending on your install and your organization's evolution. We therefore recommend that you use technologies that enable you to increase the size of your file system easily. |
Logs
/var/log/bm-backoffice/Logs are written into subdirectories of the
/var/log/
directory:
Directory | Content |
---|
bm | core logs |
bm- |
dav//var/log/bm-eas//var/log/bm-elasticsearch//var/log/bm-hps//var/log/bm-ips//var/log/bm-kb//var/log/bm-lmtpd//var/log/bm-locator//var/log/bm-mq//var/log/bm-node//var/log/bm-tika//var/log/bm-tomcat//var/log/bm-webmail//var/log/bm-xmpp//var/log/ysnp/For other components you may want to monitor, the following locations may be used:
- /var/log/mail.err
- /var/log/mail.info
- /var/log/mail.log
- /var/log/mail.warn
- /var/log/nginx/
- /var/log/php5-fpm.log
- /var/log/postgresql/
For more informations, please see Logs - Fichiers journauxelasticsearch | elasticsearch logs |
bm-hps | hps logs |
bm-lmtpd | LMTP service logs |
bm-locator | locator logs |
bm-mapi | mapi service logs |
bm-node | node logs |
bm-tika | Tika logs |
bm-webserver | webserver logs |
bm-webmail | webmail logs |
bm-xmpp | XMPP logs |
bm-ysnp | YNSP logs |
For other components you may want to monitor, the following folders or sub-directories can be used:
Folder/directory | Contents |
---|
mail.err | Postfix/Cyrus errors |
mail.log | Postfix/Cyrus logs |
nginx/ | NGinx logs |
bm-php5-fpm/ | FPM logs (/var/log/bm-php-fpm/ on RedHat) |
postgresql/ | PostgreSQL logs |
For more information, please see Logs - Fichiers journaux