RTAddressRegexp - Revision history

Admin: 8 revisions imported

2016-04-06T20:24:41Z

8 revisions imported

← Older revision	Revision as of 16:24, 6 April 2016
(No difference)

14.201.100.176: fix formatting

2014-07-20T04:38:06Z

fix formatting

← Older revision		Revision as of 00:38, 20 July 2014
Line 1:		Line 1:
	$'''~~RT''''''Address''''''Regexp~~''' is used to prevent RT messaging itself and generating mail loops, for example when $[[ParseNewMessageForTicketCcs]] is enabled and other. Anyway to protect you from loops and other problems you must set up this option.		'''$RTAddressRegexp''' is used to prevent RT messaging itself and generating mail loops, for example when $[[ParseNewMessageForTicketCcs]] is enabled and other. Anyway to protect you from loops and other problems you must set up this option.

	In this option you '''MUST''' cover every email address that can be used to interact with RT via email. If you have aliases of redirect messages to RT from some address those also should be covered.		In this option you '''MUST''' cover every email address that can be used to interact with RT via email. If you have aliases of redirect messages to RT from some address those also should be covered.

67.214.159.125: /* Simple way */

2011-05-05T20:11:33Z

Simple way

← Older revision		Revision as of 16:11, 5 May 2011
Line 30:		Line 30:
	* escaped: <code>bugs\@my\.com</code>, <code>bugs-comment\@my\.com</code>, <code>sales\@my\.com</code> and <code>sales-comment\@my\.com</code>		* escaped: <code>bugs\@my\.com</code>, <code>bugs-comment\@my\.com</code>, <code>sales\@my\.com</code> and <code>sales-comment\@my\.com</code>
	* regexp: <code>^(bugs\@my\.com\|bugs-comment\@my\.com\|sales\@my\.com\|sales-comment\@my\.com)$</code>		* regexp: <code>^(bugs\@my\.com\|bugs-comment\@my\.com\|sales\@my\.com\|sales-comment\@my\.com)$</code>
	* <code>^(bugs\|sales)(-comment)?\@(my.com)$</code>		* <code>^(bugs\|sales)(-comment)?\@(my\.com)$</code>

	As you can see this can get very long if there are several names for the server.		As you can see this can get very long if there are several names for the server.

60.242.154.3: /* Simple way */

2011-01-30T21:49:01Z

Simple way

← Older revision		Revision as of 17:49, 30 January 2011
Line 30:		Line 30:
	* escaped: <code>bugs\@my\.com</code>, <code>bugs-comment\@my\.com</code>, <code>sales\@my\.com</code> and <code>sales-comment\@my\.com</code>		* escaped: <code>bugs\@my\.com</code>, <code>bugs-comment\@my\.com</code>, <code>sales\@my\.com</code> and <code>sales-comment\@my\.com</code>
	* regexp: <code>^(bugs\@my\.com\|bugs-comment\@my\.com\|sales\@my\.com\|sales-comment\@my\.com)$</code>		* regexp: <code>^(bugs\@my\.com\|bugs-comment\@my\.com\|sales\@my\.com\|sales-comment\@my\.com)$</code>
	* <code>^(bugs\|sales)(-comment)\@(my.com)$</code>		* <code>^(bugs\|sales)(-comment)?\@(my.com)$</code>

	As you can see this can get very long if there are several names for the server.		As you can see this can get very long if there are several names for the server.

60.242.154.3: /* Simple way */

2011-01-30T21:48:29Z

Simple way

← Older revision		Revision as of 17:48, 30 January 2011
Line 30:		Line 30:
	* escaped: <code>bugs\@my\.com</code>, <code>bugs-comment\@my\.com</code>, <code>sales\@my\.com</code> and <code>sales-comment\@my\.com</code>		* escaped: <code>bugs\@my\.com</code>, <code>bugs-comment\@my\.com</code>, <code>sales\@my\.com</code> and <code>sales-comment\@my\.com</code>
	* regexp: <code>^(bugs\@my\.com\|bugs-comment\@my\.com\|sales\@my\.com\|sales-comment\@my\.com)$</code>		* regexp: <code>^(bugs\@my\.com\|bugs-comment\@my\.com\|sales\@my\.com\|sales-comment\@my\.com)$</code>
			* <code>^(bugs\|sales)(-comment)\@(my.com)$</code>

	As you can see this can get very long if there are several names for the server.		As you can see this can get very long if there are several names for the server.

