Fwd: mail server design

David Stainton dstainton415 at gmail.com
Thu May 29 10:33:25 UTC 2014


Hey Michael,

This reminds me of a conversation that came up a few days ago.
If you are going to write the client AND the server then why use SMTP at all?
Why not just use pond (https://pond.imperialviolet.org/)?


David


On Wed, May 28, 2014 at 11:50 PM, Michael Samuel <mik at miknet.net> wrote:
> Hi,
>
> I've drawn up a design for a mail server, which uses Tahoe-LAFS as a
> storage medium.
>
> The server part of this is relatively easy - getting clients right is
> almost certainly the hard part!
>
> A current brain dump of my design is here:
> https://gist.github.com/therealmik/4cd07c8025757d0d85e3
>
> Feedback is more than welcome - I don't expect to start coding for a few weeks.
>
> I'm not 100% familiar with LAFS semantics or API yet, so I expect
> parts of my design to be completely wrong/stupid.
>
> My project goals are:
> - Implement Inbound SMTP server
> - Implement Outbound SMTP server
> - Implement IMAP server
> - Implement Android sync client
>
> If there was a way to implement race-free directory changes, I'd
> implement this as just Maildir.  So if
> anyone can think of a high-level abstraction to achieve this I'd love
> to know about it.
>
> Regards,
>   Michael
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev



More information about the tahoe-dev mailing list