Saturday, March 31, 2007

Redditted and Digged

My Mailinator Architecture article was on reddit and digg today.

These were posted up there when the article was originally written but didn't get pushed to the front. Someone resubmitted apparently and off they went.

I've gotten a ton of nice comments - thanks folks!


Eric said...

Hey Paul. I highly recommend you scope out "greylisting".

It fits your application well and will cut ~80% of your traffic.

I've had it work for a similar sized production mail system for the last 6 months.

Great article btw....I enjoyed the read.

Ben Marklein said...

Hey Paul, great stuff. I recently wrote a Flash XMLSocket server with some high scalability requirements in Java. I looked at NIO and using it directly looked pretty hairy, so I figured that someone most have written a higher-level framework based on it. There are a bunch out there, and I ended up using Apache Mina. It's extremely easy to use, I had working code in a couple of hours. If you do decide to go the NIO route I'd highly recommend it. said...

Great Article. Two questions.

1. What do you think about people buying domains and redirecting them to Mailinator. I would be willing to pay the registration cost and have mailinator eat the mail.

2. Any chance of you releasing the compiled code so that other people can set up their copy.

You have done some great work. : Anatomy of a Spammy Campaign

Mailinator is a popular disposable email service. It's also become a great tool for QA Teams to test email receipt, acknowledgment, au...