News for hackers. Stuff that matters.

A comment on Ten Commandments of How to Write an IMAP Client (2006). Parent comment

Re:Ten Commandments of How to Write an IMAP Client (2006) by pjc50 on Monday October 28, 2019 @07:46AM (#21376040)
It was bad even 20 years ago, I remember a discussion when we were trying to implement something coining the phrase "University of Washington brain damage". It seems to have been extremely tightly tied to the UW-IMAP implementations.

The need for a better protocol is why JMAP exists: https://jmap.io/spec-core.html

Although I see their point about non-REST, I think there's still a case for having a REST flavour available even if it may not be the most efficient.

I wonder if anyone's tried mail delivery over git repo yet.

[ Parent | on HN ]
Re:Ten Commandments of How to Write an IMAP Client (2006) by hyperrail on Monday October 28, 2019 @12:23PM (#21378353)
> University of Washington brain damage

This phrase made me laugh, because UW imapd was largely written by Mark Crispin, who invented the IMAP protocol!

It seems that in about 2007, Crispin forked UW IMAP to create his own IMAP server, "Panda IMAP" [1], which at least one website claims to be "fully compliant" with the IMAP RFCs while UW IMAP is not. [2]

[1] https://github.com/jonabbey/panda-imap

[2] https://imapwiki.org/ImapTest/ServerStatus

[ Parent | on HN ]
Re:Ten Commandments of How to Write an IMAP Client (2006) by Boulth on Monday October 28, 2019 @05:26PM (#21381887)
> Although I see their point about non-REST, I think there's still a case for having a REST flavour available even if it may not be the most efficient.

I was pretty disappointed when I found out how ugly are JMAP requests. I'd also like to see REST variant as messages and their parts should be easily mappable to resources. Too bad SMTP was not also included in JMAP. ActivityPub comes really close to SMTP over HTTP/JSON in my opinion.

[ Parent | on HN ]