Re: Three new drafts and a question

["Nigel Swinson" <[e-mail]>]

> I sent out three new sieve drafts last week that may be of interest:

As if this list wasn't busy enough at the moment ;o)

>  <http://www.ietf.org/internet-drafts/draft-degener-sieve-copy-00.txt>
>
> fileinto :copy, redirect :copy -- keyword parameter that
> prevents cancelling the implicit "keep".

Spelling mistake in first line of this paragraph... should read "possible"

   It is possibly to generate sieve code that perfectly
    <snip>

Yeah I like this idea.  I found the whole interaction between implicit keep
and discard really difficult to get my head round.  this extension sounds
like it will help.

>
<http://www.ietf.org/internet-drafts/draft-degener-sieve-editheader-00.txt>
>
>   Deleting, adding, and changing message header fields.

Heh, was thinking of authoring one of these soon.  Thanks for beating me to
it.  I haven't been able to digest it in detail yet but it looks ok to me on
a first pass :o)

>
<http://www.ietf.org/internet-drafts/draft-degener-sieve-multiscript-00.txt>
>
> Sequential execution of (unrelated) sieve scripts by the
> environment.  A meta-feature -- it doesn't define new sieve
> language elements -- that's interesting in particular in
> contrast to Cyrus's "include" draft.

When you are doing server/domain level filtering, you might want to allow a
server script to file into a specific user folder.  So you could have a user
folder called "Bulk" or "Spam" or something, and the server level script
could have ask to file a message into that users "Bulk" folder (rather than
just delete it).

In MailSite we have server and domain level scripts, and there seemed to be
a few possible interpretations of the "fileinto" command.  Either it could:

a) "fileinto" a folder on the local file system
b) file into a folder of the target user (at server/domain level there may
be many recipients in the envelope at this stage)
c) file into a folder of the server/domain postmaster.

Sadly we chose a), which I thought was going to be the most useful, but now
we have a need to do b) as well.  So we were wondering if fileinto should
have some kind of arg to say:

    fileinto :filesystem "DirectoryName";

To file into the "DirectoryName" folder on the file system of the MTA, or

    fileinto "Spam";

To fileinto the Spam folder of the recipient (if local) or

    fileinto :user "Postmaster" "Spam";

To file into the Spam folder of the Postmaster mailbox.

I know most of this is probably a spearate extension, but the draft as it
stands implies that it's only Keep and implicit Keep actions in previous
scripts that can allow subsequent scripts to be executed, and I'm not sure
that's true.

I think fileinto(s) in a previous script should "change the location" of
where implicit keep would post the message.  Explicit Keep could probably
change the filed location to Inbox (or add Inbox if there were multiple
fileintos in a previous script).  Another fileinto would change the filed
location (or add the new folder if there were multiple fileintos in a
previous script).

I think we need to think through all this pretty carefully, but it'll be
worth it...

Cheers,

Nigel