« Conservative coding | Main | What do you do when your success ... sucks? »

The Architecture of Mailinator

Fascinating description of the architectural evolution of the Mailinator service, from a what-you-would-expect sendmail connected to a web interface to mailboxes thing, to the current form. Which includes

  • Never touches disk - did away even with checkpointing!
  • Has its own simple smtp server to receive connections
  • Uses adaptive forgetting as a scaling tool
  • Deliberately manages smtp session length -- takes longer to accept mail when the server isn't busy, to slow spammers down, but goes fast when the server is loaded because it needs to. wow. Points for the idea, 10x score for actually implementing it :)
  • Optimized for "survival" above all other criteria

Well worth reading the whole thing through on the mailinator blog, there is is much wisdom here...

(via programming.reddit.com)

Comments (1)

dave:

Mailinator is one of the oldest disposable email service providers but unfortunately it is too popular and most of the webmasters have have blocked using @mailinator.com email addresses. when it comes to disposable emails it is always better to use multiple providers. try http://www.spaml.com (An instant disposable email service with less user interaction. It is a "no-click" service, where the user does not need to click to get the disposable address.)

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About

This page contains a single entry from the blog posted on March 31, 2007 12:13 AM.

The previous post in this blog was Conservative coding.

The next post in this blog is What do you do when your success ... sucks?.

Many more can be found on the main index page or by looking through the archives.

Powered by
Movable Type 3.33