Serge My 2c..
1/ *don't* access James for config, that is officially discouraged, and Not Supported, it may well not be possible in the next release. 2/ use the nastylooking hack for now, we can improve mailet/matcher config if its wanted, or use config files for your mailets I see no reason why that shouldn't be acceptable. 3/ tell us what you want from the config. look at the mailet plans wiki page. Why can't you split this all up into seperate mailet/matchers in their own linear processor? : <processor name="root"> <mailet match="RecipientIs=test1@localhost" class="ToProcessor"> <processorname>bounceprocessor</processorname> </mailet> </processor> <processor name="bounce> <mailet match="All" class="DNSBounce"/> <mailet match="All" class="....."/> </processor> Without knowing what your doing its hard to say exactly what the answer should be. d. > -----Original Message----- > From: Serge Sozonoff [mailto:[EMAIL PROTECTED]] > Sent: 27 January 2003 10:17 > To: James Developers List > Subject: Mailet Configuration > > > Hi Guys, > > Continuing on with my BounceHandler mailet idea, I would need to do > something like this in my configuration block for my mailet > > <mailet match="RecipientIs=test1@localhost" class="BounceHandler"> > <bounceHandlers> > <bounceHandler class="DSNBounce"/> > <bounceHandler class=".........."/> > </bounceHandlers> > <bounceProcessors> > <bounceProcessor class="DBBounceProcessor"> > <database>.....</database> > <....>...</...> > <bounceProcessor> > </bounceProcessors> > </mailet> > > However the mailet API does not give me access to this sort of thing and I > have not figured out if I can gain access directly to the James > Configuration object from my Mailet. I think not. > > As a temporary work around I could do something like this: > > <mailet match="RecipientIs=test1@localhost" class="BounceHandler"> > > <bounceHandlers>class=DSNBounce;class=QmailBounce;class=etc</bounc > eHandlers> > > <bounceProcessors>name=DBBounceProcessor;database=......</bouncePr > ocessors> > </mailet> > > But this is not very elegent and idealy I would at the very > minimum need to > pass additional config parameters to the bounceProcessors. > > Anyone have any ideas, suggestions? > > Thanks, > Sergei > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
