You need to include both, the queue email addresses, AND anything that forwards email to RT.
That setting prevents RT from sending emails that will “loop” infinitely in your system.
RT is setup with the basic autoreply, and reply on correspondence etc.
RT has 2 queues, email@example.com goes to general, and firstname.lastname@example.org goes to IT queue.
If email@example.com emails firstname.lastname@example.org the general queue will autoreply to email@example.com which will create a ticket and autoreply to firstname.lastname@example.org which will create a ticket and auto-reply to email@example.com etc etc etc…
Big loop, never ending, blow up RT
If you set the regular expression to firstname.lastname@example.org when RT emails out, it’ll filter any emails going to email@example.com. This will ensure no loop happens.
SO to recap, RTAddressRegexp has to be a regular expression that ALL email addresses that send stuff to RT will validate through.
Hope this helps!
Mike.On Tue, Jul 27, 2010 at 1:35 PM, Joseph Spenner firstname.lastname@example.org wrote:
Upon nearly completing my RT installation, and running:
I got the message:
[Tue Jul 27 17:12:29 2010] [error]: The RTAddressRegexp option is not set in the config. Not setting this option results in additional SQL queries to check whether each address belongs to RT or not. It is especially important to set this option if RT recieves emails on addresses that are not in the database or config. (/home/packages/rt-3.8.8/sbin/…/lib/RT/Config.pm:343)
Now inserting data
Done inserting data
If I have 3 queues, ie:
Do I need to list all those addresses (and any future addresses) in that RTAddressRegexp option ? Or is this only if I have something at (ie:) email@example.com forwarding to my RT system in which case I’d want to add: firstname.lastname@example.org to the RTAddressRegexp option ?
So this ‘loop’ should only occur if:
- auto respond/reply is enabled for the queue defined in the scrips
- somehow, an RT queue address (with auto reply enabled) somehow gets included into another queues ticket
Is this potential something new? I’ve been using RT2 since about 2001 and never seen this happen. Or is it just a safeguard?