--On 6 May 2008 14:23:53 -0400 Barry Warsaw <[EMAIL PROTECTED]> wrote:
Does any of that help? You should definitely look at the Mailman 3 code and I'll be happy to answer any more questions you might have.
I'm sure all of that will help when I get into the kitchen, but I'm having problems finding the right street. I thought I'd be able to leap right in, but the more I look, the more I find that I need a map. Perhaps something describing the lifecycle of a typical email, and which bits of top level code are responsible for handling it at which stage. Or maybe just a recommended order for reading the doctests would do the job.
With that understanding, I can follow the API calls to get at the detail. -- Ian Eiloart IT Services, University of Sussex x3148 _______________________________________________ Mailman-Developers mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
