This subject has come up a few times. I suggested an approach to handling mailet and matcher config better, as did a few others. I even offered to write it. However, due to the distinct lack of enthusiasm for my (or any other) solution, I lost interest. I could be convinced to revisit this if some of the committers indicated that they were interested.
Cheers
ADK
Serge Sozonoff wrote:
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</bounceHandlers>
<bounceProcessors>name=DBBounceProcessor;database=......</bounceProcessors>
</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]>
