IsRTAddress in RT3

In RT2’s config.pm there was the subroutine IsRTAddress, of which it was
very easy to have lots of lines such as the following to determine which
addresses RT should not send to upon sending a ticket, or it would
create another ticket.

return(1) if ($address =~ /^rt\@example.com$/i);
return(1) if ($address =~ /^(foo|bar|baz)-queue\@example.com$/i);

In RT3, this looks like it’s been replaced with

Set($RTAddressRegexp, 'regexp');

Now, in our RT setup we have about 30 queues, some with names that
overlap (ie, foo and foo-feedback). Do I have to specify just one
regexp for all of these queues? Forming such a regexp would be a total
nightmare for us!

Is there no better way to do this in RT_SiteConfig.pm, or would I be
better off just hacking the IsRTAddress sub directly in EmailParser.pm?

Thanks,
Jeremy Doran fox-rt_users@vulpes.net

Is there no better way to do this in RT_SiteConfig.pm, or would I be
better off just hacking the IsRTAddress sub directly in EmailParser.pm?

no, you’d create an EmailParser_Local.pm file containing your own
IsRTAddress routine, per the perldoc of most, if not all of the core RT
classes.

Thanks,

Jeremy Doran fox-rt_users@vulpes.net


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

http://www.bestpractical.com/rt – Trouble Ticketing. Free.

Is there no better way to do this in RT_SiteConfig.pm, or would I be
better off just hacking the IsRTAddress sub directly in EmailParser.pm?

no, you’d create an EmailParser_Local.pm file containing your own
IsRTAddress routine, per the perldoc of most, if not all of the core RT
classes.

Whoops - my bad. I thought the *Local.pm’s were just for the Overlays. I
see that’s not the case now.

Is there any similar kind of ‘local’ customization for the HTML/mason
templates?

Jeremy Doran fox-rt_users@vulpes.net