Dovecot: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: protocols: Unknown protocol: sieve

  • by

1.0 Error:

While configuring the Dovecot Mail Delivery Agent, the Dovecot server would not start and the following error messages were printed.

$ sudo systemctl start dovecot
Job for dovecot.service failed because the control process exited with error code. See "systemctl status dovecot.service" and "journalctl -xe" for details.
$ systemctl status dovecot.service
● dovecot.service - Dovecot IMAP/POP3 email server
   Loaded: loaded (/lib/systemd/system/dovecot.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2018-02-05 04:25:20 UTC; 39s ago
     Docs: man:dovecot(1)
           http://wiki2.dovecot.org/
  Process: 3983 ExecStart=/usr/sbin/dovecot (code=exited, status=89)
$ sudo journalctl -xe
...
Feb 05 04:25:20 Example systemd[1]: Starting Dovecot IMAP/POP3 email server...
-- Subject: Unit dovecot.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dovecot.service has begun starting up.
Feb 05 04:25:20 Example dovecot[3983]: doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf
Feb 05 04:25:20 Example dovecot[3983]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: protocols: Unknown protocol: si
Feb 05 04:25:20 Example systemd[1]: dovecot.service: Control process exited, code=exited status=89
Feb 05 04:25:20 Example systemd[1]: Failed to start Dovecot IMAP/POP3 email server. 
-- Subject: Unit dovecot.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dovecot.service has failed.
-- 
-- The result is failed.
Feb 05 04:25:20 Example systemd[1]: dovecot.service: Unit entered failed state.
Feb 05 04:25:20 Example systemd[1]: dovecot.service: Failed with result 'exit-code'.

The syslog had following messages.

...
Feb  5 04:25:20 Example dovecot[3983]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: protocols: Unknown protocol: sieve
Feb  5 04:25:20 Example systemd[1]: dovecot.service: Control process exited, code=exited status=89
Feb  5 04:25:20 Example systemd[1]: Failed to start Dovecot IMAP/POP3 email server. 
Feb  5 04:25:20 Example systemd[1]: dovecot.service: Unit entered failed state.
Feb  5 04:25:20 Example systemd[1]: dovecot.service: Failed with result 'exit-code'.

2.0 Solution

The problem was resolved by installing the dovecot-sieve and dovecot-managesieved packages.

$ sudo apt-get install dovecot-sieve dovecot-managesieved
Subscribe
0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments

You may like these, also

  • POSIX message queues in LinuxPOSIX message queues in Linux 1.0 POSIX Message queues POSIX interprocess comunication (IPC) was introduced in the POSIX.1b standard (IEEE Std 1003.1b-1993) for real time…
  • POSIX Shared Memory in LinuxPOSIX Shared Memory in Linux 1.0 Shared Memory Shared memory is the fastest method of interprocess communication (IPC) under Linux and other Unix-like systems. The…
  • POSIX Semaphores in LinuxPOSIX Semaphores in Linux 1.0 Semaphores Semaphores are used for process and thread synchronization. Semaphores are clubbed with message queues and shared memory under…
  • fork and exec system calls in Linuxfork and exec system calls in Linux 1.0 fork and exec system calls Suppose we wish to write a "shell program" which would execute another program. Now,…
  • Connecting two computers with Ethernet LAN cableConnecting two computers with Ethernet LAN cable Quite often, we wish to connect two computers back to back using an Ethernet LAN cable. It may be because…
  • D-Bus TutorialD-Bus Tutorial 1.0 D-Bus D-Bus is a mechanism for interprocess communication under Linux and other Unix-like systems. D-Bus has a layered architecture.…
  • Socket programming using the select system callSocket programming using the select system call 1.0 Client-Server Paradigm The Client-Server paradigm divides the software architecture of a system in two parts, the server and its…
  • System V message queues in LinuxSystem V message queues in Linux 1.0 Message queues Message queues are one of the interprocess communication mechanisms available under Linux. Message queues, shared memory and…
  • POSIX Threads Synchronization in CPOSIX Threads Synchronization in C 1.0 POSIX Threads Synchronization POSIX Threads provide multiple flows of execution within a process. The threads have their own stacks…
  • System V Shared Memory in LinuxSystem V Shared Memory in Linux 1.0 Shared Memory Shared memory is one of the three interprocess communication (IPC) mechanisms available under Linux and other Unix-like…