Don't know whether anybody of you guys uses #Apple Mail but I'd rather be careful:

https://www.linkedin.com/feed/update/urn:li:activity:7349803754226868224/

TL;DR: UI prefers #STARTTLS over #TLS for #IMAP (but actually for some reason uses both ports). Apple Product Security doesn't see a reason for immediate action.

My bottom line: a) Apple doesn't take security as relevant as they say b) there are probably lots of users like I was who have STARTTLS configured and don't know that.

I recommend to check whether you're affected. If so I'd configure that as recommended above and change your passwords.

#Apple #Mail.app + #Notes.app still use #STARTTLS #IMAP protocol as a default?

Did a "lsof -i Pn" on my Macbook to learn that Mail used for my providers both port 143 (insecure STARTTLS) + port 993 (#TLS). For sure I didn't explicitly configure this.

The checkbox in Accounts => Advanced and then ~"configure connection preferences automatically" is the culprit. Unchecking that, choose port 993 instead of 143 , restart the Mail.app (and Notes.app) everything is fine.

@ Apple : #wtf ?

So I guess I either try courier-imap server or cyrus-imapd. Not sure of the differences between the two or whether one is better than the other.

For a brief moment in time, #mutt was the perfect #email program for me, I had it configured just right, it really took email work off my hands. I tried it again many years ago, maybe with mutt-ng, but I remember configuring it was a nightmare, especially with several #IMAP servers, using different #SMTP.s for different accounts, automatically detecting and switching sender addresses, etc.
Any chance anyone has a suggestion how I should approach this to substitute Thunderbird at least partly?

Developing the twom database for Cyrus IMAP,
by Bron Gondwana at Fastmail (@fastmail).

"""
TIL: fcntl isn’t fair. Releasing the lock didn’t magically let a waiting writer proceed, the same process would often pick up the lock again without giving another process a chance. On busy files, writers could entirely starve.
"""

https://www.fastmail.com/blog/introducing-twom/

Sharing @futurile's excellent blog series on how to configure #IMAP and #SMTP for #NeoMutt, including setups for Runbox.

Configure IMAP, SMTP or msmtp, set up multiple accounts - this tutorial has you covered.

Check out the posts here: https://www.futurile.net/archives.html
https://www.futurile.net/2025/05/18/neomutt-email-native-imap-tutorial/

Big thanks to https://mastodon.social/@futurile

#Roundcube 1.5.10 (#LTS) has been released (#Webmail / #Mail / #IMAP / #SMTP / #LDAP / #Managesieve / #PHP / #MariaDB / #MySQL / #PostgreSQL / #SQLite / #OracleDB / #MSSQL / #LongTermSupport) https://roundcube.net/

#Roundcube 1.6.11 (stable) has been released (#Webmail / #Mail / #IMAP / #SMTP / #LDAP / #Managesieve / #PHP / #MariaDB / #MySQL / #PostgreSQL / #SQLite / #OracleDB / #MSSQL) https://roundcube.net/

Second part of my blog series on NeoMutt for CLI based email is out. All about how to configure #imap and #smtp for #neomutt :

https://www.futurile.net/2025/05/18/neomutt-email-native-imap-tutorial/

Also if you're into #gmail or using a specialist email provider like @runbox then it's covered.

Sending email using native #smtp or using msmtp

I just re-remembered that if I'd composed a bit of writing on my email client on one machine, I'd have been able to continue on another with no fuss and bother. it would "just be there."

We had a lot of The Cloud we needed with #IMAP back in 1986.

Messenger: Delta Chat

Obwohl es mehr als genug Messenger gibt, überzeugt Delta Chat durch Benutzerfreundlichkeit und erprobte Technik.

#Messenger #Delta_Chat #IMAP #GPG #E_Mail #Linux

https://gnulinux.ch/messenger-delta-chat

Anybody ever had problems with an #iphone and #IMAP on a #selfhosted #email server? Feel free to boost for fun.

I was just helping my wife and her mail app (iPhone 13, iOS 18.3.2) would just spin saying “connecting”. I’m standing next to her, with my iPhone 13 Pro, iOS 18.3.2 and I’m on the same WiFi checking email on the same server just fine.

I tried a bunch of things. Rebooting, using cellular data instead of WiFi, closing the mail app and opening it again. Nothing fixed it. The root cause seems to have been low power mode. Her battery was low; so the phone was in low power mode. I plugged it in, took it out of low power mode, and poof! Mail connects just fine.

This is reproducible. If I go to low power mode and pull down on the screen to try to fetch, no imap. It just spins saying “connecting.” Come out of low power mode, imap is fine and fast. One thing we both do that is not the default is fetch email. The default is to push, and the phone polls quite often. I figure that’s a waste of battery, so we have ours set to fetch every 30 minutes. I’m a bit of a nut, so there are probably LOTS of other things that are not the default.

Anybody have any ideas?

I’m sure all of us have used low power mode before, and I’m fairly sure I’ve checked email under low power mode. I’ve never seen this before. #selfhosting

@delta @feld @adbenitez
I've been trying #deltachat with #chatmail and normal #imap server the last few days (since my last messages). One thing I miss is a device management feature. For example, in case a device gets lost, I would like to be able to remove access. Afaik this is still not supported, correct? In that case, what would be the best way to discuss this as a feature proposal?

I've been working on a document