>>>>> "NB" == Norbert Bollow <firstname.lastname@example.org> writes:
NB> I have to disappoint you here...
Not at all.
NB> [...] I'm going to call validate from bf-batcher (a replacement for TLB
NB> which will allow Bouncefilter to be used outside of its natural
That's one of the reasons I removed the validator's need for globals.
You'll probably have to get rid of the logging calls, though.
When you say you're "replacing" TLB, are you duplicating all of the
functionality? Unless you're rolling it all yourself, I think the
Mj::Deliver code is better than what's in TLB. And it might be nice to
make use of the delivery_rules syntax so we have some uniformity.
(delivery_rules allows all of the expressiveness of the TLB config file
stuff without any Perl. And I'm proud of my nested keyed list parser.)
Actually I think you can just use Mj::Deliver as is; it has no reliance on
any other part of Majordomo except for the Logger and its input variables.
But if you're using the TLB code, beware the unfixable Perl signal bug
which makes non-SMTP delivery completely unreliable.
This reminds me: the current lack of explicit copyright on the code means
that you can't legally do anything with it. We're going to have to pick a
license, which is something I've been dreading. I like an Apache/BSD style
that says you can do anything you want except remove the copyright notice
or advertise a derivative work as Majordomo. Unfortunately I hate legal
stuff. Anyone want to form the "Majordomo Development Group" (or
consortium or whatever)?