Issue Attention if you planted Plesk Update to Obsidian 18.0.73 - DOVECOT Setting and Function

[vampsm]

Server operating system version

Ubuntu 24.04.3 LTS

Plesk version and microupdate number

Plesk Obsidian 18.0.73 Web Pro Edition

Now we have running update to Obsidian 18.0.73

After update cannot start Dovecot Service ..

Dovecot Setting must be migrate from 2.3 to 2.4

AND our BIG problem, we used Dovecot Shared Mailboxes - this function is now only for PRO Account available !?!?!?!?!

 

[vampsm]

We need a CLEAN default dovecot conf file ? That we can this migrate to 2.4 with our config......

 

[Arro]

The same problem with my 2 Servers, temporary i changed to courier, but i'm waiting for the resolve of the problem

 

[Dog66]

Another one that is the same, have you used the courier so far?

 

[King555]

Check the reason with journalctl -xeu dovecot.service

There is probably an invalid configuration entry, see also here: Issue - Plesk Obsidian 18.0.73 Dovecot failed to start after install

 

[vampsm]

https://doc.dovecot.org/main/installation/upgrade/2.3-to-2.4.html

 

[vampsm]

I Think i Understand why other users have no problem,

We used shared mailbox with our own config, in the dovecot.conf ORG file. We replace this files after update with with our files.

Can someone from Plesk Team, post last dovecot.conf file

Thank you

 

[vampsm]

I found it .... now search a solution for shared folder conf

 

[LRLD]

We used shared mailbox with our own config, in the dovecot.conf ORG file. We replace this files after update with with our files.

Instead of editing the main /etc/dovecot/dovecot.conf file, you should create a new file /etc/dovecot/conf.d/99-shared-mbox.conf and add your config there. That way your config will be retained after updates.

Regards

LD

 

[G J Piper]

Instead of editing the main /etc/dovecot/dovecot.conf file, you should create a new file /etc/dovecot/conf.d/99-shared-mbox.conf and add your config there. That way your config will be retained after updates.

I did exactly that. Mine contains this:

# Added by PCS

plugin {
  sieve_after = /etc/dovecot/conf.d/37-pcs-sieve/pcs_global_after.sieve
}

auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789.-_@'

# Uncomment for email debugging and to see password attempts:
#auth_mechanisms = login digest-md5 cram-md5 apop
#auth_verbose_passwords = plain
#auth_debug_passwords = yes

# Fix for https://talk.plesk.com/threads/lda-error-message-since-last-plesk-core-update.352822
service stats {
unix_listener stats-writer {
group = dovecot
mode = 0666
user = root
}
}

And when the 18.0.73 update was finished, dovecot would not start and email could not be sent either despite having a smarthost set up.
I could start dovecot after commenting out the "plugin" directive, but still couldn't send email out. I had to restore the entire server from backup.

 

[LRLD]

See the Dovecot upgrade docs...
https://doc.dovecot.org/main/installation/upgrade/2.3-to-2.4.html

sieve_after

Replaced by sieve_script_type = after for sieve_script filter.

I hope it helps.
Regards

LD

 

[G J Piper]

I had to replace the plugin section with this:

sieve_script pcs_global_after {
...
}

Then dovecot would start without errors, but I still had no SMTP capability for some reason. Seems there are quite a few problems as the Plesk 18.0.73 installation wouldn't get past "trying to start dovecot" until I went in and commented out the plugin section.

 

[LRLD]

Cool, glad you got it sorted.
Yeah, I couldn't send either, I started this thread in case it helps anyone else...

Issue - Plesk 18.0.73 - postfix/smtpd fatal: no SASL authentication mechanisms

Morning, I was just sending a test mail on my systems to make sure everything was ok after the Dovecot update, only to find my mail being held in the queue. I see lots of...mail postfix/smtpd[3261]: fatal: no SASL authentication mechanisms in the mail.err log since the update to 18.0.73...

talk.plesk.com