86.64.170.7: /* Regexp rules you must know */

2011-01-07T15:05:03Z

Regexp rules you must know

← Older revision		Revision as of 11:05, 7 January 2011
Line 40:		Line 40:
	* <code>.</code> - matches any character, so you usually should escape them		* <code>.</code> - matches any character, so you usually should escape them
	* <code>@</code> - is used to access arrays, so you escape it to match @ literaly		* <code>@</code> - is used to access arrays, so you escape it to match @ literaly
	* <code>^</code> and <code>$</code> - match at begin and end of the string respectively, note that regexp <code>rt\@example\.com</code> would match robert@example.com and rt@example.com.au addresses, most probably '''it's not''' what you want, use <code>^rt\@example\.com$</code> regexp.		* <code>^</code> and <code>$</code> - match at begin and end of the string respectively, note that regexp <code>rt\@example\.com</code> would match robert@example.com and rt@example.com.au addresses, most probably '''it is not''' what you want, use <code>^rt\@example\.com$</code> regexp.
	* <code>()</code> - group things, often used with <code>\|</code> to group alternatives		* <code>()</code> - group things, often used with <code>\|</code> to group alternatives
	* <code>\|</code> - separator for alternative parts, note that <code>^rt\@foo\.com\|rt\@bar\.com$</code> matches rt@foo.com.au and robert@bar.com as <code>^</code> applies to the left alternative part and <code>$</code> to the right only, so you can ~~ready~~ this expression as "address starts with rt@foo.com or ends with rt@bar.com". You must group alternatives <code>^(rt\@foo\.com\|rt\@bar\.com)$</code>		* <code>\|</code> - separator for alternative parts, note that <code>^rt\@foo\.com\|rt\@bar\.com$</code> matches rt@foo.com.au and robert@bar.com as <code>^</code> applies to the left alternative part and <code>$</code> to the right only, so you can read this expression as "address starts with rt@foo.com or ends with rt@bar.com". You must group alternatives <code>^(rt\@foo\.com\|rt\@bar\.com)$</code>
	* <code>?</code> - makes ~~precedence~~ atom optional, for example <code>^rt(-comment)?\@example\.com$</code> matches rt@example.com and rt-comment@example.com		* <code>?</code> - makes previous atom optional, for example <code>^rt(-comment)?\@example\.com$</code> matches rt@example.com and rt-comment@example.com

	== See also ==		== See also ==

	[[EmailInterface]] and [[SiteConfig]]		[[EmailInterface]] and [[SiteConfig]]

94.195.196.89: fixed stray character breaking syntax

2010-12-09T22:08:07Z

fixed stray character breaking syntax

New page

$'''RT''''''Address''''''Regexp''' is used to prevent RT messaging itself and generating mail loops, for example when $[[ParseNewMessageForTicketCcs]] is enabled and other. Anyway to protect you from loops and other problems you must set up this option.

In this option you '''MUST''' cover every email address that can be used to interact with RT via email. If you have aliases of redirect messages to RT from some address those also should be covered.

An example expression:

Set($RTAddressRegexp , '^help(-comment)?\@(help|admin)\.(example\.org|ourother\.domain\.com)$');

Would work for a server with the names "help" and "admin" and multiple domains. This will catch:

help@help.example.org
help-comment@help.example.org
help@admin.example.org
.
.
.
help-comment@admin.ourother.domain.com

== Simple way ==

If you don't understand perl regular expression you can use simple way:

* collect list of addresses you must cover
* escape . (dot), @ and + symbols with \
* fill them into template ^(escaped address 1|escaped address 2|escaped address 3|...)$

Example:

* addresses: bugs@my.com, bugs-comment@my.com, sales@my.com and sales-comment@my.com
* escaped: <code>bugs\@my\.com</code>, <code>bugs-comment\@my\.com</code>, <code>sales\@my\.com</code> and <code>sales-comment\@my\.com</code>
* regexp: <code>^(bugs\@my\.com|bugs-comment\@my\.com|sales\@my\.com|sales-comment\@my\.com)$</code>

