[Rt-devel] Behaviour of RTAddressRegexp

Ruslan Zakirov ruz at bestpractical.com
Mon May 24 13:23:06 EDT 2010

On Fri, May 21, 2010 at 7:34 PM, Jesse Vincent <jesse at bestpractical.com> wrote:
> On Fri, May 21, 2010 at 11:44:58AM +0200, Emmanuel Lacour wrote:
>> Dear RT hackers,
>> why don't we add automatically queues correspond/comment address to the
>> RTAddressRegexp check to avoid users to maintain a huge regexp for
>> sometimes hundreds of queues/emails?
>> IMHO, RTAddressRegexp should only be needed to add aliases that has an
>> RT queue as target.
> I'm with you. I recall Kevin/Ruslan having pointed out some important nuances here. There may even be existing work on a branch to improve things.

I'm not with you. In trunk we do our best:
1) if option is not set we lookup in DB
2) we still allow regexp
3) we warn admin via logs if regexp is not defined

It's flexible enough to protect careless admins and allow smart to
setup fast matching and cover addresses not stored in the DB.

I saw setups
* where not all RT addresses are in the DB
* with many queues, but very small and fast regexp

My idea is that usually hundreds emails turns into short regular
expression. If it's not the case for you then you can use "no value"
and DB lookups.

> -jesse
> _______________________________________________
> List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

Best regards, Ruslan.

More information about the rt-devel mailing list