Mastodon

Bjarni |grep -i techOne of the things <a href="https://floss.social/tags/Mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailpile</a> 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 <a href="https://floss.social/tags/moggie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#moggie</a> 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?

Bjarni |grep -i techWatching <a href="https://floss.social/tags/moggie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#moggie</a> copy e-mails out of my old encrypted <a href="https://floss.social/tags/Mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailpile</a> 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 <a href="https://floss.social/tags/Mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailpile</a> into a new <a href="https://floss.social/tags/moggie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#moggie</a> setup, then my migration toolchain will be complete!

Bjarni |grep -i techI 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 <a href="https://floss.social/tags/Mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailpile</a> was hot shit and <a href="https://floss.social/tags/Snowden" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Snowden</a>'s revelations all the news and there were [maybe] spies at our community cons, I'd be VERY suspicious right about now...

Swapneel PatnekarFolks, I am exploring webmail clients for my personal use.My first preference was Mailpile (<a href="https://www.mailpile.is/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.mailpile.is/</a>) but it's still under development. Something similar with OpenPGP support would be great. What are you using?<a href="https://infosec.exchange/tags/mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mailpile</a> <a href="https://infosec.exchange/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a>

Bjarni |grep -i techToday I am porting <a href="https://floss.social/tags/Mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailpile</a> v1's bayesian filter over to <a href="https://floss.social/tags/moggie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#moggie</a>.Mostly for <a href="https://floss.social/tags/spam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#spam</a>, but also for auto-tagging other things. So far I've deleted a lot of unused code, which seems like a good thing!

Bjarni |grep -i techIn <a href="https://floss.social/tags/Mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailpile</a> 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)

Bjarni |grep -i techI've been having a random brainwave today, which I am going to sleep on for weeks (probably months) before I take action.For <a href="https://floss.social/tags/Mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailpile</a> 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 freedomsSecurity does suffer. But how much? Dunno, I need to mull it over. Feel free to object!

Bjarni |grep -i techIt 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 <a href="https://floss.social/tags/mbox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mbox</a> 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 href="https://floss.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a> <a href="https://floss.social/tags/moggie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#moggie</a> <a href="https://floss.social/tags/mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mailpile</a>

Bjarni |grep -i techI've been helping friend these past few days, as they struggle to get <a href="https://floss.social/tags/Mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailpile</a> v1 to do their bidding. To be honest, the jury is still out on whether we succeed or throw in the towel.So many things are just broken!I'd like to blame bit-rot, but honestly, the design was just wrong in too many places. And at the same time, I keep coming across little things that were also really well done.Weird feeling. Pride and shame all jumbled together. Glorious mistakes and cringe victories.

syd 💕<a href="https://floss.social/@HerraBRE" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@HerraBRE</a> Really cool! Very excited maybe one day hosting mails with <a href="https://github.com/mjl-/mox" rel="nofollow noopener noreferrer" target="_blank">https://github.com/mjl-/mox</a> and reading them with <a href="https://mastodon.social/tags/mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mailpile</a> <3

Bjarni |grep -i techI just published a new blog post on the <a href="https://floss.social/tags/Mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailpile</a> website, discussing the grant we are getting from <a href="https://floss.social/tags/NLNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NLNet</a> and what we are going to do with the money: <a href="https://www.mailpile.is/blog/2023-05-01_A_Mail_Client_in_Six_Steps.html" rel="nofollow noopener noreferrer" target="_blank">https://www.mailpile.is/blog/2023-05-01_A_Mail_Client_in_Six_Steps.html</a>The tl;dr is that we are bringing <a href="https://floss.social/tags/moggie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#moggie</a> from "a thing Bjarni hacks on as often as he can", to "a new terminal mode e-mail client which people should be able to use."I'm pretty excited about this!

Bjarni |grep -i techThis morning I taught `moggie email` to generate e-mails with protected headers, as described in this Internet Draft (co-authored by yours truly):<a href="https://www.ietf.org/archive/id/draft-autocrypt-lamps-protected-headers-02.html" rel="nofollow noopener noreferrer" target="_blank">https://www.ietf.org/archive/id/draft-autocrypt-lamps-protected-headers-02.html</a>This extends PGP/MIME signatures to cover important message headers, and optionally allows header encryption, including the Subject in particular.Progress!<a href="https://floss.social/tags/moggie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#moggie</a> <a href="https://floss.social/tags/mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mailpile</a> <a href="https://floss.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> <a href="https://floss.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a>

Bjarni |grep -i techIt's kinda fun when you need some sample data, and you know that there is an Internet Draft with your name on it, that contains exactly what you need...<a href="https://www.ietf.org/archive/id/draft-bre-openpgp-samples-01.html" rel="nofollow noopener noreferrer" target="_blank">https://www.ietf.org/archive/id/draft-bre-openpgp-samples-01.html</a><a href="https://floss.social/tags/openpgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openpgp</a> <a href="https://floss.social/tags/moggie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#moggie</a> <a href="https://floss.social/tags/mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mailpile</a>

Bjarni |grep -i techInstalling the old <a href="https://floss.social/tags/mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mailpile</a> v1 has become more and more difficult. This is kinda OK, as development there has halted and I don't want new users on that code-base...But it's also really not OK for those who want to examine Mailpile v1 or worse, have old Mailpile data lying around which they now have trouble accessing.So today I built and published <a href="https://floss.social/tags/Docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Docker</a> images which make it easy to run Mailpile v1 on a modern distro: <a href="https://github.com/mailpile/Mailpile-v1-Docker" rel="nofollow noopener noreferrer" target="_blank">https://github.com/mailpile/Mailpile-v1-Docker</a>Feedback is welcome!

njoseph :fbx:<a href="https://social.treehouse.systems/@deadsuperhero" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@deadsuperhero</a> Did you give <a href="https://social.masto.host/tags/Mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailpile</a> a try? <a href="https://www.mailpile.is/" rel="nofollow noopener noreferrer" target="_blank">https://www.mailpile.is/</a>

Bjarni |grep -i techIt has been a good, geeky work-week so far. Not much tootin' been busy.I did some <a href="https://floss.social/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devops</a> twiddling for <a href="https://floss.social/tags/pagekite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pagekite</a>. Yay SSL certs?Made more progress on grant applications for <a href="https://floss.social/tags/Mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailpile</a>.Studied <a href="https://floss.social/tags/Matter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Matter</a> (<a href="https://en.wikipedia.org/wiki/Matter_(standard)" rel="nofollow noopener noreferrer" target="_blank">https://en.wikipedia.org/wiki/Matter_(standard)</a> ) a bit, within the context of <a href="https://floss.social/tags/esp32" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#esp32</a> and <a href="https://floss.social/tags/micropython" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#micropython</a> development.I also had multiple naps and stared out the window a lot going HMM.Now it's time for another window gazing session, before I dive back into <a href="https://floss.social/tags/moggie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#moggie</a> related <a href="https://floss.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenPGP</a> work...

Bjarni |grep -i techFeeling vaguely proud of the old <a href="https://floss.social/tags/Mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailpile</a> v1 bayesian <a href="https://floss.social/tags/spam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#spam</a> filter, which successfully showed me my legit <a href="https://floss.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a> from DHL last week, while still sending all the DHL-themed <a href="https://floss.social/tags/phishing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#phishing</a> straight to spam.This is without using any DNS based blacklists or anything of that nature, just pure content analysis.Generating keywords that represent message structure and other such things, to better train the spam filter, is one of the more interesting parts of this project. It's fun to see it work!

Bjarni |grep -i techHaving idle thoughts about replication and non-email data (contacts, calendar events) for <a href="https://floss.social/tags/moggie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#moggie</a>.<a href="https://floss.social/tags/Mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Mailpile</a> v1 couldn't replicate. It was a significant limitation which I should probably address this time around.So many things to think about...

Bjarni |grep -i techI wrote a long e-mail to <a href="https://floss.social/tags/NLNet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NLNet</a> yesterday, answering questions they have about my <a href="https://floss.social/tags/moggie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#moggie</a> / <a href="https://floss.social/tags/mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mailpile</a> v2 development plans.How did I come up with X months? It's just how much time I have available! Do I have a roadmap? Not really, but it's in my head? Do I plan collaboration with other projects? Not just yet, I'm being introverted and stealthy still?Not sure it's what they wanted to hear, but honesty is the only policy. I gave lots of details.But maybe I *should* publish a better roadmap?

Bjarni |grep -i techA milestone! `moggie email` made its first SMTP connection today, and successfully failed to send a message!Successfully, because it correctly gathered and reported the errors.Sending is easy - making sense of things when they fail, in a way I can present clearly to an end-user, is a bit more work.The SMTP client design is based on Mailpile v1 code, but rewritten from scratch using <a href="https://floss.social/tags/aiosmtplib" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aiosmtplib</a>.This tool is very close to being useful now.<a href="https://floss.social/tags/moggie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#moggie</a> <a href="https://floss.social/tags/mailpile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mailpile</a> <a href="https://floss.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#email</a> <a href="https://floss.social/tags/smtp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#smtp</a>

Recent searches

Search options

Administered by:

Server stats:

#mailpile