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
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
feld
in reply to Armin Pirkovitsch • • •well, I've been running the same IMAP server for over 10 years and it hasn't even received updates in all that time. And it still keeps going strong. No CVEs either.
It's missing some newer features, but it "just works".
archiveopteryx.org
Armin Pirkovitsch
in reply to feld • • •Even with no CVEs, it relies on external libraries and to be honest I’m astonished that it still works.
If I had started using it 10 years ago, I probably wouldn't have migrated to different solution as well, but I wouldn't want to take that route now.
feld
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)
feld
in reply to feld • • •feld
in reply to feld • • •Armin Pirkovitsch
in reply to feld • • •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
in reply to Armin Pirkovitsch • • •Armin Pirkovitsch
in reply to feld • • •I only require fileinto right now.
The whole thing just sucks as I've set up that server about 6 months ago…
Thanks for the advice!
feld
in reply to Armin Pirkovitsch • • •every time I experiment with another IMAP server I keep coming back to it due to its utter simplicity (and great performance with large amounts of email)
It's one of those pieces of software nobody ever talks about so nobody knows it exists. Doesn't even seem to come up in internet searches...
Armin Pirkovitsch
in reply to feld • • •Nonetheless, even libraries in base can have API changes with major releases.
I’m curious about the custom pgsql client though - the port pulls the client from ports if I see that correctly - what makes it custom?
feld
in reply to Armin Pirkovitsch • • •that's actually my mistake, it doesn't need to be in the port! Can't believe I didn't notice I'd left that in all these years...
the custom postgres db client code is here
github.com/aox/aox/tree/master…
aox/db at master · aox/aox
GitHubfeld
in reply to feld • • •port no longer relies on the pg client, thanks for noticing it 🥲
github.com/freebsd/freebsd-por…
mail/archiveopteryx{-devel}: Remove build dependency on PostgreSQL cl… · freebsd/freebsd-ports@28cffb3
GitHub