Help Center

ONLYOFFICE Mail for Docker

Portal Configuration. Getting Started

How to deploy Community Server using Docker service

Enabling vsyscall on Debian

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

If you are using one of the latest Debian versions, you may need to enable vsyscall which is disabled by default for some kernel versions, for example, for Debian 9 (Stretch) with kernel 4.18.x.bpo and Debian 10 (Buster) RC1 with kernel 4.19.0.

vsyscall is a mechanism that is used to accelerate certain system calls in Linux. It is required for the ONLYOFFICE Mail to work correctly. To be able to run the ONLYOFFICE Mail Docker container and to ensure the ONLYOFFICE Mail correct work, please follow the instructions below.

Checking if vsyscall is disabled

To check if your system has disabled vsyscall execute the following command:

cat /proc/self/maps | egrep 'vdso|vsyscall'

You'll see output similar to the following:

7fffccfcc000-7fffccfce000 r-xp 00000000 00:00 0                          [vdso]

or you'll see output like this:

7fffe03fe000-7fffe0400000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]

If you do not see a vsyscall mapping, add the vsyscall=emulated to the kernel options in your bootloader as it is described in the next step.