Your message dated Fri, 10 Oct 2025 21:41:51 +0200
with message-id <[email protected]>
and subject line Re: Bug#1116021: dovecot-pgsql: libdriver_pgsql.so not linked 
against libpq5.so (or any others)
has caused the Debian Bug report #1116021,
regarding dovecot-pgsql: libdriver_pgsql.so not linked against libpq5.so (or 
any others)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1116021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116021
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dovecot-pgsql
Version: 1:2.4.1+dfsg1-7
Severity: grave
Justification: renders package unusable

Dear Maintainer,

This morning, my Sid system upgraded dovecot-pgsql from 1:2.4.1+dfsg1-6
to 1:2.4.1+dfsg1-7. During the same upgrade, libpq5 was updated from 17.6 to 
18~rc2.

After this, dovecot is unable to connect to the database, spewing errors
like:

Sep 23 10:38:58 mango dovecot[4295]: auth: Error: Couldn't load plugin 
/usr/lib/dovecot/modules/auth/libdriver_pgsql.so: dlopen() failed: 
/usr/lib/dovecot/modules/auth/libdriver_pgsql.so: undefined symbol: PQsendQuery
Sep 23 10:38:58 mango dovecot[4295]: auth: Fatal: passdb sql: Unknown database 
driver 'pgsql'

Looking at ldd for ldd /usr/lib/dovecot/modules/libdriver_pgsql.so, I
see that it is not linked against libpq5.so.

I tried reinstalling either package, but this did not fix the issue.

The same file on Debian Trixie is linked against libpq5.so. There might
have been a change between the dovecot in Trixie and Sid, or the Sid
package might need to be rebuilt and linked against the new libpq5?

I don't seem to have a copy of the old package file around, so I am
converting my installation to not use Postgresql to ensure I can receive
email.

Best regards,

Pieter Lexis


-- Package-specific info:

dovecot configuration
---------------------
# 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf
# Pigeonhole version 2.4.1-4 (0a86619f)
# OS: Linux 6.16.8+deb14-amd64 x86_64 Debian forky/sid
# Hostname: mango.plexis.eu
# 4 default setting changes since version 2.4.0
dovecot_config_version = 2.4.0
auth_mechanisms = plain
dovecot_storage_version = 2.4.0
fts_autoindex = yes
fts_autoindex_max_recent_msgs = 999
fts_search_add_missing = yes
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
mail_privileged_group = mail
protocols {
  imap = yes
  lmtp = yes
  sieve = yes
}
sql_driver = pgsql
ssl = required
pgsql localhost {
  parameters {
    dbname = mail
    host = /var/run/postgresql
    user = mailreader
  }
}
passdb sql {
  default_password_scheme = SHA512
  query = SELECT email as user, password from users where email = '%{user}'
}
userdb sql {
  query = SELECT email as user, '/srv/mail/maildir/'||maildir as mail_path, 
'/srv/mail/home/'||maildir as home, 500 as uid, 500 as gid FROM users WHERE 
email = '%{use
r}'
}
namespace inbox {
  inbox = yes
  mailbox Drafts {
    auto = subscribe
    special_use = "\\Drafts"
  }
  mailbox Junk {
    auto = subscribe
    special_use = "\\Junk"
  }
  mailbox Trash {
    auto = subscribe
    special_use = "\\Trash"
  }
  mailbox Sent {
    auto = subscribe
    special_use = "\\Sent"
  }
  mailbox "Sent Messages" {
    special_use = "\\Sent"
  }
}
service imap-login {
  inet_listener imap {
  }
  inet_listener imaps {
  }
}
service pop3-login {
  inet_listener pop3 {
  }
  inet_listener pop3s {
  }
}
service lmtp {
  unix_listener /var/spool/postfix/private/dovecot-lmtp {
    group = postfix
    mode = 0666
    user = postfix
  }
}
service imap {
}
service pop3 {
}
service auth {
  unix_listener auth-userdb {
  }
  unix_listener /var/spool/postfix/private/auth {
    group = postfix
    mode = 0666
    user = postfix
  }
}
service auth-worker {
}
service dict {
  unix_listener dict {
  }
}
ssl_server {
  cert_file = /etc/letsencrypt/live/mail.plexis.eu/fullchain.pem
  key_file = /etc/letsencrypt/live/mail.plexis.eu/privkey.pem
}
protocol imap {
  mail_max_userip_connections = 30
}
protocol lmtp {
  hostname = mail.plexis.eu
  mail_plugins {
    sieve = yes
  }
  postmaster_address = [email protected]
}
service managesieve-login {
  inet_listener sieve {
    port = 4190
  }
}
service managesieve {
}

-- System Information:
Debian Release: forky/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.16.8+deb14-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dovecot-pgsql depends on:
ii  dovecot-core  1:2.4.1+dfsg1-7
ii  libc6         2.41-12

dovecot-pgsql recommends no packages.

dovecot-pgsql suggests no packages.

Versions of packages dovecot-pgsql is related to:
ii  dovecot-core [dovecot-common]  1:2.4.1+dfsg1-7
pn  dovecot-dev                    <none>
pn  dovecot-gssapi                 <none>
ii  dovecot-imapd                  1:2.4.1+dfsg1-7
pn  dovecot-ldap                   <none>
ii  dovecot-lmtpd                  1:2.4.1+dfsg1-7
ii  dovecot-managesieved           1:2.4.1+dfsg1-7
pn  dovecot-mysql                  <none>
ii  dovecot-pgsql                  1:2.4.1+dfsg1-7
pn  dovecot-pop3d                  <none>
ii  dovecot-sieve                  1:2.4.1+dfsg1-7
pn  dovecot-sqlite                 <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Re: Noah Meyerhans
> Postgres maintainers: dovecot's configure script wasn't detecting libpq
> from the postgres 18 beta/rc libpq-dev packages.  With the final
> postgres 18 release, the issue seems resolved.  No actions were taken
> within the dovecot package to resolve this issue, so it seems that
> something must have changed on the postgres side.

I don't think anything changed on the PostgreSQL side either.

If everything works now, there's probably little point in digging this
up anyway.

Cheers,
Christoph

--- End Message ---

Reply via email to