--- Steve Brewin <[EMAIL PROTECTED]> 內容：
> One thing that immediately troubles me is how Mailet
> pipelining would work.
> Currently we have a Linear Processor that is
> responsible for workflow;
> invoking Mailets based on a mail's state.
The avalon powered Mailet behave in exactly the same
way a
t-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/javamail-1.3/mail.jar:/usr/local/gump/public/workspace/avalon/framework/target/avalon-framework-20040623.jar:/usr/local/gump/public/workspace/avalo
Hi,
Just a quick note to say thanks for the input. I'm going to have to brush up
on my Avalon knowledge before I can understand the impact of such an
approach - gains, losses, level of effort, etc - and make any meaningful
comments.
One thing that immediately troubles me is how Mailet pipelining
Mine are simple...
0) Debug the mbox random access file class, update the mbox file handler and
commit them both
1) Sort out user attributes. This is done for file user stores, but the db
stuff needs to be re-worked as I'm not happy with it
2) Get the current mailbox system to support folders
3) G
I remember mailet and smtpserver logs...
If I have the problem again, I'll adopt Hes' scheme, probably.
Regards.
Carlos.
Noel J. Bergman escribió:
I had logs with 20MB and folder size was more than 700MB in less than 5
minutes.
Sounds like you might have a problem in your config. Which logs a
