Lamson - email app coding without the palm sweat

Re:Lamson - email app coding without the palm sweat by snprbob86 on Friday July 03, 2009 @10:01PM (#686799)

I spent about 35 hours developing the first version of the mail handler we use on <www.classlet.com>. I took the knowledge I gained from that, turned around, and re-wrote it from scratch in about 15 hours.

Weighing in at under 500 lines of code, it makes heavy use of Python's mimetype and smtp libraries as well as some abstractions from Django's mail library. It operates on mail piped into stdin by procmail every 10 seconds as retrieved by fetchmail. The subsystem has basic logging and in the event of errors procmail dumps the entire message into an mbox file and notifies me. Retrying is as simple as `cat mbox | classlet/procmail.py`

That said: I applaud any attempt to make this easier, more robust, and more standard. Our mail processor is actually quite simple, but has a long way to go in terms of maturity.

I'd love to hear about other experiences with this stuff. I know the Posterius guys lurk around here, how about some insight? :-)

[ Parent | on HN ]

Re:Lamson - email app coding without the palm sweat by uggedal on Saturday July 04, 2009 @05:03AM (#687040)

I've also extracted Django's mail abstractions (since django.core.mail is dependant on django.settings) for a unreleased project I'm working on. We (I?) should probably make this a stand alone package (with the relevant tests from Django's test suite).

[ Parent | on HN ]

Re:Lamson - email app coding without the palm sweat by snprbob86 on Saturday July 04, 2009 @05:17AM (#687046)

That sounds like you're volunteering. Have at it; I won't steal your thunder :-)

[ Parent | on HN ]