On Thu, 24 Jul 2003, Ken Murchison wrote:
> It would be possible to autocreate on fileinto, but how do you determine
> that this is what the user wants vs. the mailbox name being typed
> incorrectly.
You can tell this via a -create flag to fileinto.
> What really should happen is that a warning
Andrew Morgan wrote:
On Thu, 24 Jul 2003, Ken Murchison wrote:
Andrew Morgan wrote:
Is it possible for sieve to auto-create folders that don't already exist
when it tries to fileinto? I've got a sieve script like the following:
require "fileinto";
# Filter spam
if header :contains "X-Spam-
On Thu, 24 Jul 2003, Ken Murchison wrote:
>
>
> Andrew Morgan wrote:
>
> > Is it possible for sieve to auto-create folders that don't already exist
> > when it tries to fileinto? I've got a sieve script like the following:
> >
> > require "fileinto";
> >
> > # Filter spam
> > if header :contain
Andrew Morgan wrote:
Is it possible for sieve to auto-create folders that don't already exist
when it tries to fileinto? I've got a sieve script like the following:
require "fileinto";
# Filter spam
if header :contains "X-Spam-Flag" "YES" {
fileinto "INBOX.junk-mail";
}
But the folder
On Thu, 24 Jul 2003, Andrew Morgan wrote:
> It would simplify our setup and management of sieve scripts if we could
> have the folder automatically created if it does not already exist. Is
> there a way to enable this?
Nope, there's an extention I've heard being discussed in the IETF but the
du
Is it possible for sieve to auto-create folders that don't already exist
when it tries to fileinto? I've got a sieve script like the following:
require "fileinto";
# Filter spam
if header :contains "X-Spam-Flag" "YES" {
fileinto "INBOX.junk-mail";
}
But the folder "INBOX.junk-mail" mu
