@oceanhaiyang

This is just after a reboot.
CPU: Intel Core 2 Quad Q9550 (4) @ 2.545GHz
Memory: 0.70GiB / 3.70GiB (18%)
Disk (/): 23G / 40G (61%)

It is running #Nextcloud, and so effectively does the cloud storage, calendar & contacts. I've been running this since before Nextcloud (I used to use OwnCloud).

This and SSH is all that is accessible outside of home. Both have MFA and China is currently blocked (I mean to expand this list).

However it also handles DHCP & DNS for the home LAN using #dnsmasq and I use it as an email archive (#dovecot). There is a functional #fetchmail install, but this is currently switched off.

It also has my #Subversion archive. That stays until I get around to having a proper look at #git.

With #USA going downhill I do have plans to get it do do more - but I'm playing with using #docker containers so if anything gets hacked, that will minimise the damage. I currently have too much running on the raw iron.

I'm using #borg for backups onto an external HDD that then occasionally is copied elsewhere (physical media off-site).

#selfHosting

For anyone who just upgraded to #dovecot 2.4 (it's now in debian testing), the deliver command now doesn't work unless you specify -d <user> as well as -m <mailbox>

This bit me badly because I use procmail with deliver and it was simply throwing away all inbound email.

Handling output of #Dovecot's #doveadm made easy with #Python:

https://people.mpi-klsb.mpg.de/~pcernko/dovewrap.shtml

@blog As an old IT geek that started in this game long before the modern internet (I had an email address in the 1980s when all it could do was talk to UK or US universities or the military via JANET or DARPANET etc.over UUCP) I have been increasingly depressed at how big US tech has worked so hard at killing off the original,, open, standardised, federrated design principles of the web and sucking everyone into their closed silos.

Email is one of the original protocols in use and is still federated in theory but nearly everyone iis forced onto Google or Microsoft as there are few good alternatives.

I have hosted own email (plus calendar and contacts) for 25 years now. Not too tricky if you are IT savvy... but...

My stack (all open source):

Opensuse Linux
Postfix email server
MariaDB database
Dovecot IMAP server
Apache web server
Amavis anti-spam/anti-virus
Spamassasin spam filters
SOGo groupware

Plus good secure DNS with SPF, DKIM and DMARC records and reverse-ip for the server.

Give it a go!

#opensuse #linux #postfix #dovecot #mariadb #apache #sogo #selfhosting #email

Debugging #Dovecot for three months to end up, writing this mail:

https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/6JSKVADVT36H7HZE3LNN5D5OWQKPJG5H/

So imapsync is not packaged any more in Debian (I understand it's partly proprietary these days?), and Cyrus IMAP and Dovecot packages cannot be installed simultaneously. This is not going to make migration easier.

#dovecot #cyrusimap #debian #imapsync

@frehi I'm already thinking about forking the replication code and porting it to 2.4. This was even motivated by a mail from Aki on the mailing list.

I'm using #Dovecot now for >20y and still think, it is the best solution currently. But I also need to check for alternatives like #Stalwart.

Upgrading from Debian 12 Bookworm to Debian 13 Trixie

Debian 13 Trixie is currently frozen and will be released later this year in 2025, I expect somewhere in or near summer. If you are a bit familiar with Debian and with reporting bugs, now is a good moment to start updating your desktop systems to Trixie and reporting bugs. In my experience, Trixie is very stable on the desktop and offers a lot of improvements over Bookworm. Keep in mind that […]

https://blog.frehi.be/2023/06/04/upgrading-from-debian-12-bookworm-to-debian-13-trixie/

#Debian #dovecot #Linux #trixie

Migrating to Cyrus IMAP sounds tempting now.

#cyrus #imap #mailserver #dovecot

Dovecot 2.4 entered Debian Trixie. I'm a bit nervous to do the update,because the configuration has changed a lot, so this will require a bit of work.

#debian #trixie #dovecot

Alors j’aime beaucoup la rolling-release, mais parfois, c’est vraiment la punition des enfers… Surtout quand le soft n’a prévu **AUCUN** upgrade path.

Le passage de #dovecot 2.3 à 2.4, c’est la misère. Alors oui, ils ont publié une page longue comme le bras de changements, et oui, c’est du perso donc j’ai pas un deuxième serveur pour faire la migration. Mais il faut littéralement TOUT reprendre. Et quand c’est une conf qui a évolué au fil de l’eau depuis 10 ans, c’est IN-FER-NAL…

#sysadmin

Hey #BSD friends!

Is there a way to set up oauth2 on Dovecot for authentication? (All local Auth, no Google or Microsoft involved). Do I have to run some big chunky java blob like keycloak or is there a much lighter weight implementation in C somewhere?

#OpenBSD #dovecot #opensmtpd #oauth2

P.S. I got down from 33GB to 22GB in one mailbox. Individual mail differences in compression between level 3 and level 22 did not exceed 0.05% #zstd #mail #compression #dovecot

2/2 I also tested the impact of compression levels and I can say, it is not worth the CPU to go beyond the default #zstd level of 3. Base64 encoded mail attachments do not compress very well. This way it is fast and reliable.

To move the mailbox to the new server, I just resynced the newly creates maildir:username@domain.tld and configured the new dovecot similarly for compression and access.

Voila!

#mail #compression #dovecot

1/2 I had to move my #mail server and wanted to use #compression. The docs are, as often, not really helpful. Ultimately, after some testing the best way to do it is, as in a side note in the #dovecot docs, to use "doveadm". First configure to use zlib globally in mail_plugins and configure it to use zstd with the default level. Then just do

doveadm -v -o maildir_copy_with_hardlinks=no backup -u username maildir:user@domain.tld

Whilst migrating from my very manual email setup to something orchestrated by ansible and highly-available, I have come upon all sorts if jankiness I don't remember configuring.

Currently, I have multiple working MX servers, but only one postfix submission server. The MX's currently all point to a single dovecot server for LMTP, and it also pulls double-duty as my IMAP server.

Next on my list for ansible configuration:

• Set up acme.sh so that each MX can handle its own certificates for postfix and dovecot
• Configure Submission, LMTP and IMAP
• Configure extra mail services, such as opendkim, opendmarc, spf checking, dovecot indexing

This has been a real learning experience, and with any luck will get me to the point where I'm able to spin up/down new mail handlers just by adding hostnames to an ansible inventory list.

#sysadmin #homelab #ansible #dovecot #postfix #highavailability

I can't use the v3 mail-compress and I can't use the scripts flying around, so I wanted to do it using on-board tools of dovecot.
#Dovecot #zlib #dsync #help

#Dovecot Does anyone know how I can use the #zlib plugin to compress my mail archive while transferring from another server? I tried to set it up, but the mail just comes over as-is. The docs suggest that it should convert with #dsync to compressed files. I seem to miss something. #help

https://doc.dovecot.org/2.3/configuration_manual/zlib_plugin/

Bericht KW17:

- Mo: Feiertag
- Di-Do: Reise nach #Dresden zur Vorbereitung einer Migration von #SoGo nach #Groupoffice. #Dokumentation erstellt, #Konten aufgeräumt und den kompletten E-Mail Bestand (680GB) des #Dovecot #IMAP Servers migriert. GroupOffice eingerichtet und an Kundenwünsche angepasst.
- Fr: Nacharbeiten, Buchhaltung, Kleinigkeiten

Highlight: Es ist schön zu sehen wie liebevoll manche Geschäftsführer das Arbeitsumfeld der Mitarbeiter gestalten. So hält man Ressourcen!