[prev] [thread] [next] [lurker] [Date index for 2006/03/21]
On 2006-03-21 at 07:44 +0100, A. Pagaltzis wrote:
> I have forever meant to write my own mail filter script and
> retire that nasty paleolithic excuse for a hack...
I'm actually not hating Sieve. It seems to work well, reasonably clean
design if you remember that it's designed to be machine-editable too, so
get used to stuff like:
require ["fileinto", "envelope"];
if envelope :is "from" [
"owner-all1@xxxxxxx.xxx",
"owner-all2@xxxxxxx.xxx",
"allhands-sender-for-this-week@xxxxxxxxx.xxx.xxx"
] {
fileinto "INBOX.site"; stop;
}
if header :matches "Subject" [ "Foo *", "Bar *" ] {
fileinto "INBOX.fred"; stop;
}
Nice enough RFC, plus RFCs and drafts for various "require" extensions.
Supported by Cyrus IMAP (now there, I have some hate) and Exim.
Snippet from RFC 3028 follows.
Regards,
-Phil
2.7.2. Comparisons Across Character Sets
All Sieve scripts are represented in UTF-8, but messages may involve
a number of character sets. In order for comparisons to work across
character sets, implementations SHOULD implement the following
behavior:
Implementations decode header charsets to UTF-8. Two strings are
considered equal if their UTF-8 representations are identical.
Implementations should decode charsets represented in the forms
specified by [MIME] for both message headers and bodies.
Implementations must be capable of decoding US-ASCII, ISO-8859-1,
the ASCII subset of ISO-8859-* character sets, and UTF-8.
If implementations fail to support the above behavior, they MUST
conform to the following:
No two strings can be considered equal if one contains octets
greater than 127.
There's stuff above here
Generated at 12:00 on 03 Apr 2006 by mariachi 0.52