HN user

Mailtemi

112 karma
Posts0
Comments63
View on HN
No posts found.

As a JMAP client implementer, there’s a big plus, beside JMAP, in having an integrated server for email, contacts, and files. Some setups take days even for email, so an easy, fast setup saves a lot of time.

Also, after code the CalDAV ↔ JSCalendar part, using only IANA time zones instead of scattered ones in CalDAV components makes things much simpler.

Can confirm that (implemented JMAP). Deltas and asking for the entire mailbox instead of folder by folder is really good. And as a side effect: 1. Less client-side logic for sync. 2. There are many JSON parsers compared to IMAP, making it way easier to use. For example, in C++, you only need a JSON headers-only library, whereas IMAP is meh—only Linux, or clunky usage. Btw, I made one from scratch (IMAP Parser). 3. Goodies like offloading HTTP to the mobile network stack, which supports TLS 1.3 and offline (background) sync, compared to manually extracting certificates from an IMAP connection to validate against the device keychain. It's just 10x easier.

Mozilla diversifies by increasing the CEO's salary for nothing.

Wiki: In 2020, after returning to the position of CEO, Baker's salary was more than $3 million. In 2021, her salary rose again to more than $5 million, and again to nearly $7 million in 2022.

The new CEO brings computing for AI money bleed that almost no one wants.

Ten Years of JMAP 2 years ago

This is just a step toward offline support. It's not available yet, because Android comes first.

The app is ready for offline use, but I don't want to implement it without 'full text search.' I plan to use SQLite FTS5. My initial tests with search show that offline search is storage-expensive, which could be problematic for mobile devices. So, the edge cases have started to appear. But it's the most requested feature, and the most interesting/challenging to me :)

Ten Years of JMAP 2 years ago

Can you give an example of expensive binary data parsing?

Having implemented JMAP and IMAP protocols myself, I haven’t encountered a need in either protocol to send binary data to the server for sync/search operations that would require the server to perform expensive parsing.

JMAP offers many improvements, such as a stable messageId for each message and a state mechanism that allows the server to be queried for changes since the last saved state. This avoids the need for numerous IMAP SELECT commands per folder to check the state using CONSTORE/QRESYNC.

If CONSTORE/QRESYNC aren’t supported by the client, it results in very costly chunked queries just to verify if message flags are still the same.

The same applies to SEARCH—if a user has many folders, it requires multiple network hops to SELECT and query each folder. With JMAP, this can be done in a single API call.

Ten Years of JMAP 2 years ago

Neither Fastmail's JMAP for third-party apps nor Stalw.art supports Contacts/Calendars yet. Fastmail said that it will be enabled once it passes IETF standardization. Stalw.art also mentioned they will add support after the standard is finalized.

Ten Years of JMAP 2 years ago

JMAP uses fewer resources server-side, and with their scale, it will probably reduce operating costs. But it will depends on how much they will save compared with devel/migration costs.

Ten Years of JMAP 2 years ago

MSGraph is slower and not as convenient for email compared to JMAP. In addition to requiring more API calls for the same result, MSGraph starts throttling with HTTP 429 responses after several calls, making the initial synchronization much slower than JMAP or even IMAP.

Hopefully, next year there will be JMAP support for Contacts. As RFC drafts, there are already JMAP specifications for Files and Calendar...

I've followed your advice, 'Google it.'

"According to the company's filings, Mitchell Baker's compensation went from $5,591,406 in 2021 [PDF] to $6,903,089 in 2022." Did not continue to dig further.

Mozilla tanked a lot, even Thunderbird is doing better recently. So definitely part of the 'parasitic upper class.

Gmail is successful because it naturally is the biggest honeypot. Most antispam API filters are like accumulators. When a trend is detected, the rest are protected. But overall, it's about scale.

I used multi_index a lot in the past. However, since I also frequently use sqlite, I have decided to exclusively use SQLite for multi_index in memory. If there is a problem, temporarily using sqlite as a file makes it a lot easier to track the issue. When multi_index patterns become too complex, it's natural to wrap them in a unit test specifically designed for sqlite (multi_index).

Each JMAP server should include IMAP QRESYNC like functionality at least. Plus the ability to batch JMAP calls. For instance, if you have five folders with IMAP, it might take at least five hops to access them. With JMAP, it could be accomplished in just one call, returning the location of each new email in each folder.

Initially, the proposition relied on Fastmail protocol, which was/is superior to IMAP. It was pleasing that standardization began, as MS Activesync charged a few dollars per user just for the protocol. Even the Apache James mail server supported it as a draft. Despite becoming a standard make it better , but lost momentum.

Still hope at least both will add push notification to 3th party apps. And a BIG hope for https://stalw.art/

Already useful.

After googling for 1 hour how to test some features with openssl. Want to add comments for QA's, how to test production with pure openssl with som exotics like FIPS. Many links but scattered info.

Then I typed "how to test server not accept non fips ciphers with openssl 3". Wow!

IMAP IDLE needs an open connection. When the phone is locked all apps are suspended(connection closed) except if they are VOIP. So this makes IDLE unusable. Moreover an open connection takes more energy. So here comes push notification and from open protocols only JMAP has it.

The only credentials which will flow is OAuth/API token. Mailtemi (future)server would not store it, only ephemeral (http + cert check) connection to advice for push notification.JMAP and MSGraph protocols are fine by design. Gmail needs a bit of tweaking to hash email addresses , because in their API the key is email. There are edge cases like non ascii email addresses.

For IMAP there is no push protocol without a password knowledge. No plan/wish to deal/know/store it. But still I think of small open source AWS golang/nodejs code(+markeplace bridge). Just the password possession should be only of the owner.

Yes , I guess I need to update the site to include this info , as this question emerges too often. Some extra features like push notification will require subscription (probably a few $ a year). Right now it works (only in a dev environment) with MSGraph and Gmail. Just waiting for JMAP push notifications to be enabled by Fastmail , to release support for the tree protocols.

Honestly not sure how to answer this. Mailtemi is just like any other iOS email app. Actually it doesn't include even crash logging, just avoid sending anything to 3th party service. Just curious , is there any iOS open source email app? Proton-mail is not really an email client ,it's more like a viewer for their service.

It's not a hobby project. The app will remain free as it is now. But some extra features like push notification will require subscription (probably a few $ a year).