#mbox — Public Fediverse posts

Lafite is the email client application of Medley Interlisp. The Lafite-to-mbox tool converts from the file format of Lafite mail, derived from the Laurel mailer developed at Xerox PARC for the Alto workstation, to the Unix mbox format.

https://github.com/Interlisp/lafite-to-mbox

#mbox #interlisp #email #retrocomputing

M-Box Adds Automated Agitation to the Lab-Box Film Development System https://petapixel.com/2025/09/05/m-box-adds-automated-agitation-to-the-lab-box-film-development-system/ #filmdevelopment #agitator #develop #Analog #analog #News #film #mbox

Me he hecho un script rapido en python para pasar los mensajes de #Gmail bajados en formato #mbox con #googletakeout con fecha a partir del 1 de enero de 2023 a un nuevo fichero mbox para importar en @Tutanota el mobox completo de 15GB ya está #7z con contraseña en un @veracrypt si todo va bien compartiré el python en un gist (es mu tonto y muy a lo rápido eso si).

#dataprivacy #ethicaldata

#Thunderbird のプロファイルをネットワークドライブに放り出しているとメールボックスが壊れがちなんですが、 #mbox 形式のメールボックスが1つの巨大なファイルという弱点を露呈しているだけで、 #Maildir 形式のメールボックスにすれば壊れづらくなるんじゃないかと思ってみたりはする ( #NFS でマウントしていた当時のワークステーションはどうなってるんだ)

#Thunderbird のプロファイルをネットワークドライブに放り出しているとメールボックスが壊れがちなんですが、 #mbox 形式のメールボックスが1つの巨大なファイルという弱点を露呈しているだけで、 #Maildir 形式のメールボックスにすれば壊れづらくなるんじゃないかと思ってみたりはする ( #NFS でマウントしていた当時のワークステーションはどうなってるんだ)

What do you use for backing up #IMAP (specifically, IMAP4) and keeping that backup up to date? #Maildir or #mbox format preferred, in that order.

What do you use for backing up #IMAP (specifically, IMAP4) and keeping that backup up to date? #Maildir or #mbox format preferred, in that order.

What do you use for backing up #IMAP (specifically, IMAP4) and keeping that backup up to date? #Maildir or #mbox format preferred, in that order.

What do you use for backing up #IMAP (specifically, IMAP4) and keeping that backup up to date? #Maildir or #mbox format preferred, in that order.

What do you use for backing up #IMAP (specifically, IMAP4) and keeping that backup up to date? #Maildir or #mbox format preferred, in that order.

I wrote a non-portable #RubyLang script to mangle #Maildir++ directories created from #MacOS #AppleMail exports using mb2md.pl from #Dovevot #IMAP under the hood. Apple Mail is weird; I don't know of anything that handles it natively.

To import stuff back, it needs to be in #mbox format. The separate *.mbox directories containing table_of_contents files may or may not be needed by Mail.

Alternatives to appending all the maildir files back into an mbox with the #formail utility for re-import?

I wrote a non-portable #RubyLang script to mangle #Maildir++ directories created from #MacOS #AppleMail exports using mb2md.pl from #Dovevot #IMAP under the hood. Apple Mail is weird; I don't know of anything that handles it natively.

To import stuff back, it needs to be in #mbox format. The separate *.mbox directories containing table_of_contents files may or may not be needed by Mail.

Alternatives to appending all the maildir files back into an mbox with the #formail utility for re-import?

I wrote a non-portable #RubyLang script to mangle #Maildir++ directories created from #MacOS #AppleMail exports using mb2md.pl from #Dovevot #IMAP under the hood. Apple Mail is weird; I don't know of anything that handles it natively.

To import stuff back, it needs to be in #mbox format. The separate *.mbox directories containing table_of_contents files may or may not be needed by Mail.

Alternatives to appending all the maildir files back into an mbox with the #formail utility for re-import?

Alright!

I think I've got code which generates numeric IDs for messages within a Maildir or Mbox, where the happy path is a relatively efficient direct-ish lookup of the target message, but enough info is encoded in the ID to recover and do the right thing if the message has moved, changed slightly or been replaced by an imposter.

Along with hooks to notify the calling code that IDs have become inefficient and a re-indexing might be warranted.

I can sleep now.

#moggie #email #maildir #mbox

Alright!

I think I've got code which generates numeric IDs for messages within a Maildir or Mbox, where the happy path is a relatively efficient direct-ish lookup of the target message, but enough info is encoded in the ID to recover and do the right thing if the message has moved, changed slightly or been replaced by an imposter.

Along with hooks to notify the calling code that IDs have become inefficient and a re-indexing might be warranted.

I can sleep now.

#moggie #email #maildir #mbox

Alright!

I think I've got code which generates numeric IDs for messages within a Maildir or Mbox, where the happy path is a relatively efficient direct-ish lookup of the target message, but enough info is encoded in the ID to recover and do the right thing if the message has moved, changed slightly or been replaced by an imposter.

Along with hooks to notify the calling code that IDs have become inefficient and a re-indexing might be warranted.

I can sleep now.

#moggie #email #maildir #mbox

Alright!

I think I've got code which generates numeric IDs for messages within a Maildir or Mbox, where the happy path is a relatively efficient direct-ish lookup of the target message, but enough info is encoded in the ID to recover and do the right thing if the message has moved, changed slightly or been replaced by an imposter.

Along with hooks to notify the calling code that IDs have become inefficient and a re-indexing might be warranted.

I can sleep now.

#moggie #email #maildir #mbox

Alright!

I think I've got code which generates numeric IDs for messages within a Maildir or Mbox, where the happy path is a relatively efficient direct-ish lookup of the target message, but enough info is encoded in the ID to recover and do the right thing if the message has moved, changed slightly or been replaced by an imposter.

Along with hooks to notify the calling code that IDs have become inefficient and a re-indexing might be warranted.

I can sleep now.

#moggie #email #maildir #mbox

@evan,

Good thing that's come out of this conversation is the emergence of a comparative stack for those unfamiliar the general pattern for interacting with inboxes and outboxes unleashed via #email.

#GMAIL is the hosted equivalent of @Mastodon.

#SMTP is the server-server protocol for delivering #mbox docs to inboxes and outboxes.

#IMAP4 is the client-server protocol (implemented by GMAIL but missing from Mastodon).

#ActivityStreams is the mbox payload equivalent.

/cc @Mastodon @mike

@evan,

I didn't say or insinuate that. I was simply expressing concern about the server-server centricity of @Mastodon in relation to its #ActivityPub support.

Simplest example is #Email where #SMTP plays the role of #ActivityPub re moving #mbox docs across outboxes and inboxes; with #IMAP4 (a client-server protocol) handling retrieval.

Even #GMAIL supports #IMAP4 (and #POP3) while also having its own #API.

@Mastodon should operate in similar fashion is my point 😀

/cc @mike

#b4 is a handy tool for managing code review via emailed patches. It was designed to work with #publicinbox archives but it works on arbitrary #mbox's as well. #sourcehut supports pulling the mbox for a thread so it works there too!

https://lists.sr.ht/~sircmpwn/public-inbox/patches/20099

who needs github...