Hi Kent,
put a code like the following before your custom mailets get invoked:
<!-- Logs any messages to the repository specified -->
<mailet match="All" class="ToRepository">
<repositoryPath> file://var/mail/emergency/</repositoryPath>
<passThrough> true </passThrough>
</mailet>
With <passThrough> true </passThrough> a copy of the email will be saved in the
repository and the original one will
continue to flow through the processors; if you just want to save the email and
stop processing it, put instead
<passThrough> false </passThrough> (it's the default behaviour).
Hope it helps,
Vincenzo
Kent Butler wrote:
> Hi -
> We've got a mailet failing in production - what I'd like to do is:
> * continue to accept emails from clients
> * trap these in the repository, before my custom mailets get invoked in
> the handler chain
> * process these after I fix the problem
>
> I know how to do the third part. Sorry that the second item is fuzzy -
> it's my poor memory of exactly how the internals operate. Our
> configuration is pretty standard, just a couple deployed custom Mailets.
>
> We're using the default FS repository. I would figure this out for
> myself if it weren't an emergency!
>
> Thanks for ideas -
> Kent
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
