Solved Dovecot fails to update using custombuild

mediumfriedchips

Verified User
Joined
Oct 23, 2020
Messages
9
I am having an issue where dovecot is failing to update from dovecot-2.3.19.1 to dovecot:2.3.20

The error during the update is

Code:
checking for "/usr/lib64/dovecot/dovecot-config"... not found

configure:

configure: Use --with-dovecot=DIR to provide the path to the dovecot-config file.

configure: error: dovecot-config not found

Trying to make pigeonhole 0.5.20

make: *** No targets specified and no makefile found.  Stop.

*** The make has failed. Exiting...


Checking the dovecot status showed the following errors

Code:
Jan 08 12:09:59 server systemd[1]: Started Dovecot IMAP/POP3 email server.
Jan 08 12:09:59 server dovecot[2597831]: doveconf: Error: Couldn't load plugin /usr/lib/dovecot/settings/libmanagesieve_login_settings.so: Module is for different ABI version 2.3.ABI...Iv20(2.3.20))
Jan 08 12:09:59 server dovecot[2597831]: doveconf: Error: Couldn't load plugin /usr/lib/dovecot/settings/libmanagesieve_settings.so: Module is for different ABI version 2.3.ABIv19(2....Iv20(2.3.20))
Jan 08 12:09:59 server dovecot[2597831]: doveconf: Error: Couldn't load plugin /usr/lib/dovecot/settings/libpigeonhole_settings.so: Module is for different ABI version 2.3.ABIv19(2.3...Iv20(2.3.20))
Jan 08 12:09:59 server dovecot[2597831]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve.conf line 18: Unknown setting: managesieve_max_line_length
Jan 08 12:09:59 server systemd[1]: dovecot.service: main process exited, code=exited, status=89/n/a
Jan 08 12:09:59 server systemd[1]: Unit dovecot.service entered failed state.
Jan 08 12:09:59 server systemd[1]: dovecot.service failed.
 
We had this issue on our servers as well.
It seems that imunify plugin creates a symlink in a wrong dir:
Bash:
find /usr/lib64/dovecot/ -ls

Finds only one file:
Bash:
[root@nsc ~]# find /usr/lib64/dovecot/ -ls
101627746    4 drwxr-xr-x   3 root     root         4096 Oct 27 03:24 /usr/lib64/dovecot/
101627747    4 drwxr-xr-x   2 root     root         4096 Dec 16 03:16 /usr/lib64/dovecot/auth
101580844    0 lrwxrwxrwx   1 root     root           52 Dec 16 03:16 /usr/lib64/dovecot/auth/lib_imunify360.so -> /usr/lib64/i360_pam_imunify/lib_imunify360_2.3.18.so

The fix is to move that symlink to a correct dir.
Bash:
mv /usr/lib64/dovecot/auth/lib_imunify360.so /usr/lib/dovecot/auth/

And then remove the empty skeleton:
Bash:
rm -rfv /usr/lib64/dovecot/

After that, the build dovecot should work fine:
Bash:
/usr/local/directadmin/custombuild/build dovecot
 
We had this issue on our servers as well.
It seems that imunify plugin creates a symlink in a wrong dir:
Bash:
find /usr/lib64/dovecot/ -ls

Finds only one file:
Bash:
[root@nsc ~]# find /usr/lib64/dovecot/ -ls
101627746    4 drwxr-xr-x   3 root     root         4096 Oct 27 03:24 /usr/lib64/dovecot/
101627747    4 drwxr-xr-x   2 root     root         4096 Dec 16 03:16 /usr/lib64/dovecot/auth
101580844    0 lrwxrwxrwx   1 root     root           52 Dec 16 03:16 /usr/lib64/dovecot/auth/lib_imunify360.so -> /usr/lib64/i360_pam_imunify/lib_imunify360_2.3.18.so

The fix is to move that symlink to a correct dir.
Bash:
mv /usr/lib64/dovecot/auth/lib_imunify360.so /usr/lib/dovecot/auth/

And then remove the empty skeleton:
Bash:
rm -rfv /usr/lib64/dovecot/

After that, the build dovecot should work fine:
Bash:
/usr/local/directadmin/custombuild/build dovecot

Thanks, that solved the problem.
 
We had this issue on our servers as well.
It seems that imunify plugin creates a symlink in a wrong dir:
Bash:
find /usr/lib64/dovecot/ -ls

Finds only one file:
Bash:
[root@nsc ~]# find /usr/lib64/dovecot/ -ls
101627746    4 drwxr-xr-x   3 root     root         4096 Oct 27 03:24 /usr/lib64/dovecot/
101627747    4 drwxr-xr-x   2 root     root         4096 Dec 16 03:16 /usr/lib64/dovecot/auth
101580844    0 lrwxrwxrwx   1 root     root           52 Dec 16 03:16 /usr/lib64/dovecot/auth/lib_imunify360.so -> /usr/lib64/i360_pam_imunify/lib_imunify360_2.3.18.so

The fix is to move that symlink to a correct dir.
Bash:
mv /usr/lib64/dovecot/auth/lib_imunify360.so /usr/lib/dovecot/auth/

And then remove the empty skeleton:
Bash:
rm -rfv /usr/lib64/dovecot/

After that, the build dovecot should work fine:
Bash:
/usr/local/directadmin/custombuild/build dovecot
thanks, its working
 
Got the same issue too. This resolved it!

Sending emails is my second issue, and every incoming mail now seems to get this auto-replied:

550 5.7.360 Remote server returned message denied by administrative policy

EDIT: Restarting Exim did the trick! All solved!
 
Last edited:
Back
Top