[rt-users] blah.blah at foo.com is an address RT receives mail at

[Kevin Falcone]

On Thu, Jul 25, 2013 at 10:20:52AM +0100, LAW Andy wrote:
> Nothing was listed in the root System Configuration page when I
> checked it, so I don't know how I would go about getting that
> information out? Happy to try suggested stuff if it helps debug
> something that might trip others up in the future.

This implies that one of your Queue Level Correspond/Comment addresses
is blahblahblah at foo.com

In the case that you don't specify a regexp, RT checks the config and
then searches all the Queues.

If you're running an out-of-date RT it would generate and cache a regexp, but
that hasn't happened in awhile (mid-3.8).

I'll push a branch to remove the lie from RT_SiteConfig.pm

-kevin

> 
> To be honest, we don't have the system set up to accept *incoming* emails (due to a long and painful history of working with a succession of Mordacs) so I've never really had to bother with that section of configuration.
> 
> 
> On 25 Jul 2013, at 10:00, Craig Ringer <craig at 2ndquadrant.com> wrote:
> 
> > On 07/25/2013 04:52 PM, LAW Andy wrote:
> >>>> I don't have an RTAddressRegexp set - I was relying on the 'auto generation' feature. The comment and correspond email addresses bear little relation to the problematic address though.
> >>>> 
> >>>> I will try manually setting a regexp and see if that improves the situation.
> >>>> 
> >> That fixes it. Thanks for the push.
> > 
> > It'd be interesting if you could get the address regexp that RT
> > generates when one is not specified. Maybe there's an issue there, or
> > maybe it's with one of your queues.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20130725/131ede78/attachment.sig>