Mailman architectural overview incomplete?

This document:
http://terri.zone12.com/doc/mailman/mailman-admin.pdf
describes on p. 4 the basics of incoming queue management. But it stops with outgoing queue details absent. Is this written up somewhere?
Dave
-- In modern fantasy (literary or governmental), killing people is the usual solution to the so-called war between good and evil. My books are not conceived in terms of such a war, and offer no simple answers to simplistic questions.
----- Ursula Le Guin

On 10/21/18 2:42 PM, Dave Stevens wrote:
This document:
http://terri.zone12.com/doc/mailman/mailman-admin.pdf
describes on p. 4 the basics of incoming queue management. But it stops with outgoing queue details absent. Is this written up somewhere?
If you're talking about section 2.4, replace the sentence "Messages in the incoming queue may also be stored for appending to digests." with "Messages in the incoming queue are finally stored in the outgoing queue for distribution to regular members and added to a digest.mbox for eventual distribution to digest members."
There really isn't more to say at that level.
For more detail about how outgoing messages are handled, see <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/...> and <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/...>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Dave Stevens
-
Mark Sapiro