Articles avec le tag :
Parcourir tous les tags
Fermer
Changelog
Fermer
Essayer dans le cloud
Essayer dans le cloud
Centre d'aide
ONLYOFFICE Mail for Docker
Search

Modifier le domaine associé à ONLYOFFICE Mail

ONLYOFFICE Mail v1.6 ONLYOFFICE Mail changelog
Open in new window

Version 1.6.57

Release date: 04/25/2019

New features

  • Added permanent Fail2Ban ignoreip section for docker containers and its gateway;
  • Added the possibility to create sieve rules for users inside /var/vmail/sieve/;
  • Added new extension to sieve: sieve_extensions -> editheader;
  • Exposed port 4190 for ManageSieve service;
  • Added the possibility to run an external script from the /var/vmail/external.sh or /app/onlyoffice/MailServer/data/external.sh path;
  • Changed the default FIRST_DOMAIN parameter;
  • Replaced the hard-coded password used for the first mailbox with a random one;
  • Removed old useless descriptions for iRedMail administrator console path;
  • Added backticks to the 'CREATE DATABASE' commands;
  • Added the possibility to send mail messages from alias_domain, alias_address and full alias;
  • Added the imapsync command;
  • Added the new Python scripts allowing to create mailboxes, change password and run imapsync batch in /usr/src/iRedMail/tools/scripts folder inside the onlyoffice-mail-server container;
  • Added the Python PIP manager and installation requirements.

Bug fixes

  • Fixed the bug with mailbox not being removed when using third level domain (issue: wrong domain regex);
  • Fixed the bug with the Cannot load 1024-bit DH parameters from file /etc/pki/tls/dhparams.pem warning;
  • Fixed the bug with the No such file or directory being shown in many cases;
  • Fixed the bug with the ECHO_INFO: command not found warning.

Version 1.6.25

Release date: 07/03/2017

Runtime

  • Updated OpenSSL to the latest version (1.0.2).

Version 1.6.21

Release date: 04/26/2017

Runtime

  • Fixed the issue when the amavisd-new interface could not start without the properly configured IPv6.

Version 1.6.20

Release date: 12/13/2016

Connection Settings

  • Added page to the Settings for the integration of Community Server (Windows version) with Mail Server.

Installation Script

  • Fixed the error shown if the mail domain is not specified, now Mail Server will not be installed if this is the case.

Version 1.6.7

Release date: 06/22/2016

Refactoring

  • Removed version from the iRedMail folder;
  • iRedMail completed with commits from v.0.9.2;
  • Deleted unused packages from iRedMail;
  • Added the SpamAssassin setup with initial bayes_tokens.

Runtime

  • Fixed the incorrect MySQL server name in the config;
  • Fixed the issue with the config section duplication when starting the Docker container;
  • Fixed the issue with sending mail to a group/alias address;
  • Fixed the startup API issue.

Logging

  • Fixed logging during the installation.

Networking

  • Fixed the fail2ban and iptables issue when starting Docker in a network mode;
  • Fixed the issue with Mail Server on an external physical server.

Version 1.6.0

Release date: 03/09/2016

Settings

  • Redesigned Mail Server settings page.

Version 1.5.0

Release date: 04/20/2015

Mail Server

  • Mail Server for Docker first release.

Introduction

Si vous souhaitez modifier le domaine associé à ONLYOFFICE Mail, il faut actualiser les informations concernant celui-ci dans votre système. Veuillez suivre les étapes ci-dessous pour mettre en œuvre ce processus correctement.

Étape 1. Arrêter et supprimer le conteneur ONLYOFFICE Mail

Premièrement, il fait arrêter le conteneur avec ONLYOFFICE Mail. Accédez à l'ordinateur sur lequel ONLYOFFICE Mail est installé et exécutez la commande suivante.

docker stop onlyoffice-mail-server

Ensuite, supprimez le conteneur:

docker rm onlyoffice-mail-server

Étape 2. Réinstaller ONLYOFFICE Mail avec une nouvelle adresse de domaine

Maintenant, réinstallez ONLYOFFICE Mail avec une nouvelle adresse de domaine:

bash workspace-enterprise-install.sh -ics false -ids false -icp false -ims true -md {NEW-MX-DOMAIN} -es true

Où {NEW-MX-DOMAIN} est la nouvelle adresse qui sera associée à ONLYOFFICE Mail (en générale il s'agit de l'adresse mx.yourdomain.com ou une pareille adresse).

Étape 3. Actualiser l'information concernant le domaine

Ensuite, il faut actualiser l'information sur la domaine dan la base de données. Exécutez les commandes suivantes:

docker exec -it onlyoffice-mysql-server mysql -pmy-secret-pw --silent -e "use onlyoffice; update mail_server_server SET mx_record  = '{NEW-MX-DOMAIN}';"
docker exec -it onlyoffice-mysql-server mysql -pmy-secret-pw --silent -e "use onlyoffice; update mail_server_server ms inner join mail_mailbox_server s on ms.smtp_settings_id = s.id or ms.imap_settings_id = s.id SET s.hostname = '{NEW-MX-DOMAIN}';"

Où {NEW-MX-DOMAIN} est la nouvelle adresse associée à ONLYOFFICE Mail.

Étape 4. Lancer ONLYOFFICE Mail

Vous pouvez donc lancer ONLYOFFICE Mail:

docker logs -f onlyoffice-mail-server

Le résultat doit ressembler à ceci:

...
Starting fail2ban:                                         [  OK  ]
Starting server
Download Host on your own server Available for
Docker, Windows and Linux
Cela peut vous aider aussi :
Fermer