2/5 Further, the “native” connection to EWS/OWA within Thunderbird is only available in 140 when you enable a custom setting (search for “ews”). What you see in the new Account Hub will depend on whether that custom setting is enabled.
5/5 TbSync was a small challenge because, as has happened in the past with major Thunderbird updates, it was declared unsupported and automatically disabled by Thunderbird 140esr. Following the instructions in https://github.com/jobisoft/TbSync/issues/753#issuecomment-3051737579 (file-based reinstall of TbSync and EAS-4-TbSync) resolves the issue for now.
3/5 Right now, Exchange requires add-ons to work. Usually this means TbSync or OWL. Each of these has its own set of features and limitations to consider. Account Hub will show you Exchange in two flavors… one says “add-on required” and the other doesn’t. It’s the latter one that is the native integration in experimental form at this time (and does email ONLY for now).
4/5 Until now, I have been using IMAP+SMTP, and TbSync for address books and calendars. After going through a few iterations, I have now settled on using Exchange (native, experimental) accounts (yes, plural) for email and sticking with TbSync for calendars and address books.
1/5 @padraig @thunderbird Took a little searching but I am working again! Yay. The complexity is that which setup to use with Exchange can be legacy (POP3, IMAP+SMTP, EAS, EWS/OWA) or current Graph API. Thunderbird 140 supports all of the legacy API but not yet Graph API.
This is possibly SMTP error 552 
"552 Requested mail action aborted: exceeded storage allocation"
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?
#tfw You have to email a government agency, explain in excruciating detail why your mail server (and any other that enforces #DMARC) can't receive certain emails they're sending that fail their DMARC policy, and then cross your fingers and pray that the tier 1 customer service rep who reads your email forwards it to someone who can fix the problem AND said someone actually takes the time to do it. *sigh*
#smtp #SysAdmin #MailAdmin
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/
Remember the threads¹² about #LetsEncrypt removing a crucial key usage from certificates issued by them in predictive obedience to their premium sponsor Google?
We were at first concerned about #SMTP. While I had lived through this problem with #StartSSL by #StartCom back in 2011, I only had a vague recollection of Jabber but recalled in detail that it broke server-to-server SMTP verification (whether the receiving server acted on it or just documented it).
Well, turns out someone now reported that it indeed breaks #XMPP entirely: https://community.letsencrypt.org/t/do-not-remove-tls-client-auth-eku/237427/66
This means that it will soon no longer be possible at all to operate Jabber (XMPP) servers because the servers use the operating system’s CA certificate bundle for verification, which generally follows the major browsers’ root stores, which has requirements from the CA/Browser forum who apparently don’t care about anything else than the webbrowser, and so no CA whose root certificate is in that store will be allowed to issue certificates suitable for Jabber/XMPP server-to-server communication while these CAs are the only ones trusted by those servers.
So, yes, Google’s requirement change is after all breaking Jabber entirely. Ein Schelm, wer Böses dabei denkt.
While https://nerdcert.eu/ by @jwildeboer would in theory help, it’s not existent yet, and there’s not just the question of when it will be included in operating systems’ root CA stores but whether it will be included in them at all.
Google’s policy has no listed contact point, and the CA/B forum isn’t something mere mortals can complain to, so I’d appreciate if someone who can, and who has significant skills to argument this in English and is willing to, to bring it to them.
① mine: https://toot.mirbsd.org/@mirabilos/statuses/01JV8MDA4P895KK6F91SV7WET8
② jwildeboer’s: https://social.wildeboer.net/@jwildeboer/114516238307785904
Hi @delta 
I am making updates to https://delightful.coding.social/delightful-activitypub-development and bumped into this interesting #SMTP to #ActivityPub proof of concept. Just a heads-up to make you aware, in case it is interesting for #DeltaChat in some way or other.
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
@timixretroplays yikes...
Tho granted all #Freemailers are shit and some like https://web.de & https://gmx.de do force people to login on their website so their accounts don't get wiped.
Personally I use #aliases & forwarder for inbound eMails.
Maintenant, « Auto-hébergez une messagerie e-mail qui délivre » par les gens de #Galae.
Pourquoi auto-héberger ? Parmi les réponses : « parce que c'est possible »
Is it possible to configure #Gmail (web client) to send an email “from” an alias on a domain that I own, like alias@example.com, but using Gmail’s own #SMTP server, because I don’t have my own SMTP service for example.com?
Yes, I know that’s ripe for spam abuse. But Gmail docs are not clear on this. And I can verify that I control the alias and the domain.
This is for occasional one-off low-volume sends (eg not ongoing email marketing or newsletter).
Thanks!
From the archives, to ease your boredom:
"RFC7505 Means Yes, Your Domain Can Refuse to Handle Mail. Please Leave Us a TXT If You Do." (from 2021) https://nxdomain.no/~peter/rfc7505_means_yes_you_can_refuse_to_handle_mail.html #email #spam #antispam #rfc7505 #smtp #dns #cybercrime
@rl_dane @ShinjiLE if you or someone else wants to help argue, the thread is at https://community.letsencrypt.org/t/do-not-remove-tls-client-auth-eku/237427 (Discourse, so JS webbrowser), I’m exhausted.
