[Top] [All Lists]

FW: Body test

2003-08-08 15:03:34

FYI - I sent this to ietf-mta-filters(_at_)imc(_dot_)org yesterday but that list seems to be down. The last post was: I will try and send it agin now with you as the Cc: Just a short answer would be very much appreciated.

/postfix/sieve configuration, Manfred Friedrich, Sat, 19 Jul 2003 11:31:29 -0700 (PDT)(envelope-from owner-ietf-mta-filters(_at_)mail(_dot_)imc(_dot_)org)


I am currently conducting a Procmail vs. SIEVE test on an account that
gets roughly 1000-1500 messages per day.  The most useful tool I have
with Procmail is the "Body test" which seems to be absent from SIEVE.
Please correct me if I am wrong.

I was reading the following RFC, and wondered if someone could elaborate
on the second paragraph for me (namely which vendors).

1. Introduction

   The proposed "body" test checks for the occurrence of one
   or more strings in the body of an e-mail message.
   Such a test was initially discussed for the [SIEVE] base
   document, but was subsequently removed because it was
   thought to be too costly to implement.

   Nevertheless, several server vendors have implemented
   some form of the "body" test.

   This document reintroduces the "body" test as an extension,
   and specifies it syntax and semantics.

The reason I ask is I have been unsuccessfully trying the following
syntax with no success.  The script is active.

myscript  <- active script
get myscript
require ["body", "fileinto"];

# Save any message with any text MIME part that contains the
# worlds "missile" or "coordinates" in the "secrets" folder.

if body :content "text" :contains ["missile", "coordinates"] {
        fileinto "INBOX.secrets";

if body :raw :contains "missile" {
    fileinto "INBOX.secrets";

I *need* to filter based on body test and Any additional info would be
greatly appreciated.  I would be willing to implement alpha and beta
versions of SIEVE if they implement the "body test" and are available

Thanks in advance,



I would also like to know how to enable the most verbose logging for
SIEVE if anyone has some suggestions they would be greatly appreciated.

<Prev in Thread] Current Thread [Next in Thread>