Re: Emergency! Workaround needed for failing mailet

[Ian Lewis <ia...@gmail.com>]

Kent,

I'm guessing a lot but If by "trapping these in the repository" you mean
putting them in local mailboxes then I would guess that you could just put
the LocalDelivery or ToRepository (or whatever you are using) mailet before
your custom mailets in the processor part of the config.xml and restart
James.

However, though I'm not sure what your custom mailets do or how your mailet
is failing, since your mailet IS failing I would guess you just want to
comment out the mailet that is failing from the config.xml and restart
James. Then it would continue to process the mails into the repository but
would omit running the failing mailet.

After you fix the problem, redeploy your custom mailet that was failing,
uncomment out the mailet in the config.xml and restart james again.

2007/12/6, Kent Butler < kbutler@englehomes.com>:
>
> 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: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
>


-- 
Ian Lewis
ianlewis@member.fsf.org
http://www.ianlewis.org/