Just noticed that if I try to create a ticket with a particular “client” as requestor, I get the message that this is the RT email address and that I will create a mail loop.
This most certainly is NOT the RT correspondence address.
I see a couple of previous threads mentioning this, but no obvious resolution. Any clues or pointers as got how to fix this apparent configuration problem?
Later,
Andy
Yada, yada, yada…
Disclaimer: This e-mail and any attachments are confidential and intended solely for the use of the recipient(s) to whom they are addressed. If you have received it in error, please destroy all copies and inform the sender.
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
I see a couple of previous threads mentioning this, but no obvious resolution. Any clues or pointers as got how to fix this apparent configuration problem?
It sounds like the address must match your $RTAddressRegexp .
Have you tested this manually?
Try:
cpan
install Devel::REPL
re.pl
‘the@address’ =~ qr{^…my-rt-address-regexp-here…$};
see if you get any match(es).
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
I see a couple of previous threads mentioning this, but no obvious resolution. Any clues or pointers as got how to fix this apparent configuration problem?
It sounds like the address must match your $RTAddressRegexp .
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.
Have you tested this manually?
Try:
cpan
install Devel::REPL
re.pl
‘the@address’ =~ qr{^…my-rt-address-regexp-here…$};
see if you get any match(es).
–
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Later,
Andy
Yada, yada, yada…
Disclaimer: This e-mail and any attachments are confidential and intended solely for the use of the recipient(s) to whom they are addressed. If you have received it in error, please destroy all copies and inform the sender.
Later,
Andy
Yada, yada, yada…
Disclaimer: This e-mail and any attachments are confidential and intended solely for the use of the recipient(s) to whom they are addressed. If you have received it in error, please destroy all copies and inform the sender.
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
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.
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
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.
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@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.
–
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Later,
Andy
Yada, yada, yada…
Disclaimer: This e-mail and any attachments are confidential and intended solely for the use of the recipient(s) to whom they are addressed. If you have received it in error, please destroy all copies and inform the sender.
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
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@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
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@foo.com
That may well be true. This user was an active user in the past and did have their own ‘private’ queue. I may have set the correspond/comment addresses for that queue to their email address.
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.
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.
Later,
Andy
Yada, yada, yada…
Disclaimer: This e-mail and any attachments are confidential and intended solely for the use of the recipient(s) to whom they are addressed. If you have received it in error, please destroy all copies and inform the sender.
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.