Earlier quoted context omitted.
It also misses one of the biggest fundamental problems with SMTP: Lack of per-recipient replies. Though you could potentially mandate a single recipient per request. We wrote a plugin to emulate that in Haraka, where you just 400 (temp fail) each subsequent recipient. The downside is some sources just plain don't retry.
LMTP is a small modification of SMTP with a per-recipient response code - but I'm not sure what it's intended for. It isn't used on the internet. It's sometimes used as IPC within a mail server.
Modern email can be built from borrowed parts
151–160 of 165 posts
Re: Modern email can be built from borrowed parts
#152Earlier quoted context omitted.
That was on mobile. If that's intent, the result is highly aggravating.
I think you're focusing too much on your best practices paradigm and not enough on my design vision.
Anyhow. Depending on the viewport your panels do get in the way, it's 1/3 of the screen on mine for example. If you're going to hide the panels, hide them properly. That you show them at the top and bottom automatically, fine, though they could be smaller on mobile. However, you could at least consider the UX of using it on smaller viewports. If I want to scroll up a little bit while reading, they pop into view, making me have to scroll down to hide them again. Meaning I have to scroll higher up than intended, so I have enough space to scroll down. Another common user pattern is to slowly continually scroll too, and a tiny jitter upwards causes them to reappear, but requires comparatively massive downwards scrolling to hide again. Your site is not the only one to do this, but it's just bad design. Vision or no, and it's no justification, just an excuse. And then, what about left handed people? It's easier to accidentally click into the message box field, which opens up the keyboard and you'll have to close it. Pair this with it taking up the majority of thumb space for scrolling, given its size, and, well. Is it unreasonable for people to tell you it's aggravating? No. And this is without considering, and doing the minimum for, people who may suffer with controlling devices for whatever reason. Not by "bending over backwards" as some would have it, but at least taking such into consideration.
It's fine to have a vision of your intended or wanted design, but it's also important to be willing to reflect on how your vision may not necessarily be good design, depending on how one judges it, rather than just deflecting critique.
Re: Modern email can be built from borrowed parts
#153Earlier quoted context omitted.
The combination of "I have an idea for changing one of the fundamental experiences of modern life" and "my website is obnoxious and hostile" didn't really work for me.
The entire website is accessible; I dedicated ample time to it. This was a minor oversight, but I wouldn't call it hostility.
Strange then that you reject critique elsewhere. Accessibility is not just a checkbox, it's to consider and test the actual use of it.
Re: Modern email can be built from borrowed parts
#154Earlier quoted context omitted.
And HTTP transports many, many more things than hypertext. It seems like a sensible choice for this use case in terms of capabilities.
Why, what advantage does adding the extra layer bring? You can just open a socket and send JSON to it, you know, you don't need this layer. But if the layer brings advantages then you should, but you have to explain the advantages.
Re: Modern email can be built from borrowed parts
#155Earlier quoted context omitted.
Can you provide more feedback? What do you hate so much about current GUIs? (Working in this exact space)
None of them have good (or any) support for managesieve. Without managesieve (or some other autotagging mechanism), email is just a big pile of junk. Even Gmail doesn't support editing filters on the mobile app. It's ludicrous in 2026. And their filters are strictly weaker than Sieve. None of them have a feature to "quickly generate a filter rule from a message". None of them have a way to generate a forum-like inter…
Re: Modern email can be built from borrowed parts
#156Earlier quoted context omitted.
The unknown request will be buried in spam - a problem we have already, but worse. And I do not want an infinite thread conversation. I want to be able to split off - and perhaps archive and export - different conversations by topic. I recently had to some legal things, which included forwarding copies of a certain conversation to a lawyer. This turns out to be unreasonably difficult because email clients quote previ…
> The unknown request will be buried in spam - a problem we have already, but worse. Keep in mind that many people around the world already use this solution. In my case, I give senders a mechanism to go into my inbox without my explicit approval. The server sends them an email with a URL. They follow the instructions, and their email gets whitelisted. https://blog.nawaz.org/posts/2018/Sep/solving-my-email-probl...
Re: Modern email can be built from borrowed parts
#157Earlier quoted context omitted.
LMTP is a small modification of SMTP with a per-recipient response code - but I'm not sure what it's intended for. It isn't used on the internet. It's sometimes used as IPC within a mail server.
LMTP is for delivering to an IMAP (or JMAP) mailbox, generally. We also have a plugin for that. But it has certain flaws for exposing it to the internet (I just forget what they are right now).
Re: Modern email can be built from borrowed parts
#158Earlier quoted context omitted.
I think you're focusing too much on your best practices paradigm and not enough on my design vision.
Or perhaps you shouldn't get defensive of critique on your "design vision" such that you just write them off entirely like it has no value? You might like driving in the opposite lane, but rules say otherwise, and best practice can be likened to it because it's been decided on or landed that way due to multiple people being involved in the process of deciding those rules. Just as with best practices. There are best p…
Re: Modern email can be built from borrowed parts
#159Earlier quoted context omitted.
I think you're focusing too much on your best practices paradigm and not enough on my design vision.
Or perhaps the opposite is true. The content is solid. The presentation very much Gets In The Way.
Re: Modern email can be built from borrowed parts
#160Earlier quoted context omitted.
I'm sorry, but I disagree. The lowest interaction cost is scrolling; it's a natural, continuous, and almost involuntary gesture. Having to click or tap a button requires the user to stop, evaluate whether the title interests them, and decide to make the effort to tap. The interactions you're describing are intentional and measured. I'm sorry but if the content is truly all you care about, I recommend the previous opt…
> almost involuntary gesture Exactly, which is why attaching large UI shifts to that involuntary gesture makes the experience feel very unpredictable > activating your browser's reading mode Reading mode is a hack that's only needed because sites aren't already readable. You shouldn't have to activate it to be able to read the content. In addition, it doesn't always work well if the website didn't test it. On your we…