[Rt-commit] r3110 - in rt/branches/QUEBEC-EXPERIMENTAL: . etc

jesse at bestpractical.com jesse at bestpractical.com
Wed Jun 8 23:07:08 EDT 2005


Author: jesse
Date: Wed Jun  8 23:07:07 2005
New Revision: 3110

Modified:
   rt/branches/QUEBEC-EXPERIMENTAL/   (props changed)
   rt/branches/QUEBEC-EXPERIMENTAL/etc/RT_Config.pm.in
Log:
 r19667 at hualien:  jesse | 2005-06-08 18:43:09 -0400
  r19648 at hualien:  jesse | 2005-06-08 18:28:34 -0400
   r19326 at hualien (orig r3073):  jesse | 2005-06-05 17:30:17 -0400
   
   * Updated EmailSubjectTagRegex documentation. Thanks to Phil Homewood for spotting it.
   
  
 


Modified: rt/branches/QUEBEC-EXPERIMENTAL/etc/RT_Config.pm.in
==============================================================================
--- rt/branches/QUEBEC-EXPERIMENTAL/etc/RT_Config.pm.in	(original)
+++ rt/branches/QUEBEC-EXPERIMENTAL/etc/RT_Config.pm.in	Wed Jun  8 23:07:07 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.


More information about the Rt-commit mailing list