> Clearly something needs to be done about locking and thrashing in
> Majordomo, but I'm not sure this change (exponential backoff) isn't
> going to cause more problems than it solves.
This may be approaching heresey, but here goes:
Have any of you considered integrating the Majordomo features into
Manfredi's MailAgent package? Rafael has done considerable work in the
"infrastructure" needed to support a generic mail server and filter, but
as a mail server, it needs an "application" to build on top of it.
IMHO, Majordomo would be a good such application.
The win for Majordomo would be a fairly robust queueing mechanism and
underlying infrastructure to support the mail server functions.
Conceptually, it shouldn't be that hard: Mailagent is written in Perl,
and has good support for Perl "hooks", with an optional C code
interpreter for those who want it to go really fast, and don't have to
worry about multiple architectures running the filter.
I've done a *lot* of improvements to Majordomo, and am now at a nexus
requiring a decision to either:
a. submit my diffs to majordomo-workers for integration with Majordomo
proper;
b. migrate the features of Majordomo to another mail server "platform",
which has the necessary support for heavily-used mailers.
Any thoughts?
Alan
Follow-Ups:
|
|
