> I'll look over your code. :-) I don't think we need THREE sets > of matchers > and mailets for list serving, though, right?
No, one nice one would be great. subscription Moderation and confirmation is a top wish... ;-) > Based upon your earlier > comments regarding the API, is it OK to use sqlResources as a > utility class? I would say so, it depends whether you want to write a portable application or a James specific one.. > I don't expect that you'd want the Avalon Frameworks as a necessary > substrate. Doesn't bother me in this context, thats the point I was trying to make. > I really am not finding this to be true. JDBCListserv requires > two tables. > A member table and a list description table. The important queries look > like: Yeah, I'm confused now, I *thought* it worked, but perhaps I'm missing something. d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