As you can see this can get very long if there are several names for the server.

== Regexp rules you must know ==

Short perl regexps rules you must know:

* \ - is used to escape character with special meaning, like dot, @, parens and other
* <code>.</code> - matches any character, so you usually should escape them
* <code>@</code> - is used to access arrays, so you escape it to match @ literaly
* <code>^</code> and <code>$</code> - match at begin and end of the string respectively, note that regexp <code>rt\@example\.com</code> would match robert@example.com and rt@example.com.au addresses, most probably '''it's not''' what you want, use <code>^rt\@example\.com$</code> regexp.
* <code>()</code> - group things, often used with <code>|</code> to group alternatives
* <code>|</code> - separator for alternative parts, note that <code>^rt\@foo\.com|rt\@bar\.com$</code> matches rt@foo.com.au and robert@bar.com as <code>^</code> applies to the left alternative part and <code>$</code> to the right only, so you can ready this expression as "address starts with rt@foo.com or ends with rt@bar.com". You must group alternatives <code>^(rt\@foo\.com|rt\@bar\.com)$</code>
* <code>?</code> - makes precedence atom optional, for example <code>^rt(-comment)?\@example\.com$</code> matches rt@example.com and rt-comment@example.com

== See also ==

[[EmailInterface]] and [[SiteConfig]]

Ghoti at 21:32, 22 October 2010

2010-10-22T21:32:07Z

New page

$'''RT''''''Address''''''Regexp''' is used to prevent RT messaging itself and generating mail loops, for example when $[[ParseNewMessageForTicketCcs]] is enabled and other. Anyway to protect you from loops and other problems you must set up this option.

In this option you '''MUST''' cover every email address that can be used to interact with RT via email. If you have aliases of redirect messages to RT from some address those also should be covered.

An example expression:

Set($RTAddressRegexp , '^help(-comment)?\@(help|admin)\.(example\.org|ourother\.domain\.com)$');]

Would work for a server with the names "help" and "admin" and multiple domains. This will catch:

help@help.example.org
help-comment@help.example.org
help@admin.example.org
.
.
.
help-comment@admin.ourother.domain.com

== Simple way ==

If you don't understand perl regular expression you can use simple way:

* collect list of addresses you must cover
* escape . (dot), @ and + symbols with \
* fill them into template ^(escaped address 1|escaped address 2|escaped address 3|...)$

Example:

* addresses: bugs@my.com, bugs-comment@my.com, sales@my.com and sales-comment@my.com
* escaped: <code>bugs\@my\.com</code>, <code>bugs-comment\@my\.com</code>, <code>sales\@my\.com</code> and <code>sales-comment\@my\.com</code>
* regexp: <code>^(bugs\@my\.com|bugs-comment\@my\.com|sales\@my\.com|sales-comment\@my\.com)$</code>

As you can see this can get very long if there are several names for the server.

== Regexp rules you must know ==

Short perl regexps rules you must know:

* \ - is used to escape character with special meaning, like dot, @, parens and other
* <code>.</code> - matches any character, so you usually should escape them
* <code>@</code> - is used to access arrays, so you escape it to match @ literaly
* <code>^</code> and <code>$</code> - match at begin and end of the string respectively, note that regexp <code>rt\@example\.com</code> would match robert@example.com and rt@example.com.au addresses, most probably '''it's not''' what you want, use <code>^rt\@example\.com$</code> regexp.
* <code>()</code> - group things, often used with <code>|</code> to group alternatives
* <code>|</code> - separator for alternative parts, note that <code>^rt\@foo\.com|rt\@bar\.com$</code> matches rt@foo.com.au and robert@bar.com as <code>^</code> applies to the left alternative part and <code>$</code> to the right only, so you can ready this expression as "address starts with rt@foo.com or ends with rt@bar.com". You must group alternatives <code>^(rt\@foo\.com|rt\@bar\.com)$</code>
* <code>?</code> - makes precedence atom optional, for example <code>^rt(-comment)?\@example\.com$</code> matches rt@example.com and rt-comment@example.com

== See also ==

[[EmailInterface]] and [[SiteConfig]]