> While Mailman is not current a good choice for this, the
> architecture that we've been discussing for V3 (essentially a mix of
> discrete processing and process queues) would adapt to this pattern
> easily.
My current thought are to leave queue management and outward mail delivery
with exim, as we can use the logging output in an integrated fashion with
normal mail. This will likely be a dedicated exim process/queue/etc. rather
than part of the normal mailer. I *like* the way exim queues mail, attempt
retries and logs success and error...
The rest of the processes; mailing list membership management,
authentication, sender verification, digests, archives etc. will be
somewhere else.
The current candidate is a set of perl modules / functions built ontop of
MIMI:: and Mail:: objects. More later...
Peter
