<p>In most environments I have been, the RT system is not the primary mail server of course, so you end up with various aliases and forwarding making your rt environment look like a cohesive part of the email domain. Using a regex with appropriate wild cards makes this work well.</p>
<p>Cheers,<br>
Brian<br>
</p>
<p><blockquote type="cite">On May 24, 2010 1:23 PM, "Ruslan Zakirov" <<a href="mailto:ruz@bestpractical.com">ruz@bestpractical.com</a>> wrote:<br><br><p><font color="#500050">On Fri, May 21, 2010 at 7:34 PM, Jesse Vincent <<a href="mailto:jesse@bestpractical.com">jesse@bestpractical.com</a>> wrote:<br>
> On Fri, May 21, 20...</font></p>I'm not with you. In trunk we do our best:<br>
1) if option is not set we lookup in DB<br>
2) we still allow regexp<br>
3) we warn admin via logs if regexp is not defined<br>
<br>
It's flexible enough to protect careless admins and allow smart to<br>
setup fast matching and cover addresses not stored in the DB.<br>
<br>
I saw setups<br>
* where not all RT addresses are in the DB<br>
* with many queues, but very small and fast regexp<br>
<br>
My idea is that usually hundreds emails turns into short regular<br>
expression. If it's not the case for you then you can use "no value"<br>
and DB lookups.<br>
<p><font color="#500050"><br>> -jesse<br>> _______________________________________________<br>> List info: <a href="http://lists.bestpractical.">http://lists.bestpractical.</a>...</font></p><font color="#888888">--<br>
Best regards, Ruslan.<br>
</font><p><font color="#500050">_______________________________________________<br>List info: <a href="http://lists.bestpractical.com/cgi-bin/ma.">http://lists.bestpractical.com/cgi-bin/ma.</a>..</font></p></blockquote></p>