[Rt-commit] r3073 - rt/branches/3.4-RELEASE/etc

[jesse at bestpractical.com]

Author: jesse
Date: Sun Jun  5 17:30:17 2005
New Revision: 3073

Modified:
   rt/branches/3.4-RELEASE/etc/RT_Config.pm.in
Log:

* Updated EmailSubjectTagRegex documentation. Thanks to Phil Homewood for spotting it.


Modified: rt/branches/3.4-RELEASE/etc/RT_Config.pm.in
==============================================================================
--- rt/branches/3.4-RELEASE/etc/RT_Config.pm.in	(original)
+++ rt/branches/3.4-RELEASE/etc/RT_Config.pm.in	Sun Jun  5 17:30:17 2005
@@ -28,12 +28,26 @@
 
 
 # This regexp controls what subject tags RT recognizes as its own.
-# Be VERY CAREFUL with it. Note that it overrides $rtname.
-#
 # If you're not dealing with historical $rtname values, you'll likely
-# never have to enable this feature
-# Set($EmailSubjectTagRegex, qr/\Q$rtname\E/ );
+# never have to enable this feature.
+#
+# Be VERY CAREFUL with it. Note that it overrides $rtname for subject
+# token matching and that you should use only "non-capturing" parenthesis
+# grouping. For example:
+#
+# 	Set($EmailSubjectTagRegex, qr/(?:example.com|example.org)/ );
+#
+# and NOT
+# 
+# 	Set($EmailSubjectTagRegex, qr/(example.com|example.org)/ );
 #
+# This setting would make RT behave exactly as it does without the 
+# setting enabled.
+#
+# Set($EmailSubjectTagRegex, qr/\Q$rtname\E/ );
+
+
+
 # You should set this to your organization's DNS domain. For example,
 # fsck.com or asylum.arkham.ma.us. It's used by the linking interface to
 # guarantee that ticket URIs are unique and easy to construct.