[exim-cvs] cvs commit: exim/exim-doc/doc-txt README.SIEVE

トップ ページ
このメッセージを削除
このメッセージに返信
著者: Philip Hazel
日付:  
To: exim-cvs
題目: [exim-cvs] cvs commit: exim/exim-doc/doc-txt README.SIEVE
ph10 2005/03/29 16:21:57 BST

  Modified files:
    exim-doc/doc-txt     README.SIEVE 
  Log:
  Small documentation change from Michael Haardt.


  Revision  Changes    Path
  1.3       +5 -4      exim/exim-doc/doc-txt/README.SIEVE


  Index: README.SIEVE
  ===================================================================
  RCS file: /home/cvs/exim/exim-doc/doc-txt/README.SIEVE,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- README.SIEVE    1 Mar 2005 10:21:43 -0000    1.2
  +++ README.SIEVE    29 Mar 2005 15:21:57 -0000    1.3
  @@ -1,4 +1,4 @@
  -$Cambridge: exim/exim-doc/doc-txt/README.SIEVE,v 1.2 2005/03/01 10:21:43 ph10 Exp $
  +$Cambridge: exim/exim-doc/doc-txt/README.SIEVE,v 1.3 2005/03/29 15:21:57 ph10 Exp $


                 Notes on the Sieve implementation for Exim


@@ -114,13 +114,14 @@
are filed into "inbox" due to an error in the filter.


-Strings Containing Header Names
+Strings Containing Header Names Or Envelope Elements

RFC 3028 does not specify what happens if a string denoting a header
-field does not contain a valid header name, e.g. it contains a colon.
+field or envelope element does not contain a valid name, e.g. it
+contains a colon for a header or it is not "from" or "to" for envelopes.
This implementation generates an error instead of ignoring the header
-field in order to ease script debugging, which fits in the common
-picture of Sieve.
+field in order to ease script debugging, which fits in the common picture
+of Sieve.


Header Test With Invalid MIME Encoding In Header