RE: Email personalization

I'm just going to answer the ZMailman-specific questions on this
list.  Everything else is better discussed on mailman-developers.

>>>>> "TT" == Trevor Toenjes <[email protected]> writes:

    TT> The payload idea is the only way I can think of to handle this
    TT> efficiently.  Zope crunches a list from Mailman and creates a
    TT> database of the email address and email.  Mailman picks this
    TT> up and starts crunching delivery.  My guess this is better
    TT> than handing off emails one at a time.

I don't see how you can avoid handing the email off one at a time,
unless you're providing a template and expecting Mailman to fill that
template in with some data.  But then, of course, it's Mailman who's
handing it off one at a time to the MTA.  You can't have
personalization without a unique message per recipient.

In general, I think it's better to have Zope craft the email however
it wants, and then hand them off to Mailman one at a time.  There's
probably little difference in performance either way, and it would
complicate the interface if Mailman had to do it.

-Barry