<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><br><br>--- On <b>Tue, 7/27/10, Mike Johnson <i><mike.johnson@nosm.ca></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br><div id="yiv1655098671"><div>You need to include both, the queue email addresses, AND anything that forwards email to RT.</div>
<div> </div>
<div>That setting prevents RT from sending emails that will "loop" infinitely in your system.</div>
<div> </div>
<div>For example.</div>
<div> </div>
<div>RT is setup with the basic autoreply, and reply on correspondence etc.</div>
<div> </div>
<div>RT has 2 queues, <a rel="nofollow" ymailto="mailto:support@here.com" target="_blank" href="/mc/compose?to=support@here.com">support@here.com</a> goes to general, and <a rel="nofollow" ymailto="mailto:it@here.com" target="_blank" href="/mc/compose?to=it@here.com">it@here.com</a> goes to IT queue.</div>
<div> </div>
<div>If <a rel="nofollow" ymailto="mailto:it@here.com" target="_blank" href="/mc/compose?to=it@here.com">it@here.com</a> emails <a rel="nofollow" ymailto="mailto:support@here.com" target="_blank" href="/mc/compose?to=support@here.com">support@here.com</a> the general queue will autoreply to <a rel="nofollow" ymailto="mailto:it@here.com" target="_blank" href="/mc/compose?to=it@here.com">it@here.com</a> which will create a ticket and autoreply to <a rel="nofollow" ymailto="mailto:support@here.com" target="_blank" href="/mc/compose?to=support@here.com">support@here.com</a> which will create a ticket and auto-reply to <a rel="nofollow" ymailto="mailto:it@here.com" target="_blank" href="/mc/compose?to=it@here.com">it@here.com</a> etc etc etc....</div>
<div> </div>
<div>Big loop, never ending, blow up RT :P</div>
<div> </div>
<div>If you set the regular expression to <a rel="nofollow" ymailto="mailto:support@here.com" target="_blank" href="/mc/compose?to=support@here.com">support@here.com</a> when RT emails out, it'll filter any emails going to <a rel="nofollow" ymailto="mailto:support@here.com" target="_blank" href="/mc/compose?to=support@here.com">support@here.com</a>. This will ensure no loop happens.</div>
<div> </div>
<div>SO to recap, RTAddressRegexp has to be a regular expression that ALL email addresses that send stuff to RT will validate through.</div>
<div> </div>
<div>Hope this helps!</div>
<div>Mike.<br><br></div>
<div class="yiv1655098671gmail_quote">On Tue, Jul 27, 2010 at 1:35 PM, Joseph Spenner <span dir="ltr"><<a rel="nofollow" ymailto="mailto:joseph85750@yahoo.com" target="_blank" href="/mc/compose?to=joseph85750@yahoo.com">joseph85750@yahoo.com</a>></span> wrote:<br>
<blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;" class="yiv1655098671gmail_quote">
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td valign="top">Upon nearly completing my RT installation, and running:<br><br># make initialize-database<br><br>I got the message:<br><br>==<br>[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)<br>
Now inserting data<br>Done inserting data<br>Done.<br>==<br>If I have 3 queues, ie:<br><a rel="nofollow" ymailto="mailto:support-help@bob.domain.com" target="_blank" href="/mc/compose?to=support-help@bob.domain.com">support-help@bob.domain.com</a><br><a rel="nofollow" ymailto="mailto:sales-help@bob.domain.com" target="_blank" href="/mc/compose?to=sales-help@bob.domain.com">sales-help@bob.domain.com</a><br>
<a rel="nofollow" ymailto="mailto:it-requests@bob.domain.com" target="_blank" href="/mc/compose?to=it-requests@bob.domain.com">it-requests@bob.domain.com</a><br>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:) <a rel="nofollow" ymailto="mailto:help@jack.somewhere.com" target="_blank" href="/mc/compose?to=help@jack.somewhere.com">help@jack.somewhere.com</a> forwarding to my RT system in which case I'd want to add: <a rel="nofollow" ymailto="mailto:help@jack.somewhere.com" target="_blank" href="/mc/compose?to=help@jack.somewhere.com">help@jack.somewhere.com</a> to the RTAddressRegexp option ?<br>
<br><br></td></tr></tbody></table><br></blockquote></div></div></blockquote><div id="yiv1655098671">So this 'loop' should only occur if:<br><br>1) auto respond/reply is enabled for the queue defined in the scrips<br>2) somehow, an RT queue address (with auto reply enabled) somehow gets included into another queues ticket<br><br>?<br><br>Is this potential something new? I've been using RT2 since about 2001 and never seen this happen. Or is it just a safeguard?<br></div><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div id="yiv1655098671">
</div></blockquote></td></tr></table><br>