> When I am finished, Redirect will have some additional functionality, and > will be the basis for all mailets that have redirect/forwarding behavior, > which is what Danny intended in the first place.
Yup, there is a lot of duplicated functionality in the standard mailets, I think we should be using inheritance properly to encapuslate this in one place. Plus a discussion on this list determined that the principle of mailets is not governed by any designed imperative to keep them small. > > I really like JDBCVirtualUserTable, the only thing it's missing for my > > need is a one to many relationship between aliases. > > Yes, I understood. :-) My primary concern is how the SQL query > is used to > implement the mapping, but I'll play with it. As you noted, the issue is > coming up with "a good database design that allows [mulitple rows to > represent] the 1:n relationship and still support the single select that > falls back to a catch-all alias." Just dipping my toe in this discussion.. Can't you simply allow mail which has no aliases from the single select, even if it matches the criteria, to pass through and be processed by a subsequent mailet, so that if there are no recipients it could be bounced or forwarded to the postmaster? d. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
