dovecot - Mar 2018 - Authentification fails in dovecot 2.3.0.1

Hi

I've upgraded dovecot from 2.2.22 to 2.3.0.1. Now I can't authenticate
any
longer. My mail client says that the user name and password are rejected
by
dovecot.

I get this line in /var/log/auth.log:
Mar  6 19:28:02 desktop auth: PAM audit_log_acct_message() failed:
Operation not permitted

And this in /var/log/dovecot.log:
Mar 06 19:28:02 auth: Debug: Loading modules from directory:
/usr/lib/dovecot/modules/auth
Mar 06 19:28:02 auth: Debug: Module loaded:
/usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so
Mar 06 19:28:02 auth: Debug: Module loaded:
/usr/lib/dovecot/modules/auth/libdriver_sqlite.so
Mar 06 19:28:02 auth: Debug: Read auth token secret from
/var/run/dovecot/auth-token-secret.dat
Mar 06 19:28:02 auth: Debug: auth client connected (pid=5615)
Mar 06 19:28:02 auth: Debug: client in: AUTH    1       PLAIN  
service=imap    secured session=ggZPmsJmIoh/AAAB        lip=127.0.0.1  
rip=127.0.0.1   lport=993       rport=34850     local_
Mar 06 19:28:02 auth-worker(5617): Debug: Loading modules from
directory: /usr/lib/dovecot/modules/auth
Mar 06 19:28:02 auth-worker(5617): Debug: Module loaded:
/usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so
Mar 06 19:28:02 auth-worker(5617): Debug: Module loaded:
/usr/lib/dovecot/modules/auth/libdriver_sqlite.so
Mar 06 19:28:02 auth-worker(5617): Debug:
pam(v,127.0.0.1,<ggZPmsJmIoh/AAAB>): lookup service=dovecot
Mar 06 19:28:02 auth-worker(5617): Debug:
pam(v,127.0.0.1,<ggZPmsJmIoh/AAAB>): #1/1 style=1 msg=Password:
Mar 06 19:28:02 auth-worker(5617): Info:
pam(v,127.0.0.1,<ggZPmsJmIoh/AAAB>): pam_authenticate() failed: System
error
Mar 06 19:28:04 auth: Debug: client passdb out: FAIL    1       user=v
Mar 06 19:28:06 imap-login: Info: Aborted login (auth failed, 1 attempts
in 4 secs): user=<v>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS,
session=<ggZPmsJmIoh/AAAB>


Now it seems I can't go back to 2.2.22 as well:
https://wiki2.dovecot.org/Upgrading/2.3 says "Downgrading is possible to
v2.2.27 and later. (v2.2.27 accidentally broke dovecot.index* backwards
compatibility a bit.)"

What should I do now? Remove the dysfunctional dovecot server and try a
fresh
new 2.3.0.1 install? How would I migrate my mail?



Here's my dovecot -n:

# 2.3.0.1 (ffd8a29): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.0.1 (d33dca2)
# OS: Linux 4.4.0-116-generic x86_64 Ubuntu 16.04.4 LTS
auth_debug = yes
auth_username_format = %n
auth_verbose = yes
auth_verbose_passwords = plain
hostname = volker-wysk.de
log_path = /var/log/dovecot.log
mail_debug = yes
mail_location = mdbox:~/lib/Dovecot-Mail
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date index ihave duplicate mime foreverypart
extracttext imapsieve vnd.dovecot.imapsieve
namespace inbox {
  inbox = yes
  location   mailbox Drafts {
    special_use = \Drafts
  }
  mailbox Entw?rfe {
    special_use = \Drafts
  }
  mailbox Junk {
    special_use = \Junk
  }
  mailbox Papierkorb {
    special_use = \Trash
  }
  mailbox Sent {
    special_use = \Sent
  }
  mailbox "Sent Messages" {
    special_use = \Sent
  }
  mailbox Trash {
    special_use = \Trash
  }
  mailbox "Versendete Nachrichten" {
    special_use = \Sent
  }
  prefix   separator = .
}
passdb {
  driver = pam
}
plugin {
  imapsieve_mailbox1_before file:/usr/lib/dovecot/sieve/report-spam.sieve
  imapsieve_mailbox1_causes = COPY
  imapsieve_mailbox1_name = Spam
  imapsieve_mailbox2_before file:/usr/lib/dovecot/sieve/report-ham.sieve
  imapsieve_mailbox2_causes = COPY
  imapsieve_mailbox2_from = Spam
  imapsieve_mailbox2_name = *
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/lib/Sieve
  sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment
  sieve_pipe_bin_dir = /usr/lib/dovecot/sieve
  sieve_plugins = sieve_imapsieve sieve_extprograms
}
postmaster_address = post at volker-wysk.de
protocols = imap lmtp sieve
ssl = required
ssl_cert = </etc/ssl/certs/dovecot.pem
ssl_dh =  # hidden, use -P to show it
ssl_key =  # hidden, use -P to show it
userdb {
  driver = passwd
}
protocol lmtp {
  mail_plugins = " sieve mail_log notify"
}
protocol lda {
  mail_plugins = " sieve"
}
protocol imap {
  mail_max_userip_connections = 50
  mail_plugins = " imap_sieve"
}



Bye
Volker

Hi!

"Downgrading is possible to v2.2.27 and later. (v2.2.27 accidentally broke
dovecot.index* backwards compatibility a bit.) "

I've thrown caution to the winds, and downgraded back to 2.2.22, by turning
off the Dovecot-PPA, deinstalling 2.3.0.1, and installing 2.2.22 again from the
Ubuntu package sources. Then I could at least log in to the dovecot server
again.

But i still needed Pigeonhole 0.4.14, and in 2.2.22 there is only 0.4.13.
"IMAP Sieve" is not added before 0.4.14. I have a Kubuntu 16.04.3 LTS
System, and the contained version is only 2.2.22. So I downloaded and installed
the needed dovecot packages from the newer Ubuntu version 17.10. That's
version 2.2.27.

And now - I can log in, and there are no complaints about the
IMAPSieve-configuration not being recognized. (I need IMAPSieve for the training
of a spam filter). Now I can continue with that spam filter.

So far, I habe no problems with the broken indexes - yet(??) (see above).

Eventually it can be said that the problem is probably an incompatibility
between the dovecot wich ich packaged for Ubuntu, and the version from the
dovecot PPA.

Tsch??
Volker