From b50a4b4f4526a42fbf7d5f8c5373b7fcb0a34a36 Mon Sep 17 00:00:00 2001
From: Stephan Bosch <stephan@rename-it.nl>
Date: Sat, 28 Dec 2013 09:24:42 +0100
Subject: [PATCH] doc/extensions/spamtest-virustest.txt: Clarified that these
 extensions use the extended POSIX regular expressions.

---
 doc/extensions/spamtest-virustest.txt | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/extensions/spamtest-virustest.txt b/doc/extensions/spamtest-virustest.txt
index 892874748..07976c1ff 100644
--- a/doc/extensions/spamtest-virustest.txt
+++ b/doc/extensions/spamtest-virustest.txt
@@ -42,10 +42,10 @@ sieve_spamtest_status_header = <header-field> [ ":" <regexp> ]
   against "0".
 
   This is a structured setting. The first part specifies the header field name.
-  Optionally, a POSIX regular expression follows the header field name,
-  separated by a colon. Any whitespace directly following the colon is not part
-  of the regular expression. If the regular expression is omitted, any header
-  content is accepted and the full header value is used. When a regular
+  Optionally, an extended POSIX regular expression follows the header field
+	name, separated by a colon. Any whitespace directly following the colon is not
+	part of the regular expression. If the regular expression is omitted, any
+	header content is accepted and the full header value is used. When a regular
   expression is used, it must specify one match value (inside brackets) that
   yields the desired spam scanner result. If the header does not match the
   regular expression or if no value match is found, the spamtest will match
-- 
GitLab