- 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.
600pageid | 49972308Packages supplied with BlueMind
Packages are available in /var/spool/bluemind-pkgs/
Aptitude (Debian/Ubuntu) and yum (RedHat) shell commands allow you are used to search and list available and/or installed packages.
Services
utilisés par used by BlueMind
| Service | UtilisationUse |
|---|
net.bluemind.eas.push | synchronisation des périphériques mobiles via le protocole syncing of mobile devices through the Exchange Active Sync protocol |
| net.bluemind.dav.server.dav | synchronisation CardDav et and CalDav des syncing of Apple clients Apple |
| net.bluemind.milter.milter | service milter service |
| net.bluemind.xmpp.server.launcher.tigase | messagerie instantanéeinstant messaging |
| net.bluemind.core.launcher.core | main service principal |
| net.bluemind.node.server.nodelauncher | communication entre les différentes serveurs dans le cas d'une installation multi-serveursbetween different servers in multi-server installations |
| net.bluemind.tika.server.tika | détection et extraction des métadonnées et textes de detection and extraction of metadata and texts from documents |
| net.bluemind.proxy.http.launcher.hpslauncherproxy d'authentification | authentication proxy |
| exchange.http | communication avec with MAPI |
| net.bluemind.webmodules.launcher.webLauncher | HTTP proxy HTTP pour les for webservices |
| net.bluemind.locator.app | service de localisation des différents serveurs dans le cas d'une installation multi-serveurslocation service for different servers in multi-server installations |
| org.elasticsearch.bootstrap.Elasticsearch | service d'indexation et de rechercheindexing and search service |
| net.bluemind.ysnp.ysnp | authentification SMTP et and IMAP authentication |
| net.bluemind.lmtp | service local de transfert de courrierlocal mail transfer service |
| postgresql | base de donnéesdatabase |
| postfix | serveur de messageriemail server |
nginx | proxy HTTP + IMAP server |
php-fpm | interpréteur PHP pour les interpreter for web applications web (webmail) |
| cyrus (imapd et and pop3d) | service pour la synchronisation imap et pop de logiciels de messagerie tiers (lourds ou mobilesand pop syncing service for third-party mail software (thick or mobile clients) |
Data used by BlueMind
Backup
/etc
The directories listed below files and directories found in /etc/contain the configuration of the components used by BlueMind uses.
| FichierFile/répertoiredirectory | ContenuContents |
|---|
bm | bm.ini, les certificats et clés ssh de bm-node .certificates and ssh keys |
bm-node | rsync.excludes |
| bm-webmail | configuration de php5-fpm pour configuration for BlueMind et and nginx-webmail.conf |
| cyrus.conf | Cyrus configuration de cyrus |
| imapd.conf | imap configuration de imap (généré par generated by bm-core) |
| nginx | nginx configuration de nginx |
| php5 | php5 configuration de php5 |
| postfix | postfix configuration de postfix, notamment les including transport maps de transport | Avertissement |
|---|
Il est possible d'ajouter des maps postfix supplémentaires mais il ne faut en aucun cas enlever ou modifier les maps déjà existantes et utilisées par You can add extra postfix maps but under no circumstances should you remove or edit existing maps used by BlueMind. |
|
| postgresql | postgresql configuration de postgresql |
/
etc/postfix/main.cfusr/share
Subfolders located in /usr/share/ contain web modules and applications. The data in these directories is installed by the BlueMind packages and must not be edited.
| 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
Les sous-répertoires situés dans /usr/share/ contiennent les modules et applications web. Les données présentes dans ces répertoires sont installées par les paquets BlueMind et ne doivent pas être modifiés
/var/spool
The directories below /var/spool/ sub-directories contain the data used by BlueMind (excluding the data contained in the postgresql database).
| RépertoireDirectory | DonnéesData | type stockageStorage Type |
|---|
bm-docs | BlueMind documents BlueMind (user/resource photos utilisateurs/resources) | tousall |
| bm-elasticsearch | ElasticSearch index ElasticSearch | block device |
| bm-hsm | mails archivésarchived emails | tousall |
| bm-filehosting | pièces jointes détachés des mails | linked email attachments | alltous |
| cyrus/data | mailsemails | tousall |
| cyrus/meta | metadonnées des mailsemail metadata | block device |
| postfix | files d'attentes postfix queues | tousall |
| sieve | script sieve | tousall |
| bluemind-pkgs | données d'installation de BlueMind - utilisé à l'installation et tant qu'on n'a pas de souscription | tous |
/var/lib
The data below must not be modified manually.
| Répertoire | Contenu |
|---|
bm-ca | autorité de certification généré lors de l'installation |
| postgresql | base de données postgresql |
| cyrus | informations administratives de Cyrus - liste des BAL, ACLs, quota, quota utilisé |
Logs
Les logs sont écrits dans des sous-répertoires du répertoire /var/log/ :
| Répertoire | Contenu |
|---|
bm | logs du core |
| bm-elasticsearch | logs elasticsearch |
| bm-hps | logs hps |
| bm-lmtpd | logs service LMTP |
| bm-locator | logs locator |
| bm-mapi | logs service mapi |
| bm-node | logs du node |
| bm-tika | logs de Tika |
| bm-webserver | logs du webserver |
| bm-webmail | logs du webmail |
| bm-xmpp | logs XMPP |
| bm-ysnp | logs YNSP |
For other components you may want to monitor, the following locations may be used:
| Fichier/répertoire | Contenu |
|---|
| mail.err | erreurs Postfix/Cyrus |
| mail.log | logs Postfix/Cyrus |
nginx/ | logs NGinx| 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/postgresql | block device | ~20Gb |
| 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
Logs are written into subdirectories of the /var/log/ directory:
| Directory | Content |
|---|
bm | core logs |
| bm-elasticsearch | 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
