Replied to Yann Büchau 
@nobodyinperson
I've been doing that for over 20 years with #dovecot. For a while I even used #fetchmail to pull down emails to it.
Recent searches
Search options
#dovecot
2 posts2 participants2 posts today
Replied to Yann Büchau
@nobodyinperson yes, #Dovecot is fine for this. Very stable too.
#eMail #selfHosting gurus: I am looking for the simplest possible way to host myself a mailbox I can add to my email clients (Thunderbird, phone, etc.) as usual, so I can move mails there to free up space on the 3rd party "real" emails, then back them up separately on my server.
I do not want receiving or sending emails to work. Just an IMAP or whatever box I can shove emails in the face by dragging them in Thunderbird or with a script.
Ideally available in #NixOS
I had struggles with the #Dovecot 2.4.0 update, because of the completely changed config spec (fedi reported).
Guess what, the update from 2.4.0 to 2.4.1 broke it again.
This time, because there popped up a new CFLAG in the build script, requiring the CPU to have #AVX suppport.
Well, my servers CPU is a Dual-Core Pentium G3220 _not_ knowing this extension 
Replied in thread
@stalwartlabs@mastodon.social @florianoverkamp@ohai.social @hans@social.woefdram.nl
would #dovecot still be a viable solution for single instance with very few users?
would #dovecot still be a viable solution for single instance with very few users?
I just found out that Dovecot 2.4 is a crippled version of Dovecot 2.3: no more clustering support, the director function has been removed. If you want to do clustering now, you'll have to buy a Pro license.
https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html#removed-features
So, although I've used Dovecot for years, both private and for work, it seems like this is the end of the line for me.
At the same time I see what @Stalwart Labs can do. Yes, clustering, for one. And a whole lot more, including bayesian classification, analysis of DMARC reports and even a reputation database.
I'm really impressed by what it can do. Bit hesitant about the fact that it's still only version 0.11.5 though, smells alpha...
Looks like Stalwart is the future for me.
https://stalw.art/docs/cluster/overview
#Dovecot #Stalwart #E-mail #DMARC
https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html#removed-features
So, although I've used Dovecot for years, both private and for work, it seems like this is the end of the line for me.
At the same time I see what @Stalwart Labs can do. Yes, clustering, for one. And a whole lot more, including bayesian classification, analysis of DMARC reports and even a reputation database.
I'm really impressed by what it can do. Bit hesitant about the fact that it's still only version 0.11.5 though, smells alpha...
Looks like Stalwart is the future for me.
https://stalw.art/docs/cluster/overview
#Dovecot #Stalwart #E-mail #DMARC
doc.dovecot.org2.3 to 2.4 | Dovecot CEDovecot CE Documentation
Bin gerade sooo zufrieden. #Dovecot ist auf #FreeBSD nun so konfiguriert, dass ich weiterhin #mutt und #procmail wie gewohnt nutzen kann und parallel dazu, ohne Konflikte, #IMAP Clients wie #K9Mail und #Thunderbird.
Nicht, dass ich mit #mutt unzufrieden wäre: Aber gerade am Smartphone ist #K9Mail schon praktischer als mit #connectbot via ssh #mutt zu bedienen.
Und manche Emails sind - leider - mit Thunderbird besser zu handhaben, z.B. solche mit Bestätigungs-URLs mit > 512 Zeichen.
I've set up #dovecot on my #vps #mailserver, and I want #systemd to restart it on failure or if it's killed. So in `/etc/systemd/system/dovecot.service.d/restart.conf` I have
`[Service]
Restart=always
RestartSec=5s`
But when I pkill the process it doesn't seem to be restarting. I have rebooted. Anyone know why that would be?
#AskFedi #FediTechSupport #Linux
I've Got Mail https://bonesmoses.org/2025/ive-got-mail/
bonesmoses.org · I've Got MailI’ve finally gotten tired of maintaining my own mail server. I’ve been maintaining it since 1999 in one way or another, and I think it’s just time to take it behind the shed and put it out of my misery.
As to how I reached this decision and what I intend to do about it, well… that’s a story.
Oh my fucking god.....you renamed all of the SSL setting keys, but you didn't take the opportunity to name them tls_*, but kept them ssl_*??!
#fedihelp , please: I'm #selfhosting #dovecot and #postfix and running out of disk space with my mails reaching back into last century. I'd like to remove the oldest ones and keep an archive of any kind on a different host. What would be the easiest way to achieve that?
Maybe just imap-sync to some special maildir?
Edit:typo
Considering to migrate off #Google and other US #bigtech dependencies since they seem to get stuck deep in #Trump|s asshole. What is supposed to be the "gold standard" replacement for self hosting a tiny OSS mail server (own domain, 4 accounts, IMAP + mobile + web client) these days? Long years ago I've used #postfix + #dovecot. Is still still the way to go?
found #k9 #Android or #thunderbird #Windows11 email client had expired #certificate error and would not download emails so I restarted dovecot on Linux server and error stopped #dovecot #postfix #certificate #error #linux certificate had been updated but Dovecot had not synced @thunderbird
Mein Mailserver läuft mit #Dovecot
Ich hab in einem Anfall geistiger Umnachtung in der Nacht am WE noch schnell auf 2.4 aktualisiert... und nicht realisiert, dass das massive Änderungen in den Config-Dateien zur Folge hat...
Also "noch schnell" die Configs angepasst...
Fairemail verbindet sich.
Aber Thunderbird zickt seither herum. Aber ordentlich!!!
Er kann sich nicht mehr einloggen.
Ich krieg im Dovecot-Log, dass die Verbindung zwar aktzeptiert wird (ssl) aber kein authentication_attempt stattfindet.
#Thunderbird schreibt mir, dass "Url failed with code..."
Das ist das Debug-Log von Thunderbird:
2025-02-26 07:46:15.775740 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop entering [this=770954ef3f00]
2025-02-26 07:46:15.776145 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop entering [this=770957d74600]
2025-02-26 07:46:15.776820 UTC - [Parent 677248: Main Thread]: I/IMAP exceeded connection cache limit:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen
2025-02-26 07:46:15.776853 UTC - [Parent 677248: Main Thread]: I/IMAP queuing url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen
2025-02-26 07:46:15.776869 UTC - [Parent 677248: Main Thread]: I/IMAP considering playing queued url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen
2025-02-26 07:46:15.776881 UTC - [Parent 677248: Main Thread]: I/IMAP creating protocol instance to play queued url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen
2025-02-26 07:46:15.776897 UTC - [Parent 677248: Main Thread]: I/IMAP exceeded connection cache limit:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen
2025-02-26 07:46:15.776909 UTC - [Parent 677248: Main Thread]: I/IMAP failed creating protocol instance to play queued url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen
2025-02-26 07:46:15.777125 UTC - [Parent 677248: Main Thread]: I/IMAP 770954ef3f00:imap.domain.tld:NA:SetupWithUrlCallback: clearing IMAP_CONNECTION_IS_OPEN
2025-02-26 07:46:15.777217 UTC - [Parent 677248: Main Thread]: I/IMAP 770954ef3f00:imap.domain.tld:NA:SetupSinkProxy: got m_imapMailFolderSink
2025-02-26 07:46:15.777302 UTC - [Parent 677248: Main Thread]: I/IMAP 770957d74600:imap.domain.tld:NA:SetupWithUrlCallback: clearing IMAP_CONNECTION_IS_OPEN
2025-02-26 07:46:15.777317 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:ProcessCurrentURL: entering
2025-02-26 07:46:15.777348 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:ProcessCurrentURL:imap://my.user@imap.domain.tld:143/discoverallboxes: = currentUrl
2025-02-26 07:46:15.777362 UTC - [Parent 677248: Main Thread]: I/IMAP 770957d74600:imap.domain.tld:NA:SetupSinkProxy: got m_imapMailFolderSink
2025-02-26 07:46:15.777404 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:ProcessCurrentURL: entering
2025-02-26 07:46:15.777420 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:ProcessCurrentURL:imap://my.user@imap.domain.tld:143/select%3E/INBOX: = currentUrl
2025-02-26 07:46:15.822761 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:CreateNewLineFromSocket: * OK [CAPABILITY +SPECIAL-USE STARTTLS AUTH=PLAIN] Dovecot ready.
2025-02-26 07:46:15.823122 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:CreateNewLineFromSocket: * OK [CAPABILITY +SPECIAL-USE STARTTLS AUTH=PLAIN] Dovecot ready.
2025-02-26 07:46:15.823329 UTC - [Parent 677248: IMAP]: D/IMAP SetConnectionStatus(0x80004005)
2025-02-26 07:46:15.823509 UTC - [Parent 677248: IMAP]: D/IMAP URL failed with code 0x80004005 (imap://my.user@imap.domain.tld:143/discoverallboxes)
2025-02-26 07:46:15.823573 UTC - [Parent 677248: IMAP]: D/IMAP SetConnectionStatus(0x80004005)
2025-02-26 07:46:15.823816 UTC - [Parent 677248: IMAP]: D/IMAP URL failed with code 0x80004005 (imap://my.user@imap.domain.tld:143/select%3E/INBOX)
2025-02-26 07:46:15.824515 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:ProcessCurrentURL: aborting queued urls
2025-02-26 07:46:15.824529 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:ProcessCurrentURL: aborting queued urls
2025-02-26 07:46:15.824723 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:TellThreadToDie: close socket connection
2025-02-26 07:46:15.824748 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop leaving [this=770954ef3f00]
2025-02-26 07:46:15.824760 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:TellThreadToDie: close socket connection
2025-02-26 07:46:15.824785 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop leaving [this=770957d74600]In Dovecot sehe ich bloß diese beiden Zeilen
Feb 26 08:52:16 mail dovecot[204586]: imap-login: Login aborted: Connection closed (no auth attempts in 0 secs) (no_auth_attempts): user=<>, rip=172.30.0.1, lip=172.30.0.9, session=<ryQk2gYvMp+sHgAB>
Feb 26 08:52:16 mail dovecot[204586]: imap-login: Login aborted: Connection closed (no auth attempts in 0 secs) (no_auth_attempts): user=<>, rip=172.30.0.1, lip=172.30.0.9, session=<zR8k2gYvIp+sHgAB>Es wird also nicht einmal ein Username mitgeschickt...
Es ist zum Verzweifeln.
Alle anderen Clients funktionieren.
Note to self (and anyone else interested): #Dovecot (which I use for #IMAP) does not seem to automatically notice when certificate PEM files are updated, so will happily just carry on using the ones it loaded at last restart through past their expiry despite those files on disc having been replaced. I don't think any of the other things I have using auto-renewed #LetsEncrypt certs need poking to load new certs... easy to fix, restart Dovecot. I wonder if there's an existing way to automate that with the cert renewal.
Continued thread
www.tiltedwindmillpress.comRun Your Own Mail Server paperback/ebook bundle – Tilted Windmill Press
A few months ago, I wrote an article about how to use a Dovecot plugin to give yourself push email on iOS devices: https://colincogle.name/blog/dovecot-with-apple-push/
Well, thanks to @gctnwl@newsie.social and countless GitHub users — i.e., https://github.com/freswa/dovecot-xaps-daemon/issues/43 — I regret to inform you all that the XAPPLEPUSHSERVICE concept might be dead.
This project relied on using macOS Server’s API’s to request a certificate for the Apple Push Notification Service, so that one could send yourself notifications. Well, macOS Server died a long time ago, configurations evolved into MDM profiles (which, honestly, are easier), and the certificate API was deprecated and then disabled last autumn to little fanfare.
Is there any hope for push IMAP on iOS in the future? Only time will tell. If you have a valid certificate, XAPSd will keep working until it expires, but after that, who knows? I might have to go back to fetching my email!
(Oh, and if it works for you, don’t upgrade to Dovecot 2.4. I wasted an evening migrating and unmigrating my config files.)
If anyone knows anyone at Apple, please let me know how to complain to something that’s not a feedback form.
Colin Cogle · Push Comes to Dove’By adding a few things to your Dovecot IMAP server, you can have instant new mail notifications on your Apple devices.
Continued thread
Ok what the heck, that looks like a thing to coordinatedly start on a Saturday 
E.g. I have Maildir as format.
Now docs say Maildir is just kept alife with little effort blabla.
Sounds like I should change that 
But to what? dbox?
For now, the fix is to pin 2.3 
*Info from dad: Mail-Server down
*checks docker ps: Dovecot "Restarting"
*checks docker logs: Permission denied 
*corrects permissions, to what log expects
*Still restarting 
*docker log: "unknown setting"
*checks docker tag
*searches release notes 
*
Dovecot 2.4 secure IMAP server has been released with a new signing key, experimental ARM64 Docker support, and major config changes.
https://linuxiac.com/dovecot-2-4-secure-imap-server-released/
