On 3/25/07, Steve Brewin <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote:
>
>
> On 3/24/07, Steve Brewin <[EMAIL PROTECTED]> wrote:
> > robert burrell donkin wrote:
> > >
>
> <snip>
>
> > > i've finished a MailAdapter that i can use to test SIEVE scripts.
> > > basically, it wraps a javamail message and preserves a
> recording of
> > > the actions accumulated when execute was called. this
> should allow me
> > > to test the (rather long) sieve script i spent last week
> generating
> > > from my client side filtering rules (in the end i used
> groovy since
> > > the XSLT was becoming unreadable).
> > >
> > > perhaps a sieve script check is something that others might find
> > > useful. shall i tidy it up and commit?
> >
> > Do you think this level of logging could be usefully folded
> back into JSieve
> > itself?
>
> maybe a delegating, monitoring MailAdaptor implementation would be
> generally useful but these utilities are just a simple way to automate
> script testing before upload.
I was thinking of a sandbox. Something which copied the target subset of the
live mailbox folder hierarchy to a temporary area and ran the script against
the copy with dummy implementations of the commands that cause mail to be
sent. Every action would be logged as normal and the resultant folder
contents examined so the effectiveness of the script could be fully
understood.
This would need to be tightly bound to the underlying mail server. As you
say, a specialized MailAdapter is probably the way to go.
No more than a low priority nice to have feature.
sounds like a good idea
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
