[Mailman-Developers] Intern

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On May 7, 2008, at 5:37 AM, Ian Eiloart 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.

I would definitely start with the docs in mailman/queue/docs.  These  
describe the various queues, what their responsibilities are, where  
they get mail from and where they send mail to.  Most messages will  
come in via the lmtp or incoming queues, so think of these as the  
entrances for email into the system.

There are some general docs in mailman/docs which describe the data  
objects you'll be dealing with, such as users, addresses, mailing  
lists, etc.

Next, look at the mailman/pipeline/docs for how the message pipeline  
processor works, and at mailman/rules/docs for how the individual rule  
implementations work.

If that still doesn't help, let me know and I will attempt to add more  
doctests to fill in the gaps.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkgw3FEACgkQ2YZpQepbvXGsBQCfaa37srmcZ5iQpo0NEra70TUX
8+YAoKjk1KmCb8qre6R5Ff8mTodLFDn5
=hE8+
-----END PGP SIGNATURE-----