That whole #dovecot breaking update (and from what I've seen the unreasonable pro version, at least for small setups) makes me question self-hosting my mail server…
I'm fine with investing time to setup something the first time - but updates (especially not minor) should never be breaking… - neither should they require quiet some time investment imho…
#SelfHosting #mailserver
in reply to Armin Pirkovitsch

No, it doesn't rely on external libraries except the normal stuff you'd expect, libz, and openssl. On FreeBSD this means zero libraries except those already provided by the base OS.

Even the PostgreSQL client is custom to avoid this problem (as the pg wire format is standardized)

/usr/local/sbin/archiveopteryx:
libc++.so.1 => /lib/libc++.so.1 (0x77f86001000)
libcxxrt.so.1 => /lib/libcxxrt.so.1 (0x77f86be1000)
libcrypto.so.30 => /lib/libcrypto.so.30 (0x77f87bc6000)
libm.so.5 => /lib/libm.so.5 (0x77f883d7000)
libcrypt.so.5 => /lib/libcrypt.so.5 (0x77f88ab5000)
libssl.so.30 => /usr/lib/libssl.so.30 (0x77f898a3000)
libz.so.6 => /lib/libz.so.6 (0x77f8ac7e000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x77f89d3c000)
libthr.so.3 => /lib/libthr.so.3 (0x77f8bc57000)
libc.so.7 => /lib/libc.so.7 (0x77f8c99a000)
[vdso] (0x77f85901000)

in reply to feld

@feld they have to be to create a software that survives that long. Them playing part in the RFCs helps of course.
Software is never finished - especially when it's based on a changing standard (RFC 9051, the current version of IMAP has been published in 2021)
Although I haven't checked what changes were made to it since 2014, but ... it just doesn't help my gut feeling.
Archiveopteryx might be an exception, but my experience with “unmaintained” projects isn't the best.
@feld