One of the things #Mailpile never did well, was processing bounces and other delivery status notifications (DSNs).
I am currently being side-tracked from what I was working on (sending mail), to add the features #moggie needs to do better.
As a start, I just want to recognize the DSN as part of the thread, the error is a reply to the message. Once the two are linked in this way, I can iterate on how they are presented in the UI.
Mutt doesn't appear to do even this much. Do other mail clients?
Watching #moggie copy e-mails out of my old encrypted #Mailpile storage, into a shiny new Maildir-in-a-ZIP is really very satisfying.
It would be nice if it were faster, but in practice this will be such a rare operation that it's probably not worth optimizing. At least not yet!
If I create a relatively simple command that replicates the tags from #Mailpile into a new #moggie setup, then my migration toolchain will be complete!
I moved back to Iceland from the UK a couple of months ago. Am in the UK for a few days, visiting, in our old flat.
There is a parcel! With my name on it! An EE WiFi hub and some other gadget as well? I didn't order this. Called EE - they have no record of sending this, no account in my name. They told me to bin it.
If this were 2014, when #Mailpile was hot shit and #Snowden's revelations all the news and there were [maybe] spies at our community cons, I'd be VERY suspicious right about now...
Folks, I am exploring webmail clients for my personal use.
My first preference was Mailpile (https://www.mailpile.is/) but it's still under development.
Something similar with OpenPGP support would be great. What are you using?
In #Mailpile v1, I one of the bits of code I spent the most time on, was exactly that - the TLS validation system.
At the time (it has improved since), Python's standard libraries made it almost impossible to make secure outgoing connections.
And TLS issues were hard to troubleshot. And because we had Opinions(tm), we wanted to sometimes use a TOFU policy for certs, and CA-based security at others. And sometimes we wanted to connect over Tor. But not always.
Thus: the Connection Broker. (2/n)
I've been having a random brainwave today, which I am going to sleep on for weeks (probably months) before I take action.
For #Mailpile v1, we were adamant that we would never provide a hosted service. For good reasons!
I find myself reconsidering, for two reasons:
1. Not everyone wants to host their own software
2. I think I've figured out how to do this in a way that doesn't harm user freedoms
Security does suffer. But how much? Dunno, I need to mull it over. Feel free to object!
It is very easy to write code that *usually* works with an mbox file.
It is surprisingly tricky to write code that *reliably* works with an #mbox file.
Almost impossible, actually, since there are multiple incompatible variants of the format.
I keep coming back to this code and finding new problems with it. That is a good thing, I guess? Making progress...
A free & open modern, fast email client with user-friendly encryption and privacy features - GitHub - mailpile/moggie: A free & open modern, fast email client with user-friendly encryption ...
GTech Booster
Bjarni |grep -i tech
Swapneel Patnekar
vo